I agree that troubleshooting dump files using native debuggers like cdb, ntsd or windbg isn’t that straightforward. Even if you are debugging a managed application, there is a steep learning curve before you can become really savvy with these debuggers. There is however one tool that can be helpful without going through all that learning cycles. DebugDiag comes with a component called “DebugDiag Analysis Only”. The idea is that you collect process dump file with any of your favourite tool (like Task Manager, ADPlus, ProcDump, WER etc) and just have DebugDiag analyze this dump file and find root cause of the problem. And best of all, DebugDiag is a free tool you can download from Microsoft website. If you haven’t used it before, go ahead and give it a shot.
Until next, happy debugging.