Dr Watson Debugger problems

G

Guest

Hi, After doing a general search i've found that lots of people seem to be
having the same problem with Dr Watson basically causing XP to crash and
being unable to access pretty much everything. After some research i've
found the problem may lie in the registry and i've followed the instructions
from microsoft to solve the problem by deleting the "AeDebug" key from the
registry, this is not solving anything, as when i then click anything on the
desktop everything disappears and then re-appears............ please help!!
Helen
 
D

Don Taylor

=?Utf-8?B?SGVsbHlwb29o?= said:
Hi, After doing a general search i've found that lots of people seem to be
having the same problem with Dr Watson basically causing XP to crash and
being unable to access pretty much everything. After some research i've
found the problem may lie in the registry and i've followed the instructions
from microsoft to solve the problem by deleting the "AeDebug" key from the
registry, this is not solving anything, as when i then click anything on the
desktop everything disappears and then re-appears............ please help!!
Helen

I tend to believe that Dr Watson might not be what is causing your
crash. My reasoning for this is that Dr Watson is usually started
AFTER something has crashed and it is supposed to then capture what
details it can so this can be reported, and somewhere in all our
dreams, get them to fix it.

As a tiny bit of evidence to support my claim, you turned off Dr
Watson and you still see the failure.

The desktop disappearing and reappearing, that is Windows Explorer,
not Internet Explorer, crashing and automatically restarting.

This is a very common failure, I probably see that half a dozen
times a day. Immediately after installing SP2 hundreds of people
reported almost identical failures with Windows Explorer. I spent
MONTHS with Microsoft trying to help get them to track down this
very repeatable problem and who knows, maybe even fix it. They had
me do dozens and dozens of things, some repeatedly even after we
had conclusively ruled them out as a possible cause, and nothing
they did ever found the source of this. They finally wouldn't even
answer email about this.

NOBODY here has a clue what to do about this, other than the usual
chant that it is probably all viruses and spyware, even though that
failed to be confirmed by all but one of the hundreds of people
who reported the Windows Explorer post-SP2 failure, but it is easy
to claim, fairly easy to check, and makes you go away for a while,
maybe you won't come back and bother them with this again afterwards.

Google can search this group for my postings dating back to last
August, which has a long list of things that have been claimed to
be the source of this. It probably won't do you any good but you
could try each of those things and see if a miracle happens.
Unfortunately Windows Explorer crashes so often that my guess is
it was decided to remove all the event log reporting, so it wouldn't
look so bad, and thus there is almost no information that can be
used to track down the actual source of this and fix it.

My apologies.
And they spent a billion bucks for this?!?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top