Debug the dump file in windbg

For windows programmers, the blue screen is the most depressing thing during program running. How to find the reason for the blue screen is the first thing to solve. Fortunately, Microsoft provides a series of methods, it provides convenience for us to debug the blue screen.

The first tool to use is windbg, which can be downloaded from Microsoft's official website.

Http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.402.msi

You need to download and install a symbolic link library, which is also available on the official website of Microsoft. This should be selected based on the version of your debugging system.

Http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx#d

You can also directly ask windbg to download the symbolic link information on the Internet without downloading the symbol library.

 

After the tool and software are ready, you can start setting up. First, go to "my computer"> "properties"> "advanced" and select the "Start and fault recovery" tab, in the "Write debugging information" column, select the dump file dump mode and fill in the SAVE path of the dump file in "dump File. When a blue screen appears, the system will save the field and save the running information during dump so that we can use windbg for analysis. Note that if you select a full memory dump, the system will save all the information in the memory to the file, which will be quite slow, so you can see that there is a beating number on the blue screen, that is, the progress of the storage, you must wait patiently for it to save to 100%.

 

When the blue screen occurs again, we have a dump file in our hand, which is usually in the windows directory. DMP, or in the miniDump folder under windows *. the dmp format is saved. Copy the. dmp file and use windbg for debugging.

First, you need to set up the windbg Symbol library, go to windbg's "File"-> "symbol File Path", and enter the installation directory of the downloaded Symbol library in the "symbol path" dialog box, enter SRV * c:/temp * http://msdl.microsoft.com/download/symbolshere to allow windbgto automatically download the signed information.

After completing the settings, you can start debugging. open "File"> "Open Crase Dump" and select. when the dmp file appears, windbg starts to download the symbol library and perform preliminary analysis.

**************************************** ***************************************
**
* Bugcheck Analysis *
**
**************************************** ***************************************

Use! Analyze-v to get detailed debugging information.

BugCheck 1000007F, {8, f772ffe0, 0, 0}

Probably caused by: bxnd52x. sys (bxnd52x + 365f)

Followup: MachineOwner
---------

You can enter

! Analyze-v; r; kv; lmtn;. logclose;

You can see the result after you press Enter.

 

Bugcheck_str: 0x7f_8

Customer_crash_count: 3

Default_bucket_id: driver_fault_server_minidump

Current_irql: 2

Last_control_transfer: From 00000000 to f759a65f

Stack_text:
F78dc000 00000000 00000000 00000000 00000000 bxnd52x + 0x365f

Stack_command: KB

Followup_ip:
Bxnd52x + 365f
F759a65f 53 push EBX

Symbol_stack_index: 0

Symbol_name: bxnd52x + 365f

Followup_name: machineowner

Module_name: bxnd52x

Image_name: bxnd52x. sys

Debug_flr_image_timestamp: 44a55446

Failure_bucket_id: 0x7f_8_bxnd52x + 365f

BUCKET_ID: 0x7f_8_bxnd52x + 365f

Followup: MachineOwner
---------

The blue screen may be due to bxnd52x. A problem with the sys driver, Baidu, this bxnd52x. sys is the NIC Driver. Download a later version of the driver and reinstall it. The blue screen problem is solved.