svchost error when rebooting after installing february updates.

I've seen this error on many different computers after installing updates
released in feb. sometime. Seen it all brands of PC and all types, Celerons,
Semprons, P4s, Athlon 64s you name it. HP, compaqs, clones, PCs big and
small. It generally only happens once, then never again, but on some the
error will pop up again. Some PCs never experience the error EVER! It's
totally random except for the fact it's exact same error on many different
types PCs after installing the same set of updates. I suspect the error is
generated during shutdown since it sticks
"UserFault" "dumprep 0 -u" in the registry.

If anyone knows what it is and how to fix it, I'd like to know.
If anyone knows which one of the 5 or so updates that were released last
month is the culprit, lemmi know.
If anyone gets the error, please the send the error report. Maybe if MS
gets a trillion of them, it'll send off some sort of bug alarm bell :-)

Thanks,
Klaus

"kthane",

We watch for this condition (lots of the same error) constantly. I am not
sure what problem you are having. Are you saying that shutdown sticks?
Shutdown does not work properly? Are you stuck right now on one of your
PC's? I'd like to understand more. Would you mind attempting to reproduce
the problem and sending us the relevant entries from the WindowsUpdate.log?
This is assuming you are using Windows XP. Are you using Windows XP?

Sincerely,

Pat Walters [MSFT]


"kthane" <> wrote in message
news:90A31ED4-696C-475B-8D74-...
> I've seen this error on many different computers after installing updates
> released in feb. sometime. Seen it all brands of PC and all types,
Celerons,
> Semprons, P4s, Athlon 64s you name it. HP, compaqs, clones, PCs big and
> small. It generally only happens once, then never again, but on some the
> error will pop up again. Some PCs never experience the error EVER! It's
> totally random except for the fact it's exact same error on many different
> types PCs after installing the same set of updates. I suspect the error
is
> generated during shutdown since it sticks
> "UserFault" "dumprep 0 -u" in the registry.
>
> If anyone knows what it is and how to fix it, I'd like to know.
> If anyone knows which one of the 5 or so updates that were released last
> month is the culprit, lemmi know.
> If anyone gets the error, please the send the error report. Maybe if MS
> gets a trillion of them, it'll send off some sort of bug alarm bell :-)
>
> Thanks,
> Klaus