A Windows stop code is the short name or number shown on a Blue Screen of Death. It does not always name the exact broken part, but it usually points you toward the right category: driver, memory, storage, hardware, or system-file damage.
This guide applies to Windows 10 and Windows 11 PCs that show a blue screen stop code.
Does This Affect You?
If your PC crashed with a code such as IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, or CRITICAL_PROCESS_DIED, matching the code before trying fixes saves time. Use the list below as a triage guide, then follow the article or troubleshooting path for that code.
Common Stop Codes and What They Usually Mean
- IRQL_NOT_LESS_OR_EQUAL: Often a driver, especially network, graphics, or antivirus, tried to access memory incorrectly. Roll back or update recent drivers first.
- PAGE_FAULT_IN_NONPAGED_AREA: Commonly points to RAM trouble, a failing drive, a bad driver, or corrupted system files. Test memory and check storage health.
- CRITICAL_PROCESS_DIED: A core Windows process stopped. Run SFC, DISM, and System Restore if it began after an update.
- SYSTEM_SERVICE_EXCEPTION: Usually a driver made an invalid Windows system call. Start with graphics, network, chipset, and storage drivers.
- KMODE_EXCEPTION_NOT_HANDLED: Driver-level fault. Check Device Manager and update or reinstall suspicious drivers.
- DPC_WATCHDOG_VIOLATION: Frequently linked to storage controller drivers, SSD firmware, or NVMe issues. Update storage drivers and check SSD firmware.
- WHEA_UNCORRECTABLE_ERROR: Hardware-level problem, often CPU, RAM, overheating, or overclocking. Return overclocks to default and check cooling.
- UNEXPECTED_KERNEL_MODE_TRAP: Often tied to hardware instability, especially RAM or CPU overheating. Run memory diagnostics and inspect cooling.
- VIDEO_TDR_FAILURE: The graphics driver stopped responding and Windows could not recover it. Clean-install the GPU driver from NVIDIA, AMD, or Intel.
- INACCESSIBLE_BOOT_DEVICE: Windows cannot reach the boot drive. Storage mode changes, boot order, corrupted boot files, or drive failure are common causes.
What to Do After Identifying the Code
Read Minidump Files
Windows often stores crash reports in C:WindowsMinidump. WhoCrashed, BlueScreenView, or Microsoft WinDbg can inspect those files and may identify the exact driver file.
Run Memory Tests for RAM-Looking Codes
For PAGE_FAULT, MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, or changing/random stop codes, run Windows Memory Diagnostic and consider a deeper overnight memory test if crashes continue.
Undo the Most Recent Change
If the blue screen started after new hardware, a driver update, BIOS tuning, a Windows update, or an overclock, undo that change first. A precise rollback beats broad troubleshooting.
Different Codes Can Mean Hardware
A single software bug tends to repeat the same stop code. Different blue screens on each crash often suggest RAM, storage, overheating, or power instability.
Sources
- Microsoft Learn: Bug Check Code Reference
- Microsoft Support: Troubleshoot blue screen errors
- Microsoft Learn: Blue screen data