System crash due to Windows update

[Preben Krabben]

On the 28 of October I autamatic updated my licensed
Windows XP home OS. After that update I have not been able
to start the computer. No old configuration has been
saved. Neither of the safe-mode works. Bootlog files
cannot be generated. The only thing that works is the
Windows recovery console which tells me that the system
crashes after the last SERVICE_BOOT_START driver is
loaded. Does anybody have an idea what the problem is and
how I can solve it ?

Preben

 

[Malke]

On the 28 of October I autamatic updated my licensed
Windows XP home OS. After that update I have not been able
to start the computer. No old configuration has been
saved. Neither of the safe-mode works. Bootlog files
cannot be generated. The only thing that works is the
Windows recovery console which tells me that the system
crashes after the last SERVICE_BOOT_START driver is
loaded. Does anybody have an idea what the problem is and
how I can solve it ?

Preben

Unfortunately, this isn't enough information to give you a specific
answer. There's no way to tell whether the update was coincidental with
the problem. This could be hardware or software. Here are generic
troubleshooting steps for the hardware. First open the computer and run
it open, observing all fans (overheating will cause freezing). Then do
a RAM test - I like Memtest86 from www.memtest86.com - and if
necessary, continue on to test the hard drive and motherboard. If you
can't do this yourself, take the machine to a good local computer shop
(not a CompUSA or Best Buy store). If the hardware is OK, you're
probably going to have to do at least a Repair Install, but I'd check
the hardware first.

Malke

 

[Alex Nichol]

On the 28 of October I autamatic updated my licensed
Windows XP home OS. After that update I have not been able
to start the computer. No old configuration has been
saved. Neither of the safe-mode works. Bootlog files
cannot be generated. The only thing that works is the
Windows recovery console which tells me that the system
crashes after the last SERVICE_BOOT_START driver is
loaded.

One thing that is *possible* - I have had reports of a similar problem
being caused by an updated copy of ntoskrnl.exe to build #1151

You *may* be able to find an earlier copy on the machine, but the only
certain place for the right one is in the
windows\driver cache\i386\driver.cab or sp1.cab (If you have SP1).

So try, from that Recovery Console, giving

expand "C:\windows\driver cache\i386\sp1.cab" /f:ntoskrnl.exe
C:\Windows\system32\drivers

(That is all a single line) - if you do not have SP1 use driver.cab
instead of sp1.cab.
..
Then

copy C:\Windows\system32\drivers\ntoskrnl.exe
C:\windows\system32\ntoskrnl.exe

(again one line): You need to have it in the drivers first to stop File
Protection possibly overwriting with the one there

Please let me know if this works - I'm trying to collect evidence