Q: Blue Screen on laptop running XP: Stop: 0x0000006B (0xc0000102, 0x00000002, 0x00000000, 0x000000000) This thread is locked from future replies

We have a six year old Dell laptop running XP. We recently had a memory upgrade and it has been working great.

Yesterday we got what I now know to be a BSOD (blue screen of death!). I am unable to get beyond the blue screen and perform any function. I have tried all of the advanced options, including all 3 safe modes. 

The message is "Process1_Initialization_Failed "

Stop: 0x0000006B (0xc0000102, 0x00000002, 0x00000000, 0x000000000). Is anyone aware of how to recover and/or if I can salvage any files on the laptop without being able to  initialize windows? 


I have a Windows xp home edition reinstallaton cd, but if I put it in the drive, it isn't recognized and the BSOD remains. Thanks





I knew there was an AVG in there somewhere...  AVG is at least part of your problem.

Here is how to fix it the STOP error:

If you are seeing a message like this:

*** STOP:  0x0000006B  (0c00000034), 0x00000002, 0x00000000, 0x00000000)

That usually means your c:\windows\system32\ntdll.dll file is missing.

Of course the file should never be missing, but it may have been quarantined (effectively deleted) by your antivirus/antimalware software.

There are other copies of the missing file on your system in other places so you just need to replace it. 

You can replace the file from the XP Recovery Console. 

If you do not have a genuine bootable XP installation CD to boot into the XP Recovery Console (or if you are not sure what you have) you should make an XP Recovery Console CD and be sure (no XP media required).  If you need to know how to do that, just ask.

Once booted into the XP Recovery Console, do this::

A good idea before starting things is to first verify the integrity of your file system using the chkdsk command.

From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.

Running chkdsk is fine even if it doesn't find any problems.  It will not hurt anything to run it.

Assuming your boot drive is C, run the following command:

chkdsk C: /r

Let chkdsk finish and correct any problems it might find.  

It may take a long time for chkdsk to complete or it may appear to be 'stuck'.  Be patient.  If the HDD light is still flashing, chkdsk is doing something.  Keep an eye on the percentage amount to be sure it is still making progress.  It may even appear to go backwards sometimes.

We know that XP keeps copies of critical system files in the following folder:


From the XP Recovery Console prompt enter the following command:

copy c:\windows\system32\dllcache\ntdll.dll   c:\windows\system32

Respond in the affirmative if asked to overwrite the existing file and then you should see a message that 1 file(s) was copied.

If the copy command can't find a copy of the file in the dllcache folder, this command may work depending on how your XP was installed:

copy c:\windows\ServicePackFiles\i386\ntdll.dll   c:\windows\system32

Type 'exit' to leave the Recovery Console and the system will restart.

You may then see a boot options menu so if you do, choose to Start Windows Normally.

Did this solve your problem?

Sorry this didn't help.

1 person was helped by this reply

Question Info

Views: 9,860 Last updated: February 28, 2018 Applies to: