This is an older article (2006) but still an excellent resource for anyone who has to do deep troubleshooting and research to determine the cause of a crash in a .NET application. With these tips, and perhaps just a little luck, you can even trace the issue down to the exact line of code that’s causing the crash.
“I’ve written quite a few posts on memory issues because that is the type of problem we get most frequently in support, but I thought I’d break it up a little bit with a post on a crash scenario.
This is a problem that I have seen a number of times in cases throughout the years and it also turns out to be a pretty nice sample for showing how to debug a stackoverflow crash in .net.”
View the complete post: A .NET Crash: How not to write a global exception handler