Sign in with
Sign up | Sign in

Lastest Windows XP Update Causes BSOD Loop

By - Source: Tom's Hardware US | B 10 comments

An update that addresses the 17-year-old kernel bug in Windows XP is causing the Blue Screen of Death.

Consumers still using Windows XP may want to avoid the latest Microsoft security update released on Tuesday. Security blogger Brian Krebs reports that complaints are flooding the Redmond company's support forums, indicating that the update is crippling some systems with the notorious Blue Screen of Death. The systems thus falls into a reboot loop.

Early Wednesday morning an unofficial fix was posted on the support forum thread, suggesting that users boot from the Windows XP installation disk, launch the Recovery Console, and enter a chain of commands at the Repair Screen. After exiting the Recovery Console, the system should return to normal.

Unfortunately, the fix doesn't apply to netbook users suffering the BSOD issue.

But by early Thursday morning, more than 120 messages filled the support thread; more than 2,800 consumers had actually viewed the thread since its creation. Krebs had also updated his blog to reveal that the problematic update is KB977165 (MS10–15:Vulnerabilities in Windows kernel could allow elevation of privilege”). MS10-15 addresses a 17-year-old kernel bug in all 32-bit versions of Windows XP.

Other users in the support forum thread also verified the source of the BSOD as MS10-15, and said that uninstalling that particular update returns the system to normal. Currently Microsoft has not issued a hotfix for repairing or removing the MS10-15 error.

MS10-15 is one of thirteen security updates released by Microsoft on "Patch Tuesday."

Display all 10 comments.
This thread is closed for comments
  • 0 Hide
    badaxe2 , February 11, 2010 10:26 PM
    Good link to the update fix.
  • 1 Hide
    thedreadfather , February 11, 2010 10:28 PM
    I've been putting off that update because I'm too lazy to restart my computer.
    And my teachers/parents said that laziness never pays off.

    Let's hope that this is can be fixed/only under certain configurations. I'd like the security update, but if it causes problems...
  • 0 Hide
    techguy911 , February 11, 2010 10:33 PM
    So far i have fixed 5 machines with this problem having to uninstall updates is a waste of my time, microsoft should be testing these patches more.
  • 0 Hide
    thedreadfather , February 11, 2010 11:02 PM
    I meant fixed on Microsoft's side btw
  • 0 Hide
    NewJohnny , February 12, 2010 1:46 AM
    I encountered this Wednesday morning on a clients pc. 0x00000050. A repair install fixed it right up.
  • 3 Hide
    Anonymous , February 12, 2010 2:28 AM
    I heard you can repair by
    1. Boot from your Windows XP CD or DVD and start the recovery console
    Once you are in the Repair Screen..
    2. Type this command: CHDIR $NtUninstallKB977165$\spuninst
    3. Type this command: BATCH spuninst.txt
    4. Type this command: systemroot
    5. When complete, type this command: exit
  • 0 Hide
    rhino13 , February 12, 2010 11:12 AM
    Time to upgrade...
  • 0 Hide
    dwlee28 , February 12, 2010 1:14 PM
    I am running XP Pro SP 3, update installed this patch, have had no issues at all with it. May just be a problem with certain configurations.
  • 0 Hide
    Anonymous , February 12, 2010 7:02 PM
    what sucks, is when you have that problem. but the update screwed your system so hard, that you cant boot from disk.. theres alot of people including myself who have that problem:) .
  • 0 Hide
    Anonymous , February 13, 2010 3:07 PM
    This is why I generally don't do automatic updates...