Lastest Windows XP Update Causes BSOD Loop
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."
- Ron Jeremy Says Violent Games Bad, Sex Good!
- Intel Launches New 2 Billion Transistor Itanium
- Dead Space 2 PC Not Out of the Picture; Still Hope
- Steam Gamers Upgrading to 64-bit Win 7 Quickly
- Student's Robot Becomes Intel's Processor Demo
- Logitech Desktop Can Keep Rolling for 3 Years
- Microsoft Hotfixes Windows 7 Memory Leak
- (Update) StarCraft II Multiplayer Beta This Month!
- EA: Star Wars Old Republic MMO Beyond Q2'11
- VOTW: Dungeons & Dragons on Microsoft Surface
- Microsoft, Apple Both Targeted in Patent Lawsuit
- WD's 1TB SATA 6.0 Gbps HDD Out in Japan
- Postage Stamp-Sized SSDs On The Horizon
- Lian Li's T1 Pitstop PC Case Looks Like a Spider
- Firefox 3.7 Alpha 1 Arrives for Preview
- Small Utility Helps Tweak SSD Performance
- Microsoft: "We Were Smoked" By Apple iTunes
- Microsoft Pushing Patch to Snuff Out Win 7 Pirates
Good link to the update fix.
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...
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.
I meant fixed on Microsoft's side btw
I encountered this Wednesday morning on a clients pc. 0x00000050. A repair install fixed it right up.
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
http://www.krebsonsecurity.com/201 [...] -xp-users/
Time to upgrade...
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.
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
.
This is why I generally don't do automatic updates...