Can not boot XP at all - Getting Bluescreen error

Anonymous
2010-02-10T15:31:35+00:00

Hi all,

I am running XP SP3 on a Dell Vostro 1510 A10 BIOS with a SATA drive and Intel Core2 Duo CPU (warranty is expired). I recently got malware and removed it, with some experienced help, using ComboFix and HijackThis. It was successfully removed, computer rebooted, and Kaspersky online virus scan showed no more problems. Then windows updater (which was disabled by the virus) downloaded and installed updates. Yes, I see several people are having similar problems. On the next reboot attempt after installing the updates, I got a BSOD, error codes 0x0000007E (0xC000001D, 0x80537008, 0xBA4CF3B8, 0xBA4CF0B4). I cannot enter safe mode - system freezes during list of drivers - last driver listed is mup.sys. I cannot enter windows recovery - another BSOD with error code 0x0000007B. I cannot get into the HD to recover my data, so I do not really want to completely re-install. Oh, my systems diagnostics say the HD is ok. I appreciate any assistance you can provide.

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.

0 comments No comments
Answer accepted by question author
Anonymous
2010-02-10T17:14:37+00:00

Try this...

Symptoms: Computer started, loaded raid drivers and showed the XP startup screen for a half-second then went to BSOD with a Stop Error Code of 0x0000007E - many users also seeing (0xC0000001D, 0x----------, etc) as well.

Solution: 

  1. Boot from your Windows XP CD and start the recovery console. You may need to press F6 while RC loads in order to load SATA drivers; you will then have a c:\WINDOWS console prompt.
  2. Type: CD $NtUninstallKB977165$\spuninst (this is the update I had to uninstall to get out of the boot loop, other updates may be uninstalled by changing the directory name to $NtUninstallKBCODE$, where KBCODE is the KB code)
  3. Type: BATCH spuninst.txt
  4. Type: exit

Be sure to set your system to boot from the HD before resuming. Hope this helps. Saved me a lot of hassle today.

If that doesn't work, MS also issued updates for KB978262, KB971468, KB978037, KB975713, KB978251, KB978706, KB 975560 and KB 977914 last night.  You can insert those codes in place of the KB above and try until you get a solution.


Tom Steele

Was this answer helpful?

0 comments No comments

68 additional answers

Sort by: Newest
  1. Anonymous
    2010-06-16T04:25:18+00:00

    READ FULLY. This may help you....

    Although a very good solution and promising for most people, the fix above didnt work for me.

    My issue.

    As others have stated, last night, my computer auto updated the following Microsoft updates:

    975560, 975713, 977165, 977914, 978037, 978262, 978251, 978706

    This morning I get the endless restart loop and blue screen for 1/2 a second. After video taping the error so that I can load the video onto another computer and view the blue screen error message, I tracked it down (somehow) to a fault windows update that happened the evening of Feb 9th.

    Safe mode froze on an AVG driver file, aftger removing that file in dos, it later froze on the mup driver file. No luck.

    Last known good configuration...didnt work.

    I found a website that gives instruction on how to do some manual system restore file copying from within the windows recovery console. Nope. Notta.

    A call to Microsoft and 2 hours later, I found a Microsoft support specialist in asia somewhere who gave me some help.

    First she said that they are overwhelmed with this issue this morning and many people are calling with the same issues.

    She said that renaming and movi9ng one file has helped "most" customers.

    She had me boot to windows CD, go into the recovery console, then at the windows directory do the following:

    _______________Do not do this!!_____________

    cd system32\config

    ren system system.old

    cd \

    cd windows\repair

    copy system C:\windows\system32\config\system

    exit

     

    THis will take you into the config folder, rename an important file, back out into the windows repair directory, copy a file from tehre into the config folder.

    That didnt work for me. Instead, I am not UNABLE to get back into the windows recovery console at all.

    She said this has helped MOST people and her next suggestion was to do a XP repair install (install XP over the top of itself) also from the recovery console (which I am no longer able to get into) Ouch!

     

    Her final option was to do a clean install. Sorry, not an option for me at this time.

     

    She said that Microsoft was working on the issue and perhaps tomorrow, more would be known. She suggested searching on Bing tomorrow for the phrase "Windows Update Error"...the most recent results should have some more information on this widespread issue.

     

    I am stopping, after 6 hours of troubleshooting and will start over tomorrow.

     

    Good luck to all.

    Note: It took me 3 hours to UNDO what the microsoft tech told me to do. By replaceing the "system" file in the config directory, it replaced it with a copy from the rapair directory, which caused LOTS - o - problems.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-06-09T23:49:50+00:00

    I got the BSoD on June 5 a few days ago and got this error code:

    0X0000007E (0XC0000005, 0X0301003C, 0XF7A7CCB4, 0XF7A7C9B0)

    I kept having to restart my computer until it booted up again.  It's been happening for days!  And even worse, my MB of memory is decreasing rapidly.  Does this error code have something to do with the Wireless thing or with the KB update that has the code?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-06-03T01:37:01+00:00

    Tom,

    I had to reload XP from scratch. How do I get Live update to bypass all these files? Should I just turn the function off?

    Thanks

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-03-25T17:21:14+00:00

    Hello everyone.

    I've  got a much easier fix for this issue,I've repaired it on 2 separate computers by installing the affected drive in another computer as a second drive and running Windows Check Disk on the problem drive.Both were running XP Pro

    Check disk will delete the failed update that caused the reboot loop and half second BSOD.

    I found this fix completely by accident while trying to repair an older Compag  that had the same issue,was  pulling files in preparation for reinstalling XP

    when the computer I had installed the affected drive in ran check disk on that drive,reinstalled in the original Compag and it booted just like normal.This was after about a

    week of searching for solutions and not having any success.

    It only took between 30 min and an hour to repair the second one.

    Was this answer helpful?

    0 comments No comments