This article describes common bug check codes displayed on the bug check screen. You can use the !analyze extension in the Windows Debugger (WinDbg) to display information about a bug check code.
The information in this article is intended for programmers. Depending on your scenario requirements, you might be interested in another article:
If you're a customer whose system is displaying a bug check code, see Resolving Blue Screen errors in Windows.
If you're an IT professional, you can find more information in Advanced troubleshooting for stop code errors.
For general information about bug check system halt errors, see Bug checks.
If you're looking for a specific bug check code that isn't described in this article, you can use the !analyze extension in WinDbg. This command causes WinDbg to display information about the specified bug check code.
Run the extention in kernel mode with the syntax !analyze -show <code>. Replace the <code> placeholder with the bug check code to analyze. If your default number base (radix) isn't 16, prefix the <code> value with 0x.
If you want to display any available parameter information, include the stop code parameters in the !analyze command. To display information on Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE for a parameter 1 value of 0x3, you use the command !analyze -show 0x9F 0x3. The following example demonstrates the syntax and output:
1: kd> !analyze -show 0x9F 0x3
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: 0000000000000000, Physical Device Object of the stack
Arg3: 0000000000000000, nt!_TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: 0000000000000000, The blocked IRP
To download WinDbg, see Debugging tools for Windows. To learn more about the WinDbg development tools, see Get started with Windows debugging.
Work with dump filesWhen a bug check occurs, a bug check dump file might be available. The file contains more information about the memory contents when the stop code occurred. To understand the contents of memory during a failure, knowledge of processor memory registers and assembly is required. For more information, see:
Live dump stop codes don't reset the operating system. They allow for the capture of memory information for abnormal situations where the operating system can continue. This article doesn't list the live dump stop codes. For more information, see Kernel live dump code reference.
Review bug check codesThe following table lists the bug check codes and provides links for more information about each code.
Related articlesRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4