Blue Screen error 0x0000007B in Windows XP after installing KB977165 (MS10-015 – February 2010)

Anonymous
2010-02-10T05:46:19+00:00

I updated 11 windows xp updates today from Microsoft.com and restarted my pc like it asked me to. (There has definitely been absolutely NO CHANGE in my computer software or hardware installation apart from this updates)

From then on, Windows cannot restart again! It is stopping at the blue screen with the following message:

A problem has been detected and windows has been shutdown to prevent damage to your computer.

PAGE_FAULT_IN_NONPAGED_AREA

Technical Information:STOP: 0x00000050 (0x80097004, 0x00000001, 0x80515103, 0x00000000).

I tried all kinds of restarting option namely, safe modes etc.  but everything is returning to the blue screen.

I hope Microsoft technical support has an answer as to how to resolve this problem.

Please respond if anyone has an answer.

Thanks

Windows for home | Previous Windows versions | Windows update

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-16T21:14:54+00:00

If you are not experiencing the Blue Screen on reboot and you have successfully installed the KB977165 update you do not need to do anything.

The only situation in which you need uninstall the update is if you are experiencing blue screens on reboot.

I hope this helps.

Thanks,

Kevin


If you find that my answer was what you were looking for, please remember to click the "mark as answer" box below!

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2010-02-15T21:44:15+00:00

Hello Everyone,

I wanted to post a link to the MSRC Team Blog that discusses this particular situation.

This is the best place to go for updates regarding the issue being discussed in this thread.

http://blogs.technet.com/msrc/

Thanks to everyone for the great discussion, I will be sure to update the thread as more information becomes available.

Thanks, Kevin

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2010-02-11T21:17:30+00:00

Hello Everyone,

I wanted to thank everyone for the great information and discusion in this thread!

We have found that there is only one patch that requires un-installation to resolve the blue screen issue. KB977165 is the patch in question, the other patches do not seem to cause the blue screen behaviour and do not need to be uninstalled.

With that in mind, here's the updated solution steps:

  1. Boot from your Windows XP CD or DVD and start the recovery console (see this Microsoft article for help with this step)

Once you are in the Repair Screen..

  1. Type this command: CHDIR $NtUninstallKB977165$\spuninst        
  2. Type this command: BATCH spuninst.txt
  3. When complete, type this command: exit

IMPORTANT: If you are able to uninstall the patch and get back into Windows, in order to stay protected you can use the following automated solution which secures your PC against the vulnerabilities that are resolved with KB977165 until you can successfully get the update installed without the blue screens.

Please see the link below for the article describing the vulnerability that is fixed with KB977165 and how you can get protected without installing the actual KB update:

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

I also wanted to thank maxyimus for the great thread, and LThibx for their participation as well!

Thanks,

Kevin


If you find that my answer was what you were looking for, please remember to click the "mark as answer" box below!

Was this answer helpful?

0 comments No comments

434 additional answers

Sort by: Oldest
  1. Anonymous
    2010-02-16T00:36:03+00:00

    My problem was not exactly the same. I had a hang of 19 minutes with just the desktop background showing. I could access Task Manager. After 19 minutes, the boot would complete seemingly as normal. The problem was definitely caused by the Feb 10th Windows update.

    I have had a week of frustrating and frightening researching and diagnostics. The solution has finally been very simple. Uninstall and Reinstall the Message Queuing service in the Add/Remove Windows Components.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-02-16T01:34:50+00:00

    In this instance I think it's rather superficial to make vague general accusations that the problems are only encountered on machines infected with a virus. If this is true, then I'm amazed that Microsoft didn't in advance try the effect of this update on an infected machine to determine the outcome!? I'm attempting to fix this problem on two XP machines - both Toshiba laptops, but different models. BOTH had up to date Anti-virus (one has McAfee, the other has Norton Internet Security 2010) and both were set to automatically update signatures and had done so within the last week. One machine has XP home, the other has XP Pro (Service Pack 3). So far it's not been possible to succesfully roll back the KB977165 patch on either machine by using any of the methods listed here. It's looking increasingly likely that the best option for these is going to be using a boot disk with utilities to copy their respective owner's data and then re-install the OS. I think it's fair to say that both owners are NOT happy! I've also encountered one generic desktop machine running Vista Home premium that had a BSOD after the update - the customer had fixed themselves by restoring to an earlier System Restore point. Just BTW I am an MCSE and MCP+I and have been working on Microsoft (and Linux) machines - desktops and servers - since DOS right through to Windows 7 and am generally a fan of Microsoft, but am finding this last "patch Tuesday" hard to defend!

    Was this answer helpful?

    0 comments No comments