Categories About Us Contact Us Become a Member

Critical Process Died on Windows 11 and 10: How to Fix the Blue Screen

Critical Process Died is a blue screen that says Windows lost a system process it cannot work without. Start with updates, then repair system files and test your memory and disk. If Windows will not reach the desktop, use the Windows Recovery Environment path below.

By Neeraj Singh ~7 min Updated Nov 2026 Checked against Microsoft Support
Error message
Your device ran into a problem and needs to restart. Stop code: CRITICAL_PROCESS_DIED
Summary

CRITICAL_PROCESS_DIED is bug check 0x000000EF. Windows shows it when a critical system process ends or its state is corrupted or damaged. Remove new hardware, install Windows updates and check Device Manager for drivers with a yellow exclamation point first. Then repair system files with SFC and DISM, check the disk with chkdsk and test your memory with Windows Memory Diagnostic. If Windows will not start, use Safe Mode, Startup Repair or System Restore from the recovery environment. Back up your files before you select Reset this PC.

What Critical Process Died means

Critical Process Died is the on-screen name for bug check 0xEF with the stop code CRITICAL_PROCESS_DIED. Windows crashes on purpose when a critical system process ends.

Microsoft says this happens when the state of the process is corrupted or damaged. Windows then questions its own integrity and stops to protect itself.

Microsoft lists csrss.exe, wininit.exe, logonui.exe, smss.exe, services.exe, conhost.exe and winlogon.exe as built in critical processes. Parameter 1 on the bug check is the process object.

Windows 11 and Windows 10 show the same stop code and share the same fixes.

Common causes of Critical Process Died

A critical Windows process with a corrupted or damaged state, which Microsoft names as the trigger.
Recently added hardware, drivers or services that Microsoft tells you to remove or update.
A device marked with a yellow exclamation point in Device Manager.
Damaged system files that SFC can find and repair.
A BIOS or firmware version that has an update available from your PC maker.

✓ How to fix it

Method 1

Check Hardware, Drivers and Windows Updates First

1Shut down your PC, remove any new hardware you added before the blue screen started and restart. Microsoft lists this as its first step for stop code errors.
2Right-click the Start button and select Device Manager. Look for any device marked with a yellow exclamation point, right-click it and select Update driver. Steps are on the Microsoft Support Device Manager driver page.
3If the blue screen began after a driver update, right-click the device and open Properties. Open the Driver tab and select Roll Back Driver. Restart if Windows asks.
4Go to Settings, Windows Update and select Check for updates. Install everything it finds and restart.
5Check your PC maker site for a BIOS or firmware update, because Microsoft lists this in its bug check steps. Microsoft also suggests keeping some free space on your drive.
6Read the full list on the Microsoft Support stop code guide.
Method 2

Uninstall a Recent Windows Update

1Open Settings and select Windows Update.
2Under More options, select Update history.
3Under Related settings, select Uninstall updates.
4Choose the update that arrived just before the blue screen and select Uninstall. Microsoft notes that some updates cannot be uninstalled.
5Restart your PC. Details are on the Microsoft Support page on uninstalling a Windows update.
Method 3

Repair System Files With SFC, DISM and chkdsk

1Open Command Prompt as administrator.
2Check and repair protected system files. Microsoft lists this command in its bug check steps.
sfc /scannow
3Check the Windows image next and repair it if DISM finds damage. The Microsoft Learn repair a Windows image page explains both commands.
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
4Check the disk for errors. The /r switch finds bad sectors and includes the /f fixes. Windows asks to schedule the check for the next restart because your system drive is in use.
chkdsk C: /r
5Type Y, restart your PC and let the check finish. Large drives take a long time. Switch details are on the Microsoft Learn chkdsk page.
Method 4

Test Your Memory With Windows Memory Diagnostic

1Save your work and close your apps.
2Press Windows key + R, enter this and select OK.
mdsched
3Select Restart now and check for problems (recommended). Windows restarts and starts the test on its own.
4Press F1 on the test screen if you want to change Test Mix from Standard to Extended, then press F10.
5Sign in after the restart and read the result notification. Steps are on the Microsoft Support Windows Memory Diagnostic steps.
Method 5

Fix Critical Process Died When Windows Will Not Start

1Let the PC fail to start a few times. Microsoft says Windows enters the Windows Recovery Environment on its own after it fails to start correctly more than once.
2If you can reach the sign in screen, hold Shift and select Restart from the power menu. Settings also works through System, Recovery and Restart now next to Advanced startup.
3Select Troubleshoot and then Advanced options. Choose Startup Repair to fix common problems that stop Windows from starting.
4For Safe Mode, select Startup Settings and Restart then press 4 or F4. Press 5 or F5 for Safe Mode with Networking. Then use Methods 1 to 4 from Safe Mode.
5If a recent update caused the crash, select Uninstall Updates in Advanced options.
6Have your BitLocker recovery key ready, because Microsoft says encrypted devices need it for some recovery tools. See the Microsoft Support Windows recovery environment page and the Microsoft Support Windows startup settings page.
Method 6

Use System Restore or Reset this PC

1Open Troubleshoot and Advanced options in the recovery environment and select System Restore. This rolls back system files and settings and leaves personal files alone.
2Choose a restore point from before the blue screen started and follow the prompts.
3Back up your files to another drive before the next step. Microsoft says a reset removes apps and settings.
4If nothing else works, select Troubleshoot and then Reset this PC. You can keep your personal files or remove everything.
5Compare both choices on the Microsoft Support recovery options page before you continue.

Critical Process Died is bug check 0xEF and Microsoft says it happens when a critical process is corrupted or damaged. Remove new hardware, update Windows and drivers, then use SFC, DISM, chkdsk and Windows Memory Diagnostic. If Windows will not start, use Startup Repair, Safe Mode or System Restore and back up your files before a reset.

Frequently asked questions

What does Critical Process Died mean?
Critical Process Died is the blue screen for bug check 0x000000EF. Windows stops when a critical system process ends or its state is corrupted or damaged.
How do I fix Critical Process Died on Windows 11?
Remove new hardware, install Windows updates and update or roll back drivers in Device Manager. Then repair system files with SFC and DISM, check the disk with chkdsk and test your memory. System Restore and Reset this PC come last.
How do I fix it when Windows will not start?
Microsoft says Windows opens the recovery environment on its own after it fails to start correctly more than once. Select Troubleshoot, then Advanced options, then Startup Repair. Safe Mode and System Restore sit in the same menu.
Which processes does the error name?
Microsoft lists csrss.exe, wininit.exe, logonui.exe, smss.exe, services.exe, conhost.exe and winlogon.exe as built in critical processes. A developer can also set a service to restart the computer when it stops.
Will Reset this PC delete my files?
Microsoft says you can keep your personal files or remove everything. Both choices remove apps and settings. Back up your files first.
Can a Windows update cause Critical Process Died?
Yes, a recent update can leave a system process damaged. Go to Settings, Windows Update, Update history and Uninstall updates to remove it. Some updates cannot be uninstalled.
Do I need BitLocker recovery key in the recovery environment?
Microsoft says encrypted devices need the BitLocker recovery key to use certain recovery tools. Find the key before you start.

Still not working?

If the blue screen keeps returning, read Inaccessible Boot Device and Kernel Security Check Failure for related stop codes. See Windows Errors and Fixes for more guides. Still seeing the blue screen? Send us your stop code and the steps you tried and we add the missing fix.

Was this fix helpful? Thanks for your feedback!