How to fix it

CRITICAL_PROCESS_DIED is a blue screen that means a process Windows considers essential stopped running. Windows can't keep going without it, so it halts. The key question is why that process died — and the answer is almost always one of three things: a corrupt driver, a failing disk, or damaged system files.

What it means

Windows keeps a set of protected system processes running (the ones that manage the desktop, the kernel, security, and I/O). If one of them stops, Windows raises CRITICAL_PROCESS_DIED. The message points at the victim; the cause is usually something that killed it — most commonly a driver or a disk error.

Where you'll usually see it

  • After a driver update (especially graphics, chipset, or storage drivers)
  • After installing new software or hardware
  • Randomly, when a hard drive or SSD is failing
  • After a failed Windows Update

Common causes

  • A bad or conflicting driver (the single most common cause)
  • A failing disk with bad sectors or a dying controller
  • Corrupt system files
  • A recent software/driver conflict

Quick fixes (try these first)

  1. Restart — if it was a one-off, you're done. If it recurs, continue.
  2. Unplug non-essential USB devices — a faulty peripheral or its driver can do this.
  3. Boot into Safe Mode (Settings → Recovery → Advanced startup → Startup Settings → Safe Mode) and see if the error still happens there. Safe Mode loads minimal drivers.

Detailed fixes

Uninstall recent software and drivers. In Safe Mode, go to Settings → Apps → Installed apps and remove anything you installed in the last few days. Then in Device Manager, right-click recent devices (graphics, storage, network) → Uninstall device, tick the option to remove the driver, and reboot so Windows reinstalls a clean copy.

Repair system files. From an admin prompt:

`` sfc /scannow ``

If it reports files it couldn't fix:

`` dism /online /cleanup-image /restorehealth ``

then run sfc /scannow again and reboot.

What these do: SFC replaces damaged protected Windows files with clean copies; DISM repairs the underlying component store. Both are non-destructive to your personal files and apps.

Check your disk health. A failing disk is the most common hardware cause. From an admin prompt:

`` chkdsk C: /scan ``

What this does: chkdsk /scan checks the file system and metadata for errors and repairs what it can, without needing a reboot (the older /f requires one). It does not delete your data, but it is good practice to have a backup before running any disk check on a drive that's showing instability. For a real health read, use your drive manufacturer's tool (Crucial Storage Executive, Samsung Magician, WD Dashboard, etc.) and look at the SMART status.

Check the crash dump for the actual driver. If you can boot, open Event Viewer → Windows Logs → System, find the crash, and note the failing driver name. There are also minidump files in C:\Windows\Minidump that a tool like BlueScreenView can read to name the exact module.

When it's safe to ignore

A single CRITICAL_PROCESS_DIED after a rough shutdown can be harmless. It only becomes a real problem when it recurs — that's when you dig into drivers and disk health.

Related errors

  • 0xC000021A — system process terminated / access violation
  • DRIVER_POWER_STATE_FAILURE — a driver failed a power-state request
  • BAD_SYSTEM_CONFIG_INFO — boot configuration missing