Periodically my ASP.NET application crashes (usually because memory consumption exceeds maximum allowed by application pool) and DW20.exe starts up. This is a big problem because it uses huge amounts of memory and CPU for minutes at a time.

I want to know how to stop DW20.exe from running. Please note, I have already tried these often mentioned solutions:

  • Disabling error reporting in Control Panel > System > Advanced > Error Reporting

  • Disabling the Error Reporting Service

  • Modifying the registry as in http://support.microsoft.com/kb/841477 (however I might have done this wrong - this doc says "add a DWReportee value of 1" - what I did was add a DWORD entry with hexadecimal value of 1 - is this right? Also only 2 of the 4 keys were present, so I only modified these, e.g. there was no HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\PCHealth key at all)

So, zero points for suggesting any of the above (unless you can see I have modified the registry incorrectly)! Also zero points for suggesting I resolve whatever is causing the application crashes :) - I am figuring this out, I just want something in the mean time to stop DW20.exe eating up all the server resources.

By the way, this is a Windows 2003 SP1 server, with IIS 6 and SQL 2005 installed. There is no MS Office.

link|improve this question

20% accept rate
did you name the dword value DWReportee? – David May 21 '10 at 17:37
Would it be acceptable to blacklist the DW20.exe using a Local Group Policy Software Restriction? Or would that be "too hacky"? – jscott Sep 27 '11 at 12:29
You could fix your application to not exceed the memory pool. It's not DW20.exe that's causing your issues. I would spend more time on fixing the memory issues in your application. Doctor Watson is trying to tell you something is wrong. – Joseph Kern May 9 at 2:31
feedback

1 Answer

I think what you want may actually be here: http://support.microsoft.com/kb/325075/ it was linked to from the kb article you mentioned.

Sorry, that looks specific to office, maybe worth a try tho.

This might be more helpful: http://msdn.microsoft.com/en-us/library/bb204634(VS.85).aspx

This is kinda a prelude to the prior mentioned article: http://msdn.microsoft.com/en-us/library/2ac5yxx6.aspx

Looks to me like your best bet currently would be to try clearing the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\AeDebug\Debugger String, make sure to back it up first.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.