Bug Check Code Reference section contains descriptions of common bug check codes that are displayed on the blue bug check screen. This section also describes how you can use the !analyze extension in the Windows Debugger to display information about a bug check code.
Note
This topic is for programmers. If you are a customer whose system has displayed a blue screen with a bug check code, see Troubleshoot blue screen errors.
Using WinDbg to display stop code information
If a specific bug check code does not appear in this topic, use the !analyze extension in the Windows Debugger (WinDbg) with the following syntax (in kernel mode), replacing <code> with a bug check code:
!analyze -show <code>
Entering this command causes WinDbg to display information about the specified bug check code. If your default number base (radix) is not 16, prefix <code> with 0x.
Provide the stop code parameters to the !analyze command to display any available parameter information. For example, to display information on Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE, with a parameter 1 value of 0x3, use !analyze -show 0x9F 0x3 as shown here.
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 Download Debugging Tools for Windows. To learn more about the WinDbg development tools, see Getting Started with Windows Debugging.
Bug check dump files
When a bug check occurs, a dump file may be available that contains additional information about the contents of memory 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:
- Analyzing a Kernel-Mode Dump File with WinDbg
- !analyze
- Processor Architecture
Live Dumps
Live Dump stop codes to not reset the OS, but allow for the capture of memory information for abnormal situations where the operating system can continue. For information about live dumps, see Bug Check Code Reference – Live Dump