svpewing

Ok guys I fixed it this morning and it may have been a fluke how it happened but this is what i did. I basically said screw it and decided to re-install windows. I booted from the cd and decided to choose the option of reinstalling, then it said it was damaged and would begin an attempt to repair it before reinstalling. It took 5 minutes to that then rebooted. NO BSOD! But I got the installation screen that you would normally get if you were installing windows again, the weird thing is after the installation ALL MY STUFF WAS STILL THERE. Weird. But I afterwards disabled automatic updates and will continue to update it myself. You can try this... it may solve it for you.

tim95691

funny was trying the same thing as i read your post


but it has taken alot longer than 5 minutes ,its been more like 25 and its still trying


hope it works like yours did

progcode

More examples of other people experiencing the same problem at roughly the same time.

People either knew the pc was being updated and found the bsod when they came back, or they just leave the pc running (presumably updated automatically) and when they came to it found the bsod. All within the last couple days.

http://answers.yahoo.com/question/in...5121838AAalv7o

http://www.howtofixcomputers.com/for...ly-264127.html

http://www.techspot.com/vb/topic136293.html

http://fix-windows-blue-screen.com/b...-mean#comments

afccarl666

These things happen after updates sometimes, if the update doesn't install correctly on your system. If the update had a problem, I think you would find half the net crammed with problems like this one.

As I mentioned before, if you have a full XP CD, you should run a repair install. Here is a guide to help: http://www.geekstogo.com/forum/How-t...s-XP-t138.html

mrackbar

I'm having the exact same issue as the others above. I understand that the only current way to resolve this is to do a repair install, but honestly this is something microsoft needs to address rather than us doing a repair install. My 2 cents.

On the flip side, i even tried to do a system restore from the recovery console and still no dice.

AikenDrum

FWIW I also allowed XP to apply the updates yesterday and have battled with the endless BSOD loop since then. Glad to know we are not alone.

In summary, Normal mode = BSOD. Safe Mode = BSOD. Last Known Good Config = BSOD. Disable reboot allows me to see 0x0000007 error, no other clues.

Booting with BartPE usb stick I can see Bootlog that shows drivers loading up to mup.sys and ivicd.sys and then from acpi onwards I see many entries along the lines of "did not load driver ACPI uniprocessor PC" - hundreds of them in what appears to be a loop (I see the same driver names repeated).
NB: disbale ACPI in BIOS makes no difference.


Booting with WinXP disc works okay, and did Repair, but no change to the problem.

Have now resorted to fresh install of XP (leaving existing file system intact) and this works 100%. However I would still like to get the original install to work.

I am sure that it is an issue caused by one of the updates. If anyone gets any clues, please let me know.

Thanks

AikenDrum

Just stumbled on this link hinting that it may be a virus.
http://forums.techguy.org/windows-nt-2000-xp/868562-solved-windows-xp-pro-startup.html
Will try booting now with USB stick again and see if regedit helps.

mrackbar

FIXED. Ok so i checked the link above and went through my registry as indicated but didn't find any of the files specified. So, i decided to go through and uninstall the latest patches one at a tine. In my case i found that kb971486 was the culprit. I had to uninstall this from the recovery console.

boot off your windows xp cd
press r for recovery console
select your windows install (1 in my case)
enter your administrator password

when at the c:\windows prompt enter:
cd $ntuninstallkb971486$
cd spuninst
batch spuninst.txt

it will run some commands

exit

reboot

problem fixed

windows xp Media Center sp3 HP pavilion dz8000

iamgap

After following AikenDrum's link to another post, I found mrackbar's fix (that I would have found had I scrolled just a wee bit more. :)

So I'll say it again here.

ackbar,

I joined this site just to say that you are AWESOME!!

The Youth Leader for our church just had this bad patch break her computer. I came up to the church to prepare slides for Sunday's service, and she asked me to look at it. Had it not been for your post, I would have been up for hours (and really tired for my trip to see Toby MAC tomorrow) rebuilding her PC.

Thanks again!!!


gap

hansieinthemix

mrackbar you're the best !!!!

petrops

i am having the exact problem described above. Dell Latitude with windows xp and the BSOD following an update and restart. I tried installing the dell windows reinstall disk but get no love at all. Just the BSOD. This disk does not reference "repair" just "Reinstall".

Is there a difference? and what am i supposed to do after installing this disk? There is virtually no control that I have over this machine at this point other than the few options enabled by F8 during bootup.

Thanks

Jack

mrackbar

Do you recall all the options you went through when you did a "reinstall" from the disc? and to your credit a dell reinstall disc isn't the same as a standard windows install disc.

afccarl666

Hi Jack

mrackbar is right, an OEM CD (In your case dell) is much different to a normal XP CD. The reinstall option will likely wipe the drive and start fresh.

LFC4EVER

This BSOD problem has had me contemplating computer homicide since yesterday. You people have my eternal respect and gratitude.

mrackbar, please call mrgates and educate the man!!

Many Thanks (from my little girls too)

Paul

progcode

i've tried mrackbar's suggestion, $ntuninstallkb971486$, spuninst

it did uninstall the item, but now when I boot I get the bsod with the 0x00000050 stop code plus the page fault in nonpaged error, on normal boot, on last known good, and on all flavors of safe mode boot.

I went further and ran the spuninst for as many of the other kb's as I could that installed that night (10-15-09 shortly after midnight), but with the same result.

Here is the list of the KB's that installed and notes about them
kb953295 at 12:03
kb954155 at 12:07 (there was no directory called $ntuninstallkb954155$, could not run spuninst on this one)
kb958869 at 12:10
kb968389 at 12:02
kb969059 at 12:07
kb971486 at 12:04
kb973525 at 12:04
kb974112 at 12:07
kb974455-IE8 at 12:11 (there was no directory called $ntuninstallkb974455-IE8$, could not run spuninst on this one)
kb974571 at 12:06
kb975025 at 12:07
kb975467 at 12:02

afccarl666

Have you tried this?

I told you not all PC will be fixed by the same method

bfreeman

I had two XP machines update on Weds night and got BSOD and reboot loop since Thursday am. Been trying to find the fix ever since. One machine may be beyond hope as I've tried numerous solutions and am about to reformat. The other is back up thanks to this quick easy solution. It was the same update, 971486. Thanks a bunch!!

progcode

Of course that's my next step. I'm trying to figure out what happened, since it's obviously not just the one kb that's the culprit. I figured posting what little additional info I had might be helpful for someone else fighting the same fight. I have already placed an order with Microsoft for a replacement OEM install disc of XP Media Center 2005. I was never given one, and the "recovery" discs don't recover anything, they do a factory disc image. :)

marcelbrown

We've got a good discussion and resolution of this issue going on here: http://www.stateofthetech.com/?p=117

progcode

Didn't want to wait a week for the discs I ordered to arrive, so asked around. Luckily found a co-worker who had the OEM install discs for XP Media Center 2005. Exactly what I needed and already ordered. Went through the repair process fully expecting it not to work, but to my surprise, after over an hour, the pc is seemingly back to normal.

One thing to note, might not be related but who knows... about halfway through the repair, the USB mouse and USB keyboard stopped working. They continued not to work when the repair was complete. They would work in BIOS, but the lights would turn out as soon as Windows started booting. Weirdness. Luckily I had a PS2 keyboard also plugged in and was able to navigate to device mangler and forced windows to update the USB drivers. The one that did the trick was the "Standard OpenHCD USB Host Controller".

And of course now I see this link to the thread on the other forum. I could tell when it happened that it was Microsoft's fault, and have been saying so all along. I figure a better solution will be discovered, but my results are at least successful after three days of hell! :)