Microsoft, you have a BUG in one of your patches

[Steve N.]

The next time you see this error, look to see if it offers to send the crash
info to Microsoft. If so, let it send, and then follow the link to see
whether there is any relevant information. The cause of this type of crash
can be lots of different reasons (as you might have surmised from the
various replies on this thread), and while it may be commonly repro'd by
your systems, it doesn't sound like everyone is seeing the same thing. The
crash reporting system uses a sophisticated analysis system to identify
specific issues, and many of them have a fix or workaround available, or
provide other useful info.

Kinda hard to send the error to OCA when the error only happens whan it
is disconneted from the network, donchya think?

Steve

 

[John [MSFT]]

You can plug the network cable back in AFTER getting the message that there
was a problem and BEFORE you hit "Send this to Microsoft".

 

[Guest]

Here's my take. I'm a novice. I used the Networking Wizard to set up a
cross-over cable network between two XP Pro machines, both SP2 and updated.
The Wizard bridged the 10/100 card and the phone line networking card. I
removed the bridge and the svchost start-up error occurred occasionally.
Restoring the bridge eliminated the error. I've followed this over several
months with the administrative tools event viewer logs and when the bridge is
removed the error occurs, when the bridge is present, the error ceases.
Spooky.

 

[Kelly]

Here is the deal: I run a computer shop and we often have to do

reloads to computers due to spyware and viruses eating them up.

I do the same here at home out of my repair shop and have never had to
reinstall XP due to these conditions. There are other measures that take
common sense to resolve.

--

All the Best,
Kelly (MS-MVP)

Troubleshooting Windows XP
http://www.kellys-korner-xp.com

 

[SepticTank]

Kelly,

Ths is off-topic, but I felt a need to reply to this.

Yes, it's about a 50% shot at removing spyware from someone's system.
Sometimes the tools available (like Ad-Aware or MS's anti-spyware)
work. Often times, the spyware is so insidious that it will keep
reoccuring, it's embedded within the registry.

I have two options: spend an inordinate amount of time poking around
the registry trying to find entries, doing resrarch on the internet,
etc. all of which probably won't resolve anything. Or I can, in one
fell swoop, blow it all away and start over.

Which do you think is the most time and cost effective for the
customer? Which is the route of common sense?