Reader-supported: we earn a commission on some links, at no extra cost to you. How this works
Windows ErrorsGuide

How to Fix the Critical Process Died Blue Screen

Critical Process Died (0x000000EF) means a system-critical Windows process stopped. Here are the real causes and step-by-step fixes for the blue screen.

The Critical Process Died blue screen (stop code 0x000000EF) means a process Windows needs to keep running suddenly stopped, so Windows shut down to protect itself. The common causes are corrupt system files, a faulty or outdated driver, bad memory or disk sectors, or malware. You fix it by booting into Safe Mode or Recovery and repairing the files, drivers, or hardware behind it.

Why this happens

Certain background processes, such as those handling sessions and system services, are marked critical. If one of them is corrupted or blocked from working, Windows cannot continue safely and triggers this stop error.

  • Corrupted Windows system files after a bad update, power loss, or failed install.
  • A buggy, outdated, or incompatible device driver (often display, storage, or chipset).
  • Failing RAM or bad sectors on the drive that damage what is loaded into memory.
  • Malware that alters or deletes system processes.
  • Recently installed software that hooks deep into Windows.

Is this normal?

No. It is a protective crash, not routine behavior. A single occurrence can be a one-off glitch, but repeated crashes always mean an underlying file, driver, or hardware issue that needs fixing.

Does it cause any problems?

Yes. It forces an immediate restart, so unsaved work is lost, and if it loops it can stop you from using the PC. Frequent crashes can also point to failing hardware that will get worse over time.

How to fix or check it

  1. Restart and see if it happens again. If it boots normally, note what you did just before the crash.
  2. If it loops, enter the Recovery Environment (force shutdown during boot three times) and choose Startup Settings, then boot into Safe Mode.
  3. Open Command Prompt as administrator and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth to repair system files.
  4. Run chkdsk /f /r C: to check the disk for errors and let it schedule on the next restart if asked.
  5. Uninstall any driver or program you added just before the crashes started. Update remaining drivers from the maker's website, especially display and chipset drivers.
  6. Run a full malware scan with Windows Security or a trusted scanner.
  7. Test your memory with the built-in Windows Memory Diagnostic (type mdsched.exe and restart) to rule out bad RAM.
  8. If it began after a recent update, use Recovery to Uninstall Updates or perform a System Restore to a point before the problem.

Frequently asked questions

Is Critical Process Died a hardware or software problem?

It can be either. Corrupt files and bad drivers are the most common causes, but failing RAM or a failing drive can also trigger it. Work through the software fixes first, then test hardware.

Will I lose my files fixing this?

No. Running SFC, DISM, chkdsk, driver updates, and System Restore does not delete personal files. Only a reset or reinstall risks your data, so keep those as a last resort.

Why does it only happen sometimes?

Intermittent crashes often mean a driver that only fails under certain conditions, or hardware that is starting to fail. The memory and disk tests help catch causes that appear at random.

More in this topic

More in Windows Errors

See the full guide →