First, use the blue screen problem WinDBG treatment, to ensure that the system has generated a memory dump file.
Confirmed the existence of a memory dump file
The default configuration of Windows 7, the resulting core dump file may be (Kernal Memory Dump) or a small memory dump file (Minidump). If the core dump file, the default will be saved as C: \ Windows \ Memory.dmp, if it is a small memory dump files, relevant documents will be saved in C: \ Windows \ MiniDump directory.
Therefore, a blue screen, please check the system has no C: \ Windows \ Memory.dmp this file, or C: \ Windows \ MiniDump directory file named by date. For example, Mini010810-01.dmp is January 8, 2010 the first small memory dump file.
If you do not have the memory dump file, please refer to the relevant documentation.
Install Windows Debugging Tool (WinDBG)
Next, we want to install Windbg the. WinDBG can download the Microsoft 32-bit address is: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
, 64-bit address is:
Note WinDBG only in English. You just find a place to both download and install the latest version of it. If you do not really understand English, you download directly to these two addresses: 32:
, 64 bit:
Next all the way to safety and then turn on it. An WinDBG transfer file size, probably around 15-30 trillion.
Configuring Windows Debugging Tool (WinDBG)
Analysis of the memory dump file by WinDBG, we want to configure what WinDBG.
First, choose a temporary directory stored Symbol files. For example, create a directory called C: \ Temp
Then, open WinDBG, in the File Menu - "choose Symbol File Path. In the Open dialog box, enter:
SRV * c: \ temp * http://msdl.microsoft.com/download/symbols
Select OK OK. WinDBG to configured.
With the Windows Debugging Tool (WinDBG) of memory dump file
In WinDBG which, in the File menu, select Open Crash Dump, and then find that in front of said core memory dump file or a small memory dump file, select Open. Wait a moment, if you need to download from the Microsoft Web site Symbole documents, the time may be rather long. If not a large number of Warning, it means setup is successful. If Your debugger is not using the correct symbols like the information on configuration issues, to carefully check the previous step.
Wait until there Use! Analyze-v to get detailed debugging information. Words and 0: kd> prompt.
Follow the prompts, enter! Analyze-v command. Wait for command to complete.
Analysis of Windows Debugging Tool (WinDBG) results