A blue screen (or a black one, on newer versions of Windows 11) saying "Your device ran into a problem and needs to restart" is a stop error: Windows shut down on purpose to avoid damaging your data. If it happened once, restarting is usually enough. If it keeps happening, the stop code at the bottom tells you where to start. Here is what to do and what 50 of those codes mean.
What a blue screen is and why it happens
Microsoft calls it a stop code error (also a bug check, kernel error or BSOD). Windows stops when it finds something that puts its safe operation at risk, such as a driver writing where it should not or a drive that does not respond. According to Microsoft's analysis of the root causes of these crashes:
| Cause | Share |
|---|---|
| Third-party driver code | 70% |
| Hardware issues | 10% |
| Microsoft code | 5% |
| Unknown (the memory is too corrupted to analyze) | 15% |
In other words, most of the time the culprit is a driver, not a broken part. That is why it pays to start with the software before buying replacement parts.
How to see the blue screen stop code
- On the screen: at the bottom you will see "Stop code" followed by a name in capitals (for example
MEMORY_MANAGEMENT) and sometimes "What failed" with the name of a.sysfile: that is the driver that was running. Take a photo with your phone, because the screen does not stay up for long. - If you did not manage to read it: Windows saves a memory dump file in
C:\Windows\Minidump(the small ones) orC:\Windows\MEMORY.DMP, according to Microsoft. If that file exists, the blue screen was recorded. - With the code in hand, look it up in Windows error codes: it accepts the name (
IRQL_NOT_LESS_OR_EQUAL) or the number (0x0000000Aor0xA).
What to do if the blue screen keeps coming back
These are the basic steps Microsoft Support gives, in order, with the commands we use on each code's page:
- Remove the last thing you added. If you installed a new part (RAM, graphics card, drive, a USB adapter) just before it started, shut down, remove it and try again.
- If it does not start properly, use safe mode. From there you can do the rest of the steps.
- Check Device Manager (right-click Start). If a device has an exclamation mark, update its driver; if that does not fix it, uninstall it. To get the right driver, use official drivers by brand.
- Free up disk space. Microsoft recommends keeping 10% to 15% of the system drive free.
- Install updates from Settings › Windows Update › Check for updates.
- Repair the Windows files with
DISM /Online /Cleanup-Image /RestoreHealthand thensfc /scannow, in Command Prompt as administrator. They are explained in Windows repair commands. - Roll back. If nothing works, use a restore point or the Windows recovery options. As a last resort, reinstalling Windows rules out any software problem.
What each code means
We grouped the 50 codes by what they point to in Microsoft's description. Each name leads to its page with the causes, the steps and the official source.
Drivers (19)
Microsoft names them as the most common cause. They usually appear after installing or updating a driver, a program with its own driver (antivirus, VPN, RGB or overclocking software) or a new part.
| Code | Number | What it means |
|---|---|---|
IRQL_NOT_LESS_OR_EQUAL | 0xA | A driver used memory it should not have |
DRIVER_IRQL_NOT_LESS_OR_EQUAL | 0xD1 | A driver accessed invalid memory |
SYSTEM_SERVICE_EXCEPTION | 0x3B | An internal system function failed |
KMODE_EXCEPTION_NOT_HANDLED | 0x1E | A system component raised an error nobody caught |
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED | 0x7E | A system thread failed with no handler |
DPC_WATCHDOG_VIOLATION | 0x133 | A driver took too long to respond |
DRIVER_POWER_STATE_FAILURE | 0x9F | A driver failed while sleeping, shutting down or waking up |
BAD_POOL_CALLER | 0xC2 | A driver requested memory incorrectly |
DRIVER_VERIFIER_DETECTED_VIOLATION | 0xC4 | Driver Verifier found an error |
ATTEMPTED_WRITE_TO_READONLY_MEMORY | 0xBE | A driver tried to write to protected memory |
THREAD_STUCK_IN_DEVICE_DRIVER | 0xEA | A driver got stuck waiting for the hardware |
WDF_VIOLATION | 0x10D | A driver built on the Windows framework failed |
DRIVER_OVERRAN_STACK_BUFFER | 0xF7 | A driver wrote outside its memory space |
BUGCODE_USB_DRIVER | 0xFE | Error in a USB driver |
APC_INDEX_MISMATCH | 0x1 | A driver left internal tasks out of order |
DRIVER_CORRUPTED_EXPOOL | 0xC5 | A driver corrupted system memory |
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY | 0xFC | A driver tried to run protected memory |
REFERENCE_BY_POINTER | 0x18 | A driver miscounted a system object |
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL | 0xD5 | A driver used memory it had already freed |
RAM (7)
They point to corrupted data in memory. A driver can cause them, but if they repeat with different codes, test the RAM.
| Code | Number | What it means |
|---|---|---|
MEMORY_MANAGEMENT | 0x1A | Serious memory management error |
PAGE_FAULT_IN_NONPAGED_AREA | 0x50 | Windows looked for data in memory and did not find it |
BAD_POOL_HEADER | 0x19 | Damaged system memory |
PFN_LIST_CORRUPT | 0x4E | Damaged internal memory list |
KERNEL_MODE_HEAP_CORRUPTION | 0x13A | Damaged internal system memory |
FAULTY_HARDWARE_CORRUPTED_PAGE | 0x12B | Memory damaged by a hardware fault |
UNEXPECTED_KERNEL_MODE_TRAP | 0x7F | The processor raised an error Windows could not catch |
Hard drive or SSD (8)
Windows could not read or write what it needed on the drive. If the drive is old or making noise, copy your files first.
| Code | Number | What it means |
|---|---|---|
INACCESSIBLE_BOOT_DEVICE | 0x7B | Windows cannot access the drive it is installed on |
KERNEL_DATA_INPAGE_ERROR | 0x7A | Windows could not read data from the drive |
KERNEL_STACK_INPAGE_ERROR | 0x77 | Windows could not read system data from the drive |
NTFS_FILE_SYSTEM | 0x24 | Error in the drive's file system |
UNMOUNTABLE_BOOT_VOLUME | 0xED | Windows could not open the system partition |
UNEXPECTED_STORE_EXCEPTION | 0x154 | Unexpected error in Windows compressed memory |
CRITICAL_PROCESS_DIED | 0xEF | An essential Windows process stopped |
CRITICAL_OBJECT_TERMINATION | 0xF4 | An essential system process ended |
Graphics card (4)
The graphics card or its driver stopped responding. They usually appear while gaming or when changing resolution.
| Code | Number | What it means |
|---|---|---|
VIDEO_TDR_FAILURE | 0x116 | The graphics card stopped responding |
VIDEO_SCHEDULER_INTERNAL_ERROR | 0x119 | Serious error in graphics scheduling |
VIDEO_DXGKRNL_FATAL_ERROR | 0x113 | The DirectX graphics kernel detected an error |
VIDEO_MEMORY_MANAGEMENT_INTERNAL | 0x10E | Error managing the graphics card memory |
CPU, motherboard and power (7)
The hardware reported an error it could not correct, or power management failed. Check temperatures, overclocking and the BIOS.
| Code | Number | What it means |
|---|---|---|
WHEA_UNCORRECTABLE_ERROR | 0x124 | The hardware reported an error it could not correct |
CLOCK_WATCHDOG_TIMEOUT | 0x101 | A CPU core stopped responding |
MACHINE_CHECK_EXCEPTION | 0x9C | The CPU detected a hardware error |
INTERNAL_POWER_ERROR | 0xA0 | Serious power management error |
ACPI_BIOS_ERROR | 0xA5 | The BIOS does not meet the power standard (ACPI) |
NMI_HARDWARE_FAILURE | 0x80 | Hardware failure |
HYPERVISOR_ERROR | 0x20001 | The hypervisor (Windows virtualization) failed |
Windows files and kernel (5)
Internal parts of Windows are damaged or modified. Repairing the system files is usually the first step.
| Code | Number | What it means |
|---|---|---|
BAD_SYSTEM_CONFIG_INFO | 0x74 | The Windows registry is damaged |
CRITICAL_STRUCTURE_CORRUPTION | 0x109 | A protected part of the system was modified |
KERNEL_SECURITY_CHECK_FAILURE | 0x139 | Windows found damaged internal data |
SECURE_KERNEL_ERROR | 0x18B | Serious error in the Windows secure kernel |
WINLOGON_FATAL_ERROR | 0xC000021A | An essential sign-in process failed |
When it is a hardware problem
- The code changes every time (one day
MEMORY_MANAGEMENT, anotherIRQL_NOT_LESS_OR_EQUAL): it is often the RAM. Test it with Windows Memory Diagnostic (search for "mdsched" in Start). - It only happens while gaming or under load: check temperatures and the power supply. Is my CPU temperature normal? compares your reading with the official maximum for your model, and the PSU calculator tells you whether yours is enough.
- Drive codes (
KERNEL_DATA_INPAGE_ERROR,INACCESSIBLE_BOOT_DEVICE,NTFS_FILE_SYSTEM): back up your files before trying anything else. - It keeps happening on a fresh Windows install with no extra programs: then it is hardware. The safest route is a diagnosis with known-good test parts.
If your PC also does not start, or starts with a black screen, see laptop turns on but the screen is black.