How to Fix CRITICAL_PROCESS_DIED in Windows 10/11 (6 Proven Fixes)

Getting a CRITICAL_PROCESS_DIED blue screen on Windows? This crash means a core Windows process stopped running and the system could not recover. Windows forces a restart the moment it detects this, with no warning and no way to save what you were doing.

Unlike hardware-only errors, this one points at a Windows process that died unexpectedly. That process could have been killed by corrupted system files, a bad driver, a failed update, or in some cases, failing hardware underneath it all.

This guide covers the most effective fixes in order from quickest to most thorough. Most people solve it by Fix 2 or Fix 3. If the error (0x000000EF) started right after a Windows update, go straight to Fix 4.

What This Error Means at a Glance

A Windows system process stopped unexpectedly and could not be restarted.
Most common causes: corrupted system files, a bad driver update, or a failed Windows update.
Less common causes: failing RAM, a dying hard drive or SSD, or malware targeting system files.
This is different from most blue screens because it always involves a process Windows itself depends on.
Affects Windows 10 and Windows 11. More common after major Windows updates or new driver installs.

Error Type

BSOD / System Process

Root Cause

Files / Drivers / Updates

Affects

Windows 10 / 11

Difficulty

Beginner to intermediate

Time to Fix

10 min – several hours

Table of Contents

Video: How to Fix CRITICAL_PROCESS_DIED on Windows

Watch the full fix walkthrough for CRITICAL_PROCESS_DIED on Windows 10 and 11, covering the SFC scan, driver rollback, Windows Update removal, and RAM test steps shown below.

What Causes CRITICAL_PROCESS_DIED?

This error has several possible causes. Knowing which one fits your situation helps you skip straight to the right fix. Check the list below before working through the numbered steps.

Corrupted System Files (Most Common)

Core Windows files that system processes depend on can be corrupted by a bad update, a sudden power loss, or a forced shutdown at the wrong moment. When a critical process tries to load a broken file, it dies and takes the whole system down.

Bad or Outdated Drivers

A driver running in kernel space (the core of Windows) can crash a critical process if it behaves incorrectly. GPU drivers, chipset drivers, and storage drivers are the most common offenders. If the error started after a driver update, rolling it back is often the fastest fix.

Failed or Interrupted Windows Update

A Windows update that did not finish cleanly can leave system files in a broken state. This is one of the most common triggers for CRITICAL_PROCESS_DIED appearing suddenly on a PC that was working fine. Rolling back or uninstalling the update often resolves it immediately.

Faulty RAM

Bad memory can cause a critical process to read or write corrupted data, which kills the process. RAM problems tend to produce random crashes with no obvious pattern. If all software fixes fail, testing your RAM is the next step.

Failing Hard Drive or SSD

When Windows reads a system file from a drive with bad sectors or hardware errors, the file read can fail and crash the process depending on it. This is more common on older spinning drives but can happen on SSDs nearing the end of their life.

Malware

Some malware targets Windows system processes directly, either replacing them or injecting code that causes them to crash. If your PC picked up an infection recently and software tests come back clean, a deep malware scan is worth running.

How to Fix CRITICAL_PROCESS_DIED

Work through these fixes in order. Most people are done by Fix 3 or Fix 4.

Do a Clean Restart and Check for Startup Conflicts

Before anything else, rule out a one-time glitch and third-party software conflicts. A full shutdown and clean boot takes five minutes and sometimes resolves the error entirely.

Step 1. Do a full shutdown (not restart): click Start, hold Shift, and click Shut down. Wait 30 seconds, then power on. This clears the fast startup cache that a regular restart leaves in place.
Step 2. If the crash comes back, open System Configuration by pressing Windows key + R, typing msconfig, and pressing Enter.
Step 3. Go to the Services tab. Check Hide all Microsoft services, then click Disable all. Click OK and restart.
Step 4. If the crashes stop with third-party services disabled, re-enable them one group at a time to find the conflict. Once found, uninstall or update that software.

Tip: Security software (antivirus, VPN clients, firewall tools) runs deep in the system and is one of the most common third-party triggers for this error. If you installed new security software recently, try disabling it first.

🛠️ Tip: Want a faster way? Try a trusted repair utility like Malwarebytes Premium to automatically fix broken Windows components.

Run SFC and DISM to Repair System Files

Corrupted system files are the single most common cause of CRITICAL_PROCESS_DIED. SFC (System File Checker) scans Windows files and replaces damaged ones. DISM repairs the Windows image that SFC pulls replacement files from. Run both, in this order.

Step 1. Click Start, type cmd, right-click Command Prompt, and select Run as administrator.
Step 2. Type sfc /scannow and press Enter. Wait for it to finish. This takes 10 to 20 minutes. Do not close the window.
Step 3. Once SFC completes, run this DISM command: DISM /Online /Cleanup-Image /RestoreHealth
Step 4. Restart your PC when both scans finish, then monitor for crashes.

If SFC says it cannot repair files: Run the DISM command first to restore the Windows image, then run SFC again. DISM needs an internet connection to download replacement files from Microsoft.

Update or Roll Back Device Drivers

A driver running incorrectly in the core of Windows can bring down a critical process. If the error started after a driver update, roll it back immediately. If your drivers are old, updating them is worth trying before going further.

Step 1. Right-click the Start button and select Device Manager.
Step 2. Look for any devices with a yellow warning icon. Right-click them and select Update driver.
Step 3. For GPU drivers, go to the NVIDIA, AMD, or Intel website and download the latest driver for your graphics card. Install it directly from the manufacturer rather than through Windows Update.
Step 4. If the error started after a specific driver update, right-click the device in Device Manager, select Properties, open the Driver tab, and click Roll Back Driver.
Step 5. Restart after any driver change and monitor for crashes.

Clean GPU driver reinstall: If you suspect a corrupt GPU driver, download DDU (Display Driver Uninstaller) from Wagnardsoft, boot into Safe Mode, run DDU to strip the old driver completely, then restart and install a fresh driver from the manufacturer’s site.

Uninstall a Recent Windows Update or Use System Restore

If CRITICAL_PROCESS_DIED appeared right after a Windows update, removing that update is often the fastest fix. System Restore takes your PC back to a saved state before the problem started, without affecting your personal files.

Try System Restore first if you have restore points available.

Search for System Restore in the Start menu and open it. Choose a restore point dated before the error started. System Restore does not delete your personal files, but it will uninstall apps and drivers installed after that date.

Step 1 (Uninstall a specific update). Go to Settings, then Windows Update, then Update History. Click Uninstall updates at the top. Find the most recent update, right-click it, and select Uninstall.
Step 2. Restart your PC after uninstalling the update and check if the error comes back.
Step 3. If the crashes stop but Windows tries to reinstall the same update automatically, go to Windows Update settings and use Pause updates to give yourself time to investigate. Check the Microsoft update catalog for known issues with that update before allowing it back.

Note: Do not leave Windows Update paused permanently. Security patches protect against real threats. Once you confirm which update caused the problem, check Microsoft’s support pages for a known fix or replacement patch.

Test Your RAM for Errors

Faulty RAM can cause a critical process to crash by feeding it corrupted data. RAM problems tend to produce random crashes at unpredictable times. If all software fixes have failed, test your memory before looking at anything else hardware-related.

Step 1 (Quick test). Press Windows key + R, type mdsched, and press Enter. Choose Restart now and check for problems. Windows will reboot and run the memory test automatically.
Step 2 (Thorough test). Download MemTest86 from memtest86.com, write it to a USB drive using the included tool, boot from the USB, and let it run for at least two full passes. One pass takes roughly 30 to 90 minutes depending on how much RAM you have.
Step 3. If MemTest86 reports errors, try removing one RAM stick at a time and re-running the test to find the faulty stick. Replace any stick that fails.
Step 4. Even if RAM passes all tests, try reseating the sticks. Power down, remove each one, and firmly press them back into the slots. A loose connection can produce intermittent crashes that look exactly like software problems.

Check Your Hard Drive or SSD for Errors

A drive that is starting to fail can cause system file reads to return bad data, which kills whatever process was using that file. Check drive health before concluding the problem is RAM or something deeper.

Step 1. Open This PC, right-click your main drive (usually C:), and select Properties.
Step 2. Go to the Tools tab and click Check under Error Checking. Let Windows scan the drive.
Step 3. Download CrystalDiskInfo (free). It reads the drive’s health data directly and flags drives that are starting to fail. A result of “Caution” or “Bad” means the drive needs to be replaced soon.
Step 4. If the drive shows any “Bad” health sectors, back up your data immediately and replace the drive before doing anything else.

Quick Checklist: What to Try First

Fix	Time Needed	Best If
Clean restart and check startup conflicts	5 – 10 min	Error is new, happened once or twice
SFC and DISM scan	15 – 30 min	Any situation — always try this first
Update or roll back drivers	10 – 20 min	Error started after a driver update
Uninstall Windows update or System Restore	15 – 30 min	Error started right after a Windows update
RAM test (MemTest86)	1 – 3 hours	Random crashes with no obvious trigger
Check drive health	10 – 20 min	PC is old, slow to boot, or making clicking sounds

Still Getting CRITICAL_PROCESS_DIED? Advanced Steps

Read the minidump file to identify the exact process

Every BSOD creates a small crash log called a minidump. Open Event Viewer (search in Start), go to Windows Logs, then System, and look for Critical errors near the crash time. You can also use WhoCrashed (free tool from Resplendence) to read minidump files in plain language. It will usually name the exact process or driver that caused the crash, which tells you exactly where to focus.

Run a malware scan

Malware that targets system processes can produce this exact error. If no hardware test has turned up a problem and SFC found nothing, run a full scan before going further. Windows Defender is a solid start. For a deeper scan that also checks for corrupted registry entries and hidden infections, Malwarebytes Premium is worth running.

🔧 Tip: If Windows Defender is already running, a second-opinion scan from Malwarebytes Premium can catch threats that Defender misses, especially rootkits that hide inside system processes.

Boot into Safe Mode to isolate the cause

Safe Mode loads Windows with only the minimum required drivers and services. If the crashes stop in Safe Mode, a third-party driver or service is the cause. Restart your PC and press F8 (or hold Shift while clicking Restart and navigating to Troubleshoot, Advanced Options, Startup Settings) to access Safe Mode. From there, use Device Manager to roll back or uninstall the problem driver.

Check for BIOS and firmware updates

Motherboard manufacturers release BIOS updates that improve hardware stability and fix known issues with certain CPUs and RAM configurations. Find your motherboard model (printed on the board or listed in System Information under “BaseBoard Product”), visit the manufacturer’s support site, and check for a newer BIOS version. Follow their flashing instructions carefully. A power cut during a BIOS update can make the board unable to boot, so only do this on a stable power connection.

Reset Windows as a last resort

If every software fix has failed and hardware tests come back clean, a Windows reset (Settings, System, Recovery, Reset this PC) with the “Keep my files” option reinstalls Windows while leaving your personal files in place. This fixes deeply corrupted system files that SFC and DISM cannot reach. If crashes continue after a clean install, the fault is hardware and you will need to isolate and replace the failing component.

Frequently Asked Questions

What does CRITICAL_PROCESS_DIED mean on Windows?

It means a core Windows process stopped running unexpectedly and the system could not recover. Windows protects itself by forcing a restart when this happens. Common causes include corrupted system files, a bad driver, a failed Windows update, or faulty RAM. It is different from most blue screens because it always points at a process Windows itself depends on, not just an app or game.

Is CRITICAL_PROCESS_DIED caused by hardware or software?

It can be either. Software causes (corrupted system files, bad drivers, failed Windows update) are more common and usually fixable. Hardware causes (failing RAM, a dying hard drive or SSD) are less common but will keep producing the error until the hardware is replaced. Running SFC and DISM first rules out software causes before you start opening your PC.

Can a Windows update cause CRITICAL_PROCESS_DIED?

Yes. A failed or interrupted Windows update can corrupt core system files, which triggers this blue screen. If your error started right after an update, roll it back using System Restore or uninstall the update from Windows Update history. Then run SFC and DISM to repair any file damage.

Will CRITICAL_PROCESS_DIED delete my files?

No. The blue screen itself does not delete or damage your files. Windows forces a restart to protect the system. However, if the underlying cause is a failing hard drive or SSD, your data is at risk from the hardware problem itself. Back up your files before testing hardware.

Can malware cause CRITICAL_PROCESS_DIED?

Yes. Malware can corrupt or replace core system files and drivers, triggering this blue screen. If hardware tests come back clean and SFC does not find corruption, run a full malware scan before assuming the problem is deeper hardware failure.

How do I stop CRITICAL_PROCESS_DIED from happening again?

Fix the root cause. Run SFC and DISM, update or roll back drivers, uninstall any recent Windows updates that triggered it, and test your RAM and drive health. If the error only started after installing new software or a driver, that is almost certainly the cause. Remove it and monitor for crashes.

Is CRITICAL_PROCESS_DIED fixable without reinstalling Windows?

In most cases, yes. SFC and DISM repair corrupted system files without reinstalling. Updating or rolling back drivers and uninstalling bad Windows updates fix the majority of cases. A full Windows reinstall is only needed when system files are too damaged to repair and no other fix works.