How To Resolve The BSOD Error CRITICAL_PROCESS_DIED Windows 10

You usually see the BSOD error CRITICAL_PROCESS_DIED when Windows 10 has detected that certain system files are being modified in a certain way which they should not.  You might also see this error after your machine did not shut down correctly, such as your machine lost power when it was turned on.  The below screen will appear



When this error appears you will need to manually restart your machine.  Sometimes your system will be stuck in a loop and will not go past this CRITICAL_PROCESS_DIED blue screen of death,  If this is the case jump to the "Fixing Looping BSOD Error CRITICAL_PROCESS_DIED" section below.

Below is a video I created on youtube which shows you how to resolve this issue



Fixing Random BSOD Error CRITICAL_PROCESS_DIED Crashes


If you are lucky to be able to boot to windows 10 desktop and to only see this blue screen of death randomly we should be able to resolve the issue quickly.  We will need to do two things.  The issue will most likely be some sort of an issue with a device driver or a corrupt file system.

Step 1 - Fix Corrupted System Files To fix the corrupted file system files click the start menu and type in CMD then right click on "Command Prompt" and select "Run as administrator"




Then in the command prompt type in chkdsk /r /i you will get prompted if you want to run the scan at next system restart, type Y and hit enter.  Now restart your machine and let the chkdsk run.



Step 2 - Update Device Drivers  Next we will need to update the device drivers on your system. When I want to update the drivers for my machine I usually go to google and type in "Machine model drivers" for example  HP Elitebook 820 G1 Drivers and will click on this page which lists all the latest drivers for my system.

I recommend to download all drivers and install them. If you don't want to download all drivers make sure you update the following drivers.
  • Display Adapter
  • Network 
  • Chipset

After you have updated the drivers reboot your machine.

Step 3 - Update Your Systems BIOS On the same page as where you located the driver updates you should see a update for your BIOS,  Download this update and run it and reboot your machine.

Fixing Looping BSOD Error CRITICAL_PROCESS_DIED Crashes


If your windows 10 system crashes to the BSOD error critical_process_died on every system startup do not panic, We can fix this issue easily.

Insert your Windows 10 install DVD and boot to it. If you dont have a windows 10 DVD you can create a bootable windows 10 USB drive by following this guide or watch the video below



Now perform each step detailed below,  At the end of every step reboot your machine to see if the issue has been resolved, If the issue is resolved you dont need to perform the next step.  The steps we will need to perform are
  • Perform a CHKDSK
  • Startup Repair
  • Run a SFC Scan

Perform a CHKDSK - Now you have booted to the Windows 10 install media, On the first screen you get click on "troubleshoot"



Next click on "advanced options"

Then Click on "command prompt"



Now in the black window type in chkdsk /r /i you will get prompted if you want to run the scan at next system restart, type Y and hit enter.  Now restart your machine and let the chkdsk run. Hopefully your machine will boot to the windows 10 desktop and we will not see the BSOD Error CRITICAL_PROCESS_DIED.  If you do get a BSOD again continue to the next step.

Startup Repair - Boot to the windows 10 install media then click troubleshoot > advanced options > Startup repair.  Follow the prompts and let it scan your machine, the scan will automatically find and fix any issues which are on your system.

Run a SFC Scan - Boot to the windows 10 install media then click troubleshoot > advanced options > command prompt.  In the command prompt type in sfc /scannow and hit enter. Let the scan run, When it has finished reboot your machine.
How To Resolve The BSOD Error CRITICAL_PROCESS_DIED Windows 10 How To Resolve The BSOD Error CRITICAL_PROCESS_DIED Windows 10 Reviewed by Citrix Tips on 08:52 Rating: 5

No comments: