Windows & Office Error Code Lookup
Search by error code (like 0x80070005), stop code name (like IRQL_NOT_LESS_OR_EQUAL), Excel formula error (like #REF!), or plain description.
Don't have an exact code yet? See common Windows error messages explained in plain English first.
21 results
0X0000001A — MEMORY_MANAGEMENT
Points to a problem with how memory is being handled — faulty RAM, a driver mismanaging memory, or disk corruption.
0X0000000A — IRQL_NOT_LESS_OR_EQUAL
Almost always a driver issue — most commonly network, audio, or graphics drivers.
0X000000EF — CRITICAL_PROCESS_DIED
A core Windows process crashed unexpectedly — often tied to a recent update or corrupted system files.
0X0000001E — KMODE_EXCEPTION_NOT_HANDLED
A driver running in kernel mode hit an error it couldn't recover from — usually a specific faulty or outdated driver.
0X0000007B — INACCESSIBLE_BOOT_DEVICE
Windows can't access the drive it needs to boot from — often after a storage driver change, BIOS setting change, or drive connection issue.
0X0000009F — DRIVER_POWER_STATE_FAILURE
A driver mishandled a transition into or out of sleep/hibernation — very commonly network or USB drivers.
0X000000D1 — DRIVER_IRQL_NOT_LESS_OR_EQUAL
A driver tried to access memory at the wrong priority level — nearly always a specific faulty driver, most often network or a security/VPN tool.
0X0000003B — SYSTEM_SERVICE_EXCEPTION
A system service call failed unexpectedly — commonly graphics drivers during gaming or video playback.
0X00000050 — PAGE_FAULT_IN_NONPAGED_AREA
Windows tried to access memory that doesn't exist or isn't where it expected — often faulty RAM or a driver bug.
0X00000124 — WHEA_UNCORRECTABLE_ERROR
A hardware-level error was detected — often CPU, RAM, or power delivery, especially in overclocked systems.
0X0000007E — SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an error a driver didn't catch — very commonly graphics or Wi-Fi drivers right after an update.
0X0000008E — KERNEL_MODE_EXCEPTION_NOT_HANDLED
Similar to KMODE_EXCEPTION_NOT_HANDLED — a kernel-level error a driver couldn't recover from.
0X000000C2 — BAD_POOL_CALLER
A driver incorrectly requested or freed a block of memory — almost always a specific faulty or outdated driver.
0X00000019 — BAD_POOL_HEADER
Memory pool corruption, usually caused by a buggy driver or, less often, failing RAM.
0X000000F4 — CRITICAL_OBJECT_TERMINATION
A critical process or thread Windows depends on was unexpectedly terminated — often tied to a failing drive.
0X0000004E — PFN_LIST_CORRUPT
Corruption in the page frame number list Windows uses to track memory — usually faulty RAM.
0X00000133 — DPC_WATCHDOG_VIOLATION
A driver took too long responding to a routine check — commonly storage (SSD/NVMe) drivers or firmware.
0X00000116 — VIDEO_TDR_ERROR
The graphics driver stopped responding and failed to recover — usually a driver issue, sometimes an unstable GPU overclock.
0X0000009C — MACHINE_CHECK_EXCEPTION
The CPU detected a hardware-level error — commonly overheating, an unstable overclock, or failing hardware.
0X00020001 — HYPERVISOR_ERROR
The Windows hypervisor — the low-level layer behind Hyper-V, Windows Sandbox, and Virtualization-Based Security features like Memory Integrity — hit a fatal error it couldn't recover from. Unlike a typical driver crash, this is reported at the platform level, so the crash dump usually points to a generic function rather than one specific named driver.
IRQL-UNEXPECTED-VALUE — IRQL_UNEXPECTED_VALUE
A related but distinct stop code from IRQL_NOT_LESS_OR_EQUAL — here a driver attempted to lower its interrupt request level improperly, or accessed something unexpected while running at an elevated one. Like its more common relative, it's almost always a driver issue, most often network adapter drivers specifically.