Windows will not start further than BSoD

[mr_banana_pants]

Last night I let Windows XP install its automatic updates upon shutdown.

 

Today I switch my computer on...and I get BSoD.

 

I start in "Last Known Good Configurations"...and I get BSoD

 

Same with Safe Mode.

 

I get the following error:

 

 

 

It asks me to check if I have adequate disc space (I'm sure I did). Or if a driver identified in the stop message to disable it.

 

STOP: 0X0000007E (0x80000003, 0x8053355E, 0xF79593BC, 0xF79590B8)

 

I'm sorry but this level of computing is way beyond me.

 

I tried repairing windows. I must point out that I bought my PC 2nd hand from an office that were selling on they're hardware. Its a legitimate buy with a proper Windows disc/Windows Product Key.

 

After Windows has thought about repairing itself the computer restarts, it asks me to press 1 to select the copy of Windows I wish to repair. Then it asks me to enter an administrator key, which I do.

 

Then nothing. It just says c: windows and expect me to put in a command prompt from one of those listed under Help.

 

I apologise for my dimness. I really want to avoid reformatting the computer if I can help. Especially when it seems to have been caused by an automatic windows update!

 

Thanks so much in advance.

 

Darrell

[RandyL]

I just read this cnet article earlier today. It seems that one of the updates is indeed the problem. At the bottom of the article is the fix.

[mr_banana_pants]

Brilliant!!thanks for link I've just tried it now and all seems to be working fine again.

Much appreciated!

 

Cheers

 

Darrell

[RandyL]

That's great Darrell. It's a good thing I had time to read cnet news yesterday. :)

 

Best of luck.

[Plastic Nev]

Funnily enough I read about this problem update elsewhere earlier today. The rogue update only seems to be a problem on some computers and not others. I have checked my set up and that update went in without any problem, weird or what?

The update concerned is-

KB977165

It is supposed to be just an ordinary security patch.

Nev.

[RandyL]

Even more on the problem is a better link.

 

Also it seems that the update was incomatable with XP machines that had rootkits installed according to the ZDNet article Hackers "fix" XP BSoD rootkit.

 

If that's true you would be wise to run some rootkit scans.

[Plastic Nev]

A good one to run is F-Secure's Blacklite from here-

BlackLight

 

Nev.