[HOME]10:50 AM November 30, 2016

BSOD: PROCESS1_INITIALIZATION_FAILED STOP: 0X0000006B

Even though I couldn't fix this issue without resetting the computer, I have come across some info that others claimed had worked for them. So it might work for you. It was somebody else's computer and I spent two days trying to clear this out, sorry for the lack of screen shots.

I was trying to fix a Toshiba laptop with Windows 7. It would boot to a BSOD even in safe mode. Unfortunately by default computers seem to reboot automatically after a BSOD - Blue Screen Of Death. This is basically where something goes wrong, your computer crashes and you get a blue screen with white letters telling you what the problem is. Restarting automatically isn't so bad if it only happens once. If it keeps rebooting in a loop and you can't read the error message to fix it, that's bad.

So I restarted the computer in Safe mode, by pressing the F8 key, until I got to the Advanced Options for Windows 7 screen with the safe mode options. Of course first I tried just going into safe mode but still just the BSOD. I needed to see the BSOD message to troubleshoot it. In the Advanced Options menu there is just that. So I restarted, pressing F8, and picked instead of Safe Mode, the option to Disable automatic restart on system failure. When the BSOD popped up it didn't reboot automatically so I could get the information I needed.

The error message was PROCESS1_INITIALIZATION_FAILED STOP: 0X0000006B. I found a solution that worked temporarily. You would need to boot of some CD/DVD, my choice is Hiren's. http://www.hirensbootcd.org/download/. Boot to the Mini Windows Xp option, then when loaded open up Windows Explorer and navigate to c:\windows\system32\codeintegrity. You’ll find there a file called bootcat.cache which is very probably corrupted and deleting it is supposed to clear it up. So delete it and then restart your computer normally, or try. It worked for a while. I decided to run a few scans for malware just in case, the owner was saying something about a virus embed in the browser. I tried running Malwarebytes and it seemed to have got hung up on it's root kit scanning. At this point I suspected an infection may have caused this damage.

CodeIntegrity-bootcat.cache

So I decided to restart in safe mode and run a scan from there but I chose to do it through the msconfig utility. Either in the search bar or run bar type msconfig and hit enter. Then on the Boot tab under Boot options check Safe boot and Network, gives you Internet access just in case.

Windows msconfig utility

Unfortunately, the computer again booted to a BSOD. So now not only did I have a rebooting computer it was stuck trying to boot up in Safe Mode. I followed the same procedure before, booting of Hiren's going to c:\windows\system32\codeintegrity, deleting the bootcat.cache but this time it didn't work.

This file should of been recreated upon reboot but it wasn't so I assumed that safe mode was interfering which I couldn't disable. So I had to figure out how to disable it. On line I went and found out the following.

So I waited until the computer rebooted to the Advanced boot options and chose Startup Repair but canceled it as it came up. After confirming my choice I went to the System Recovery Options and clicked on the Command Prompt option and typed the following.

Windows System Recovery Options

bcdedit /enum

Then in the screen that displays look under the section Windows Boot Loader and make note of the identifier (includes brackets). In my case it was {default}. So I had to type the following:

bcdedit /deletevalue {default} safeboot

Replace {default} with your own. If I run this command on my own system I get {current}:

identifier from my computer

It worked, getting rid of the Safe Mode loop but not the BSOD loop. Just it case it was the safe mode option interfering, I booted of Hiren's again...you know the procedure. By the way during this entire mess, Windows Startup Repair popped up in the menu every other restart, I must of run it like a half a dozen times but it could not fix the issue. Three is the recommended times to run it.

My mind drifted back to a possible infection. So I needed a CD/DVD/USB scanner. I decided on Dr. Web LiveDisk - http://www.freedrweb.com/livedisk/ (the USB version). So I downloaded the program, ran the install, set up the flash drive. Booted up the Toshiba laptop of the drive by pressing F12 and going to the boot menu and choosing the USB option and ran the scanner.

Before running the scanner I had to connect it to my Internet, same thing as connecting through Windows but the icon looks a little bit different. Then the first icon on the desktop, top left, is the Update Virus Databases option. After updating I ran a scan and it found two items.

A driver at C:\windows\system32\drivers\swdumon.sys, which I think is a part of the Slimdrivers driver updater program. Not really sure of it was a threat or not. The program offered to Move it so I allowed it.

The other issue was a registration issue: HLM\SOFTWARE\Wow6432Node\Microsoft\WindowsNT\CurrentVersion\Winlogon, userinit - which it Cured.

After the scan there is a big yellow/orange button to click on called Neutralize. After rebooting the computer, no luck.

results-of-dr-web-scan

Other things I tried:

System Restore - a number of times using different restore points.

SFC /scannow - this wouldn't work at first. It claimed there was a job pending. Reboot and run again only to come up with the same error. To fix this run the following command: del c:\windows\winsxs\pending.xml. Sometimes when booting of CD/DVD/flashUSB the Windows drive might not be C:. Change the letter accordingly.

If you have another computer similar make and model you could try copying the file, bootcat.cache from a working computer to the non-working one. I copied the one from my computer to theirs. No dice.

Another option that seems to work for some was after replacing the bootcat.cache file to also copy over the files in the c:\windows\system32\catroot and c:\windows\system32\catroot2 folders. Some people on line had some success with this. I did not.

Tried running a full hard drive check.

One user suggested marking the file as read only.

Another replacing the Ntdll.dll file.

I decided their was only one thing to do. A factory reset. And guess what laptop doesn't doesn't have a recovery partition. I believe they replaced the hard drive on this computer before. Thus, no recovery partition. Also I had to save their pictures, 20 GB on the computer but I could only salvage 14 GB. It crossed my mind more than once that we may be dealing with a failing hard drive even when scans claim there was no problems. But no scanners is 100% perfect.

I booted of Hiren's CD, hopefully one last time and plugged in a flash drive. Then opened Windows explorer and copied the picture's from the hard drive to the flash drive. Then I popped out Hiren's and popped in the Windows install. I first chose the option to install Windows over what was there. This would back up the old install into a file called Windows.old, just in case. Everything seemed to be running smoothly until it got to the part, completing install...and I waited and waited and waited...you get the picture.

After, forcing the computer to power down, and starting it up again, I was now stuck in a install needs repair loop, thing. So one more time to Hiren's, formated the hard drive through it, ran the Windows 7 install again and finally got it installed. Still had to hunt down a few drivers on line but no big deal. Then one final step, copied their pictures back for them. Actually, I also did one more thing and that was to burn their pictures of on a DVD, four disks to be more precise.