How to Fix Critical Process Died Error in Windows?

In addition to the programs you actively use, Windows runs some critical OS processes like Windows Initialization process (wininit.exe), Session Manager Subsystem (smss.exe), or Client Server Runtime Process (csrss.exe) in the background. These core system tasks maintain OS stability, manage memory, hardware communication, and keep the system secure. When one of them stops working or is forced to close, Windows runs into a CRITICAL_PROCESS_DIED (0x000000EF) Blue Screen of Death Error. 

Microsoft’s own bug-check documentation confirms that the error occurs when a critical system process terminates, prompting Windows to stop and restart rather than continue operating in a compromised state. In some cases, Windows may crash before it can even reach the desktop, leaving the computer caught in a recurring boot loop.

Common Causes Behind the “Critical Process Died” Error

The CRITICAL_PROCESS_DIED stop code is not tied to one specific issue. Some of the most common reasons behind this error include:

• Corrupted Windows system files: Sudden shutdowns, power interruptions, or disk-related errors can damage essential system files.
• Faulty or incompatible drivers: Outdated or corrupted graphic, storage, chipset, or network drivers can halt critical Windows operations.
• Defective or failing RAM: Faulty memory modules can lead to data corruption, instability, and unexpected system crashes.
• Failing storage drives: Bad sectors or other storage problems can corrupt Windows files and prevent important processes from running properly.
• Malware infection: Certain type of malware can interfere with, modify, or inject code into critical Windows processes.
• Problematic Updates: Incomplete or faulty updates can cause driver conflicts, compatibility issues, or system instability.
• Overclocking: Excessive CPU, GPU, or RAM overclocking can make the system unstable and cause some processes to fail.

Methods to Fix Critical Process Died Error

When the crash happens before Windows finishes loading, Automatic Repair never kicks in on its own, but you can force it. Here’s how: interrupt the boot process three times in a row. Windows will then automatically switch to WinRE (Windows Recovery Environment) and launch Automatic Repair.

• Power on your PC.
• As soon as you see the spinning dots or the manufacturer logo, hold the power button for 10 seconds to force a shutdown.
• Repeat two more times.
• On the third attempt, Windows will display Preparing Automatic Repair, followed by Diagnosing your PC.
• On the Choose an option window, click Troubleshoot.

• Click Advanced options.

Once you have successfully entered the Windows RE, go to Command Prompt to perform the next troubleshooting step. Also, if your drive is encrypted with BitLocker, it may interfere with the repair process so you should temporarily suspend it, not turn off. This will keep your data encrypted while letting repair tools access the drive without interruption.

• Execute the following command via Command Prompt (replace C with your drive letter):

manage-bde -protectors -disable C:

BitLocker will resume automatically after the next successful restart, or you can re-enable it manually from the same BitLocker menu once the PC is stable.

1.      Run SFC and DISM

Since missing, outdated, or corrupted system files can trigger the CRITICAL_PROCESS_DIED, run DISM first to repair the Windows component store, then run SFC to scan system files and replace the damaged ones. Order matters here as SFC pulls its replacement files from the component store that DISM repairs.

• Open Command Prompt as administrator.
• Execute the following command: 

DISM /Online /Cleanup-Image /CheckHealth

• If that flags a problem, run the following commands, one after another:

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

• Then execute the following command:

sfc /scannow

• Wait for the scan to finish.

2.      Disable Overclocking

As stated earlier, overclocking your CPU for improved performance may trigger the Critical Process Died error on your computer. You should consider disabling the overclocking settings to effectively resolve this issue.

• Enter WinRE as described above.
• On the Choose an option window, click Troubleshoot.

• Click UEFI Firmware Settings.

• Your computer will now boot into BIOS.
• Navigate to the Advanced tab, and select Performance.
• Now find the Overclocking option and disable it (steps may vary by motherboard manufacturer).
• Press the Esc key and choose Save and Exit.

3.      Run Startup Repair

If 0xEF error is keeping you stuck in a boot loop, use Startup Repair to check for problems that may be preventing the system from booting normally. This tool scans important startup files and attempts to repair issues that may have occurred during the stalled restore process.

• Boot into WinRE.
• On the error screen, click Advanced options.
• Now go to Troubleshoot > Advanced options > Startup Repair.

• Enter your admin password and follow the prompts to proceed.
• Once the process is complete, Restart your PC.

4.      Run the Hardware and Device Troubleshooting Tool

Windows includes a built-in automated utility that is designed to scan your PC and identify any hardware-related conflicts. It automatically resolves any issues with your computer’s drivers or other physical components like USB ports, keyboards, and other attached peripherals.

• Press Win + R to launch the Run dialog box.
• Enter the following command:

msdt.exe -id DeviceDiagnostic

• Click OK.

• Click Next and follow the instructions to let it scan your PC for errors and automatically resolve them.

5.      Update Device Drivers

You need to check all your device drivers are up to date, as outdated drivers can also be responsible for error code 0x000000EF (CRITICAL_PROCESS_DIED). You can update the drivers with the following steps:

• Press Windows + X and select Device Manager. 
• Look for any device with a yellow warning icon.
• Right-click on the driver.
• Choose Update driver.
• Select Search automatically for drivers on the following prompt.
• Windows will look for the latest compatible driver for your device. If any driver version is available, download it, and reboot your system.

• If the crash happened right after a driver update, right-click that particular driver and go to Properties > Driver.
• Click Roll Back Driver.

6.      Run CHKDSK Scan

A corrupted or failing hard drive with bad sectors can also produce this error. Run CHKDSK scan to scan your disk for errors and repair it.

• Open Command Prompt as administrator.
• Type chkdsk E: /f /r and hit Enter. (Replace E: with your hard drive letter).
• Close the window once completed and reboot your system.

Note: On a drive with bad sectors, CHKDSK marks them so Windows stops using them, which can make data stored there inaccessible. Back up the drive before running CHKDSK. If you’ve already lost data, use reliable professional data recovery software to recover it.

7.      Perform a Clean Boot

A clean boot starts Windows with only essential drivers and startup programs, which helps you find whether background software is triggering the error.

• Press Windows + R, type msconfig, and press Enter to open System Configuration.
• On the Services tab, tick Hide all Microsoft services and click Disable all.

• On the Startup tab, click Open Task Manager, select each startup item, and click Disable.

• Close Task Manager, click OK in System Configuration.
• Restart your PC.

If the error disappears in a clean boot, re-enable services and startup items a few at a time to pinpoint the culprit, then update or remove it.

8.      Scan Your PC for Malware

If your PC is malware-infected, you may run into Critical Process Died error. Use Windows Defender Antivirus software to scan your system for malware or viruses. You can run this tool to check for viruses on your system and remove them with the recommended instructions.

• Press Win + S and open Windows Security.
• Click Virus & threat protection > Scan options.

• Click Windows Defender Offline Scan > Scan Now.

Let the process complete. The Windows Defender will scan your computer for existing threats.

9.      Check RAM

Memory corruption is one of the primary reasons behind CRITICAL_PROCESS_DIED (0x000000EF) Blue Screen of Death Error. Run the Windows Memory Diagnostic tool to quickly get past RAM-related problems.

• Press Win + R to launch the Run dialog box.
• Type mdsched.exe and press Enter.

• Click Restart now and check for problems (recommended).
• The PC will restart and automatically check for memory faults.

Once the scan is done, you’ll see the scan results on the screen. If it shows several RAM issues and instructions on how to fix them, follow the instructions. Else, replace your faulty RAM. You can additionally run memtest86 to test the RAM.

10.  Uninstall a Recent Windows Update

If error 0x000000EF started right after a Windows update or you’re seeing it as a Windows Update error, a buggy update is the likely trigger, and removing it often restores stability.

• Press Windows + I to open Settings. On Windows 11, select Windows Update. On Windows 10, click Update & Security > Windows Update.
• Go to Update history.
• Click Uninstall updates.

• Find the most recent update (sort by the Installed on date), select it, and click Uninstall.
• Restart your PC and check.

If the error is gone, pause updates briefly so the same patch doesn’t reinstall immediately, and wait for Microsoft to ship a fix.

Tip: For an update that fails to install with this error, run the Windows Update troubleshooter (Settings > System > Troubleshoot > Other troubleshooters > Windows Update) before retrying.

11.  Restore Your PC

If you’re not sure about what actually caused the CRITICAL_PROCESS_DIED error, restore Windows to a previous state before the error first appeared.

• Search for Create a restore point and open it.
• A System Properties dialog box will appear.
• Under the System Protection tab, click System Restore.

• Choose a restore point before the CRITICAL_PROCESS_DIED error and click Next.

• Confirm the restore point by clicking Finish and you’re good to go.

How to Recover Files Lost Due to Critical Process Died Error?

If a crash, a failed fix, or a non-booting PC has already cost you files, data recovery software can often get them back. A professional data recovery software can scan drives from a crashed or non-booting Windows PC, and it supports recovery from formatted drives, reset systems, and drives with bad sectors. Always save recovered files to a separate drive, not the one you are scanning, so you do not overwrite data that is still waiting to be recovered.

Tips to Prevent Critical Process Died Error on Your PC

Fixing this error once doesn’t mean it won’t come back. A few habits go a long way toward keeping it from happening again.

• Keep drivers updated, but don’t rush into downloading new ones. Outdated drivers cause plenty of crashes, but so do new ones that haven’t been tested yet. Update your graphics, chipset, and storage drivers regularly, and if you can, wait a few days after a major driver release before installing it.
• Never force a shutdown unless you have to. Cutting power mid-boot or mid-update is one of the fastest ways to corrupt the exact system files this error depends on. If Windows looks frozen, give it a few minutes before you hold down the power button.
• Let Windows updates finish completely. Interrupting an update partway through can leave core system files in a broken, half-updated state. Plug in and stay put until it’s done.
• Run SFC and DISM every so often, not just when something breaks. A quick system file checker every couple of months catches small file corruption before it snowballs into a boot-time crash.
• Keep an eye on your hardware, not just your software. RAM and drives fail gradually, not all at once. Running the Windows Memory Diagnostic and checking your drive’s health status every few months means you catch a failing component while it’s still an inconvenience, not a crisis.
• Stick to signed, trusted drivers. Unsigned or third-party drivers downloaded from random sites are far more likely to conflict with core Windows processes. Get drivers from the manufacturer’s official site whenever possible.
• Back up before big changes. Major Windows updates, new driver installs, or BIOS updates are exactly when this error tends to show up. A quick backup or at minimum, a System Restore point before any of these means a crash cost you time, not data.
• Don’t run two antivirus or security tools at once. Overlapping security software is a common, underrated cause of process conflicts. Pick one, and let Windows Defender handle the rest if you’re not using a third-party suite.

Wrapping Up

The CRITICAL_PROCESS_DIED (0x000000EF) error usually points to a problem with Windows system files, drivers, hardware, or a recent system change. Start by repairing corrupted files and checking drivers, then test your RAM and storage if the crashes continue. If Windows is stuck in a boot loop or you’ve already lost files, prioritize data recovery before attempting repairs that could make the situation worse. With regular backups, hardware checks, and cautious driver and Windows updates, you can also reduce the chances of the error returning.