WinDbg Analysis BSoD dump file combat

Today happens to have a system blue screen dump file, the next step to find out where the error.

1. Open the dump file with WinDbg, set the symbol path, and so on.

As shown

Has basically determined which driver is causing the problem.

2. Execute the ANALYZE-V command as shown in

This is where the problem is pointed out and the stack information is listed, indicating which line of code is problematic.

3. Confirm that you can use the KP command to view the input parameters of the function, and then use the dv/t/v command to view the local variables, confirming that the line pointer is empty caused by the problem.

WinDbg Analysis BSoD dump file combat