RE: KB925902 update causes STOP:c000021A fatal error at boot
I see this thread mainly deals with this problem in XP, however I have had my
old Windows NT (2000) system at work crash out with the same symptoms after
doing a Windows Update last weekend (looks like the first one that was done
since last December).
Can anyone advise on a fix specific to NT, or is it the same as the
procedure listed below?
Many thanks in advance...
"LA NetAdmin" wrote:
> "J Barker" wrote (paraphrased):
> Boot PC from Windows XP install CD.
> Launch the Recovery Console.
> In Recovery Console:
> cd $NtUninstallKB925902$\spuninst
> batch spuninst.txt
> Disable Automatic Updates temporarily.
> (Note: You can also do this in the Recovery Console: disable wuauserv)
> Reboot normally.
> Go to Control Panel \ Add/Remove Programs and remove the KB925902 patch.
> (make sure Show Updates is checked at the top of this page)
> Manually download KB925902 from Microsoft web site without installing.
> Boot your PC into Safe Mode.
> Run the KB925902 patch you manually downloaded
> Reboot again normally.
> Great call JB, had exact same symptoms on Dell Optiplex OEM pre-install with
> Windows XP Pro SP2.
> FYI: All booting options, including all variations of Safe-Mode and Last
> Known Good failed miserably. Since my machine had Automatically Restart on
> System Failure enabled, all I would see is the initial Windows XP graphic
> with the scrolling bar at the bottom, then bang, reboot.
> When I enabled Safe-Mode from the F8 screen, I would see the AGP440.SYS
> driver load last in the character-based mode and then as XP changed into GUI
> I had none of the driver conflicts MS has identified, so far, to blame.
> Just the likelihood that one or more of the replaced files, gdi32.dll,
> mf3216.dll, user32.dll, or win32k.sys, was locked in a way that the patch
> installer could not overcome.
> MS Support was even less helpful for me, offering only upgrade in-place,
> with possible/probable loss of data stored in All Users and possibly
> Administrator profiles too. Instead, I have a fully recovered system, with
> no loss at all.
> Thanks for posting your solution.