How to Diagnose & Fix Common Windows BSOD Stop Error Codes

What Triggers a Blue Screen of Death (BSOD)?

A Blue Screen of Death (BSOD)—technically designated as a Windows BugCheck or stop error—occurs when the Windows operating system kernel encounters an unrecoverable condition that jeopardizes data integrity or hardware safety. To prevent data corruption, Windows halts system execution immediately.

While a blue screen can feel alarming, every BSOD prints a specific Stop Code (such as CRITICAL_PROCESS_DIED or 0x0000007E) that identifies the exact subsystem or driver that triggered the crash.

The 5 Most Frequent Stop Codes & Their Fixes

1. MEMORY_MANAGEMENT (Code 0x0000001A)

• Underlying Cause: A fatal fault in the Windows memory management subsystem, usually caused by failing physical RAM sticks, unstable memory overclocks (XMP/EXPO), or bad disk sectors.
• Immediate Fix:
  1. Press Win + R, type mdsched.exe, and select Restart now and check for problems to run the Windows Memory Diagnostic.
  2. If errors are detected, run MemTest86 via a bootable USB drive to isolate the defective memory channel or stick.
  3. Enter BIOS/UEFI and temporarily disable XMP / DOCP memory profiles to test RAM stability at JEDEC base frequencies.

2. CRITICAL_PROCESS_DIED (Code 0x000000EF)

• Underlying Cause: An indispensable Windows kernel background service (such as csrss.exe, smss.exe, or services.exe) unexpectedly terminated.
• Immediate Fix:
  1. Boot into Windows Safe Mode.
  2. Open Administrator Command Prompt and run DISM and SFC:

     DISM.exe /Online /Cleanup-image /Restorehealth
     sfc /scannow

  3. Roll back recently installed Windows Cumulative Updates.

3. IRQL_NOT_LESS_OR_EQUAL (Code 0x0000000A)

• Underlying Cause: A device driver attempted to access a pageable memory address at an illegal Interrupt Request Level (IRQL) that it was not privileged to read.
• Immediate Fix:
  1. Cleanly reinstall GPU drivers using Display Driver Uninstaller (DDU) in Safe Mode.
  2. Update motherboard chipset, Wi-Fi, and audio drivers directly from your motherboard manufacturer’s support portal.

4. INACCESSIBLE_BOOT_DEVICE (Code 0x0000007B)

• Underlying Cause: The Windows boot loader cannot read the system storage partition during startup.
• Immediate Fix:
  1. Enter your motherboard BIOS/UEFI settings.
  2. Check SATA Operation Mode: Ensure it is set to AHCI (or NVMe), not legacy IDE or Intel RST RAID unless explicitly required.
  3. Verify the primary boot drive is prioritized in the UEFI Boot Order list.

5. WHEA_UNCORRECTABLE_ERROR (Code 0x00000124)

• Underlying Cause: Windows Hardware Error Architecture (WHEA) caught an uncorrectable physical hardware error directly from the CPU, PCIe bus, or NVMe drive controller.
• Immediate Fix:
  1. Remove CPU/GPU undervolts and overclocks.
  2. Clean internal dust filters and monitor CPU/GPU thermal temperatures using HWMonitor.
  3. Reseat the GPU in its PCIe x16 slot and ensure power connectors are firmly seated.

How to Analyze Minidump Files with WinDbg

When Windows crashes, it writes a small dump file (.dmp) containing the exact instruction pointer and offending driver name to C:\Windows\Minidump\.

To read these files like an engineer:

1. Download WinDbg (Windows Debugger) from the Microsoft Store.
2. Launch WinDbg as Administrator.
3. Click File > Open Dump File and browse to C:\Windows\Minidump\.
4. Once the dump loads, click the blue hyperlink in the console window that says:

   !analyze -v

5. Scroll down to the MODULE_NAME and IMAGE_NAME lines.
   • If the offending module is nvlddmkm.sys, your Nvidia graphics driver caused the crash.
   • If it is netwtw10.sys, your Intel Wi-Fi adapter driver caused the crash.
   • If it is ntoskrnl.exe, the kernel crashed due to bad RAM or unstable voltages.