Windows Stop Code (BSOD) Fix Guide: Critical Process Died, Memory Management, 0xc000021a & More

Understanding Windows Stop Codes

A Windows stop code — colloquially called a Blue Screen of Death (BSOD) — is a kernel-level halt triggered when Windows detects a condition from which it cannot safely recover. The screen displays a QR code, a sad face emoji, a human-readable stop code name (e.g., CRITICAL_PROCESS_DIED), and a hexadecimal error code (e.g., 0x000000EF). Understanding both parts is essential for diagnosis.

Stop codes are written to the Windows Event Log and to a memory dump file located at C:\Windows\Minidump\. Analyzing these dumps with WinDbg or the free tool WhoCrashed often reveals the exact driver or module at fault.

The Most Common Windows Stop Codes and Their Meanings

0xc000021a / c000021a / 21a (Critical Session Fatal Error) This stop code means the Windows Session Manager (smss.exe) or Client/Server Runtime (csrss.exe) has failed fatally. Common causes: corrupt Visual C++ Redistributables, a failed Windows Update, incompatible third-party software touching system processes, or a corrupt user profile. Variants you may see: windows stop code 0xc00021a, windows stop code oxc000021a, windows stop code 000021a, windows stop code 021a.

MEMORY_MANAGEMENT (0x0000001A) Indicates a serious error in the Windows memory manager. Causes include faulty RAM sticks, corrupt page file, outdated firmware, or failing storage drives. Related codes: PFN_LIST_CORRUPT, BAD_POOL_CALLER, FAULTY_HARDWARE_CORRUPTED_PAGE.

CRITICAL_PROCESS_DIED (0x000000EF) A critical system process (such as winlogon.exe, lsass.exe, or services.exe) has terminated unexpectedly. Usually caused by malware, corrupt system files, or a failed Windows Update.

INACCESSIBLE_BOOT_DEVICE (0x0000007B) Windows cannot access the disk containing the operating system at startup. Causes: SATA/AHCI mode changed in BIOS, corrupt or missing storage controller driver, damaged MBR/BCD, or a failing SSD/HDD. Also seen as windows stop code 0x0000007b or boot device inaccessible.

DPC_WATCHDOG_VIOLATION (0x00000133) The DPC (Deferred Procedure Call) watchdog detected a timeout, typically caused by an unresponsive driver — often a NVMe SSD firmware issue, GPU driver, or outdated SSD driver.

KERNEL_SECURITY_CHECK_FAILURE (0x00000139) A kernel data structure integrity check failed. Common culprits: incompatible drivers (especially after a Windows upgrade), overclocked hardware, or corrupt system files.

DRIVER_POWER_STATE_FAILURE (0x0000009F) A driver failed to complete a power state transition (sleep/hibernate). Usually a GPU, USB, or network adapter driver issue.

TDR_FAILURE / nvlddmkm.sys The GPU driver stopped responding and failed to recover. Almost always an NVIDIA driver issue (nvlddmkm.sys), but can also be AMD (atikmpag.sys). Solutions: clean driver reinstall using DDU, lower GPU clock speeds, check GPU temperatures.

NTFS_FILE_SYSTEM / ntfs.sys File system corruption on an NTFS volume. Usually triggered by sudden power loss, a failing drive, or bad sectors.

CRITICAL_SERVICE_FAILED A service marked as critical failed to start during boot. Often caused by corrupt system files or failed driver initialization.

Step 1: Identify Your Stop Code

If the system BSODs and reboots before you can read the code:

1. Disable automatic restart: Right-click This PC → Properties → Advanced system settings → Startup and Recovery → uncheck Automatically restart.
2. Check Event Viewer: Press Win+R, type eventvwr.msc. Navigate to Windows Logs → System and filter for Critical/Error events near the crash time.
3. Check minidump files: Install WhoCrashed or open WinDbg and load files from C:\Windows\Minidump\.

Step 2: Boot into Safe Mode or Windows Recovery Environment (WinRE)

If Windows won't start normally, boot into WinRE:

• Interrupt boot 3 times (force shutdown during Windows logo) to trigger Automatic Repair.
• Or boot from a Windows 10/11 USB and select Repair your computer.

From WinRE, open Command Prompt for all repair commands below.

Step 3: Run System File Checker and DISM

For stop codes related to corrupt system files (CRITICAL_PROCESS_DIED, KERNEL_SECURITY_CHECK_FAILURE, 0xc000021a, NTFS_FILE_SYSTEM, CRITICAL_SERVICE_FAILED):

sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

If running from WinRE, SFC requires the Windows drive letter (e.g., D: if Windows is not on C: in recovery):

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Step 4: Repair Boot Configuration (for 0xc000021a, INACCESSIBLE_BOOT_DEVICE, 0x0000007b)

From WinRE Command Prompt:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

If bootrec /fixboot returns "Access is denied", run:

bcdboot C:\Windows /s C: /f ALL

For GPT disks with EFI partition, first assign a drive letter to the EFI partition:

diskpart
list disk
sel disk 0
list part
sel part 1
assign letter=Z
exit
bcdboot C:\Windows /s Z: /f UEFI

Step 5: Check and Repair RAM

For MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, BAD_POOL_CALLER, NMI_HARDWARE_FAILURE, FAULTY_HARDWARE_CORRUPTED_PAGE:

1. Run Windows Memory Diagnostic: Press Win+R, type mdsched.exe, choose restart and check.
2. For deeper testing, use MemTest86 (bootable USB) and run at least 2 full passes.
3. If errors found: reseat RAM sticks, test each stick individually, replace faulty stick(s).
4. Reset the page file: Right-click This PC → Advanced → Performance Settings → Advanced → Virtual Memory → set to system managed.

Step 6: Fix Driver-Related Stop Codes

For TDR_FAILURE, nvlddmkm.sys, DRIVER_POWER_STATE_FAILURE, DPC_WATCHDOG_VIOLATION, netio.sys:

1. Boot into Safe Mode.
2. Use Display Driver Uninstaller (DDU) in Safe Mode to fully remove GPU drivers.
3. Download latest driver from NVIDIA/AMD official site and install clean.
4. For network drivers: Device Manager → Network Adapters → right-click → Update driver.
5. Check for Windows Update pending driver updates: Settings → Windows Update → Advanced → Optional Updates.

For WDF_VIOLATION: often caused by a USB or Bluetooth driver. Disconnect all external devices, then reinstall drivers one by one to isolate.

Step 7: Post-Update BSODs

If the stop code started after a Windows Update:

1. Boot to Safe Mode.
2. Uninstall the update: Settings → Windows Update → View Update History → Uninstall Updates.
3. Or use DISM: dism /online /get-packages to find the update KB number, then dism /online /remove-package /packagename:<name>.
4. Use System Restore: rstrui.exe from Safe Mode or WinRE.

Step 8: Check Storage Health

For NTFS_FILE_SYSTEM, UNMOUNTABLE_BOOT_VOLUME, INACCESSIBLE_BOOT_DEVICE:

chkdsk C: /f /r /x

In WinRE:

chkdsk D: /f /r

Also check S.M.A.R.T. data using CrystalDiskInfo (free) to confirm drive health.

Step 9: Nuclear Option — Windows Reset

If all steps above fail:

• Settings → System → Recovery → Reset this PC → Keep my files (or Remove everything).
• This reinstalls Windows while optionally preserving personal files.
• Always back up data first using a live Linux USB if Windows won't boot.