Critical Process Died error in Windows 10/8/7

If a critical Windows system process fails to run properly, your operating system will crash and display a Critical Process Died Stop Error 0x000000EF or Blue Screen on your Windows 10/8/7 computer. This happens because the process which was needed to run the Windows operating system ended abruptly for some reason.

There is not much documentation on this on any Microsoft site. A post however simply states that:

The CRITICAL_PROCESS_DIED bug check has a value of 0x000000EF. This indicates that a critical system process died.

critical process died CRITICAL_PROCESS_DIED

CRITICAL_PROCESS_DIED

Now if you receive a CRITICAL_PROCESS_DIED error message, here are some of the things you could try and see.

1] Run the Hardware and Devices Troubleshooter and see if that helps. Run the Driver Verifier Manager and see if it helps troubleshoot, identify & resolve the device driver problems.

2] Run sfc /scannow or System File Checker to check for and replace corrupted system files if any. If you are unable to boot to desktop, you may run System File Checker in Safe Mode or Offline.

3] You may also want to run DISM to repair a corrupt system image.

4] Open Devices Manager and see if any devices are marked with the exclamation point. Update your Drivers and see if that resolves the issue. Did you install any new device or hardware recently? Disable, remove or uninstall it and see if it helps.

5] Perform a Clean Boot. When you start the computer in clean boot, the computer starts by using a pre-selected minimal set of drivers and startup programs. Clean-boot troubleshooting is designed to isolate a performance problem.

6] If the problem started appearing recently, use System Restore to restore your computer back to a good point and see if it makes the problem go away. If it started after you updated your operating system, you may want to stop that particular update from being installed, and report the problem to Microsoft.

7] Disable Sleep and Hibernate in your Power Setting and see if it helps. You will get these settings in Control Panel > All Control Panel Items > Power Options > Edit Plan Settings. Use this process to disable Hibernation if you had earlier enabled it.

8] See in an update to your system BIOS or firmware is available.

9] If you are unable to boot into Windows, you may want to run Startup Repair from the Advanced Startup options.

Once you are able to access the desktop, you may continue with troubleshooting the issue.

If you are unable to boot into Windows or to the Advanced Startup Opions, then you may have to use a Windows installation or recovery disc, to carry out your troubleshooting.

10] Check the System Log in Event Viewer and see if and error messages point you in the direction to troubleshoot.

11] Run the online Windows 10 Blue Screen Troubleshooter from Microsoft is a wizard that is meant to help novice users fix their Stop Errors. It will help you fix this Blue Screen error and offers helpful links along the way.

If nothing helps, check this post which shows you some generic ways on how to troubleshoot Blue Screens in Windows 10.

All the best!

See this post if you receive a Kernel Security Check Failure error in Windows 10.

Download this VPN to secure all your Windows devices and browse anonymously
Posted by on , in Category Windows with Tags
Anand Khanse is the Admin of TheWindowsClub.com, a 10-year Microsoft MVP Awardee in Windows (2006-16) & a Windows Insider MVP. Please read the entire post & the comments first, create a System Restore Point before making any changes to your system & be careful about any 3rd-party offers while installing freeware.

12 Comments

  1. Thank you, very clear and helpful.

  2. Chris Wilson

    I must have missed the part where you explain how to boot into Windows so I can fix the problem that is preventing me from booting into Windows

  3. lipe123

    What a joke article, Windows is not starting and even when doing sfc in repair mode it finds no problems and the issue persists.
    All the other suggestions require windows to be running – which it is not.

  4. Salmando (a.k.a 'Bleh')

    I get so many bsod screens when i first install Windows. While the updates that will install often fix this, the update process often triggers them, which is very frustrating

  5. Sandy

    I tried all the above things, no problems found. Still getting the error. It also getting worse.
    Mine is a Brand new asus laptop
    i5 7th gen
    1TB seagate HDD
    I even completely reinstalled my OS (Win 10 Home)

  6. Ed

    It can also be caused by recently installed software that does not play well with the Creators Update, if it happens to you, think back to what may have been installed recently, uninstall it and see if the problem persists. Happened to me, uninstalled the most recent software installation ( didn’t really need to have it anyway) and the problem went away.

  7. Dunbar Services

    My thoughts exactly.

  8. Shiffy

    Hello, this is happened to me to even after re-install. Did you fix the problem? Plz respond!!

  9. Fred Brooks

    After trying all the scans, registry fixes, etc. etc. I went over to pick up the machine. Opening it up, it was clear that it had never been cleaned. I blew out about a pound of dirt with the leaf blower (after securing the fans), and it has run like a top ever since.

  10. Shaloin

    LOL every one of these suggestions will do nothing but waste peoples time.
    Why are you copy pasting generic troubleshooting steps, this error can be any number of things and NONE of what you posted is aimed at correcting it.
    You can get this when simply trying to hotspot internet from a mac even, its something wrong hardware wise and it might not even be YOUR computers hardware.

    DO NOT DO ANY OF THESE STEPS. Seriously, grow a brain and erase this entire article, thats not troubleshooting

  11. thecavemankevin

    We’ve got an HP consumer tower, it kept failing last week to install the update. We then tried a fresh install of Windows 1709 fall creators update and then tried to install this spring update and it too failed. We then tried the fresh media creation tool with the spring update 1803 built in. It will BSOD when trying to boot into the installation media. I’ve tested the hdd and SSD and ram and tweaked bios settings (and updated bios). Nothing is working. Is there a way to block this f-ing update?

Leave a Reply

Your email address will not be published. Required fields are marked *


2 + 2 =