Debugging a dump from a hung server may not be something you do every day so you may want to engage with one of our debug experts, however with this information as your guide you may find that you can narrow down a problem and save yourself a call.
My Server is hung – what do I do?
If you need additional background on debugging, this article can get you started.
Basics of Debugging Windows
· Collect a kernel dump: http://support.microsoft.com/kb/244139
· Set up the debugger: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
· Know how to use the symbol server: http://support.microsoft.com/kb/311503
Here are some additional resources that you may find useful including links to the tools, book recommendations:
· ADPlus – An automated way to use the cdb.exe to capture/create a usermode dump when a process hangs or crashes. (more info – http://msdn.microsoft.com/en-us/library/cc265629.aspx or kb286350)
· Public Symbols for Microsoft Operating Systems:
· Microsoft Public Symbol server : srv * DownstreamStore * http://msdl.microsoft.com/download/symbols
· example: srv*c:\mysyms*http://msdl.microsoft.com/download/symbols
· Microsoft Symbol packages http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx#d
· Use !Analyze-v to gather additional information about the bugcheck and a bucket-id for your dump file. The bucket-id can be submitted to Microsoft for review for similar crashes and resolutions. Try using the Microsoft Online Crash Analysis to submit your crash dump bucket-id for possible follow up from Microsoft or for Microsoft to look for trends: http://oca.microsoft.com/en/Welcome.aspx
· For concepts, tools and information about the system architecture: http://msdn.microsoft.com/en-us/default.aspx
· Windows Internal 4th edition (by Mark E. Russinovich & David A. Solomon) the whole book or Chapter 14 – Crash Dump Analysis
· Advanced Windows Debugging (by Mario Hewardt & Daniel Pravat) http://technet.microsoft.com/en-us/default.aspx