Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have asked a question about handling crashes of a command line tool in a C# application on stackoverflow. I was pointed to this forum for finding out, how to avoid that WerFault.exe jumps in and displays a crash report message for the command line tool, the crash of which I want to handle with my C# application.

share|improve this question
up vote 2 down vote accepted

Crashes are handled by Windows by default, visit Stack Overflow for a programmatic solution to hook into the process instead of waiting for a capture. But, you might not need to hook yourself:

Windows looks up

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug

in order to know what debugger needs to be launched when a crass occurs.

The most usual generators are:

The most usual debuggers are:

Of these, you might be able to just let Dr. Watson or ProcDump do it's job, after which you can open the debugging file for more information. These three links might get you going if you need to read the generated *.dmp files they produce:

Even better, you might be able to just use ProcDump and don't even need to set AeDebug\Debugger.

share|improve this answer
Thanks! Apparently automatic debugging can be deactivated for certain applications under Windows versions newer than XP/Server 2003: For older OS versions there seems to be no chance. – AlexDPC Jan 26 '11 at 14:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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