Windows 10: Critical_Process_Died almost exactly every 2 hours

  1.    08 Sep 2015 #1

    Critical_Process_Died almost exactly every 2 hours

    Recently we had a rare power outage here, and ever since then almost exactly every 2 hours on the dot I'm getting a BSoD Critical_Process_Died error.

    I've ran memtest, tried the 'system reset', start up repair, sfc /scannow, etc, but nothing has worked so far. I'd rather not reinstall windows completely as that means redownloading a lot of things on a terrible 5mbps connection, so crossing my fingers for some wizard with a solution.

    I have my logs attached below, and a few of the dumps are related to crashes because of a network driver (driver_Irql error), but the rest are all the critical process error (pretty much anything from 9/05 and onward)
      My ComputerSystem Spec

  2. axe0's Avatar
    Posts : 13,723
    Windows 10 Pro
       08 Sep 2015 #2

    Hi kneepel,

    Welcome to the 10forums.

    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.

    1. Uninstall Daemon Tools
    2. Download the SPTD standalone installer and follow these steps:
      • Double click the executable to open it
      • Click on the button shown below

    If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

    The cause of 1 of the crashes is NetLimiter 4, please remove this program or update to version .
    0: kd> lmvm nldrvstart             end                 module name
    fffff801`8a730000 fffff801`8aca8000   nldrv    T (no symbols)           
        Loaded symbol image file: nldrv.sys
        Image path: nldrv.sys
        Image name: nldrv.sys
        Timestamp:        Wed Jun 03 11:44:41 2015 (556ECC89)
        CheckSum:         0001DF58
        ImageSize:        00578000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

      My ComputersSystem Spec

  3.    08 Sep 2015 #3

    axe0 said: View Post
    Hi kneepel,
    Removing Daemon tools didn't change anything.

    Also like I said above....any stop errors caused (driver_irql_less_or_not_equal) have to do with a network driver, and in this case it's unrelated and has been fixed as of yesterday. I need help with the other vast majority of crashes which all have to do with the recent ones with the error 'Critical_Process_Died'. Sorry I couldn't remove the old minidumps, but the program I was recommended to download to create logs and such just puts all my minidumps into a zip and I dont have the debugger to look through all of them to check.
      My ComputerSystem Spec

  4. axe0's Avatar
    Posts : 13,723
    Windows 10 Pro
       08 Sep 2015 #4

    I only have taken a look at the most recent ones, the rest aren't interesting.

    Daemon tools can be a cause of many different BSOD's, because of what it uses.
    If you haven't removed because you don't have it anymore then please follow these instructions

    Critical_Process_Died almost exactly every 2 hours Diagnostic Test Critical_Process_Died almost exactly every 2 hours

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial run driver verifier.

    Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My ComputersSystem Spec

  5.    08 Sep 2015 #5

    I ran verifier up until the blue screen, and then ran again. I can't get it to run for more than 2 hours because of my crashes, but it didn't find any violations.
      My ComputerSystem Spec

  6. axe0's Avatar
    Posts : 13,723
    Windows 10 Pro
       09 Sep 2015 #6

    Please use the tool and upload a new zip file.
      My ComputersSystem Spec

  7.    10 Sep 2015 #7

    Here you go
      My ComputerSystem Spec

  8. axe0's Avatar
    Posts : 13,723
    Windows 10 Pro
       11 Sep 2015 #8

    You probably get the critical_process_died crash, because there is not enough free space in the C partition.
    You need to remove some programs, or other files to increase the free space up to at least 10-15% so windows can do its thing in the background without any problem.

    Disable startup items in taskmanager, those items could interfere with the boot process, give heavy problems because of interfering the process and also increases the boot time.
      My ComputersSystem Spec

  9.    11 Sep 2015 #9

    Cleared 150gb(lol) and ran chkdsk twice.

    Still the same.
      My ComputerSystem Spec

  10. axe0's Avatar
    Posts : 13,723
    Windows 10 Pro
       11 Sep 2015 #10

    Please make sure your CPU drivers are updated.

    Please do the following:

    • Open taskmanager
      • Go to the tab startup
      • disable everything

    • Search msconfig and open it
      • Go to the tab services
      • Check 'hide microsoft services'
      • Uncheck all other services
      • Click apply and click ok

    • Reboot if asked

    See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
      My ComputersSystem Spec


Related Threads
I have an app named "Timer+" which after it is set and finishes makes a loud beeping noise until it is turned off. I can have up to three timers running at the same time. I have discovered if my QUIET HOURS are turned on, then no sound will be...
Hi, I upgraded my computer to Windows 10 from 8.1. After around a week of using Windows 10, each time I turned on my computer, I get a blue screen saying that the computer will restart. Like in the following picture....
BSOD Repair Loop Critical_Process_Died in BSOD Crashes and Debugging
Hi, I've been wrestling with this problem for last 2 days and I don't seem to be able to find an answer anywhere hence I'm posting here. Firstly, I can't generate the dumpfile as I can't access windows at all. I can't access it through any boot...
I Got BSOD many times while setting up system settings after upgrading from windows 8.1 to 10 The last three times were when clicking on this option: 29404 another behavior that caused the BSOD 29558
Solved Critical_process_died in BSOD Crashes and Debugging
Please Help... memory.dmp 400mb = Probably Caused by ntkrnlmp.exe Absolutely random cause. need to post my dmp?
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:30.
Find Us