- The Critical process died issue appears when a critical component of Windows detects that data has been modified when it should not have been.
- A possible solution is to run an SFC scan using a command-line tool from your OS.
- You can also restore your system with the help of a dedicated third-party solution.
- Uninstalling the latest Windows updates might also do the trick and fix this problem.
BSoD errors are some of the most annoying errors in Windows. Various factors can trigger BSoD errors, including hardware and software issues.
In this article, we’re going to talk about the BSoD issues caused by the Critical process died error in Windows 10.
So, if you’re facing this error, follow the troubleshooting steps listed in this article to fix the problem.
The Critical process died issue is basically caused when a critical component of Windows detects that data has been modified when it should not have been.
This element could be a bad driver, a memory error, etc. Most of the time, this error occurs all of a sudden when users are working on their PCs.
Fortunately, there are a couple of ways to fix this issue so stick with us and check all the solutions below to fix the Critical process died BSoD.
There are many instances where this error may occur. This troubleshooting guide will show you how to fix this annoying issue in the following instances:
- Critical Process Died after update
- This error occurs shortly after users installed the latest Windows updates on their PCs or upgraded their OS.
I own a Lenovo S-510p laptop. I recently tried upgrading to Windows 10. I am currently using the Windows 8.1 – 64 Bit.
The Download finished fully and installation started, but at around 55% of installation, the system crashed due to a Critical Process Died Error.
- Critical Process Died after sleep
- Sometimes, this error occurs when users wake their PCs from sleep. Instead of being able to resume work, they can’t actually use their devices.
Every time I wake up my computer, I get a BSoD saying that a CRITICAL PROCESS DIED
- Critical Process Died after login
- Some users may be able to type their username and password in order to login, but after 30 seconds, the screen goes blue and this error code appears.
- Critical Process Died after installing the Creators Update
- This error did not affect many users when they upgraded to the Anniversary Update. On the other hand, thousands of users encountered this problem after upgrading to the Creators Update.
- Critical Process Died while gaming
- If you’re a gamer, you must be familiar with this error. It affects gamers quite frequently.
Been running my comp that I bought and seem to get an issue during gaming. The screen goes blue and comes up with the error of CRITICAL PROCESS DIED. It happens when I am gaming only and never at any other time.
- Critical Process Died Windows 10 loop
- This error may sometimes trigger reboot loops, preventing users from actually using their PCs.
Issue: 60 min loop. everything runs fine but I get the CRITICAL PROCESS DIED message on a blue screen and the system reboots. always 60 mins after the previous reboot.
- Critical Process Died Unexpected Store Exception
- The Unexpected Store Exception error occurs quite rarely, but nevertheless it’s a severe issue, as this user reports:
BSoD unexpected store exception – critical process died
Hi, i’ve got 2 BSoD errors since i upgraded to 10. Before that my notebook was fine without a crash. I can’t work and is extremely frustrating to use it.
- Critical Process Died after overclock
- If you decide to overclock your PC to enhance gaming performance, you should also know that this change may triggered BDoD issues.
- Critical Process Died on startup
- Users report that this problem may also occur the very moment they boot up their computer. A few seconds after they press the power button, the error code appears on the screen. This usually happens before the log in box appears.
- Critical Process Died Surface Pro 4
- This error affects Surface devices as well. However, judging by user reports, it appears that it’s prevalent for Surface Pro 4 devices.
- Critical Process Died Server 2012 r2
- If you recently got this error message on Windows Server 2012 R2, you’re not the only. Here’s how one user describes this issue:
I am running Windows Hyper-V Server 2012 R2 (Server Core) on three servers. […] A few weeks ago one of the systems seemed to be rebooting regularly. After connecting a monitor I saw a BSoD with a message Critical Process Died. I’m not 100% certain of this, but these BSoD reboot problems seemed to have started shortly after getting a recent automatic update(s)?
- Critical Process Died Asus, Toshiba, Lenovo, Dell
- this error affects all devices, irrespective of manufacturer. However, it appears that it occurs quite rarely on HP computers.
We hope that the following troubleshooting steps will prove useful in most of the cases listed above if not all.
How can I fix the Critical process died error in Windows 10?
1. Run an SFC scan
- Type cmd in the Windows search tab and click on Run as administrator to start Command Prompt with full privileges.
- Enter the following line, and press enter:
- Wait for the process to finish (it will take a few minutes).
- Restart your computer.
Running an SFC scan is one of the most cliché solutions for Windows-related problems, but unfortunately, it doesn’t always get the job done.
However, in this case, it may actually be helpful if fixing Critical process died error. To run SFC scan, do the previous steps.
See if the Critical process died error still causes BSoDs. If not, you’re good to go. If BSODs still occur, try some of the following solutions.
Do you find it complicated to use System File Checker? If so, you can learn to use it like a pro by using our comprehensive guide.
2. Run System Restore
- Go to Settings, click on Update & Security and click on Recovery under the left pane.
- Click on Get Started under Reset this PC and choose Keep my files.
- Follow the on-screen instructions to complete the reset.
If the Critical Process Died error started appearing recently, use the System Restore option to restore the previous configuration. If that doesn’t work, you can always reset your system by doing the previous steps.
The manual process doesn’t work every time and it sometimes can be tricky. It’s a lot easier to restore your system by using a dedicated, third-party tool.
The solution recommended below can solve this problem automatically in no time and it works so make sure you try it on your PC.
- Download and install Restoro.
- Launch the application.
- Wait for the software to identify stability issues and possible corrupted files.
- Press Start Repair.
- Restart your PC for all the changes to take effect.
3. Uninstall the latest updates
- Go to Settings and navigate to Update & Security.
- Scroll down and select the View update history button.
- Click on Uninstall Updates.
- Select the update(s) that you want to uninstall and click Uninstall.
Some users found out that the latest Windows 10 updates actually cause the Critical process died error, and to fix it, you just need to remove the problematic update.
Cumulative updates consist of all previously released updates. When Microsoft releases a new cumulative update and you download it, you’ll also receive an update you had to uninstall because it caused BSoDs.
4. Download the latest driver updates
Bad drivers, or drivers that wrongly use memory could also cause the Critical process died Windows 10 error.
Head to Device Manager, and make sure that absolutely all drivers are up to date, and compatible with Windows 10.
Important driver updates, like graphics card or sound card drivers, are also delivered through Windows Update.
All your drivers need to be updated, but doing it manually is very annoying, so we suggest doing it automatically.
An automated updating tool will help you to avoid permanent damage to your PC caused by downloading and installing the wrong driver versions.
5. Clean boot your computer
- Type System Configuration in the search box and hit Enter.
- On the Services tab select the Hide all Microsoft services check box and click Disable all.
- Click on Open Task Manager.
- On the Startup tab in Task Manager select all items and click Disable.
- Close Task Manager.
- On the Startup tab of the System Configuration dialog box, click OK and restart your computer.
A clean boot starts Windows by using a minimal set of drivers and startup programs making it perfect for troubleshooting.
6. Run a full system antivirus scan
- Go to Start, type defender and select Windows Security.
- In the left-hand pane, select the Shield icon.
- In the new window, click the Advanced scan option.
- Click on Scan options.
- Check the Full scan option and click the Scan now button to launch a full system malware scan.
Malicious software can also change your system files. It doesn’t necessarily have to be a dangerous virus, even spyware or adware can damage your system files.
You can use Windows’ built-in antivirus, Windows Defender, or third-party solutions. Some third-party antivirus programs such as the one recommended below are ideal for virus removal.
6. Check your disk for errors
- Start Command Prompt as administrator and type the chkdsk C: /f command followed by Enter (replace C with the letter of your hard drive partition).
- As a quick reminder, if you do not use the /f parameter, chkdsk displays a message that the file needs to be fixed, but it does not fix any errors.The chkdsk D: /f command detects and repairs logical issues affecting your drive.
- To repair physical issues, run the /r parameter as well.
Sometimes you can fix Critical Process Died simply by running a chkdsk scan from Command Prompt. To do that, follow the steps above.
If you don’t know how to work with Command Prompt, we’ve got an excellent guide that will help you understand it like a pro.
7. Run DISM to fix Windows 10’s system image
7.1 Run DISM using Command Prompt
- Open Command Prompt as an Administrator.
- Type the following command: DISM /Online /Cleanup-Image /RestoreHealth
- Hit Enter to run the command.
- Wait for it to perform the scan. The process can take up to 10 minutes to complete, sometimes even longer.
- After the DISM scan is completed, restart your computer.
7.2 Run DISM using a bootable media
- Mount your Windows 10 .iso file by double-clicking it.
- Open Command Prompt or PowerShell as administrator.
- Check for system health by running these commands:
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /checkhealth
dism /online /cleanup-image /restorehealth
- Run this command:
DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:SourcesInstall.wim:1/LimitAccess
Replace X with the drive letter where your Windows 10 ISO is mounted and proceed with the steps as indicated above.
We hope that this article helped you to fix the Critical process died Windows 10 error. Use the comment section below to let us know which solution worked for you.