Re: System shuts down while loading.

It would seem that quite a few people are getting the same error after
installing the last set of Microsoft critical updates. Some of the
people have not explained the symptoms too well so I will try to
explain the problem accurately: -

1) The problem occurs after updating an XP (pro or home?) machine with
the latest set of critical updates.

2) In my case the machine was fully patched before the update and
spyware/virus free (MS Antispyware + Ad-Aware + McAfee).

3) When the machine reboots after a "Successful" update, the boot
progresses to the "Loading Windows XP" screen with the progress bar.
The bar gets to 100% the screen blanks and then there is a BSOD with
the message: -

"STOP : C000021a {Fatal System Eroro} The Windows Logon Process System
process terminated unexpectedly with a status of
0xc0000018(0x00000000x00000000*) The system has been shut down"

4) Using F8 and:-

a) Trying to boot into safe mode gives the same error.

b) Trying to boot to last known configuration gives the same error.

I have read one thread from somebody who did a full clean install and
when he went to MS update and got the same bunch of patches the machine
did exactly the same which sort of implies that it is not due to
software already installed.

My son's machine is an IBM 390X laptop with 256Mb memory.

The install went smoothly on my daugthers IBM 390E laptop, both of our
Dell desktops and my Dell portable so I presume that it is hardware
related although I have no clue what.

If anyone can add any more info then please do.

The stuff in the MS KB all seem to relate to subtlely different
problems that can be cured by booting into safe mode or choosing last
know good configuration but as I said above, THAT DOES NOT WORK.

Any ideas Microsoft ????

Richtoy,

I have had the exact same problem with the exact same hex error codes you
have. I have experienced it on both my home computer and one of our laptops
at work. I have spent hours trying to track down the cause of this, but to
no avail. It is definately related to the last set of windows xp updates. I
am thinking it was the service pack 2 cumulative updates (I don't mean sp2
itself, but the updates for it).
My computer was also spyware and virus free before the suposedly
"successful" application of the updates. Happy hunting to us both!


"richtoy" wrote:

>
> It would seem that quite a few people are getting the same error after
> installing the last set of Microsoft critical updates. Some of the
> people have not explained the symptoms too well so I will try to
> explain the problem accurately: -
>
> 1) The problem occurs after updating an XP (pro or home?) machine with
> the latest set of critical updates.
>
> 2) In my case the machine was fully patched before the update and
> spyware/virus free (MS Antispyware + Ad-Aware + McAfee).
>
> 3) When the machine reboots after a "Successful" update, the boot
> progresses to the "Loading Windows XP" screen with the progress bar.
> The bar gets to 100% the screen blanks and then there is a BSOD with
> the message: -
>
> "STOP : C000021a {Fatal System Eroro} The Windows Logon Process System
> process terminated unexpectedly with a status of
> 0xc0000018(0x00000000x00000000Â*) The system has been shut down"
>
> 4) Using F8 and:-
>
> a) Trying to boot into safe mode gives the same error.
>
> b) Trying to boot to last known configuration gives the same error.
>
> I have read one thread from somebody who did a full clean install and
> when he went to MS update and got the same bunch of patches the machine
> did exactly the same which sort of implies that it is not due to
> software already installed.
>
> My son's machine is an IBM 390X laptop with 256Mb memory.
>
> The install went smoothly on my daugthers IBM 390E laptop, both of our
> Dell desktops and my Dell portable so I presume that it is hardware
> related although I have no clue what.
>
> If anyone can add any more info then please do.
>
> The stuff in the MS KB all seem to relate to subtlely different
> problems that can be cured by booting into safe mode or choosing last
> know good configuration but as I said above, THAT DOES NOT WORK.
>
> Any ideas Microsoft ????
>
>

I have had this problem on 4 machines so far. They have all been Dell GX60,
XP Pro SP2, up-to-date symantec anti-virus.

I have been able to recover the machines simply by running the repair
utility and letting it replace whatever has gone wrong, though I still dont
know what patch has caused the problem.

Although I'm unsure of what IS causing the problem, I can perhaps shed some
light on what isn't. There was one machine (same spec.) which had run
windows update on friday without any issues. Heres the list of what it
installed:
MS Windows Installer 3.1
KB890859 (MS05-018)
KB893086 (MS05-016)
KB890923 (MS05-020)
KB890830
KB893066 (MS05-019)


I ran the update this morning hoping to find the rest of the April updates
waiting to be installed however I only got .Net 1.1 SP1. I'll perhaps
install the remaining April updates individually to find the culprit.

This is all useful since I am having the samwe problem. The question is
though, how do you fix it? especially since I can't even log on or get to the
C: prompt?

"IrwinRL" wrote:

> I have had this problem on 4 machines so far. They have all been Dell GX60,
> XP Pro SP2, up-to-date symantec anti-virus.
>
> I have been able to recover the machines simply by running the repair
> utility and letting it replace whatever has gone wrong, though I still dont
> know what patch has caused the problem.
>
> Although I'm unsure of what IS causing the problem, I can perhaps shed some
> light on what isn't. There was one machine (same spec.) which had run
> windows update on friday without any issues. Heres the list of what it
> installed:
> MS Windows Installer 3.1
> KB890859 (MS05-018)
> KB893086 (MS05-016)
> KB890923 (MS05-020)
> KB890830
> KB893066 (MS05-019)
>
>
> I ran the update this morning hoping to find the rest of the April updates
> waiting to be installed however I only got .Net 1.1 SP1. I'll perhaps
> install the remaining April updates individually to find the culprit.

MichelleS wrote:

> This is all useful since I am having the samwe problem. The question is
> though, how do you fix it? especially since I can't even log on or get to the
> C: prompt?

Post a new message. Don't hijack another thread. Give a complete and
concise description of the problem, the system and all troubleshooting
you have done.

Making Good Newsgroup Posts
http://dts-l.org/goodpost.htm


--
Rock
MS MVP Windows - Shell/User

Rock, why don't you just help the girl, give some valuable advice
instead of whining about a correct procedure...the problem is already
described accurately by many people (see ABOVE messages)
I have the same problem and it is frustrating as it is, especially
working under time pressure to get it fixed.

I refer to the problem described in detail by the many other people
about the Fatal System error-blue screen. Unfortunately, I do not have
Norton installed, nor do I have a Dell that has this option of getting
the system to boot trhough a different way.
I can only press F8 and none of the options get me to either a command
prompt or into Windows.
For some reason, my computer is also not reading my cdrom drive
anymore, thus, a XP cd, boot cd or anything can not help it getting
started. HELP!

I also do not have a floppy drive. Any ideas on reinstalling windows
with these limitations?....it has been driving me crazy for the past
months and am almost ready to go out and by a new harddrive..but that
isn't the problem.

Thank you all, for your feedback and just the thought of willing to
help and advise...

Nic

Rock wrote:
> MichelleS wrote:
>
> > This is all useful since I am having the samwe problem. The question is
> > though, how do you fix it? especially since I can't even log on or get to the
> > C: prompt?
>
> Post a new message. Don't hijack another thread. Give a complete and
> concise description of the problem, the system and all troubleshooting
> you have done.
>
> Making Good Newsgroup Posts
> http://dts-l.org/goodpost.htm
>
>
> --
> Rock
> MS MVP Windows - Shell/User

Nic wrote:

> Rock, why don't you just help the girl, give some valuable advice
> instead of whining about a correct procedure...the problem is already
> described accurately by many people (see ABOVE messages)
> I have the same problem and it is frustrating as it is, especially
> working under time pressure to get it fixed.
>

<snip>

Nic I feel your frustration, but my advice to you is the same. Post a
new message with the specifics of your system, when the problem
occurred, what changes were made to the system between when the system
was running well and when the issue came up, and any troubelshooting
steps you've taken. Nic, in my experience there can be significant
differences in setup between systems. When someone says they have the
exact same problem that may mean they have some of the same symptoms,
but doesn't necessarily mean things are exactly the same. And there can
still be differences in what's causing the problem because the systems
are different.

--
Rock
MS MVP Windows - Shell/User