"COM Surrogate stopped...."

What is this message?

What does it mean?

Why doesn't it tell me which file (ideally application) is the cause of the
problem? This is like saying "a program is broken". What the hell good
does that do me?

Microsoft used to rule with wizards and with more useful, human-friendly
messages. So what happened?

squishy

squishy pretended :

> What is this message?
>
> What does it mean?
>
> Why doesn't it tell me which file (ideally application) is the cause
> of the problem? This is like saying "a program is broken". What the
> hell good does that do me?
>
> Microsoft used to rule with wizards and with more useful,
> human-friendly messages. So what happened?
>
> squishy

Look here:
http://www.vistabits.nl/tipstricks_g...urrogate_error

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

www.vistabits.nl
Let op, site layout veranderd!

MSN:
_*mamamegs@gmail.com*_

It's a crash in some DLL that was loaded in a separate process.
Historically bad third party plug-ins could bring down Explorer (or IE or
etc), so loading them in their own space prevents that "stopped working"
from bringing down Windows with it.

What's the fault bucket number:
http://zachd.com/pss/pss.html#bucket
?

If you check the Problem Reports and Solutions, you'll get some more data,
but without actually analyzing the crash dump in the Windows Debugging Tools
(available on MSDN), it can be hard to pinpoint the root cause.

Crashes are a fault in the system. It's hard to be more specific without an
analysis, and it wouldn't be fair to suggest culpability without getting a
real thorough analysis that could usually only be done by a person anyways.

-Zach
--
**Speaking for myself only.**
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--

"squishy" <squishy@inter.net> wrote in message
news:gvYYh.523$0x4.230@bignews4.bellsouth.net...

> What is this message?
>
> What does it mean?
>
> Why doesn't it tell me which file (ideally application) is the cause of
> the problem? This is like saying "a program is broken". What the hell
> good does that do me?
>
> Microsoft used to rule with wizards and with more useful, human-friendly
> messages. So what happened?
>
> squishy
>

My guess (and it's just a guess) - the Weather Bug gadget in the Sidebar
might be the culprit.


"zachd [MSFT]" <zachd@nomailplz.online.microsoft.com> wrote in message
news:e9lVpKviHHA.4188@TK2MSFTNGP02.phx.gbl...

>
> It's a crash in some DLL that was loaded in a separate process.
> Historically bad third party plug-ins could bring down Explorer (or IE or
> etc), so loading them in their own space prevents that "stopped working"
> from bringing down Windows with it.
>
> What's the fault bucket number:
> http://zachd.com/pss/pss.html#bucket
> ?
>
> If you check the Problem Reports and Solutions, you'll get some more data,
> but without actually analyzing the crash dump in the Windows Debugging
> Tools (available on MSDN), it can be hard to pinpoint the root cause.
>
> Crashes are a fault in the system. It's hard to be more specific without
> an analysis, and it wouldn't be fair to suggest culpability without
> getting a real thorough analysis that could usually only be done by a
> person anyways.
>
> -Zach
> --
> **Speaking for myself only.**
> See http://zachd.com/pss/pss.html for some helpful WMP info.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> --
>
> "squishy" <squishy@inter.net> wrote in message
> news:gvYYh.523$0x4.230@bignews4.bellsouth.net...

>
>