Friday, March

Fix CRITICAL_PROCESS_DIED With 0x000000ef Error Code

Please follow and like us:
Pin Share

I’m running Home windows 10 build 10074 on my small desktop computer. Home windows 10 is a good experience until today after i had a BSOD (Blue Screen Of Death Of Dying) all of a sudden after i was watching a relevant video. The mistake code was CRITICAL_PROCESS_DIED without any more information. I let Home windows complete its dump taking process and also the computer restarted fine with no problems.

Used to do an investigation on CRITICAL_PROCESS_DIED and learned that it had been associated with some very important Home windows procedure that couldn’t read or write in to the memory/pagefile. To begin with we will have to see more information associated with CRITICAL_PROCESS_DIED error.

With this, I made use of BlueScreenView utility to determine details about the machine dump files contained in the pc. Just run BlueScreenView and it’ll demonstrate the most recent BSODs as well as their information.

BlueScreenView dump view

Within my dump view, it states ntoskrnl.exe did something which caused the pc to shutdown abruptly. Now there might be several reasons of the crash. Let’s discuss a number of them to ensure that it’s simpler for all of us to trobleshoot and fix the issue.

This BSOD can result from a software or hardware failure. The hardware can failure could be associated with hard disk, memory or processor. Make certain these elements of the PC are running fine. The program failure could be caused because of corrupted/malfunctioning Home windows NT Kernel motorists or a 3rd party software which interacts directly with Home windows Kernel.

An anti-virus or perhaps a firewall is a good example of software which communicate with NT Kernel. Try uninstalling your security software and find out in case your system starts running correctly again. Otherwise, only then do we will have to run the machine file checker to make certain all of the system files of Home windows are intact as well as in original condition.

For running the machine file checker, do as instructed below:

  • Start your computer in Safe Mode (Shift F8 during PC startup)
  • Visit Advanced Repair Options -> Trobleshoot and fix -> Advanced Options -> Home windows Startup Settings
  • Select Restart to restart the pc
  • The PC will begin with advanced startup options. You will have to select Safe Mode to begin your computer in Safe Mode
  • Open command prompt with administrative rights and run the next command:
  • sfc /scannow

Make certain you have cellular phone DVD from the form of Home windows you’re running. The machine file checker may request the DVD whether it finds any issues with the installed system files. Hopefully this can repair the problem. It has fixed my problem and i’m not seeing the BSOD again since that time.

If you’re still getting issues with your Home windows 8.1 or Home windows 10 computer, do tell us your unique problem to ensure that we are able to solve the issue based on your needs.

Please follow and like us:
Pin Share