Blue Screen 0x0000006B - PROCESS1_INITIALIZATION_FAILED

Hi,

Because the software access methods do not work. Check the Faultwire site for the 6B code

and the "Research This Issue" links at the bottom of the page (link is above).

Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

Hi,

Is this system using RAID? This looks very much like a cabling, hard driver controller, or some

hardware function on the drive or motherboard which is affecting Windows but not the other

OS's which is very possible. In fact, since the Linux booted off the optical drive its very likely

an issue involving the hard drive.

The 1st parameter is The NT status code that caused the failure - which means there was no

applicable code. The other 3 parameters are Reserved which mean they have no meaning.

Copy the C:\Windows\Minidump  files on to removable media using one of the other OS's

and then paste into same place on another Windows 7 machine. Run BlueScreenView on

it. Also you can run WinDBG if installed on the other machine.

How to read the small memory dump files that Windows creates for debugging

http://support.microsoft.com/kb/315263/en-us?p=1

Download and Install Debugging Tools for Windows

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

BlueScreenView is considerably easier to use (by a factor of 1,000).

Check this fix which is for XP however it can work on Windows 7 as well.

STOP 0x0000006B Process1_Initialization_Failed

http://support.microsoft.com/kb/163240

How to Extract Files from the Windows 7 Installation DVD

http://www.sevenforums.com/tutorials/42776-extract-files-windows-7-installation-dvd.html

How to extract missing system files from the DVD of Windows 7/Vista.

http://blog.nirsoft.net/2009/09/17/how-to-extract-missing-system-files-from-the-dvd-of-windows-7vista/

Of course you can't do it on that machine in Windows 7 so you will need to find another route.

Check the FaultWire link and the Research This Issue.

BCCode: 6B   0x0000006B  <-- read thishttp://www.faultwire.com/solutions-fatal\_error/PROCESS1-INITIALIZATION-FAILED-0x0000006B-\*1122.html

Think hard driver related issues.

Hope this helps.

Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

Okay, I apologize for my attitude towards you.  Thank you for trying to help me with this.

One thing that is very puzzling to me is the list of parameters on the BSOD: (0x00000000, 0x00000000, 0x00000000, 0x00000000).  Is there anything significant about the fact that they are all zeros?  Other occurrences of this error that I have read about list various parameters, all different, but never all zeros.

1.  I would indeed like to use the MyEventViewer and the BlueScreenView utilities.  Since I can't boot Windows to run them, are there any similar applications that can be run in Linux or Mac OSX to access the disk?  The computer is still able to boot those, so I am still able to access all my Windows files.  Or, could I run those tools on a separate PC and somehow point them to my Windows 7 machine? (There are three Vista machines, three XP machines, three Linux boxes, and two Macs in this household that I have easy access to, if they can be on any help.)  I also have a registry editor and account editor on a bootable CD, if I can dig in that way and disable drivers through the registry.

2.  Also, the "startup repair" function of the Win7 install disk was unable to detect the problem.  Today I ran the extended version of the RAM test that is on the CD, but it said the results would be displayed the next time I logged in.  Are there any commands that can I use in its command prompt to view the event logs and the BSOD memory dump of the system? (I used to have a list of useful commands written down somewhere but I've lost it long ago.)

3.  I recall that there are more options on the boot menu (the one with all the Safe Mode options) that make it possible to turn off the automatic reboot after a BSOD.  I've been told to try F8 but that doesn't appear to respond on this menu.

Thank you for your time!

Hi,

Those are the recommended solutions from Microsoft and FaultWire which are both creditable

sources. As a poweruser you should know that all solutions do not always work. Did you try

the methods in the troubleshooter?

If those methods do not help then about the only things left are hardware and trying a re-installation

to try to see if that helps identify anything as probable cause.

Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.