Bug Check Codes
A bug check is what the kernel raises when it cannot keep running safely: it stops the machine, writes a dump, and shows the code on the blue screen. The codes come from bugcodes.h, which lists them in numeric order and says nothing about what part of the system each one belongs to. They are grouped here by hand, so that reading down one subsystem is possible at all.
Codes tagged live dump are the exception to the halt: the system captures a dump of itself and carries on running.
- Kernel (106)
- Memory manager (36)
- Drivers (34)
- Driver Verifier (12)
- Storage and file systems (38)
- Graphics and window manager (37)
- Networking (22)
- Hardware and firmware (59)
- Power management (15)
- Security and integrity (19)
- Virtualization and secure kernel (5)
- Boot and startup (49)
- Failover clustering (12)
- Debugging and diagnostics (11)
- Windows Phone (36)
- Xbox (6)
- Other (1)
- Not stop codes (15)
Kernel
The core kernel: IRQL rules, locks, threads, processes, and traps.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000001 | APC_INDEX_MISMATCH | Learn about bug check 0x00000001, which indicates a mismatch in the APC state index. |
| 0x00000003 | INVALID_AFFINITY_SET | This bug check appears very infrequently. |
| 0x00000004 | INVALID_DATA_ACCESS_TRAP | This bug check appears very infrequently. |
| 0x00000005 | INVALID_PROCESS_ATTACH_ATTEMPT | The INVALID_PROCESS_ATTACH_ATTEMPT bug check has a value of 0x00000005. |
| 0x00000006 | INVALID_PROCESS_DETACH_ATTEMPT | This bug check appears very infrequently. |
| 0x00000007 | INVALID_SOFTWARE_INTERRUPT | This bug check appears very infrequently. |
| 0x00000008 | IRQL_NOT_DISPATCH_LEVEL | This bug check appears very infrequently. |
| 0x00000009 | IRQL_NOT_GREATER_OR_EQUAL | This bug check appears very infrequently. |
| 0x0000000a | IRQL_NOT_LESS_OR_EQUAL | The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. |
| 0x0000000b | NO_EXCEPTION_HANDLING_SUPPORT | This bug check appears very infrequently. |
| 0x0000000c | MAXIMUM_WAIT_OBJECTS_EXCEEDED | This indicates that the current thread exceeded the permitted number of wait objects. |
| 0x0000000d | MUTEX_LEVEL_NUMBER_VIOLATION | This bug check appears very infrequently. |
| 0x0000000e | NO_USER_MODE_CONTEXT | This bug check appears very infrequently. |
| 0x0000000f | SPIN_LOCK_ALREADY_OWNED | This indicates that a request for a spin lock has been initiated when the spin lock was already owned. |
| 0x00000010 | SPIN_LOCK_NOT_OWNED | This bug check appears very infrequently. |
| 0x00000011 | THREAD_NOT_MUTEX_OWNER | This bug check appears very infrequently. |
| 0x00000012 | TRAP_CAUSE_UNKNOWN | This indicates that an unknown exception has occurred. |
| 0x00000013 | EMPTY_THREAD_REAPER_LIST | This bug check is not currently used by Windows. |
| 0x00000014 | CREATE_DELETE_LOCK_NOT_LOCKED | This bug check appears very infrequently. |
| 0x00000015 | LAST_CHANCE_CALLED_FROM_KMODE | This bug check appears very infrequently. |
| 0x00000016 | CID_HANDLE_CREATION | This bug check appears very infrequently. |
| 0x00000017 | CID_HANDLE_DELETION | This bug check appears very infrequently. |
| 0x00000018 | REFERENCE_BY_POINTER | This indicates that the reference count of an object is illegal for the current state of the object. |
| 0x0000001d | NO_SPIN_LOCK_AVAILABLE | This bug check appears very infrequently. |
| 0x0000001e | KMODE_EXCEPTION_NOT_HANDLED | The 0x0000001E KMODE_EXCEPTION_NOT_HANDLED bug check indicates that a kernel-mode program generated an exception the error handler didn't catch. |
| 0x0000001f | SHARED_RESOURCE_CONV_ERROR | This bug check appears very infrequently. |
| 0x00000020 | KERNEL_APC_PENDING_DURING_EXIT | This indicates that an asynchronous procedure call (APC) was still pending when a thread exited. |
| 0x00000021 | QUOTA_UNDERFLOW | This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged. |
| 0x0000002b | PANIC_STACK_SWITCH | This indicates that the kernel mode stack was overrun. |
| 0x00000030 | SET_OF_INVALID_CONTEXT | This indicates that the stack pointer in a trap frame had an invalid value. |
| 0x00000039 | SYSTEM_EXIT_OWNED_MUTEX | This indicates that the worker routine returned without releasing the mutex object that it owned. |
| 0x0000003a | SYSTEM_UNWIND_PREVIOUS_USER | This bug check appears very infrequently. |
| 0x0000003b | SYSTEM_SERVICE_EXCEPTION | This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. |
| 0x0000003c | INTERRUPT_UNWIND_ATTEMPTED | This bug check appears very infrequently. |
| 0x0000003d | INTERRUPT_EXCEPTION_NOT_HANDLED | The INTERRUPT_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000003D. |
| 0x0000004a | IRQL_GT_ZERO_AT_SYSTEM_SERVICE | This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL. |
| 0x0000004c | FATAL_UNHANDLED_HARD_ERROR | This bug check appears very infrequently. |
| 0x00000051 | REGISTRY_ERROR | This indicates that a severe registry error has occurred. |
| 0x0000007e | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED | The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check indicates that a system thread generated an exception that the error handler didn't catch. |
| 0x0000007f | UNEXPECTED_KERNEL_MODE_TRAP | Learn about the UNEXPECTED_KERNEL_MODE_TRAP bug check, value 0x0000007F. It indicates that the Intel CPU generated a trap that the kernel failed to catch. |
| 0x00000081 | SPIN_LOCK_INIT_FAILURE | This bug check appears very infrequently. |
| 0x0000008e | KERNEL_MODE_EXCEPTION_NOT_HANDLED | This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch. |
| 0x00000093 | INVALID_KERNEL_HANDLE | This bug check indicates that an invalid or protected handle was passed to NtClose. |
| 0x00000094 | KERNEL_STACK_LOCKED_AT_EXIT | This bug check indicates that a thread exited while its kernel stack was marked as not swappable. |
| 0x00000096 | INVALID_WORK_QUEUE_ITEM | This bug check indicates that a queue entry was removed that contained a NULL pointer. |
| 0x00000097 | BOUND_IMAGE_UNSUPPORTED | This bug check appears very infrequently. |
| 0x0000009e | USER_MODE_HEALTH_MONITOR | This bug check indicates that one or more critical user-mode components failed to satisfy a health check. |
| 0x000000a7 | BAD_EXHANDLE | This bug check indicates that the kernel-mode handle table detected an inconsistent handle table entry state. |
| 0x000000b8 | ATTEMPTED_SWITCH_FROM_DPC | This indicates that an illegal operation was attempted by a deferred procedure call (DPC) routine. |
| 0x000000bf | MUTEX_ALREADY_OWNED | This indicates that a thread attempted to acquire ownership of a mutex it already owned. |
| 0x000000c7 | TIMER_OR_DPC_INVALID | This is issued if a kernel timer or deferred procedure call (DPC) is found somewhere in memory where it is not permitted. |
| 0x000000c8 | IRQL_UNEXPECTED_VALUE | This indicates that the processor's IRQL is not what it should be at this time. |
| 0x000000df | IMPERSONATING_WORKER_THREAD | This indicates that a workitem did not disable impersonation before it completed. |
| 0x000000e1 | WORKER_THREAD_RETURNED_AT_BAD_IRQL | This indicates that a worker thread completed and returned with IRQL DISPATCH_LEVEL. |
| 0x000000e3 | RESOURCE_NOT_OWNED | This indicates that a thread tried to release a resource it did not own. |
| 0x000000e4 | WORKER_INVALID | This typically indicates that memory that should not contain an executive work item does contain such an item. |
| 0x000000e9 | ACTIVE_EX_WORKER_THREAD_TERMINATION | This indicates that an active executive worker thread is being terminated. |
| 0x000000ef | CRITICAL_PROCESS_DIED | Learn how the CRITICAL_PROCESS_DIED bug check has a value of 0x000000EF and indicates that a critical system process died. |
| 0x000000f4 | CRITICAL_OBJECT_TERMINATION | This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. |
| 0x000000ff | RESERVE_QUEUE_OVERFLOW | This indicates that an attempt was made to insert a new item into a reserve queue, causing the queue to overflow. |
| 0x00000102 | DPC_WATCHDOG_TIMEOUT | This indicates that The DPC watchdog routine was not executed within the allocated time interval. |
| 0x00000107 | KERNEL_EXPAND_STACK_ACTIVE | |
| 0x0000010f | RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED | The RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000010F. |
| 0x0000011c | ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE | The ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE bug check has a value of 0x0000011C that indicates that a write was attempted to the protected storage of the configuration manager. |
| 0x0000011e | TOO_MANY_RECURSIVE_FAULTS | This indicates that a file system has caused too many recursive faults under low resource conditions to be handled. |
| 0x00000128 | WORKER_THREAD_RETURNED_WITH_BAD_IO_PRIORITY | This indicates that a worker threads IOPriority was wrongly modified by the called worker routine. |
| 0x00000129 | WORKER_THREAD_RETURNED_WITH_BAD_PAGING_IO_PRIORITY | The WORKER_THREAD_RETURNED_WITH_BAD_PAGING_IO_PRIORITY bug check has a value of 0x00000129 that indicates that a worker threads Paging IOPriority was wrongly modified. |
| 0x00000132 | RESOURCE_OWNER_POINTER_INVALID | This indicates that an invalid resource owner pointer was supplied. |
| 0x00000133 | DPC_WATCHDOG_VIOLATION | The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. |
| 0x00000135 | REGISTRY_FILTER_DRIVER_EXCEPTION | This bugcheck is caused by an unhandled exception in a registry filtering driver. |
| 0x0000013c | INVALID_IO_BOOST_STATE | This indicates that a thread exited with an invalid I/O boost state. This should be zero when a thread exits. |
| 0x0000014a | KERNEL_WMI_INTERNAL | This indicates that the internal kernel WMI subsystem has encountered a fatal error. |
| 0x0000014d | EXCEPTION_SCOPE_INVALID | This indicates that an internal inconsistency in exception dispatching has been detected. |
| 0x00000152 | INVALID_PUSH_LOCK_FLAGS | This indicates that the flags supplied to one of push lock APIs were invalid. |
| 0x00000153 | KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION | This indicates that a thread was terminated before it had freed all its AutoBoost lock entries. |
| 0x00000157 | KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION | This indicates that an illegal operation was attempted on the priority floor of a particular thread. |
| 0x0000015b | WORKER_THREAD_RETURNED_WITH_SYSTEM_PAGE_PRIORITY_ACTIVE | The WORKER_THREAD_RETURNED_WITH_SYSTEM_PAGE_PRIORITY_ACTIVE bug check has a value of 0x0000015B that indicates a worker thread's system page priority was leaked. |
| 0x00000162 | KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE | This indicates that a lock tracked by AutoBoost was released by a thread that did not own the lock. |
| 0x00000163 | WORKER_THREAD_TEST_CONDITION | This indicates that a test for kernel worker threads raised a failure. |
| 0x0000016c | INVALID_RUNDOWN_PROTECTION_FLAGS | This indicates that the flags supplied to one of the rundown protection APIs were invalid. |
| 0x0000016d | INVALID_SLOT_ALLOCATOR_FLAGS | This indicates that the flags supplied to one of the slot allocator APIs were invalid. |
| 0x0000016e | ERESOURCE_INVALID_RELEASE | This indicates that the target thread pointer supplied to ExReleaseResourceForThreadLite was invalid. |
| 0x00000189 | BAD_OBJECT_HEADER | This indicates that The OBJECT_HEADER has been corrupted. |
| 0x0000018a | SILO_CORRUPT | |
| 0x0000018e | KERNEL_PARTITION_REFERENCE_VIOLATION | The KERNEL_PARTITION_REFERENCE_VIOLATION bug check has a value of 0x0000018E. |
| 0x00000192 | KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL | The KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL bug check indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above. |
| 0x00000199 | KERNEL_STORAGE_SLOT_IN_USE | This indicates that the storage slot cannot be freed because there is an object using it. |
| 0x0000019a | WORKER_THREAD_RETURNED_WHILE_ATTACHED_TO_SILO | This indicates that a worker thread attached to a silo and did not detach before returning. |
| 0x000001a3 | CALL_HAS_NOT_RETURNED_WATCHDOG_TIMEOUT_LIVEDUMP live dump | The CALL_HAS_NOT_RETURNED_WATCHDOG_TIMEOUT_LIVEDUMP live dump has a value of 0x000001A3. |
| 0x000001aa | EXCEPTION_ON_INVALID_STACK | It indicates a memory access outside of the valid stack range occurred. |
| 0x000001ab | UNWIND_ON_INVALID_STACK | It indicates that a memory access outside of the valid stack range occurred during a memory unwind operation. |
| 0x000001c5 | IO_THREADPOOL_DEADLOCK_LIVEDUMP live dump | This indicates a kernel mode threadpool encountered a deadlock situation. |
| 0x000001c6 | FAST_ERESOURCE_PRECONDITION_VIOLATION | It indicates that the current thread is performing an invalid call to a fast resource routine. |
| 0x000001c9 | USER_MODE_HEALTH_MONITOR_LIVEDUMP live dump | It indicates that one or more critical user mode components failed to satisfy a health check. |
| 0x000001ca | SYNTHETIC_WATCHDOG_TIMEOUT | A system wide watchdog has expired. This indicates that the system is hung and not processing timer ticks. |
| 0x000001cb | INVALID_SILO_DETACH | It indicates that a thread failed to detach from a silo before exiting. |
| 0x000001cc | EXRESOURCE_TIMEOUT_LIVEDUMP live dump | The EXRESOURCE_TIMEOUT_LIVEDUMP live dump has a value of 0x000001CC. |
| 0x000001cd | INVALID_CALLBACK_STACK_ADDRESS | The INVALID_CALLBACK_STACK_ADDRESS bug check has a value of 0x000001CD. |
| 0x000001ce | INVALID_KERNEL_STACK_ADDRESS | The INVALID_KERNEL_STACK_ADDRESS bug check has a value of 0x000001CE. |
| 0x000001d2 | WORKER_THREAD_INVALID_STATE | The WORKER_THREAD_INVALID_STATE bug check has a value of 0x000001D2. |
| 0x000001d6 | WORKER_THREAD_RETURNED_WITH_NON_DEFAULT_WORKLOAD_CLASS | It indicates that a worker thread changed its workload class and did not revert it before returning. |
| 0x000001ed | HANDLE_ERROR_ON_CRITICAL_THREAD | This indicates that an invalid handle access problem was detected in kernel mode on a system-critical thread. |
| 0x1000007e | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M | The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M bug check has a value of 0x1000007E. |
| 0x1000007f | UNEXPECTED_KERNEL_MODE_TRAP_M | The UNEXPECTED_KERNEL_MODE_TRAP_M bug check has a value of 0x1000007F. |
| 0x1000008e | KERNEL_MODE_EXCEPTION_NOT_HANDLED_M | The KERNEL_MODE_EXCEPTION_NOT_HANDLED_M bug check has a value of 0x1000008E. |
| 0x4000008a | THREAD_TERMINATE_HELD_MUTEX | The THREAD_TERMINATE_HELD_MUTEX bug check has a value of 0x4000008A. |
| 106 entries | ||
Memory manager
Paging, pool, page table entries, and the page frame database.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000019 | BAD_POOL_HEADER | This indicates that a pool header is corrupt. |
| 0x0000001a | MEMORY_MANAGEMENT | The MEMORY_MANAGEMENT bug check has a value of 0x0000001A and indicates that a severe memory management error occurred. |
| 0x0000001b | PFN_SHARE_COUNT | It indicates that a memory management page frame number (PFN) database element has a corrupted share count. |
| 0x0000001c | PFN_REFERENCE_COUNT | The PFN_REFERENCE_COUNT bug check has a value of 0x0000001C. |
| 0x0000003f | NO_MORE_SYSTEM_PTES | This is the result of a system which has performed too many I/O actions. |
| 0x00000040 | TARGET_MDL_TOO_SMALL | This indicates that a driver has improperly used IoBuildPartialMdl. |
| 0x00000041 | MUST_SUCCEED_POOL_EMPTY | This indicates that a kernel-mode thread has requested too much must-succeed pool. |
| 0x00000049 | PAGE_FAULT_WITH_INTERRUPTS_OFF | This bug check appears very infrequently. |
| 0x0000004d | NO_PAGES_AVAILABLE | This indicates that no free pages are available to continue operations. |
| 0x0000004e | PFN_LIST_CORRUPT | This indicates that the page frame number (PFN) list is corrupted. |
| 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA | This indicates that invalid system memory has been referenced. |
| 0x00000076 | PROCESS_HAS_LOCKED_PAGES | This bug check indicates that a driver failed to release locked pages after an I/O operation. |
| 0x00000077 | KERNEL_STACK_INPAGE_ERROR | This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. |
| 0x0000007a | KERNEL_DATA_INPAGE_ERROR | Learn about bug check 0x7A KERNEL_DATA_INPAGE_ERROR, which indicates that the requested page of kernel data from the paging file couldn't be read into memory. |
| 0x0000007d | INSTALL_MORE_MEMORY | This bug check indicates that there is not enough memory to start up the Microsoft Windows operating system. |
| 0x00000099 | INVALID_REGION_OR_SEGMENT | This bug check indicates that ExInitializeRegion or ExInterlockedExtendRegion was called with an invalid set of parameters. |
| 0x000000a2 | MEMORY_IMAGE_CORRUPT | This bug check indicates that corruption has been detected in the image of an executable file in memory. |
| 0x000000ab | SESSION_HAS_VALID_POOL_ON_EXIT | This bug check indicates that a session unload occurred while a session driver still held memory. |
| 0x000000ba | SESSION_HAS_VALID_VIEWS_ON_EXIT | This indicates that a session driver still had mapped views when the session unloaded. |
| 0x000000be | ATTEMPTED_WRITE_TO_READONLY_MEMORY | This is issued if a driver attempts to write to a read-only memory segment. |
| 0x000000c2 | BAD_POOL_CALLER | This indicates that the current thread is making a bad pool request. |
| 0x000000cc | PAGE_FAULT_IN_FREED_SPECIAL_POOL | This indicates that the system has referenced memory which was earlier freed. |
| 0x000000cd | PAGE_FAULT_BEYOND_END_OF_ALLOCATION | This indicates that the system accessed memory beyond the end of some driver's pool allocation. |
| 0x000000d9 | LOCKED_PAGES_TRACKER_CORRUPTION | This indicates that the internal locked-page tracking structures have been corrupted. |
| 0x000000da | SYSTEM_PTE_MISUSE | This indicates that a page table entry (PTE) routine has been used in an improper way. |
| 0x000000de | POOL_CORRUPTION_IN_FILE_AREA | This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk. |
| 0x000000eb | DIRTY_MAPPED_PAGES_CONGESTION | This indicates that no free pages are available to continue operations. |
| 0x000000ec | SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT | This indicates that a session unload occurred while a session driver still held memory. |
| 0x000000fc | ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY | This indicates that an attempt was made to execute non-executable memory. |
| 0x000000fd | DIRTY_NOWRITE_PAGES_CONGESTION | This indicates that there are no free pages available to continue basic system operations. |
| 0x00000127 | PAGE_NOT_ZERO | The PAGE_NOT_ZERO bug check has a value of 0x00000127. |
| 0x0000012e | INVALID_MDL_RANGE | The INVALID_MDL_RANGE bug check has a value of 0x0000012E. |
| 0x0000013a | KERNEL_MODE_HEAP_CORRUPTION | Learn how the KERNEL_MODE_HEAP_CORRUPTION bug check indicates that the kernel mode heap manager has detected corruption in a heap. |
| 0x00000154 | UNEXPECTED_STORE_EXCEPTION | Learn about the UNEXPECTED_STORE_EXCEPTION bug check, which indicates that the kernel memory store component caught an unexpected exception. |
| 0x00000191 | PF_DETECTED_CORRUPTION | The PF_DETECTED_CORRUPTION bug check has a value of 0x00000191. |
| 0x000001c7 | STORE_DATA_STRUCTURE_CORRUPTION | It indicates that the store component detected a corruption in its data structures. |
| 36 entries | ||
Drivers
Driver misbehaviour the kernel caught, across IRPs, PnP, and the device stack.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000002 | DEVICE_QUEUE_NOT_BUSY | The DEVICE_QUEUE_NOT_BUSY bug check has a value of 0x00000002. |
| 0x0000002a | INCONSISTENT_IRP | This indicates that an IRP was found to contain inconsistent information. |
| 0x00000035 | NO_MORE_IRP_STACK_LOCATIONS | This bug check occurs when the IoCallDriver packet has no more stack locations remaining. |
| 0x00000036 | DEVICE_REFERENCE_COUNT_NOT_ZERO | This indicates that a driver attempted to delete a device object that still had a positive reference count. |
| 0x00000044 | MULTIPLE_IRP_COMPLETE_REQUESTS | This indicates that a driver has tried to request an IRP be completed that is already complete. |
| 0x00000045 | INSUFFICIENT_SYSTEM_MAP_REGS | This bug check appears very infrequently. |
| 0x00000048 | CANCEL_STATE_IN_COMPLETED_IRP | This indicates that an I/O request packet (IRP) was completed, and then was subsequently canceled. |
| 0x00000092 | UP_DRIVER_ON_MP_SYSTEM | This bug check indicates that a uniprocessor-only driver has been loaded on a multiprocessor system. |
| 0x00000095 | PNP_INTERNAL_ERROR | |
| 0x000000c5 | DRIVER_CORRUPTED_EXPOOL | This indicates that the system attempted to access invalid memory at a process IRQL that was too high. |
| 0x000000ca | PNP_DETECTED_FATAL_ERROR | This indicates that the Plug and Play Manager encountered a severe error. |
| 0x000000cb | DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS | This indicates that a driver or the I/O manager failed to release locked pages after an I/O operation. |
| 0x000000ce | DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS | This indicates that a driver failed to cancel pending operations before unloading. |
| 0x000000d0 | DRIVER_CORRUPTED_MMPOOL | This indicates that the system attempted to access invalid memory at a process IRQL that was too high. |
| 0x000000d1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL | This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. |
| 0x000000d2 | BUGCODE_ID_DRIVER | This indicates that a problem occurred with an NDIS driver. |
| 0x000000d3 | DRIVER_PORTION_MUST_BE_NONPAGED | This indicates that the system attempted to access pageable memory at a process IRQL that was too high. |
| 0x000000d4 | SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD | This indicates that a driver did not cancel pending operations before unloading. |
| 0x000000d7 | DRIVER_UNMAPPING_INVALID_VIEW | This indicates a driver is trying to unmap an address that was not mapped. |
| 0x000000d8 | DRIVER_USED_EXCESSIVE_PTES | This indicates that there are no more system page table entries (PTE) remaining. |
| 0x000000db | DRIVER_CORRUPTED_SYSPTES | This indicates that an attempt was made to touch memory at an invalid IRQL, probably due to corruption of system PTEs. |
| 0x000000dc | DRIVER_INVALID_STACK_ACCESS | This indicates that a driver accessed a stack address that lies below the stack pointer of the stack's thread. |
| 0x000000e8 | INVALID_CANCEL_OF_FILE_OPEN | This indicates that an invalid file object was passed to IoCancelFileOpen. |
| 0x000000f7 | DRIVER_OVERRAN_STACK_BUFFER | This indicates that a driver has overrun a stack-based buffer. |
| 0x0000010d | WDF_VIOLATION | This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver. |
| 0x00000110 | DRIVER_INVALID_CRUNTIME_PARAMETER | |
| 0x0000011b | DRIVER_RETURNED_HOLDING_CANCEL_LOCK | The DRIVER_RETURNED_HOLDING_CANCEL_LOCK bug check has a value of 0x0000011B. |
| 0x0000011f | INVALID_DRIVER_HANDLE | This indicates that someone has closed the initial handle for a driver between inserting the driver object and referencing the handle. |
| 0x00000121 | DRIVER_VIOLATION | This bug check indicates that a driver has caused a violation. |
| 0x0000013b | PASSIVE_INTERRUPT_ERROR | This indicates that the kernel has detected issues with the passive-level interrupt. |
| 0x00000148 | IO_OBJECT_INVALID | |
| 0x000001d5 | DRIVER_PNP_WATCHDOG | A system wide watchdog has expired. This indicates that driver has failed to complete a PnP operation within a specific time. |
| 0x000001dc | DMA_COMMON_BUFFER_VECTOR_ERROR | It indicates that driver has misused the DMA vectored common buffer APIs. |
| 0x000001e1 | DEVICE_DIAGNOSTIC_LOG_LIVEDUMP live dump | The DEVICE_DIAGNOSTIC_LOG_LIVEDUMP has a value of 0x000001E1 that indicates that a device has encountered an error and generated diagnostic data. |
| 34 entries | ||
Driver Verifier
Violations only Driver Verifier or special pool is watching for.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x000000c1 | SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION | This indicates that the driver wrote to an invalid section of the special pool. |
| 0x000000c4 | DRIVER_VERIFIER_DETECTED_VIOLATION | This is the general bug check code for fatal errors found by Driver Verifier. |
| 0x000000c6 | DRIVER_CAUGHT_MODIFYING_FREED_POOL | This indicates that the driver attempted to access a freed memory pool. |
| 0x000000c9 | DRIVER_VERIFIER_IOMANAGER_VIOLATION | This is the bug check code for all Driver Verifier I/O Verification violations. |
| 0x000000d5 | DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL | This indicates that a driver has referenced memory which was earlier freed. |
| 0x000000d6 | DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION | This indicates the driver accessed memory beyond the end of its pool allocation. |
| 0x000000e6 | DRIVER_VERIFIER_DMA_VIOLATION | This is the bug check code for all Driver Verifier DMA Verification violations. |
| 0x000000f1 | SCSI_VERIFIER_DETECTED_VIOLATION | This is the bug check code for all Driver Verifier SCSI Verification violations. |
| 0x000000f6 | PCI_VERIFIER_DETECTED_VIOLATION | This indicates that an error occurred in the BIOS or another device being verified by the PCI driver. |
| 0x000001c4 | DRIVER_VERIFIER_DETECTED_VIOLATION_LIVEDUMP live dump | The DRIVER_VERIFIER_DETECTED_VIOLATION_LIVEDUMP live dump has a value of 0x000001C4. |
| 0x00000bfe | BC_BLUETOOTH_VERIFIER_FAULT | This indicates that a driver has caused a violation. |
| 0x00000bff | BC_BTHMINI_VERIFIER_FAULT | This indicates that The Bluetooth miniport extensible driver verifier has caught a violation. |
| 12 entries | ||
Storage and file systems
File system drivers, volumes, disks, and the storage stack under them.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000022 | FILE_SYSTEM | This bug check appears very infrequently. |
| 0x00000023 | FAT_FILE_SYSTEM | This indicates that a problem occurred in the FAT file system. |
| 0x00000024 | NTFS_FILE_SYSTEM | This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives. |
| 0x00000025 | NPFS_FILE_SYSTEM | This indicates that a problem occurred in the NPFS file system. |
| 0x00000026 | CDFS_FILE_SYSTEM | This indicates that a problem occurred in the CD file system. |
| 0x0000002c | PORT_DRIVER_INTERNAL | This bug check appears very infrequently. |
| 0x0000002d | SCSI_DISK_DRIVER_INTERNAL | This bug check appears very infrequently. |
| 0x00000034 | CACHE_MANAGER | This indicates that a problem occurred in the file system's cache manager. |
| 0x00000037 | FLOPPY_INTERNAL_ERROR | This bug check appears very infrequently. |
| 0x00000042 | ATDISK_DRIVER_INTERNAL | This bug check appears very infrequently. |
| 0x00000052 | MAILSLOT_FILE_SYSTEM | This bug check appears very infrequently. |
| 0x00000058 | FTDISK_INTERNAL_ERROR | This is issued if the system is booted from the wrong copy of a mirrored partition. |
| 0x00000058 | VOLMGRX_INTERNAL_ERROR | |
| 0x00000059 | PINBALL_FILE_SYSTEM | This indicates that a problem occurred in the Pinball file system. |
| 0x00000072 | ASSIGN_DRIVE_LETTERS_FAILED | This bug check appears very infrequently. |
| 0x00000082 | DFS_FILE_SYSTEM | This bug check appears very infrequently. |
| 0x00000083 | OFS_FILE_SYSTEM | |
| 0x0000009b | UDFS_FILE_SYSTEM | This bug check indicates that a problem occurred in the UDF file system. |
| 0x000000a4 | CNSS_FILE_SYSTEM_FILTER | This bug check indicates that a problem occurred in the CNSS file system filter. |
| 0x000000f0 | STORAGE_MINIPORT_ERROR | It indicates that a storage Miniport driver failed to complete a SRB request. |
| 0x000000f5 | FLTMGR_FILE_SYSTEM | This indicates that an unrecoverable failure occurred in the Filter Manager. |
| 0x000000f9 | DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN | The DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN bug check that indicates that a driver returned STATUS_REPARSE to an IRP_MJ_CREATE request with no trailing names. |
| 0x00000103 | MUP_FILE_SYSTEM | The MUP_FILE_SYSTEM bug check has a value of 0x00000103. |
| 0x00000108 | THIRD_PARTY_FILE_SYSTEM_FAILURE | This indicates that an unrecoverable problem has occurred in a third-party file system or file system filter. |
| 0x0000010b | DFSC_FILE_SYSTEM | |
| 0x0000010c | FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION | The FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION bug check has a value of 0x0000010C that indicates that a violation was detected in the FsRtl ECP package. |
| 0x0000012c | EXFAT_FILE_SYSTEM | This bug check indicates that a problem occurred in the Extended File Allocation Table (exFAT) file system. |
| 0x0000012d | VOLSNAP_OVERLAPPED_TABLE_ACCESS | The VOLSNAP_OVERLAPPED_TABLE_ACCESS bug check has a value of 0x0000012D that indicates that volsnap tried to access a common table from two different threads. |
| 0x00000134 | DRIVE_EXTENDER | This indicates that the drive extender component has experienced a severe internal error that prevents continued system operation. |
| 0x00000140 | STORAGE_DEVICE_ABNORMALITY_DETECTED | The STORAGE_DEVICE_ABNORMALITY_DETECTED bug check has a value of 0x00000140 that indicates that the storage driver stack encountered a failure to respond. |
| 0x00000149 | REFS_FILE_SYSTEM | This indicates that a file system error has occurred. |
| 0x00000180 | WVR_LIVEDUMP_REPLICATION_IOCONTEXT_TIMEOUT live dump | |
| 0x00000181 | WVR_LIVEDUMP_STATE_TRANSITION_TIMEOUT live dump | |
| 0x00000182 | WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT live dump | |
| 0x00000183 | WVR_LIVEDUMP_APP_IO_TIMEOUT live dump | |
| 0x00000184 | WVR_LIVEDUMP_MANUALLY_INITIATED live dump | |
| 0x00000185 | WVR_LIVEDUMP_STATE_FAILURE live dump | |
| 0x00000186 | WVR_LIVEDUMP_CRITICAL_ERROR live dump | |
| 38 entries | ||
Graphics and window manager
Display drivers, the DirectX kernel, and win32k.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000091 | WIN32K_INIT_OR_RIT_FAILURE | |
| 0x000000b1 | BGI_DETECTED_VIOLATION | The BGI_DETECTED_VIOLATION bug check has a value of 0x000000B1. |
| 0x000000b4 | VIDEO_DRIVER_INIT_FAILURE | This indicates that Windows was unable to enter graphics mode. |
| 0x000000cf | TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE | This indicates that a driver has been incorrectly ported to the terminal server. |
| 0x000000ea | THREAD_STUCK_IN_DEVICE_DRIVER | This indicates that a thread in a device driver is endlessly spinning. |
| 0x00000104 | AGP_INVALID_ACCESS | This indicates that the GPU wrote to a range of Accelerated Graphics Port (AGP) memory that had not previously been committed. |
| 0x00000105 | AGP_GART_CORRUPTION | This indicates that the Graphics Aperture Remapping Table (GART) is corrupt. |
| 0x00000106 | AGP_ILLEGALLY_REPROGRAMMED | This indicates that the Accelerated Graphics Port (AGP) hardware has been reprogrammed by an unauthorized agent. |
| 0x0000010e | VIDEO_MEMORY_MANAGEMENT_INTERNAL | This indicates that the video memory manager has encountered a condition that it is unable to recover from. |
| 0x00000113 | VIDEO_DXGKRNL_FATAL_ERROR | The VIDEO_DXGKRNL_FATAL_ERROR bug check has a value of 0x00000113 that indicates that the Microsoft DirectX graphics kernel subsystem has detected a violation. |
| 0x00000114 | VIDEO_SHADOW_DRIVER_FATAL_ERROR | This indicates that the shadow driver has detected a violation.This bug check appears very infrequently. |
| 0x00000115 | AGP_INTERNAL | This indicates that the accelerated graphics port (AGP) driver has detected a violation.This bug check appears very infrequently. |
| 0x00000116 | VIDEO_TDR_FAILURE | This value indicates that an attempt to reset the display driver and recover from a timeout failed. |
| 0x00000117 | VIDEO_TDR_TIMEOUT_DETECTED | This indicates that the display driver failed to respond in a timely fashion. |
| 0x00000119 | VIDEO_SCHEDULER_INTERNAL_ERROR | This indicates that the video scheduler has detected a fatal violation. |
| 0x00000137 | WIN32K_HANDLE_MANAGER | This indicates that the win32k/ntuser handle manager has detected a fatal error. |
| 0x00000141 | VIDEO_ENGINE_TIMEOUT_DETECTED | This indicates that one of the display engines failed to respond in timely fashion. |
| 0x00000142 | VIDEO_TDR_APPLICATION_BLOCKED | This indicates that an application has been blocked from accessing graphics hardware. |
| 0x00000160 | WIN32K_ATOMIC_CHECK_FAILURE | This indicates that a Win32k function has violated an ATOMICCHECK. |
| 0x00000164 | WIN32K_CRITICAL_FAILURE | This indicates that Win32k has encountered a critical failure. |
| 0x00000173 | COREMSGCALL_INTERNAL_ERROR | This indicates that the CoreMessageCall detected an unrecoverable error. |
| 0x00000174 | COREMSG_INTERNAL_ERROR | It indicates that CoreMessaging detected an unrecoverable error. |
| 0x00000187 | VIDEO_DWMINIT_TIMEOUT_FALLBACK_BDD | This indicates that video fell back to BDD rather than using the IHV driver. This always generates a live dump. |
| 0x00000190 | WIN32K_CRITICAL_FAILURE_LIVEDUMP live dump | This indicates that Win32k has encountered a critical failure. A live dump is captured to collect the debug information. |
| 0x00000193 | VIDEO_DXGKRNL_LIVEDUMP live dump | This indicates a livedump triggered by dxgkrnl occurred. |
| 0x00000197 | WIN32K_SECURITY_FAILURE | This indicates a security failure was detected in win32k. |
| 0x0000019b | TTM_FATAL_ERROR | This indicates that the terminal topology manager experienced a fatal error. |
| 0x0000019c | WIN32K_POWER_WATCHDOG_TIMEOUT | This indicates that Win32k did not turn the monitor on in a timely manner. |
| 0x000001a0 | TTM_WATCHDOG_TIMEOUT | It indicates that the terminal topology manager detected that for the configured timeouts some device specific operations did not complete. |
| 0x000001a1 | WIN32K_CALLOUT_WATCHDOG_LIVEDUMP live dump | The WIN32K_CALLOUT_WATCHDOG_LIVEDUMP has a value of 0x000001A1. |
| 0x000001a2 | WIN32K_CALLOUT_WATCHDOG_BUGCHECK | The WIN32K_CALLOUT_WATCHDOG_BUGCHECK live dump has a value of 0x000001A2. |
| 0x000001a8 | VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP live dump | It indicates that a user initiated DXGKRNL live dump for black screen scenarios has occurred. |
| 0x000001b0 | VIDEO_MINIPORT_FAILED_LIVEDUMP live dump | It indicates that the DXGKRNL detected a problem with a video miniport driver and has captured a live dump to collect debug information. |
| 0x000001b8 | VIDEO_MINIPORT_BLACK_SCREEN_LIVEDUMP live dump | It indicates that a user initiated MINIPORT live dump for black screen scenarios has occurred. |
| 0x000001e4 | VIDEO_DXGKRNL_SYSMM_FATAL_ERROR | The VIDEO_DXGKRNL_SYSMM_FATAL_ERROR bug check has a value of 0x000001E4 that indicates that the Microsoft DirectX graphics kernel system memory manager has detected a violation. |
| 0x100000ea | THREAD_STUCK_IN_DEVICE_DRIVER_M | This indicates that a device driver thread is endlessly spinning.This has the same meaning/parameters as bug check 0xEA. |
| 0x400000ad | VIDEO_DRIVER_DEBUG_REPORT_REQUEST | This bug check indicates that the video port created a non-fatal minidump on behalf of the video driver during run time. |
| 37 entries | ||
Networking
NDIS and the protocol stack, plus the file sharing that rides on it.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000027 | RDR_FILE_SYSTEM | This indicates that a problem occurred in the SMB redirector file system. |
| 0x0000004b | STREAMS_INTERNAL_ERROR | This bug check appears very infrequently. |
| 0x0000004f | NDIS_INTERNAL_ERROR | This bug check appears very infrequently. |
| 0x00000054 | LM_SERVER_INTERNAL_ERROR | This bug check appears very infrequently. |
| 0x00000057 | XNS_INTERNAL_ERROR | This bug check appears very infrequently. |
| 0x0000007c | BUGCODE_NDIS_DRIVER | This bug check indicates that the operating system detected an error in a networking driver. |
| 0x000000bb | NETWORK_BOOT_INITIALIZATION_FAILED | This indicates that Windows failed to successfully boot off a network. |
| 0x000000bc | NETWORK_BOOT_DUPLICATE_ADDRESS | This indicates that a duplicate IP address was assigned to this machine while booting off a network. |
| 0x000000fa | HTTP_DRIVER_CORRUPTED | This indicates that the HTTP kernel driver (Http.sys) has reached a corrupted state and cannot recover. |
| 0x00000112 | MSRPC_STATE_VIOLATION | This indicates that the Msrpc.sys driver has initiated a bug check. |
| 0x00000125 | NMR_INVALID_STATE | This indicates that NMR (network module registrar) has detected an invalid state. See parameter 1 for the state type. |
| 0x00000126 | NETIO_INVALID_POOL_CALLER | This indicates that an invalid pool request has been made to netio managed memory pool, e.g. FSB and MDL. |
| 0x00000146 | NDIS_NET_BUFFER_LIST_INFO_ILLEGALLY_TRANSFERRED | |
| 0x00000150 | TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK | This indicates that the NIC active reference should have been released when the send queue was fully drained. |
| 0x00000156 | WINSOCK_DETECTED_HUNG_CLOSESOCKET_LIVEDUMP live dump | This indicates that Winsock detected a hung transport endpoint close request. |
| 0x0000015e | BUGCODE_NDIS_DRIVER_LIVE_DUMP live dump | This bug code indicates that NDIS has captured a live kernel dump. NDIS does not generate a bug check in this situation. |
| 0x00000195 | SMB_SERVER_LIVEDUMP live dump | This indicates the SMB server detected a problem and has captured a kernel dump to collect debug information. |
| 0x0000019e | BUGCODE_NETADAPTER_DRIVER | |
| 0x000001a7 | SMB_REDIRECTOR_LIVEDUMP live dump | It indicates that the SMB redirector has detected a problem and has captured a kernel dump to collect debug information. |
| 0x000001d3 | WFP_INVALID_OPERATION | The WFP_INVALID_OPERATION bug check has a value of 0x000001D3. |
| 0x000001dd | BUGCODE_MBBADAPTER_DRIVER | This indicates that the operating system encountered an error caused by a networking driver managed by MbbAdapterCx. |
| 0x000001de | BUGCODE_WIFIADAPTER_DRIVER | This indicates that the operating system encountered an error caused by a networking driver managed by WiFiAdapterCx. |
| 22 entries | ||
Hardware and firmware
Machine checks, ACPI, the HAL, processors, and the buses in between.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x0000002e | DATA_BUS_ERROR | This typically indicates that a parity error in system memory has been detected. |
| 0x0000002f | INSTRUCTION_BUS_ERROR | This bug check appears very infrequently. |
| 0x00000038 | SERIAL_DRIVER_INTERNAL | This bug check appears very infrequently. |
| 0x0000003e | MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED | This indicates that the system has multiple processors, but they are asymmetric in relation to one another. |
| 0x00000055 | DATA_COHERENCY_EXCEPTION | This bug check appears very infrequently. |
| 0x00000056 | INSTRUCTION_COHERENCY_EXCEPTION | This bug check appears very infrequently. |
| 0x0000005c | HAL_INITIALIZATION_FAILED | This indicates that the HAL initialization failed. |
| 0x0000005d | UNSUPPORTED_PROCESSOR | This indicates that the computer is attempting to run Windows on an unsupported processor. |
| 0x00000061 | HAL1_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000079 | MISMATCHED_HAL | The MISMATCHED_HAL bug check has a value of 0x00000079 that indicates that the HAL revision level or configuration does not match that of the kernel or the computer. |
| 0x00000080 | NMI_HARDWARE_FAILURE | This bug check indicates that a hardware malfunction has occurred. |
| 0x0000009c | MACHINE_CHECK_EXCEPTION | This bug check indicates that a fatal machine check exception has occurred. |
| 0x000000a1 | PCI_BUS_DRIVER_INTERNAL | This bug check indicates that the PCI Bus driver detected inconsistency problems in its internal structures and could not continue. |
| 0x000000a3 | ACPI_DRIVER_INTERNAL | This bug check indicates that the ACPI driver detected an internal inconsistency. |
| 0x000000a5 | ACPI_BIOS_ERROR | The ACPI_BIOS_ERROR bug check has a value of 0x000000A5 that indicates that the ACPI BIOS of the computer is not fully compliant with the ACPI specification. |
| 0x000000a6 | FP_EMULATION_ERROR | |
| 0x000000ac | HAL_MEMORY_ALLOCATION | This bug check indicates that the hardware abstraction layer (HAL) could not obtain sufficient memory. |
| 0x000000b9 | CHIPSET_DETECTED_ERROR | This bug check appears very infrequently. |
| 0x000000c0 | PCI_CONFIG_SPACE_ACCESS_FAILURE | |
| 0x000000e0 | ACPI_BIOS_FATAL_ERROR | This indicates that one of your computer components is faulty. |
| 0x000000e7 | INVALID_FLOATING_POINT_STATE | This indicates that a thread's saved floating-point state is invalid. |
| 0x000000f2 | HARDWARE_INTERRUPT_STORM | This indicates that the kernel detected an interrupt storm. |
| 0x000000fb | RECURSIVE_MACHINE_CHECK | |
| 0x000000fe | BUGCODE_USB_DRIVER | This indicates that an error has occurred in a universal serial bus (USB) driver. |
| 0x00000101 | CLOCK_WATCHDOG_TIMEOUT | Learn how the CLOCK_WATCHDOG_TIMEOUT bug check indicates that an expected clock interrupt on a secondary processor isn't received within the allocated interval. |
| 0x00000111 | RECURSIVE_NMI | This bug check indicates that a non-maskable-interrupt (NMI) occurred while a previous NMI was in progress. |
| 0x0000011a | EM_INITIALIZATION_ERROR | |
| 0x0000011a | EM_INITIALIZATION_FAILURE | This bug check appears very infrequently. |
| 0x00000122 | WHEA_INTERNAL_ERROR | The WHEA_INTERNAL_ERROR bug check has a value of 0x00000122. |
| 0x00000124 | WHEA_UNCORRECTABLE_ERROR | Learn about the bug check 0x124 WHEA_UNCORRECTABLE_ERROR, which indicates that a fatal hardware error has occurred. |
| 0x0000012b | FAULTY_HARDWARE_CORRUPTED_PAGE | Learn how the FAULTY_HARDWARE_CORRUPTED_PAGE bug check indicates the memory manager detected corruption caused by a component accessing memory using physical addressing. |
| 0x00000130 | DYNAMIC_ADD_PROCESSOR_MISMATCH | This bugcheck indicates that a new processor added to the system is incompatible with the current configuration. |
| 0x00000131 | INVALID_EXTENDED_PROCESSOR_STATE | This indicates that an invalid combination of parameters was detected while saving or restoring extended processor state. |
| 0x00000138 | GPIO_CONTROLLER_DRIVER_ERROR | This bug check indicates that the GPIO class extension driver encountered a fatal error. |
| 0x0000013e | ERRATA_WORKAROUND_UNSUCCESSFUL | |
| 0x00000143 | PROCESSOR_DRIVER_INTERNAL | This indicates that the Processor Power Management (PPM) driver encountered a fatal error. |
| 0x00000144 | BUGCODE_USB3_DRIVER | This is the code used for all USB 3 bug checks. |
| 0x00000147 | ABNORMAL_RESET_DETECTED | This indicates that Windows underwent an abnormal reset. |
| 0x0000014b | SOC_SUBSYSTEM_FAILURE | This indicates that an unrecoverable error was encountered in a System on a Chip (SoC) subsystem. |
| 0x0000014c | FATAL_ABNORMAL_RESET_ERROR | This indicates that an unrecoverable system error occurred or the system has abnormally reset. |
| 0x0000014e | SOC_CRITICAL_DEVICE_REMOVED | This indicates that a critical SOC device has been unexpectedly removed or failed. |
| 0x00000151 | UNSUPPORTED_INSTRUCTION_MODE | The UNSUPPORTED_INSTRUCTION_MODE bug check has a value of 0x00000151. |
| 0x00000158 | ILLEGAL_IOMMU_PAGE_FAULT | This indicates that the IOMMU has delivered a page fault packet for an invalid ASID. |
| 0x00000159 | HAL_ILLEGAL_IOMMU_PAGE_FAULT | The HAL_ILLEGAL_IOMMU_PAGE_FAULT bug check has a value of 0x00000159. |
| 0x0000015a | SDBUS_INTERNAL_ERROR | This indicates that an unrecoverable hardware failure has occurred on an SD-attached device. |
| 0x0000015d | SOC_SUBSYSTEM_FAILURE_LIVEDUMP live dump | The SOC_SUBSYSTEM_FAILURE_LIVEDUMP live dump has a value of 0x0000015D. |
| 0x00000175 | PREVIOUS_FATAL_ABNORMAL_RESET_ERROR | The PREVIOUS_FATAL_ABNORMAL_RESET_ERROR live dump has a value of 0x00000175. |
| 0x0000017e | MICROCODE_REVISION_MISMATCH | It indicates that that one or more processors in the multiprocessor configuration have inconsistent microcode loaded. |
| 0x00000198 | UFX_LIVEDUMP live dump | This indicates that a UFX live dump occurred. |
| 0x000001a6 | BLUETOOTH_ERROR_RECOVERY_LIVEDUMP live dump | It indicates that the Bluetooth radio driver has initiated error recovery to attempt to reset the radio from an irremediable condition. |
| 0x000001cf | HARDWARE_WATCHDOG_TIMEOUT | The HARDWARE_WATCHDOG_TIMEOUT bug check has a value of 0x000001CF. |
| 0x000001d0 | ACPI_FIRMWARE_WATCHDOG_TIMEOUT | The ACPI_FIRMWARE_WATCHDOG_TIMEOUT bug check has a value of 0x000001D0. |
| 0x000001d4 | UCMUCSI_LIVEDUMP live dump | The UCMUCSI_LIVEDUMP live dump has a value of 0x000001D4. |
| 0x000001d8 | UCMUCSI_FAILURE | It indicates that that the UCSI class extension has encountered an error. |
| 0x000001d9 | HAL_IOMMU_INTERNAL_ERROR | It indicates that that the UcmUcsi driver has encountered an error. |
| 0x000001da | HAL_BLOCKED_PROCESSOR_INTERNAL_ERROR | The HAL_BLOCKED_PROCESSOR_INTERNAL_ERROR has a value of 0x000001DA. |
| 0x000001db | IPI_WATCHDOG_TIMEOUT | It indicates that that a processor has been stuck in an IPI loop for more than the allowed time. |
| 0x000001df | PROCESSOR_START_TIMEOUT | This indicates a processor failed to start in the allowed time. |
| 0x000001e9 | ILLEGAL_ATS_INITIALIZATION | This indicates that the driver has attempted to illegally enable the Address Translation Service (ATS) on a device which has been already been enabled for Shared Virtual Memory (SVM). |
| 59 entries | ||
Power management
Power state transitions, sleep, and the policy coordinator.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x0000009f | DRIVER_POWER_STATE_FAILURE | This bug check indicates that the driver is in an inconsistent or invalid power state. |
| 0x000000a0 | INTERNAL_POWER_ERROR | This bug check indicates that the power policy manager experienced a fatal error. |
| 0x000000bd | INVALID_HIBERNATED_STATE | The INVALID_HIBERNATED_STATE bug check has a value of 0x000000BD. |
| 0x000000e5 | POWER_FAILURE_SIMULATE | |
| 0x000000f3 | DISORDERLY_SHUTDOWN | This indicates that Windows was unable to shut down due to lack of memory. |
| 0x0000014f | PDC_WATCHDOG_TIMEOUT | This indicates that a system component failed to respond within the allocated time period. |
| 0x0000015c | PDC_WATCHDOG_TIMEOUT_LIVEDUMP live dump | The PDC_WATCHDOG_TIMEOUT_LIVEDUMP live dump has a value of 0x0000015C that indicates that a system component failed to respond, preventing entering or exiting connected standby. |
| 0x0000015f | CONNECTED_STANDBY_WATCHDOG_TIMEOUT_LIVEDUMP live dump | This indicates that a connected standby watchdog timeout has occurred. |
| 0x0000017c | PDC_LOCK_WATCHDOG_LIVEDUMP live dump | This indicates that a thread has been holding the PDC lock for too long. |
| 0x0000017d | PDC_UNEXPECTED_REVOCATION_LIVEDUMP live dump | It indicates that an activator has been revoked unexpectedly. |
| 0x0000019f | PDC_PRIVILEGE_CHECK_LIVEDUMP live dump | |
| 0x000001a4 | DRIPS_SW_HW_DIVERGENCE_LIVEDUMP live dump | The DRIPS_SW_HW_DIVERGENCE_LIVEDUMP live dump has a value of 0x000001A4. |
| 0x000001a5 | USB_DRIPS_BLOCKER_SURPRISE_REMOVAL_LIVEDUMP live dump | It indicates that a USB device will be surprise removed because it is blocking DRIPS. |
| 0x000001a9 | DIRECTED_FX_TRANSITION_LIVEDUMP live dump | It indicates that a device has failed its Directed Fx transition call. |
| 0x000001eb | DAM_WATCHDOG_TIMEOUT | This indicates that the Desktop Activity Moderator (DAM) was unable to unfreeze non-exempt user session processes within the allocated time period after the device resumed from modern standby. |
| 15 entries | ||
Security and integrity
Code integrity, cryptography, tokens, and tamper detection.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000028 | CORRUPT_ACCESS_TOKEN | This bug check appears very infrequently. |
| 0x00000029 | SECURITY_SYSTEM | This bug check appears very infrequently. |
| 0x00000046 | DEREF_UNKNOWN_LOGON_SESSION | This bug check appears very infrequently. |
| 0x00000047 | REF_UNKNOWN_LOGON_SESSION | This bug check appears very infrequently. |
| 0x00000086 | AUDIT_FAILURE | |
| 0x00000098 | END_OF_NT_EVALUATION_PERIOD | This bug check indicates that the trial period for the Microsoft Windows operating system has ended. |
| 0x0000009a | SYSTEM_LICENSE_VIOLATION | This bug check indicates that the software license agreement has been violated. |
| 0x000000c3 | SYSTEM_IMAGE_BAD_SIGNATURE | |
| 0x00000109 | CRITICAL_STRUCTURE_CORRUPTION | This indicates that the kernel has detected critical kernel code or data corruption. |
| 0x00000120 | BITLOCKER_FATAL_ERROR | This indicates that BitLocker drive encryption encountered a problem that it cannot recover from. |
| 0x00000123 | CRYPTO_SELF_TEST_FAILURE | This indicates that the cryptographic subsystem failed a mandatory algorithm self-test during bootstrap. |
| 0x00000139 | KERNEL_SECURITY_CHECK_FAILURE | The KERNEL_SECURITY_CHECK_FAILURE bug check has a value of 0x00000139, and indicates that the kernel detects the corruption of a critical data structure. |
| 0x00000145 | SECURE_BOOT_VIOLATION | This indicates that the secure Boot policy enforcement could not be started. |
| 0x00000155 | OS_DATA_TAMPERING | The OS_DATA_TAMPERING bug check has a value of 0x00000155. |
| 0x00000171 | CRYPTO_LIBRARY_INTERNAL_ERROR | It indicates that an internal error in the crypto libraries occurred. |
| 0x00000178 | ELAM_DRIVER_DETECTED_FATAL_ERROR | This indicates that ELAM driver detected a fatal error. |
| 0x0000018c | HYPERGUARD_VIOLATION | It indicates that the kernel has detected that critical kernel code or data have been corrupted. |
| 0x000001d7 | EFS_FATAL_ERROR | It indicates that an EFS error condition has occurred such that cannot be handled without data loss or data corruption. |
| 0x000001ea | SECURE_PCI_CONFIG_SPACE_ACCESS_VIOLATION | This indicates that the access to the PCI config space region from VTL0 by directly mapping the PCI MCFG range is prohibited because secure PCI is enabled. |
| 19 entries | ||
Virtualization and secure kernel
The hypervisor and the isolated kernel running under it.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x0000006f | VSL_INITIALIZATION_FAILED | |
| 0x00000118 | NTHV_GUEST_ERROR | |
| 0x0000018b | SECURE_KERNEL_ERROR | This indicates that the secure kernel has encountered a fatal error. |
| 0x0000018d | SECURE_FAULT_UNHANDLED | It indicates that a secure fault originated by the secure kernel could not be handled. |
| 0x00020001 | HYPERVISOR_ERROR | This indicates that the hypervisor has encountered a fatal error. |
| 5 entries | ||
Boot and startup
Failures before the system is up: boot devices, hives, and phase initialization.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000031 | PHASE0_INITIALIZATION_FAILED | This indicates that system initialization failed. |
| 0x00000032 | PHASE1_INITIALIZATION_FAILED | This indicates that system initialization failed. |
| 0x00000033 | UNEXPECTED_INITIALIZATION_CALL | This bug check appears very infrequently. |
| 0x00000043 | NO_SUCH_PARTITION | This bug check appears very infrequently. |
| 0x00000053 | NO_BOOT_DEVICE | This bug check appears very infrequently. |
| 0x0000005a | CRITICAL_SERVICE_FAILED | This bug check appears very infrequently. |
| 0x0000005b | SET_ENV_VAR_FAILED | This bug check appears very infrequently. |
| 0x0000005e | OBJECT_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x0000005f | SECURITY_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000060 | PROCESS_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000062 | OBJECT1_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000063 | SECURITY1_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000064 | SYMBOLIC_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000065 | MEMORY1_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000066 | CACHE_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000067 | CONFIG_INITIALIZATION_FAILED | This bug check indicates that the registry configuration failed. |
| 0x00000068 | FILE_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x00000069 | IO1_INITIALIZATION_FAILED | This bug check indicates that the initialization of the I/O system failed for some reason. |
| 0x0000006a | LPC_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x0000006b | PROCESS1_INITIALIZATION_FAILED | This bug check indicates that the initialization of the Microsoft Windows operating system failed. |
| 0x0000006c | REFMON_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x0000006d | SESSION1_INITIALIZATION_FAILED | This bug check indicates that the initialization of the Microsoft Windows operating system failed. |
| 0x0000006e | SESSION2_INITIALIZATION_FAILED | This bug check indicates that the initialization of the Microsoft Windows operating system failed. |
| 0x0000006e | BOOTPROC_INITIALIZATION_FAILED | |
| 0x0000006f | SESSION3_INITIALIZATION_FAILED | This bug check indicates that the initialization of the Microsoft Windows operating system failed. |
| 0x00000070 | SESSION4_INITIALIZATION_FAILED | This bug check indicates that the initialization of the Microsoft Windows operating system failed. |
| 0x00000070 | SOFT_RESTART_FATAL_ERROR | |
| 0x00000071 | SESSION5_INITIALIZATION_FAILED | This bug check indicates that the initialization of the Microsoft Windows operating system failed. |
| 0x00000073 | CONFIG_LIST_FAILED | This bug check indicates that one of the top-level registry keys, also known as core system hives, cannot be linked in the registry tree. |
| 0x00000074 | BAD_SYSTEM_CONFIG_INFO | This bug check indicates that there is an error in the registry. |
| 0x00000075 | CANNOT_WRITE_CONFIGURATION | This bug check indicates that the SYSTEM registry hive file cannot be converted to a mapped file. |
| 0x00000078 | PHASE0_EXCEPTION | This bug check occurs when an unexpected break is encountered during HAL initialization. |
| 0x0000007b | INACCESSIBLE_BOOT_DEVICE | Learn how the INACCESSIBLE_BOOT_DEVICE bug check indicates that the Microsoft Windows operating system has lost access to the system partition during startup. |
| 0x00000085 | SETUP_FAILURE | This bug check indicates that a fatal error occurred during setup. |
| 0x0000008b | MBR_CHECKSUM_MISMATCH | This bug check indicates that a mismatch has occurred in the MBR checksum. |
| 0x0000008f | PP0_INITIALIZATION_FAILED | This bug check indicates that the Plug and Play (PnP) manager could not be initialized. |
| 0x00000090 | PP1_INITIALIZATION_FAILED | This bug check indicates that the Plug and Play (PnP) manager could not be initialized. |
| 0x000000ed | UNMOUNTABLE_BOOT_VOLUME | This indicates that the I/O subsystem attempted to mount the boot volume and it failed. |
| 0x000000f8 | RAMDISK_BOOT_INITIALIZATION_FAILED | This indicates that an initialization failure occurred while attempting to boot from the RAM disk. |
| 0x00000100 | LOADER_BLOCK_MISMATCH | This indicates that either the loader block is invalid, or it does not match the system that is being loaded. |
| 0x0000010a | APP_TAGGING_INITIALIZATION_FAILED | This bug check appears very infrequently. |
| 0x0000012a | MUI_NO_VALID_SYSTEM_LANGUAGE | This indicates that Windows did not find any installed, licensed language packs for the system default UI language. |
| 0x0000012f | VHD_BOOT_INITIALIZATION_FAILED | This indicates that an initialization failure occurred while attempting to boot from a VHD. |
| 0x00000136 | VHD_BOOT_HOST_VOLUME_NOT_ENOUGH_SPACE | There is not enough free space to expand the VHD. |
| 0x0000013d | CRITICAL_INITIALIZATION_FAILURE | This indicates that early kernel initialization has failed. |
| 0x00000196 | LOADER_ROLLBACK_DETECTED | This indicates that the version of the OS loader does not match the operating system. |
| 0xc0000218 | STATUS_CANNOT_LOAD_REGISTRY_FILE | This indicates that a registry file could not be loaded. |
| 0xc000021a | WINLOGON_FATAL_ERROR | This means that the Winlogon process terminated unexpectedly. |
| 0xc0000221 | STATUS_IMAGE_CHECKSUM_MISMATCH | The STATUS_IMAGE_CHECKSUM_MISMATCH bug check has a value of 0xC0000221 and indicates that a driver or a system DLL is corrupted. |
| 49 entries | ||
Failover clustering
Cluster shared volumes and the cluster service watching them.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000165 | CLUSTER_CSV_STATUS_IO_TIMEOUT_LIVEDUMP live dump | This indicates that a SMB client is experiencing a timeout situation. |
| 0x00000166 | CLUSTER_RESOURCE_CALL_TIMEOUT_LIVEDUMP live dump | This indicates that a Cluster Resource call took longer than configured timeout. |
| 0x00000167 | CLUSTER_CSV_SNAPSHOT_DEVICE_INFO_TIMEOUT_LIVEDUMP live dump | This indicates that a Cluster Service call to the volsnap to query snapshot information took too long. |
| 0x00000168 | CLUSTER_CSV_STATE_TRANSITION_TIMEOUT_LIVEDUMP live dump | This indicates that a Cluster Shared Volume state transition took too long. |
| 0x00000169 | CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP live dump | This indicates that Cluster Shared Volume Manager was asked to create a new volume device object, and volume has not arrived in time. |
| 0x0000016a | CLUSTER_CSV_VOLUME_REMOVAL_LIVEDUMP live dump | This indicates that a Cluster Shared Volume Manager volume removal request has timed out. |
| 0x0000016b | CLUSTER_CSV_CLUSTER_WATCHDOG_LIVEDUMP live dump | This indicates thatthe Cluster service user mode watchdog detected that a thread is not making forward progress for a long time. |
| 0x0000016f | CLUSTER_CSV_STATE_TRANSITION_INTERVAL_TIMEOUT_LIVEDUMP live dump | This indicates that a Cluster Shared Volume next state transition request has not arrived. |
| 0x00000170 | CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG | This indicates that the Cluster disconnect is not making forward progress. |
| 0x00000179 | CLUSTER_CLUSPORT_STATUS_IO_TIMEOUT_LIVEDUMP live dump | This indicates that SMB client on the initiator node complains that an IO on target node is taking too long and fails all IOs with STATUS_IO_TIMEOUT. |
| 0x00000188 | CLUSTER_CSVFS_LIVEDUMP live dump | This indicates that CSVFS initiated this livedump to help debug an inconsistent state. |
| 0x0000019d | CLUSTER_SVHDX_LIVEDUMP live dump | This indicates that SVHDX initiated this livedump to help debug an inconsistent state. |
| 12 entries | ||
Debugging and diagnostics
Dumps taken deliberately, and the instrumentation that takes them.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x000000e2 | MANUALLY_INITIATED_CRASH | This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. |
| 0x0000011d | EVENT_TRACING_FATAL_ERROR | This bug check indicates that the Event Tracing subsystem has encountered an unexpected fatal error. |
| 0x00000161 | LIVE_SYSTEM_DUMP | This indicates that the system administrator requested the collection of a live system memory dump. |
| 0x0000017b | PROFILER_CONFIGURATION_ILLEGAL | The PROFILER_CONFIGURATION_ILLEGAL bug check has a value of 0x0000017B. |
| 0x000001c8 | MANUALLY_INITIATED_POWER_BUTTON_HOLD | The system was configured to initiate a bugcheck when the user holds the power button. |
| 0x000001d1 | TELEMETRY_ASSERTS_LIVEDUMP live dump | The TELEMETRY_ASSERTS_LIVEDUMP live dump has a value of 0x000001D1. |
| 0x000001f1 | KASAN_ENLIGHTENMENT_VIOLATION | It indicates that that KASAN enlightenment encoutered a violation when attempting to interact with memory shadow. |
| 0x000001f2 | KASAN_ILLEGAL_ACCESS | It indicates that that KASAN detected an illegal memory access being made. |
| 0x000001f5 | APPLICATION_HANG_KERNEL_LIVEDUMP live dump | This indicates that an application hung when attempting to be terminated. |
| 0x000021c8 | MANUALLY_INITIATED_BLACKSCREEN_HOTKEY_LIVE_DUMP live dump | This indicates that the system was configured to capture a live dump and the user had pressed the black screen hotkey (CTRL + SHIFT + WIN + B). |
| 0xdeaddead | MANUALLY_INITIATED_CRASH1 | This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. |
| 11 entries | ||
Windows Phone
The SAVER codes, from the Windows Phone and Mobile builds.
Xbox
Codes reserved for the Xbox system software.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000356 | XBOX_ERACTRL_CS_TIMEOUT | The XBOX_ERACTRL_CS_TIMEOUT bug check has a value of 0x00000356. |
| 0x00000357 | XBOX_CORRUPTED_IMAGE | |
| 0x00000358 | XBOX_INVERTED_FUNCTION_TABLE_OVERFLOW | |
| 0x00000359 | XBOX_CORRUPTED_IMAGE_BASE | |
| 0x00000360 | XBOX_360_SYSTEM_CRASH | |
| 0x00000420 | XBOX_360_SYSTEM_CRASH_RESERVED | |
| 6 entries | ||
Other
Codes with too little documentation to place.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x00000084 | RECOM_DRIVER | |
| 1 entry | ||
Not stop codes
Strings sharing the header with the stop codes: the boot banner, the safe mode and boot log notices, and the hardware profile prompts.
| Code | Symbolic | Abstract |
|---|---|---|
| 0x000000a8 | BOOTING_IN_SAFEMODE_MINIMAL | |
| 0x000000a9 | BOOTING_IN_SAFEMODE_NETWORK | |
| 0x000000aa | BOOTING_IN_SAFEMODE_DSREPAIR | |
| 0x000000b5 | BOOTLOG_LOADED | |
| 0x000000b6 | BOOTLOG_NOT_LOADED | |
| 0x000000b7 | BOOTLOG_ENABLED | |
| 0x4000007e | WINDOWS_NT_BANNER | Microsoft (R) Windows (R) Version %hs (Build %u%hs) |
| 0x40000087 | WINDOWS_NT_CSD_STRING | Service Pack |
| 0x40000088 | WINDOWS_NT_INFO_STRING | %u System Processor [%u MB Memory] %Z |
| 0x40000089 | WINDOWS_NT_MP_STRING | MultiProcessor Kernel |
| 0x4000009d | WINDOWS_NT_INFO_STRING_PLURAL | %u System Processors [%u MB Memory] %Z |
| 0x4000009e | WINDOWS_NT_RC_STRING | RC |
| 0x40010001 | HARDWARE_PROFILE_UNDOCKED_STRING | Undocked Profile |
| 0x40010002 | HARDWARE_PROFILE_DOCKED_STRING | Docked Profile |
| 0x40010003 | HARDWARE_PROFILE_UNKNOWN_STRING | Profile |
| 15 entries | ||
513 codes in total.