Annoyances.org
Home » Windows XP Discussion Forum » Message 1112632811 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: dwwin.exe
Monday, April 4, 2005 at 9:40 am
Windows XP Annoyances Discussion Forum
Posted by Ken (944 messages posted)


Hi all. I too had this dwwin.exe error message start to pop up at shutdown with WinXP Home Ed SP-2. It started right after installing a Gravis Gamepad Pro, and its XPerience ver 4.5 software. I also have Norton System Works 2003 installed. I have spent nearly 18 man-hours on this issue and I could have given up or chosen an easy out, but I'm the type person who likes a challenge AND demands to know EXACTLY what is causing a problem, so here's my results and opinions in the hope others can isolate their issues more quickly. I read this thread with great interest and tried nearly everything someone suggested with varying degrees of success. Here's what I recommend: 1. Do NOT turn off error reporting. You're only hiding the problem. That's like taping over your low fuel warning light and pretending it doesn't exist. 2. As someone earlier correctly pointed out, using "start /belownormal" in the registry before a Run command will simply disable that Run command, so of course the problem will appear to go away. But that will also keep the subject driver from loading at all (in my case the Gravis Grxp4exe.exe device driver), and you will not have use of its functions. The Gamepad still functions as a joystick from MS Windows drivers, but that's not why you installed the software in the first place. In my case, I wanted to use the Gamepad velcroed to my desk as a mini-keypad with all the buttons mapped to keys. You can't do that without the XPerience software driver loaded and functional. Sorry Norm, but your method is no different than simply unchecking the box in msconfig and rebooting. 3. The dwwin.exe error message appears because Dr. Watson detected an error, tried to load so it could report the error, and failed to initialize because Windows was being shut down. The key statement here is that "Dr. Watson detected an error". That's a good thing. It's your low fuel warning light. The challenge then becomes how to identify and correct the error in a logical, timely manner. 4. Software conflicts arise out of at least two applications having a problem with each other. How do you identify which two? In my case, it was easy to identify one since the problem started immediately after I installed the Gravis XPerience ver 4.5 software. I could (and did) verify that this was the problem by uninstalling it and the problem went away. But that didn't get me my mini-keyboard working. 5. After trying many suggestions in this thread and not getting anywhere, I decided to be logical about this and disabled ALL in the msconfig Startup Tab. Then I enabled the Gravis driver entirely by itself, and it worked perfectly with no dwwin.exe message. I think you can guess the rest.... 6. I re-enabled one item at a time, starting with the ones I suspected to be the culprits (Norton apps first, LOL), and rebooted each time. My conflict was not with any Norton app - they all loaded without a hitch. My conflict was found on the 8th or 9th app enabled, a memory management program I have called FreeMem Pro, ver 5.2. I immediately disabled it, and the problem went away, re-enabled it, the problem came back. Fortunately I had an earlier version of FreeMem Pro in my archives so on a whim I uninstalled 5.2 and installed 5.0. Guess what? No conflict. The difference in the two versions of this program is rather minimal, and I can easily accept that in return for no more conflicts or error messages. 7. Having found one conflict, I re-enabled ALL 20 or so other Startup items, rebooted and luckily that was the only problem. No more error messages and all my apps are coexisting peacefully again. Hope this helps others and good luck on your troubleshooting! Ken


Written in response to:
re: dwwin.exe (Ron: Tuesday, March 15, 2005 at 11:08 am)

There are presently no replies to this message.

All messages in this thread [show all]
-dwwin.exe (Leigh: Sun, Aug 18, 2002, 5:05 pm)
-re: dwwin.exe (Beecher Wood: Sun, Aug 18, 2002, 5:37 pm)
-re: dwwin.exe (Leigh: Sun, Aug 18, 2002, 5:42 pm)
-re: dwwin.exe (jcw: Sun, Aug 18, 2002, 8:25 pm)
-re: dwwin.exe (Arthur Kaljian: Tue, Oct 8, 2002, 7:11 pm)
-re: dwwin.exe (KenshinVu: Wed, Oct 1, 2003, 11:19 pm)
-re: dwwin.exe (KenshinVu: Wed, Oct 1, 2003, 11:36 pm)
-dwwin.exe (selina: Mon, Sep 18, 2006, 9:51 am)
-re: dwwin.exe (bgreen: Tue, Sep 26, 2006, 1:16 pm)
-re: dwwin.exe (GazUK: Thu, Sep 28, 2006, 12:29 am)
-re: dwwin.exe (Jilly: Thu, Sep 28, 2006, 2:40 pm)
-re: dwwin.exe (GhostB5: Tue, Nov 17, 2009, 9:47 am)
*re: dwwin.exe (GhostB5: Tue, Nov 17, 2009, 11:32 am)
-re: dwwin.exe (Metal: Thu, Oct 3, 2002, 6:18 pm)
*re: dwwin.exe (jcw: Tue, Oct 8, 2002, 10:29 pm)
-re: dwwin.exe (K: Mon, Oct 7, 2002, 10:48 am)
-re: dwwin.exe (jcw: Tue, Oct 8, 2002, 10:32 pm)
*re: dwwin.exe (Handy_man: Wed, Apr 7, 2004, 2:42 pm)
-re: dwwin.exe (Paul: Tue, Jun 1, 2004, 6:40 am)
-re: dwwin.exe (BillV: Tue, Jun 29, 2004, 11:43 am)
-re: dwwin.exe (CherokeeCandy: Mon, Aug 30, 2004, 10:31 am)
*re: dwwin.exe (tvzz: Fri, Apr 25, 2008, 8:51 pm)
*re: dwwin.exe (zzg: Mon, Feb 7, 2005, 3:31 am)
-re: dwwin.exe (jcw: Tue, Oct 8, 2002, 10:47 pm)
*re: dwwin.exe (Mutlin: Thu, Oct 10, 2002, 2:50 pm)
-re: dwwin.exe (norm: Sat, Oct 19, 2002, 8:48 am)
-re: dwwin.exe (norm: Sat, Oct 19, 2002, 8:57 am)
-re: dwwin.exe (Danny: Sun, Oct 20, 2002, 4:15 pm)
*re: dwwin.exe (Bob Barron: Sun, Jun 22, 2003, 3:10 pm)
*re: dwwin.exe (Robert Fakhoury: Mon, Oct 21, 2002, 6:39 pm)
-re: dwwin.exe (John D. Wilson: Thu, Oct 24, 2002, 8:02 am)
-re: dwwin.exe (norm: Thu, Oct 24, 2002, 8:47 pm)
-re: dwwin.exe (John D. Wilson: Fri, Oct 25, 2002, 5:18 am)
-re: dwwin.exe (norm: Fri, Oct 25, 2002, 7:36 am)
*re: dwwin.exe (John D. Wilson: Fri, Oct 25, 2002, 8:39 am)
*re: dwwin.exe (ColinFecho19: Thu, Nov 21, 2002, 2:14 pm)
-re: dwwin.exe (norm: Mon, Oct 21, 2002, 8:24 pm)
-re: dwwin.exe (Gary Burton: Fri, Oct 25, 2002, 2:45 pm)
-re: dwwin.exe (norm: Fri, Oct 25, 2002, 8:15 pm)
*re: dwwin.exe (Gary Burton: Wed, Nov 6, 2002, 4:56 pm)
*norm, you misled everyone on this forum (Glen Huffaker: Sat, Aug 30, 2003, 11:03 am)
*re: dwwin.exe (Pawolford: Fri, Jan 23, 2009, 7:46 am)
-re: dwwin.exe (Steven Bernard: Thu, Nov 28, 2002, 7:58 pm)
*re: dwwin.exe (norm: Thu, Nov 28, 2002, 8:24 pm)
-re: dwwin.exe (JimC: Sat, Jan 11, 2003, 11:00 am)
*re: dwwin.exe (norm: Sat, Jan 11, 2003, 5:53 pm)
-re: dwwin.exe Great! Norm,thanks very much (hulei: Tue, May 20, 2003, 10:49 pm)
*re: dwwin.exe Great! Norm,thanks very much (Chuck: Wed, Sep 10, 2003, 1:37 pm)
-re: dwwin.exe (Douglas: Sun, May 25, 2003, 3:05 am)
*re: dwwin.exe (Jj: Mon, May 26, 2003, 12:20 pm)
*re: dwwin.exe not simply belownormal (Godfried Hombergen: Fri, Jun 6, 2003, 12:41 pm)
*re: dwwin.exe (alan: Sun, Aug 31, 2003, 2:38 pm)
-re: dwwin.exe (Andrew Lee Chen: Sat, Feb 3, 2007, 9:24 am)
*re: dwwin.exe (AnOldMan: Sat, Feb 3, 2007, 11:03 pm)
-re: dwwin.exe (heldicus: Wed, Nov 20, 2002, 7:37 pm)
*re: dwwin.exe (Richard: Wed, Jan 8, 2003, 10:34 pm)
-re: dwwin.exe (safedot: Sat, Nov 23, 2002, 4:03 pm)
-re: dwwin.exe (Tom Carroll: Tue, Jan 21, 2003, 1:18 am)
-re: dwwin.exe (safedot: Tue, Jan 21, 2003, 4:19 pm)
-re: dwwin.exe (Tom Carroll: Tue, Jan 21, 2003, 5:01 pm)
-re: dwwin.exe (Joe: Tue, Feb 25, 2003, 9:25 am)
-re: dwwin.exe (SmallFry: Tue, May 27, 2003, 9:33 am)
-re: dwwin.exe (Tim Peakman: Sun, Jun 1, 2003, 8:53 pm)
-re: dwwin.exe (GiGi: Fri, Jun 20, 2003, 7:12 am)
*re: dwwin.exe (Moriarty: Sat, Jun 28, 2003, 2:40 pm)
*re: dwwin.exe (Foo: Wed, Sep 3, 2003, 3:13 pm)
-re: dwwin.exe (Craig G: Wed, Jul 2, 2003, 12:35 pm)
-re: dwwin.exe (Todd: Wed, Jul 2, 2003, 3:41 pm)
-re: dwwin.exe (Ray: Thu, Jul 3, 2003, 5:56 pm)
-re: dwwin.exe (heldicus: Sat, Jul 12, 2003, 10:46 pm)
-re: dwwin.exe (Big Dave: Wed, Jul 30, 2003, 5:21 pm)
-re: dwwin.exe (Colin: Fri, Aug 1, 2003, 12:50 am)
-re: dwwin.exe (kk: Sun, Aug 17, 2003, 5:57 am)
*re: dwwin.exe (RMbobELLIS: Fri, Oct 17, 2003, 9:31 am)
*re: dwwin.exe (gkwboy: Tue, Sep 9, 2003, 5:46 am)
-re: dwwin.exe (Nils: Mon, Aug 18, 2003, 2:12 am)
-re: dwwin.exe (Vengeance: Sun, Oct 12, 2003, 4:07 pm)
-re: dwwin.exe (Ruth: Mon, Oct 13, 2003, 12:06 pm)
-re: dwwin.exe (Ruth: Sat, Mar 27, 2004, 6:34 pm)
*re: dwwin.exe (Marlene: Sun, Mar 28, 2004, 1:10 pm)
-re: dwwin.exe (Ron: Tue, Mar 15, 2005, 11:08 am)
*re: dwwin.exe (Ken: Mon, Apr 4, 2005, 9:40 am)
-re: dwwin.exe (Barry Culp: Sun, Feb 1, 2004, 7:44 am)
-re: dwwin.exe (Dano: Mon, Feb 2, 2004, 2:43 pm)
-re: dwwin.exe (Bill: Mon, Feb 16, 2004, 12:17 am)
-re: dwwin.exe (Mike~: Thu, Feb 19, 2004, 8:38 pm)
-re: dwwin.exe (Jan: Sun, May 9, 2004, 8:00 pm)
*re: dwwin.exe (Jan: Sun, May 9, 2004, 8:33 pm)
*re: dwwin.exe (Jan: Sun, May 9, 2004, 8:15 pm)
*re: dwwin.exe (JohnRod: Mon, May 24, 2004, 11:12 am)
-re: dwwin.exe (Mario: Thu, Feb 26, 2004, 10:19 pm)
*re: dwwin.exe (Danyell: Tue, Jun 8, 2004, 4:59 am)
*re: dwwin.exe (guadman: Mon, Sep 27, 2004, 4:30 pm)
-re: dwwin.exe (Gamaliel Salen: Thu, Dec 9, 2004, 8:14 am)
-problem with cam (lebeca) (zola: Sat, Jun 4, 2005, 7:27 pm)
*DLL Inialization failed... (James Seymour: Mon, Jun 27, 2005, 7:45 pm)
-re: dwwin.exe (maria fe cavinta: Sat, Aug 6, 2005, 9:45 pm)
-re: dwwin.exe (Marek Konopka: Thu, Aug 11, 2005, 8:51 am)
-re: dwwin.exe (Miguel Chen: Sat, Sep 17, 2005, 11:15 am)
-re: dwwin.exe (DMS: Sun, Sep 25, 2005, 4:47 am)
-re: dwwin.exe (Falcon: Mon, Sep 26, 2005, 6:06 am)
*re: dwwin.exe (Mike Doverskog: Fri, Sep 30, 2005, 1:50 am)
-re: dwwin.exe (kHRIs: Fri, Oct 28, 2005, 4:09 pm)
*re: dwwin.exe (Florence Symons: Sat, Dec 3, 2005, 6:19 am)
-re: dwwin.exe (Joseph Schaeffer: Sun, Dec 4, 2005, 1:07 pm)
-re: dwwin.exe (Abbey: Sun, Jul 9, 2006, 8:22 pm)
*re: dwwin.exe (Vancouver Vince: Thu, Aug 17, 2006, 10:15 am)
-re: dwwin.exe (Peter Ward: Sat, Sep 9, 2006, 2:43 pm)
*re: dwwin.exe (Peter Ward: Sat, Sep 9, 2006, 4:23 pm)
-re: dwwin.exe (wyndfall: Thu, Oct 5, 2006, 4:23 pm)
-re: dwwin.exe (ablueangel: Sun, Oct 29, 2006, 4:31 pm)
*MS way to be rid of dwwin.exe (brian: Wed, Nov 8, 2006, 9:06 pm)
*re: dwwin.exe (Norman Hines: Wed, Dec 9, 2009, 10:44 am)
-re: dwwin.exe (mo: Sat, Dec 23, 2006, 3:48 pm)
-re: dwwin.exe (dan: Thu, Jan 4, 2007, 9:18 am)
*re: dwwin.exe (Eileen Souza: Sat, Feb 17, 2007, 5:02 am)
*re: dwwin.exe (TR: Tue, Feb 20, 2007, 4:43 pm)
-re: dwwin.exe (na: Thu, Mar 15, 2007, 1:45 pm)
*re: dwwin.exe (jeff: Thu, Mar 22, 2007, 10:06 pm)
-re: dwwin.exe (oward: Thu, Oct 11, 2007, 12:25 pm)
-re: dwwin.exe (felix: Thu, Oct 18, 2007, 8:39 pm)
-re: dwwin.exe (Charina Arayata: Tue, Jul 15, 2008, 10:40 pm)
*re: dwwin.exe (Spexx: Wed, Jul 16, 2008, 3:07 am)
-re: dwwin.exe (1ajb: Sun, Oct 28, 2007, 5:58 pm)
-re: dwwin.exe (Dan Ramirez: Mon, Oct 29, 2007, 10:46 am)
-re: dwwin.exe (Victoria: Fri, Mar 14, 2008, 4:16 pm)
-re: dwwin.exe (Mitch: Mon, Oct 27, 2008, 5:22 pm)
*re: dwwin.exe (Richard Sharman: Wed, Jan 7, 2009, 1:37 pm)
-re: dwwin.exe (DR: Wed, Apr 30, 2008, 12:17 pm)
-re: dwwin.exe (daintydinah: Mon, May 12, 2008, 1:49 pm)
-re: dwwin.exe (JNettik: Wed, Aug 13, 2008, 12:22 pm)
-re: dwwin.exe (Spexx: Wed, Aug 13, 2008, 12:41 pm)
*re: dwwin.exe (Pat: Thu, Sep 4, 2008, 1:18 pm)
-re: dwwin.exe (philselmer: Tue, Feb 24, 2009, 9:32 am)
*re: dwwin.exe (JBT: Fri, Mar 6, 2009, 8:31 pm)
-re: dwwin.exe (Papewaio: Thu, Apr 16, 2009, 8:22 am)
-re: dwwin.exe (John: Mon, Oct 12, 2009, 8:56 am)
*re: dwwin.exe (John: Wed, Oct 14, 2009, 4:58 pm)
Return to the Windows XP Discussion Forum


All content at Annoyances.org is Copyright ©1995-2012 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.