Stop code lookup
What does that blue screen code mean?
Type the code (0x0000009F, 9F) or the name (DRIVER_POWER_STATE_FAILURE). All 379 codes in Microsoft's Bug Check Code Reference, each linked to Microsoft's own page (except 0x1D9, HAL_IOMMU_INTERNAL_ERROR, which links to the reference list because Microsoft's own link for it is broken).
The common ones
| Code | Name | Usually points to |
|---|---|---|
| 0x0000000A | IRQL_NOT_LESS_OR_EQUAL | A driver. Windows or a driver touched memory it was not allowed to at that moment. Most often a faulty or outdated driver; sometimes failing memory. |
| 0x00000019 | BAD_POOL_HEADER | Memory (RAM). A block of kernel memory was found damaged. Usually a driver writing where it should not; sometimes failing memory. |
| 0x0000001A | MEMORY_MANAGEMENT | Memory (RAM). Windows found a serious memory-management error. Failing RAM is a common cause; a driver is the other. |
| 0x0000001E | KMODE_EXCEPTION_NOT_HANDLED | A driver. A kernel-mode program raised an error nothing handled. Usually a driver. |
| 0x00000024 | NTFS_FILE_SYSTEM | The drive or file system. The NTFS file system driver hit a problem. Disk errors or file-system damage are the usual reasons. |
| 0x0000003B | SYSTEM_SERVICE_EXCEPTION | A driver. An error happened while Windows was running a system routine. Drivers and security software are the usual suspects. |
| 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA | Memory (RAM). Windows referred to memory that was not there. Failing RAM, a faulty driver or security software are the usual reasons. |
| 0x0000007A | KERNEL_DATA_INPAGE_ERROR | The drive or file system. Windows could not read data it needed back from the disk. Points at the drive, its cable or connection, or memory. |
| 0x0000007B | INACCESSIBLE_BOOT_DEVICE | The drive or file system. Windows lost access to the drive it starts from. Storage driver, disk mode change in firmware, or a failing drive. |
| 0x0000007E | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED | A driver. A Windows system thread raised an error nothing handled. Usually a driver. |
| 0x0000007F | UNEXPECTED_KERNEL_MODE_TRAP | Hardware. The processor raised a trap the kernel could not handle. Hardware faults (memory, overclocking) or a driver. |
| 0x0000009C | MACHINE_CHECK_EXCEPTION | Hardware. The processor reported a machine check: a hardware error. |
| 0x0000009F | DRIVER_POWER_STATE_FAILURE | Power / sleep. A driver did not finish a power change (sleep, wake, shut down) in time. Often a driver for a USB, network or graphics device. |
| 0x000000BE | ATTEMPTED_WRITE_TO_READONLY_MEMORY | A driver. A driver tried to write to read-only memory. |
| 0x000000C2 | BAD_POOL_CALLER | A driver. A driver made a bad memory request. |
| 0x000000D1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL | A driver. A driver touched memory it should not at a high priority level. Almost always a driver; the network driver is a frequent one. |
| 0x000000E2 | MANUALLY_INITIATED_CRASH | Started on purpose. Someone or a tool started this crash on purpose (for example to collect a memory dump). |
| 0x000000ED | UNMOUNTABLE_BOOT_VOLUME | The drive or file system. Windows could not mount the volume it starts from. Disk or file-system damage. |
| 0x000000EF | CRITICAL_PROCESS_DIED | Windows system files. A process Windows cannot run without stopped. Damaged system files, a failing drive or security software. |
| 0x000000F4 | CRITICAL_OBJECT_TERMINATION | The drive or file system. A process or thread Windows needs ended unexpectedly. Often a storage problem. |
| 0x000000FC | ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY | A driver. Code tried to run from memory marked as not runnable. Usually a driver. |
| 0x00000101 | CLOCK_WATCHDOG_TIMEOUT | Hardware. A processor stopped answering. Processor, firmware (BIOS/UEFI) or overclocking. |
| 0x00000109 | CRITICAL_STRUCTURE_CORRUPTION | Windows system files. Windows found key kernel code or data changed. A driver, or failing memory. |
| 0x00000116 | VIDEO_TDR_FAILURE | Graphics. The graphics driver stopped responding and could not be reset. |
| 0x00000117 | VIDEO_TDR_TIMEOUT_DETECTED | Graphics. The graphics driver stopped responding (a timeout was detected). |
| 0x00000119 | VIDEO_SCHEDULER_INTERNAL_ERROR | Graphics. The graphics scheduler hit a fatal error. Graphics driver. |
| 0x00000124 | WHEA_UNCORRECTABLE_ERROR | Hardware. The hardware reported an error it could not correct (processor, memory, bus). Heat, power, overclocking or a failing part. |
| 0x0000012B | FAULTY_HARDWARE_CORRUPTED_PAGE | Memory (RAM). Windows found a memory page damaged by faulty hardware. |
| 0x00000133 | DPC_WATCHDOG_VIOLATION | A driver. A driver held a processor too long. Storage and chipset drivers or firmware are frequent causes. |
| 0x00000139 | KERNEL_SECURITY_CHECK_FAILURE | Windows system files. Windows found a key data structure corrupted. A driver, or failing memory. |
| 0x0000013A | KERNEL_MODE_HEAP_CORRUPTION | A driver. Kernel-mode memory (the heap) was found corrupted. Usually a driver. |
| 0x00000144 | BUGCODE_USB3_DRIVER | A driver. The USB 3 driver hit a fatal error. A USB device, hub or its driver. |
| 0x00000154 | UNEXPECTED_STORE_EXCEPTION | The drive or file system. The memory compression store hit an unexpected error. Often storage. |
| 0x000001C8 | MANUALLY_INITIATED_POWER_BUTTON_HOLD | Started on purpose. Recorded when the power button was held down to force the computer off. |
| 0xC000021A | WINLOGON_FATAL_ERROR | Windows system files. A key Windows user-mode process (such as Winlogon) failed. Damaged system files or a bad update. |