The CRITICAL_PROCESS_DIED blue screen appears when Windows loses a system process it depends on and restarts instead of continuing in an unsafe state.
This applies to Windows 10 and Windows 11 PCs, especially when the crash starts after a driver, update, app, or hardware change.
Does This Affect You?
The name sounds like the core Windows process itself is broken, but the trigger is usually outside it: a bad driver, corrupted system file, failed update, damaged storage, or faulty memory. Start with Safe Mode if you cannot reach the desktop, then repair drivers and system files.
Get into Safe Mode if Windows Will Not Boot Normally
Skip this section if you can already use the desktop.
- Interrupt startup three times: when the Windows logo appears, hold the power button for about 10 seconds, then turn the PC on again.
- After the third interrupted boot, open Advanced options from Automatic Repair.
- Choose Troubleshoot > Advanced options > Startup Settings, then click Restart.
- Press 4 or F4 for Safe Mode. Use 5 or F5 if you need networking for downloads.
Once Safe Mode opens, continue with the driver and repair steps below.
Roll Back or Update the Problem Driver
Graphics, network, and storage drivers are frequent triggers for this stop code.
- Right-click Start and open Device Manager.
- Look for yellow warning icons, especially under Display adapters, Network adapters, and storage-related categories.
- Right-click the device and choose Properties.
- On the Driver tab, click Roll Back Driver if it is available.
- If rollback is not available, choose Update driver > Search automatically for drivers.
- Restart and test whether the crash returns.
If you are unsure what changed, check Settings > Windows Update > Update history for driver updates installed around the first crash.
Repair Corrupted System Files
Use SFC and DISM when no single driver stands out.
- Open Command Prompt as administrator.
- Run
sfc /scannowand let it finish. - Run
DISM /Online /Cleanup-Image /RestoreHealth. Keep the PC connected to the internet. - Restart after both commands complete.
If SFC says it found corrupt files but could not fix some of them, run DISM first, then run sfc /scannow again.
More Checks if the Crash Continues
Check Windows Update
Install pending updates from Settings > Windows Update. If the problem started immediately after an update, use Update history > Uninstall updates to remove the latest one and test again.
Test Memory
Search for Windows Memory Diagnostic and choose Restart now and check for problems. Bad RAM can produce this stop code and other random blue screens.
Check the Drive
Open an administrator Command Prompt and run chkdsk C: /f /r. Type Y if Windows asks to schedule it, then restart and let the scan finish.
Reset Windows if Repairs Fail
If the error survives driver rollback, file repair, memory checks, and disk checks, back up your files and consider Reset this PC with Keep my files. This reinstalls Windows while preserving personal files.
Sources
- Microsoft Support: Troubleshoot blue screen errors
- Microsoft Learn: Bug Check 0xEF CRITICAL_PROCESS_DIED
- Microsoft Support: Fix Windows Update errors