How to track bug - Program stopped responding.

Question

Occasionaly my app crashes with just the common Windows' message - Program stopped responding. I get no error message. How to track the bug?
... Podlesnick ...

Answer 1

Sounds like there's an unhandled exception that's perhaps occurring on a background thread.  I suggest adding an event handler for your AppDomain's UnhandledException event and putting some logging in there:
https://msdn.microsoft.com/en-us/library/system.appdomain.unhandledexception%28v=vs.110%29.aspx
You may also need to modify your application's default unhandled exception behavior:
https://msdn.microsoft.com/en-us/library/ms157905%28v=vs.110%29.aspx
The information on the above pages should be enough to ensure almost* all exceptions can get caught by your code before triggering Windows Error Reporting.
(*Exceptions caused by the whole system being in an unstable state, such as a kernel mode issue, may not be caught - at that point all bets are off).
Quanta,
    I think that there is a bug in your thinking.
 - I agree that a worker thread may cause a Kernel error
 - I agree that this kernel error may cause the application to get unstable and can cause the UI thread to start to hang waiting for a return value
 - And I agree that if this happen then this message will pop 
However,
 - If the error was silent, it is that the worker thread never returned (Otherwise, the error would have been propagated.
 - If the message has popped, it is that the UI thread is hanging (deadlocked)
Then if all your threads are blocked, ... Which thread will raise the Unhanded exception event?? ... all your threads are stopped or blocked somewhere.
This is why In the code example I showed, I used a Timers.timer to create the exception and stop the application. The Timers.timer object bring a new thread in the application when the application start to hang. This thread can be used to resolve the situation.
I choose to Abort the UI thread as it is the only logical thing to do. Plus doing this gives us the stack trace and info needed for debugging