KB925902 update causes STOP:c000021A fatal error at boot

My PC automatically downloaded update KB925902 yesterday. With the update
installed, the PC would boot into a BSOD with "STOP:c000021A {Fatal System
Error} The Session Manager Initialization System terminated unexpectedly with
a status of 0xc000026c (0x00000000 0x00000000) The system has been shut down.

None of the start up options would get the machine booted. It's running XP
Home SP2 with all prior updates installed.

In the end, I got the Recovery Console up and running and removed the
KB925902 update by running 'batch spuninst.txt' This removed the BSOD problem
and allowed the machine to boot OK.

So, the machine's now running but I'm without the KB925902 update and have
disabled Automatic Updates to prevent it installing for the time being.

Two possibilities seem to exist:

1) There's a problem with the KB925902 update which needs to be fixed.

2) There's some other incompatibility on my machine which is causing the
BSOD when the KB925902 update is applied.

Any thoughts please? I gather elsewhere that the STOP message above is
indicative of a security or permissions problem with system processes
towards the end of the boot.

JB

"J Barker" <> schrieb:

> 2) There's some other incompatibility on my machine which is causing the
> BSOD when the KB925902 update is applied.

Most likely. Do you have overclocked your machine? Or "tuned" otherwise?

Bye,
Freudi

An update...

I've just called Product Support Services.

They tell me that the KB925902 update is incompatible with my XP Home SP2
and they recommend that I hide the update to prevent its installation.

I can't see the sense in this. KB925902 was issued to fix a security
vulnerability which I would then still have, so this doesn't fix the problem.

"Ottmar Freudenberger" wrote:

> "J Barker" <> schrieb:
>
> > 2) There's some other incompatibility on my machine which is causing the
> > BSOD when the KB925902 update is applied.
>
> Most likely. Do you have overclocked your machine? Or "tuned" otherwise?
>
> Bye,
> Freudi
>

No overclocking or tuning applied.

"J Barker" <> schrieb:

> No overclocking or tuning applied.

Hm, which appications/services are running in the background and
were running while applying the update?

Do you have looked for updated system drivers (BIOS, chipset etc.)
for your system?

Bye,
Freudi

"J Barker" <> schrieb:

> I've just called Product Support Services.
>
> They tell me that the KB925902 update is incompatible with my XP Home SP2
> and they recommend that I hide the update to prevent its installation.
>
> I can't see the sense in this.

Me neither. What informations did "they" asked you for to come to that
IMHO braindead conclusion?

> KB925902 was issued to fix a security
> vulnerability which I would then still have, so this doesn't fix the problem.

ACK

Bye,
Freudi

"J Barker" wrote:

> My PC automatically downloaded update KB925902 yesterday. With the update
> installed, the PC would boot into a BSOD with "STOP:c000021A {Fatal System
> Error} The Session Manager Initialization System terminated unexpectedly with
> a status of 0xc000026c (0x00000000 0x00000000) The system has been shut down.
>
> None of the start up options would get the machine booted. It's running XP
> Home SP2 with all prior updates installed.
>
> In the end, I got the Recovery Console up and running and removed the
> KB925902 update by running 'batch spuninst.txt' This removed the BSOD problem
> and allowed the machine to boot OK.
>
> So, the machine's now running but I'm without the KB925902 update and have
> disabled Automatic Updates to prevent it installing for the time being.
>
> Two possibilities seem to exist:
>
> 1) There's a problem with the KB925902 update which needs to be fixed.
>
> 2) There's some other incompatibility on my machine which is causing the
> BSOD when the KB925902 update is applied.
>
> Any thoughts please? I gather elsewhere that the STOP message above is
> indicative of a security or permissions problem with system processes
> towards the end of the boot.
>
> JB

The fix stated here works perfectly. I was receiving this same exact error
on a users pc, performed this fix and machine is now working with out any
issues.

"J Barker" wrote:

> My PC automatically downloaded update KB925902 yesterday. With the update
> installed, the PC would boot into a BSOD with "STOP:c000021A {Fatal System
> Error} The Session Manager Initialization System terminated unexpectedly with
> a status of 0xc000026c (0x00000000 0x00000000) The system has been shut down.
>
> None of the start up options would get the machine booted. It's running XP
> Home SP2 with all prior updates installed.
>
> In the end, I got the Recovery Console up and running and removed the
> KB925902 update by running 'batch spuninst.txt' This removed the BSOD problem
> and allowed the machine to boot OK.
>
> So, the machine's now running but I'm without the KB925902 update and have
> disabled Automatic Updates to prevent it installing for the time being.
>
> Two possibilities seem to exist:
>
> 1) There's a problem with the KB925902 update which needs to be fixed.
>
> 2) There's some other incompatibility on my machine which is causing the
> BSOD when the KB925902 update is applied.
>
> Any thoughts please? I gather elsewhere that the STOP message above is
> indicative of a security or permissions problem with system processes
> towards the end of the boot.
>
> JB

What reason did PSS give for the incompatibility? 925902 had installed
w/out problem on 2 WinXP Home machines here.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org

J Barker wrote:
> An update...
>
> I've just called Product Support Services.
>
> They tell me that the KB925902 update is incompatible with my XP Home SP2
> and they recommend that I hide the update to prevent its installation.
>
> I can't see the sense in this. KB925902 was issued to fix a security
> vulnerability which I would then still have, so this doesn't fix the
> problem.

"T_Oli" wrote:

> The fix stated here works perfectly. I was receiving this same exact error
> on a users pc, performed this fix and machine is now working with out any
> issues.

I'm glad I'm not the only one with this problem, then.

I've now installed the hotfix for the Realtek HD Audio that MS issued and
then re-installed KB925902. The system then crashes as before, so I've had to
go and remove it again through Recovery Console. I can't find a way of
telling Microsoft Update to stop installing it, so Automatic Updates will
have to remain off for now.

After the disappointing telephone support I got (see above), I'm going to
try and raise a support call by e-mail. Anyone else had this problem or got
any ideas?

Thanks

JB