I have this same problem but I am running windows 2000 and I bough this computer at a yard sale yesterday. it was 5 bucks so why not but it just always is getting the error I don't have any drivers or the copy of the os what should I do?
Blue Screen 0x0000006B - PROCESS1_INITIALIZATION_FAILED
original title: BSOD 0x0000006B - Work-around does NOT resolve issue - Win7 Pro x86
Running Windows 7 Pro x86 on an Asus EeePC 1000HE. I haven't had a blue screen in three months. Shocking. Now, when booting (normally, safe mode, whatever) after the loading screen, before the user password screen, a blue screen appears.
PROCESS1_INITIALIZATION_FAILED
STOP: 0x0000006B (0x00000000, 0x00000000, 0x00000000)
I have checked the numbers many times and have pictures of the screen to verify (taken from my phone). I tried the work-around as described in KB981833 (http://support.microsoft.com/kb/981833). I used an Ubuntu 8 LiveCD to navigate to /Windows/System32/CodeIntegrity/ and deleted the Bootcat.cache file. After several reboots, the blue screen still persists with the same error codes and the Bootcat.cache files has not reappeared. I can confirm that it is not a hardware problem because the other OSs (Mac OSX 10.6.1. Eeebuntu) still boot and operate normally off the same hard drive. This is just a Windows problem. (Suprise, suprise)
Also, the startup repair on the Windows 7 install disc found nothing and did nothing.
Windows for home | Previous Windows versions | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
45 answers
Sort by: Oldest
-
Anonymous
2013-08-18T18:20:43+00:00 -
Anonymous
2013-12-11T06:16:37+00:00 This will resolve BSOD With code 0x6b. Please refer my post using the following link;
-
Anonymous
2014-01-21T01:33:35+00:00 No RAID on this machine. It is a 10-inch netbook with a single 160Gb hard drive. Linux booted off of an optical usb drive, but Ubuntu and also OSX Snow Leopard are still able to boot off of the internal hard drive, the same one that Windows 7 is on. OSX has the first 80GB, Ubuntu has an ~8Gb slice in the middle, and Windows 7 has the remaining ~71Gb. I will definitely copy the dump files and use BlueScreenView on them...
1. OKAY... I tried to get the dump files, but C:/Windows/Minidump does not seem to exist on my system (I also made sure to look in case it was a hidden or system folder.) Also, I could not find any .dmp files anywhere else in my system (I looked in root, /Windows, and /System32). I found the extended boot menu and disable "reboot on system failure", so I was able to see the message that said it finished the memory dump. I also booted in "Debug Mode" and "enabled boot logging" which both resulted in the same BSOD, but I cannot find ntbtlog.txt from those, either.
2. I tried to run "sfc /scannow" from the install disk, and it says something like "unable to check system because there are other system repairs pending, please reboot your computer and try again." Well, I have no idea what repairs it's talking about, and I can't reboot like it wants me to because of this BSOD. Is there any way to cancel the pending repairs or force sfc to run anyways?
EDIT 2. I found /Windows/Winsxs/reboot.xml, and it contained the following. Could this be stopping sfc?
<?xml version='1.0' encoding='utf-8'?>
<PendingTransaction Version="3.1">
<POQ>
<DeleteKeyValue path="\Registry\Machine\COMPONENTS" name="PendingRequired"/>
</POQ>
</PendingTransaction>
3. "The 1st parameter is The NT status code that caused the failure - which means there was no applicable code." So, does this mean that there were no software errors to report?
4. At the end of Startup Repair, when it found no errors to fix, it gave me this info:
Problem signature:
Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21200990
Problem Signature 05: ExternalMedia
Problem Signature 06: 6
Problem Signature 07: 0x6b
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
btw, +1 for including notepad in the repair command prompt :)
Work Around:
Copy bootcat.cache from a working server and make it as iso((easy to attach in CD/DVD when you repair)
Boot with repair option and go in Command line mode(CUI).
xxx:
Windows\System32\CodeIntegrity:>ren bootcat.cache bootcat.cache.old(assume xxx your system drive could be E..)
move to your CD/DVD drive. example F:
F:> copy bootcat.cache E:\system32\codeintegrity
exit from command line.
restart now.
Work perfectly for Win2k8 based OS.
-
Anonymous
2014-03-25T16:37:12+00:00 This will resolve BSOD With code 0x6b. Please refer my post using the following link;
Laxmi261's solution worked perfectly! In short, you may need to obtain both bootcat.cache AND ntdll.dll from a similar machine and place them on the defective machine (there are other steps, so check his post for the details). Now, why can't Microsoft figure that out?
-
Anonymous
2014-05-12T23:30:27+00:00 I REALLY need some help. I've tried everything, and here is a list.
(Not in order)
- I deleted bootcat.cache. It didn't work so I then copied a bootcat.cache from a Windows 7 64bit laptop and put it on a flash drive, then I renamed the supposedly broken bootcat.cache to BC.OLD then I put the new bootcat.cache in the CodeIntegrity folder from Recovery Mode Console. None of this worked so I also copied the ntdll.dll from the laptop and it still didn't work!
-chkdsk in Recovery console
-scf /scannow which said that there was another repair pending or something.
-Repair didn't work either.
NONE of this has worked. I still have all my personal files.