This Microsoft software will allow the reading of crash Dumps. Simplifying the issues with Blue-Screen driver/hardware exceptions, and providing the data necessary for resolution for the problem(s).
To use it Run the executable as "Admin", Click "file" and "open Crash Dump" navigate to the Windows\Minidump file (or other location)
Vista x64 systems:
http://www.microsoft.com/whdc/devtoo...tall64bit.mspx
Vista x86/XP:
Install Debugging Tools for Windows 32-bit Version
note- for futher info on overriding the default Install location and setting dump files for default handling by the debugger (advanced Users) see:
Crash Dumps - Analyse Bugcheck and Process
Any questions/advanced dump file analysis/troubleshooting/Install/default handling Issues should be directed to the Tutorial for proper resolution.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 1
Download the debugging tool for your system
Step 2
Override installation/or Install to default Location
Step 3
Create symbol cache folder
Step 4
Set the debuggging tool path for for the symbol cache
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Download the debugger package that matches YOUR machine's architecture In other words, if you're running 32-bit Vista, install the 32-bit version of the "Debugging Tools for Windows", irrespective of whether you intend to debug 32-bit or 64-bit code. Vice versa for x64 - download and install the x64 package, and you'll still be able to debug 32-bit dumps. I suspect that few people would be running Itaniums around here, so don't grab the IA-64 build. "IA-64" (Itanium) is a vastly different architecture to "x64" (AMD64, a.k.a. EM64T when sold by Intel). Override the default install path and install to 'c:\debuggers' instead Or Install into default Programs location This is entirely optional but you'll be happier, especially if you intend to do a fair amount of dump gazing. Choose the "custom" install option and use c:\debuggers (or d:\debuggers or whatever drive) as the install path. It makes it easier to work with the tools and removes that pesky "Program Files" space from the path name. The debugger package is a lot more command-line oriented than many apps nowadays. Set your symbol path (critical- and not optional) - Start WinDBG - WITHOUT opening any dump files, click File, "Symbol File Path..." - Set the path to be the following: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols note-this works if you set "c:\SymCache" as you local file path (creating the file), If for example, you use "c:\windows\symbols" the path would be: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols It can be any valid local path, c:\Symbols or e:\MySymbols or whatever, but the SRV and http bits must be exactly as above. Don't move the local path around too much though because the idea is to build up a local cache of symbols that minimises your waiting time while symbols are being downloaded from MS. That local cache can grow quite large over time, if you do a lot of this. - Exit WinDBG. It should ask you whether you wish to save workspace settings. "Yes" is the answer. - Check that from now onwards the symbol file path is always set that way whenever you start WinDBG. Opening and analysing dumps Once you've done the preparatory steps above, "File | Open Crash Dump..." in WinDBG to get it to open up and analyse a minidump or any other memory dump, including crashes from user-mode processes. If you want to re-invoke its automated analysis engine, use the !ANALYZE -V command. The "v" switch stands for "verbose" - it spews out a bit more detail. Your done!! [Thanks to H2S04 for the Walkthrough.]