Dr. Watson shutdown/logoff error

[Unsubscribe Here!]

I'm working on a machine running XP SP2 with all the updates. The whole
configuration seems to work very smoothly and I have no complaints about its
performance.
(Mark the wall.)

But...

Everytime I log off an account or request shutdown, I get this curious
"DWWIN.EXE failed to initialize" error. It quickly goes away and the system
finishes the shutdown or logoff.

What I know about this beforehand:
1) The error refers to the Dr. Watson / Error Reporting Service attempting
to log a report about an application that is running.

2) Disabling Error Reporting doesn't stop the error from occuring.

3) No running processes have failed (to my knowledge) during the entire
session.

4) MS doesn't offer any answers in the Knowledge Base.

This error probably isn't harmful in any way. I know this. Just drives me
crazy trying to troubleshoot it.

Does anyone have any prior experience with this error?
(Does anyone know how to kill it?)

- Brent

 

[Mark L. Ferguson]

To repair all system files, go to Start/Run, and type: SFC /SCANNOW

 

[Unsubscribe Here!]

To repair all system files, go to Start/Run, and type: SFC /SCANNOW

Sorry to come back with a counter-question, Mark, but I think I should ask
before doing this...

I actually was thinking of running System File Checker. What I can't
remember is:

1) Does SFC perform the whole thing without you, or prompt you to confirm
what file(s) you intend to correct? (In case you only want to repair 1
file, etc.)

2) Does it repair by going back to the original version (on the CD)?

3) If yes to #2, does that create other problems? (My CD is pre-SP1, and
this system has SP2, and all the updates.)

- Brent

 

[Mark L. Ferguson]

SFC uses the 'hotfix' info in updates to use the correct files. It MAY require you to press 'r' for Retry hundreds of times,
depending on how you installed XP.

 

[Unsubscribe Here!]

SFC uses the 'hotfix' info in updates to use the correct files. It
MAY require you to press 'r' for Retry hundreds of times, depending
on how you installed XP.

Well, thanks, Mark, for the suggestion.
Unfortunately, it wasn't the solution. (I, for one, thought SFC was a
logical step.)

I finished running SFC and have rebooted.
When I logged off, the error is still there.

I looked through the event viewer to see if SFC tried to replace the file in
question (dwwin.exe). There were no entries.

Still lookin' for ideas. Got any more?

- Brent

 

[Mark L. Ferguson]

If we assume Dr. W is functioning correctly, and is not corrupt, it leaves the us with the Dr's old friend Sherlock, who said
'eliminate the impossible, and what is left is the answer'. I would investigate some app that is designed to crash Dr. Watson. I
have not heard of such a virus, but I suppose it would be worth a search. I looked for known bugs in Dr.W and found none.

 

[Unsubscribe Here!]

If we assume Dr. W is functioning correctly, and is not corrupt, it
leaves the us with the Dr's old friend Sherlock, who said 'eliminate
the impossible, and what is left is the answer'. I would investigate
some app that is designed to crash Dr. Watson. I have not heard of

(I can certify this system is clean at this time.)

such a virus, but I suppose it would be worth a search. I looked for
known bugs in Dr.W and found none.

Actually, I did find a few references (in other forums, not MS) to "bugs" in
the Error Reporting Service that resemble my symptom.

All the entries seemed to point to a failure for the ERS to finish writing
to a log before the logged app shutsdown, causing a dwwin.exe error on
shutdown or logoff. I can't quite figure out what exactly the conflict
might be, if indeed a conflict is what's happening, in any of these cases.

Some referred to the Gravis Exterminator (Experience) game controls as being
the "culprit". When the driver or app was uninstalled, the error went away
(for some - not all). Similar theories seemed to revolve around NAV2004.
Again, some got relief from simply ripping NAV out and putting it back in,
while others complained the error persisted - some were rid of the error
before reinstalling, others saw no change at any point.

I find these entries interesting, as I have both NAV2004 and the Gravis
Experience Control Panel (driving a Gravis Exterminator Joystick) installed.
I'm inclined to think at this point that it would probably be a good idea to
remove the game control, and test that theory. (Not that I don't believe
Norton apps could have a hand in this - it's just far more work to reinstall
a Symantec app! I'm gonna take the easy route first.)

%-(
Funny how something that really isn't supposed to be very significant to the
performance of my system can bug me to such a point that I just "have to"
fix it! (The computer's working sooo well right now!... This is definitely
a curious case of the compulsive need to fix what ain't broke.)


- Brent

 

[Unsubscribe Here!]

FOLLOWUP:
(Thought anyone else in a similar situation might appreciate the info.)


I FOUND IT!
(The crowd goes WILD!)

After closer examination of the processes that were running on my computer,
I realized there was an executable for the Gravis Game Control running.

I could see no logical reason for this to be running in the background, as
the control will load and unload on demand anyway. (Why do sooo many
applications have to do this??!) So, rather than uninstall the software, I
first tried removing this file from the Startup (msconfig).

The game control still operates properly, and the DWWIN.EXE error no longer
occurs. (And I can save a little on coffee, too!)

Thanks for your contribution here, Mark!

Cheers!
- Brent