Dec Windows Update causes BSOD 0x0000000A - can't even start safe

On Dec 15, I installed the latest Windows Updates, and then the system did a
BSOD on restart:
0x0000000A(0x00000304,0x00000002,0x00000002,0 x806FFA16)
IRQL_NOT_LESS_OR_EQUAL on my laptop

I can't start in safe mode and the "Last known good configuration" will not
start it either.
I ran system repair (an in place upgrade) using s Windows XP SP2 slipstream
disc, and the system started, and then I ran Windows Update (65 or so
updates), but then I got the Stop error again.

Not sure how to track down which update is killing the system. Any
suggestions?

Thanks!!

Darryl

TOSHIBA Satellite A70 PSA70C-KL100E
Board: TOSHIBA EDW10
BIOS: TOSHIBA V1.30 09/10/2004
TOSHIBA DVD-ROM SD-R2512 [CD-ROM drive]
HTS424040M9AT00 [Hard drive] (40.01 GB) -- drive 0, s/n MPA201Q2GASN7A, rev
MA2OA60V, SMART Status: Healthy
ATI MOBILITY RADEON 9000 IGP [Display adapter]
CPT 15.4 [Monitor] (15.4"vis, October 2004)
Realtek AC97 Audio

You installed critical updates only?
NOT any driver updates?

"Darryl Gittins" <> wrote in message
news:C1D4D408-A638-4CBF-A251-...
> On Dec 15, I installed the latest Windows Updates, and then the system did
a
> BSOD on restart:
> 0x0000000A(0x00000304,0x00000002,0x00000002,0 x806FFA16)
> IRQL_NOT_LESS_OR_EQUAL on my laptop
>
> I can't start in safe mode and the "Last known good configuration" will
not
> start it either.
> I ran system repair (an in place upgrade) using s Windows XP SP2
slipstream
> disc, and the system started, and then I ran Windows Update (65 or so
> updates), but then I got the Stop error again.
>
> Not sure how to track down which update is killing the system. Any
> suggestions?
>
> Thanks!!
>
> Darryl
>
> TOSHIBA Satellite A70 PSA70C-KL100E
> Board: TOSHIBA EDW10
> BIOS: TOSHIBA V1.30 09/10/2004
> TOSHIBA DVD-ROM SD-R2512 [CD-ROM drive]
> HTS424040M9AT00 [Hard drive] (40.01 GB) -- drive 0, s/n MPA201Q2GASN7A,
rev
> MA2OA60V, SMART Status: Healthy
> ATI MOBILITY RADEON 9000 IGP [Display adapter]
> CPT 15.4 [Monitor] (15.4"vis, October 2004)
> Realtek AC97 Audio
>

I should have mentioned that I am only installing "High-priority updates".
I'm not installing any optional driver updates from Windows Update.
This failure occurs after running a System repair, and then installing
Windows Update.

Thanks very much for reading my posts!!


"Darryl Gittins" wrote:

> On Dec 15, I installed the latest Windows Updates, and then the system did a
> BSOD on restart:
> 0x0000000A(0x00000304,0x00000002,0x00000002,0 x806FFA16)
> IRQL_NOT_LESS_OR_EQUAL on my laptop
>
> I can't start in safe mode and the "Last known good configuration" will not
> start it either.
> I ran system repair (an in place upgrade) using s Windows XP SP2 slipstream
> disc, and the system started, and then I ran Windows Update (65 or so
> updates), but then I got the Stop error again.
>
> Not sure how to track down which update is killing the system. Any
> suggestions?
>
> Thanks!!
>
> Darryl
>
> TOSHIBA Satellite A70 PSA70C-KL100E
> Board: TOSHIBA EDW10
> BIOS: TOSHIBA V1.30 09/10/2004
> TOSHIBA DVD-ROM SD-R2512 [CD-ROM drive]
> HTS424040M9AT00 [Hard drive] (40.01 GB) -- drive 0, s/n MPA201Q2GASN7A, rev
> MA2OA60V, SMART Status: Healthy
> ATI MOBILITY RADEON 9000 IGP [Display adapter]
> CPT 15.4 [Monitor] (15.4"vis, October 2004)
> Realtek AC97 Audio
>

Yes, thanks DL! I realized after posting I should have spcified this and
posted an update at the same time as you sent this!

I am only installing "High-priority updates".
I'm not installing any optional driver updates from Windows Update.
This failure occurs after running a System repair, and then installing
Windows Update, and only installing "High-priority updates".

Thanks very much for reading my posts!!


"DL" wrote:

> You installed critical updates only?
> NOT any driver updates?
>
> "Darryl Gittins" <> wrote in message
> news:C1D4D408-A638-4CBF-A251-...
> > On Dec 15, I installed the latest Windows Updates, and then the system did
> a
> > BSOD on restart:
> > 0x0000000A(0x00000304,0x00000002,0x00000002,0 x806FFA16)
> > IRQL_NOT_LESS_OR_EQUAL on my laptop
> >
> > I can't start in safe mode and the "Last known good configuration" will
> not
> > start it either.
> > I ran system repair (an in place upgrade) using s Windows XP SP2
> slipstream
> > disc, and the system started, and then I ran Windows Update (65 or so
> > updates), but then I got the Stop error again.
> >
> > Not sure how to track down which update is killing the system. Any
> > suggestions?
> >
> > Thanks!!
> >
> > Darryl
> >
> > TOSHIBA Satellite A70 PSA70C-KL100E
> > Board: TOSHIBA EDW10
> > BIOS: TOSHIBA V1.30 09/10/2004
> > TOSHIBA DVD-ROM SD-R2512 [CD-ROM drive]
> > HTS424040M9AT00 [Hard drive] (40.01 GB) -- drive 0, s/n MPA201Q2GASN7A,
> rev
> > MA2OA60V, SMART Status: Healthy
> > ATI MOBILITY RADEON 9000 IGP [Display adapter]
> > CPT 15.4 [Monitor] (15.4"vis, October 2004)
> > Realtek AC97 Audio
> >
>
>
>

I'm systematically going through and installing blocks of updates (after yet
another system rebuild). So far, I have successfully installed the following
UpdatesJanuary 1, 2007
873339
885835
885836
886185
888302
890859
891781
893756
894391
896358
896423
896424
896428
899587
899591
920670
920683
921398
922616
922582
920685
920872
925486
923414
924496
923191
924191
922819
920213
924270
925454
923980
926255
923694
925398
923689
917734
911564
So far so good – no BSOD. However, then I installed the following in one
block:
900485
900725
901017
901214
902400
904706
905414
905749
908519
After the restart, I received the following error message:

STOP: c0000221 {Bad Image Checksum}
The image ole32.dll is possibly corrupt. the header checksum does not match
the computed checksum

Boo-hoo! Another rebuild…

See replies to your own thread.

Darryl Gittins wrote:
> I've been installing the High-Priority Updates one by one, and I have
> determined that KB 902400 is causing the error. After I install the 902400
> security update, I get tf Stop error on a blue screen:
>
> STOP: c0000221 {Bad Image Checksum}
> The image ole32.dll is possibly corrupt.
> The header checksum does not match the computed checksum
>
>
>
> After this error occurs, I cannot start the computer in safe mode, and the
> "Last known good configuration" will not fix the problem either.
>
> Specifically, what happened is I ran system repair (an in place upgrade
> using s Windows XP SP2 slipstream disc), and the system started, and then
> I
> ran installed the 902400 update, and then I got the c0000221 Stop error
> again.

Receiving the image ole32.dll is possibly corrupt error message after
running Windows Updates on Microsoft Windows XP? It happened to me on a
brand new Dell Optiplex 320. The fix was to boot to a Windows XP cd,
choose the Recovery Console option, rename the
c:\windows\system32\ole32.dll file to ole32.bak, then navigate to
C:\WINDOWS\$NtUninstallKB902400$ and copy the ole32.dll file from there
to the c:\windows\system32 directory.

Reboot and voila, it was fixed. Damn Microsoft and their stupid
PC-busting updates... Other folks said KB902400 broke them too.


--
mikebailey2000
Posted via http://ms-os.com Forum to Usenet gateway

Thanks,

It turned out to be a bad drive after all for me. I think. I replaced the
drive an d now all is well (and faster too!)

"mikebailey2000" wrote:

>
> Receiving the image ole32.dll is possibly corrupt error message after
> running Windows Updates on Microsoft Windows XP? It happened to me on a
> brand new Dell Optiplex 320. The fix was to boot to a Windows XP cd,
> choose the Recovery Console option, rename the
> c:\windows\system32\ole32.dll file to ole32.bak, then navigate to
> C:\WINDOWS\$NtUninstallKB902400$ and copy the ole32.dll file from there
> to the c:\windows\system32 directory.
>
> Reboot and voila, it was fixed. Damn Microsoft and their stupid
> PC-busting updates... Other folks said KB902400 broke them too.
>
>
> --
> mikebailey2000
> Posted via http://ms-os.com Forum to Usenet gateway
>
>

Can you provide me with some insight on how to rename the
c:\windows\system32\ole32.dll file to ole32.bak?

"mikebailey2000" wrote:

>
> Receiving the image ole32.dll is possibly corrupt error message after
> running Windows Updates on Microsoft Windows XP? It happened to me on a
> brand new Dell Optiplex 320. The fix was to boot to a Windows XP cd,
> choose the Recovery Console option, rename the
> c:\windows\system32\ole32.dll file to ole32.bak, then navigate to
> C:\WINDOWS\$NtUninstallKB902400$ and copy the ole32.dll file from there
> to the c:\windows\system32 directory.
>
> Reboot and voila, it was fixed. Damn Microsoft and their stupid
> PC-busting updates... Other folks said KB902400 broke them too.
>
>
> --
> mikebailey2000
> Posted via http://ms-os.com Forum to Usenet gateway
>
>