Skip to content
PCTestHub
Guide · Windows errors

Blue Screen in Windows: What to Do and What Each Stop Code Means

Why the blue screen appears, how to read the stop code, Microsoft's steps if it keeps happening and what 50 codes mean, grouped by cause.

In this guide

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:

CauseShare
Third-party driver code70%
Hardware issues10%
Microsoft code5%
Unknown (the memory is too corrupted to analyze)15%
Source: Microsoft Learn, "Advanced troubleshooting for Stop error or blue screen error issue", read on November 19, 2026.

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 .sys file: 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) or C:\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 (0x0000000A or 0xA).

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:

  1. 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.
  2. If it does not start properly, use safe mode. From there you can do the rest of the steps.
  3. 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.
  4. Free up disk space. Microsoft recommends keeping 10% to 15% of the system drive free.
  5. Install updates from Settings › Windows Update › Check for updates.
  6. Repair the Windows files with DISM /Online /Cleanup-Image /RestoreHealth and then sfc /scannow, in Command Prompt as administrator. They are explained in Windows repair commands.
  7. 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.

CodeNumberWhat it means
IRQL_NOT_LESS_OR_EQUAL0xAA driver used memory it should not have
DRIVER_IRQL_NOT_LESS_OR_EQUAL0xD1A driver accessed invalid memory
SYSTEM_SERVICE_EXCEPTION0x3BAn internal system function failed
KMODE_EXCEPTION_NOT_HANDLED0x1EA system component raised an error nobody caught
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED0x7EA system thread failed with no handler
DPC_WATCHDOG_VIOLATION0x133A driver took too long to respond
DRIVER_POWER_STATE_FAILURE0x9FA driver failed while sleeping, shutting down or waking up
BAD_POOL_CALLER0xC2A driver requested memory incorrectly
DRIVER_VERIFIER_DETECTED_VIOLATION0xC4Driver Verifier found an error
ATTEMPTED_WRITE_TO_READONLY_MEMORY0xBEA driver tried to write to protected memory
THREAD_STUCK_IN_DEVICE_DRIVER0xEAA driver got stuck waiting for the hardware
WDF_VIOLATION0x10DA driver built on the Windows framework failed
DRIVER_OVERRAN_STACK_BUFFER0xF7A driver wrote outside its memory space
BUGCODE_USB_DRIVER0xFEError in a USB driver
APC_INDEX_MISMATCH0x1A driver left internal tasks out of order
DRIVER_CORRUPTED_EXPOOL0xC5A driver corrupted system memory
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY0xFCA driver tried to run protected memory
REFERENCE_BY_POINTER0x18A driver miscounted a system object
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL0xD5A driver used memory it had already freed
Meanings based on Microsoft's bug check code reference (checked on November 19, 2026).

RAM (7)

They point to corrupted data in memory. A driver can cause them, but if they repeat with different codes, test the RAM.

CodeNumberWhat it means
MEMORY_MANAGEMENT0x1ASerious memory management error
PAGE_FAULT_IN_NONPAGED_AREA0x50Windows looked for data in memory and did not find it
BAD_POOL_HEADER0x19Damaged system memory
PFN_LIST_CORRUPT0x4EDamaged internal memory list
KERNEL_MODE_HEAP_CORRUPTION0x13ADamaged internal system memory
FAULTY_HARDWARE_CORRUPTED_PAGE0x12BMemory damaged by a hardware fault
UNEXPECTED_KERNEL_MODE_TRAP0x7FThe processor raised an error Windows could not catch
Meanings based on Microsoft's bug check code reference (checked on November 19, 2026).

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.

CodeNumberWhat it means
INACCESSIBLE_BOOT_DEVICE0x7BWindows cannot access the drive it is installed on
KERNEL_DATA_INPAGE_ERROR0x7AWindows could not read data from the drive
KERNEL_STACK_INPAGE_ERROR0x77Windows could not read system data from the drive
NTFS_FILE_SYSTEM0x24Error in the drive's file system
UNMOUNTABLE_BOOT_VOLUME0xEDWindows could not open the system partition
UNEXPECTED_STORE_EXCEPTION0x154Unexpected error in Windows compressed memory
CRITICAL_PROCESS_DIED0xEFAn essential Windows process stopped
CRITICAL_OBJECT_TERMINATION0xF4An essential system process ended
Meanings based on Microsoft's bug check code reference (checked on November 19, 2026).

Graphics card (4)

The graphics card or its driver stopped responding. They usually appear while gaming or when changing resolution.

CodeNumberWhat it means
VIDEO_TDR_FAILURE0x116The graphics card stopped responding
VIDEO_SCHEDULER_INTERNAL_ERROR0x119Serious error in graphics scheduling
VIDEO_DXGKRNL_FATAL_ERROR0x113The DirectX graphics kernel detected an error
VIDEO_MEMORY_MANAGEMENT_INTERNAL0x10EError managing the graphics card memory
Meanings based on Microsoft's bug check code reference (checked on November 19, 2026).

CPU, motherboard and power (7)

The hardware reported an error it could not correct, or power management failed. Check temperatures, overclocking and the BIOS.

CodeNumberWhat it means
WHEA_UNCORRECTABLE_ERROR0x124The hardware reported an error it could not correct
CLOCK_WATCHDOG_TIMEOUT0x101A CPU core stopped responding
MACHINE_CHECK_EXCEPTION0x9CThe CPU detected a hardware error
INTERNAL_POWER_ERROR0xA0Serious power management error
ACPI_BIOS_ERROR0xA5The BIOS does not meet the power standard (ACPI)
NMI_HARDWARE_FAILURE0x80Hardware failure
HYPERVISOR_ERROR0x20001The hypervisor (Windows virtualization) failed
Meanings based on Microsoft's bug check code reference (checked on November 19, 2026).

Windows files and kernel (5)

Internal parts of Windows are damaged or modified. Repairing the system files is usually the first step.

CodeNumberWhat it means
BAD_SYSTEM_CONFIG_INFO0x74The Windows registry is damaged
CRITICAL_STRUCTURE_CORRUPTION0x109A protected part of the system was modified
KERNEL_SECURITY_CHECK_FAILURE0x139Windows found damaged internal data
SECURE_KERNEL_ERROR0x18BSerious error in the Windows secure kernel
WINLOGON_FATAL_ERROR0xC000021AAn essential sign-in process failed
Meanings based on Microsoft's bug check code reference (checked on November 19, 2026).

When it is a hardware problem

  • The code changes every time (one day MEMORY_MANAGEMENT, another IRQL_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.

Leer en español