Windows 10: CRITICAL_PROCESS_DIED bsod

Discus and support CRITICAL_PROCESS_DIED bsod in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi! I've been having bsod for quite some time now and decided to perform a clean Windows 10 install a few days ago as a last resort. Today it... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Jens De Ceukeleire, Oct 17, 2020.

  1. CRITICAL_PROCESS_DIED bsod


    Hi!



    I've been having bsod for quite some time now and decided to perform a clean Windows 10 install a few days ago as a last resort. Today it happened again..


    I tried to get more information use windbg myself but couldn't find anything informative. Please help!



    ------------------------------------------------------------------------------------------------


    CRITICAL_PROCESS_DIED ef

    A critical system process died

    Arguments:

    Arg1: ffff8c8382b3f200, Process object or thread object

    Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.

    Arg3: 0000000000000000

    Arg4: 0000000000000000



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 3



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-ITI54DI



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 3



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 71



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: ef



    BUGCHECK_P1: ffff8c8382b3f200



    BUGCHECK_P2: 0



    BUGCHECK_P3: 0



    BUGCHECK_P4: 0



    PROCESS_NAME: services.exe



    CRITICAL_PROCESS: services.exe



    ERROR_CODE: NTSTATUS 0x80195080 - <Unable to get error code text>



    CRITICAL_PROCESS_REPORTGUID: {2fb8db57-24b1-4850-91b7-7425478c44e2}



    IMAGE_NAME: ntdll.dll



    MODULE_NAME: ntdll



    FAULTING_MODULE: 0000000000000000



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    STACK_TEXT:

    ffffda0a`612a7938 fffff801`44b06fe2 : 00000000`000000ef ffff8c83`82b3f200 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

    ffffda0a`612a7940 fffff801`449d7d83 : 00000000`00000000 fffff801`44460ea5 00000000`00000002 fffff801`44460dcf : nt!PspCatchCriticalBreak+0x10e

    ffffda0a`612a79e0 fffff801`4484a9b0 : ffff8c83`00000000 00000000`00000000 ffff8c83`82b3f200 ffff8c83`82b3f638 : nt!PspTerminateAllThreads+0x1ee377

    ffffda0a`612a7a50 fffff801`4484a7ac : ffff8c83`82b3f200 00000000`00000000 000000c4`04cffa8c fffff801`4490470a : nt!PspTerminateProcess+0xe0

    ffffda0a`612a7a90 fffff801`44605fb8 : ffff8c83`82b3f200 ffff8c83`80195080 ffffda0a`612a7b80 ffff8c83`82b3f200 : nt!NtTerminateProcess+0x9c

    ffffda0a`612a7b00 00007ff8`7ddac314 : 00007ff8`7de22693 00007ff8`7de51364 000000c4`04cffa50 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

    000000c4`04cfe7c8 00007ff8`7de22693 : 00007ff8`7de51364 000000c4`04cffa50 00000000`00000000 00007ff8`7dd10000 : 0x00007ff8`7ddac314

    000000c4`04cfe7d0 00007ff8`7de51364 : 000000c4`04cffa50 00000000`00000000 00007ff8`7dd10000 00000000`00000004 : 0x00007ff8`7de22693

    000000c4`04cfe7d8 000000c4`04cffa50 : 00000000`00000000 00007ff8`7dd10000 00000000`00000004 00007ff8`7ddb331d : 0x00007ff8`7de51364

    000000c4`04cfe7e0 00000000`00000000 : 00007ff8`7dd10000 00000000`00000004 00007ff8`7ddb331d 00007ff8`7de51364 : 0x000000c4`04cffa50





    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_80195080_ntdll.dll!KiRaiseUserExceptionDispatcher_IMAGE_ntdll.dll



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {6f3fd284-f676-457f-be80-48a34b7d43ab}



    Followup: MachineOwner

    ------------------------------------------------------------------------------------------------


    I uploaded the minidump file here: https://1drv.ms/u/s!ArPFBAiwgxjjgW9swKJEqbKN85oH?e=5rg8W9

    :)
     
    Jens De Ceukeleire, Oct 17, 2020
    #1

  2. Critical_Process_Died BSOD

    Hi,

    In order to resolve your concern, we suggest that you to follow these steps:

    • If you've installed any new apps or devices, uninstall or unplug them and restart your PC.
    • Make sure your PC has the latest updates:
    • Go to the search box.
    • Type Windows Update then Enter.
    • Select Check for updates.
    • In the Settings menu, select Check for updates button.
    • When it's finished, restart your PC.

    You may also check this
    link
    for more troubleshooting steps regarding critical_process_died error message.

    Let us know how it goes.
     
    PreciousLeb, Oct 17, 2020
    #2
  3. NGKH5 Win User
    BSOD Error: CRITICAL_PROCESS_DIED

    My laptop experienced a BSOD with an analysis by "Who Crashed" as follows-

    On Sat 11/10/2018 2:08:03 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\MEMORY.DMP

    This was probably caused by the following module: ntkrpamp.exe (nt!PsSetLegoNotifyRoutine+0x46C)

    Bugcheck code: 0xEF (0xFFFFFFFFA8C97440, 0x0, 0x0, 0x0)

    Error: CRITICAL_PROCESS_DIED

    Bug check description: This indicates that a critical system process died.

    There is a possibility this problem was caused by a virus or other malware.

    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .

    Google query: ntkrpamp.exe CRITICAL_PROCESS_DIED

    Following is a link to my "one drive" BSOD folder with memory.dmp and other files for evaluation:

    Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

    Please advise resolution for the said BSOD. Thanx!
     
    NGKH5, Oct 17, 2020
    #3
  4. Ztruker Win User

    CRITICAL_PROCESS_DIED bsod

    Bsod critical_process_died

    Set Virtual memory to automatic:


    CRITICAL_PROCESS_DIED bsod [​IMG]
     
    Ztruker, Oct 17, 2020
    #4
Thema:

CRITICAL_PROCESS_DIED bsod

Loading...
  1. CRITICAL_PROCESS_DIED bsod - Similar Threads - CRITICAL_PROCESS_DIED bsod

  2. Computer turning off with BSOD "Critical_Process_Died"

    in Windows 10 Gaming
    Computer turning off with BSOD "Critical_Process_Died": I own a ROG Strix Scar 16 gaming computer on Windows 11, and when I shut down or restart my computer, the screen comes up with a blue screen of death with a message saying "Critical process died". I don't really know if I have some sort of malware or virus. But it happens...
  3. Computer turning off with BSOD "Critical_Process_Died"

    in Windows 10 Software and Apps
    Computer turning off with BSOD "Critical_Process_Died": I own a ROG Strix Scar 16 gaming computer on Windows 11, and when I shut down or restart my computer, the screen comes up with a blue screen of death with a message saying "Critical process died". I don't really know if I have some sort of malware or virus. But it happens...
  4. BSOD of CRITICAL_PROCESS_DIED

    in Windows 10 Gaming
    BSOD of CRITICAL_PROCESS_DIED: I am experiencing a CRITICAL_PROCESS_DIED bluescreen during startup and when i unplug my laptop from the charger. It also happened two times randomly during usage. I used a minidump scanner and it says that the BSODs are caused by ntoskrnl.exe, a Windows driver.I can send...
  5. BSOD of CRITICAL_PROCESS_DIED

    in Windows 10 Software and Apps
    BSOD of CRITICAL_PROCESS_DIED: I am experiencing a CRITICAL_PROCESS_DIED bluescreen during startup and when i unplug my laptop from the charger. It also happened two times randomly during usage. I used a minidump scanner and it says that the BSODs are caused by ntoskrnl.exe, a Windows driver.I can send...
  6. BSOD CRITICAL_PROCESS_DIED ntoskrnl.exe

    in Windows 10 Gaming
    BSOD CRITICAL_PROCESS_DIED ntoskrnl.exe: Keeps coming up with CRITICAL_PROCESS_DIED error and KMODE_EXECPTION_NOT_HANDLED .I have checked all drivers as it implicates ntoskernel.exeLink to the dump: https://drive.google.com/drive/folders/1kwAsxomB8fhf0BDA1EuwjxcVUmx8GVl_?usp=drive_linkAny help?...
  7. BSOD CRITICAL_PROCESS_DIED ntoskrnl.exe

    in Windows 10 Software and Apps
    BSOD CRITICAL_PROCESS_DIED ntoskrnl.exe: Keeps coming up with CRITICAL_PROCESS_DIED error and KMODE_EXECPTION_NOT_HANDLED .I have checked all drivers as it implicates ntoskernel.exeLink to the dump: https://drive.google.com/drive/folders/1kwAsxomB8fhf0BDA1EuwjxcVUmx8GVl_?usp=drive_linkAny help?...
  8. CRITICAL_PROCESS_DIED BSOD under GPU load and no dump file created.

    in Windows 10 Software and Apps
    CRITICAL_PROCESS_DIED BSOD under GPU load and no dump file created.: I’m experiencing persistent BSODs under GPU load, specifically during complex compute operations like RealityCapture or certain games. The crash occurs only under heavy GPU usage. No crash occurs in FurMark.My PC specs are:GPU: NVIDIA RTX 4080CPU: Intel Core i7-14700KFRAM: 32...
  9. CRITICAL_PROCESS_DIED BSOD under GPU load and no dump file created.

    in Windows 10 Gaming
    CRITICAL_PROCESS_DIED BSOD under GPU load and no dump file created.: I’m experiencing persistent BSODs under GPU load, specifically during complex compute operations like RealityCapture or certain games. The crash occurs only under heavy GPU usage. No crash occurs in FurMark.My PC specs are:GPU: NVIDIA RTX 4080CPU: Intel Core i7-14700KFRAM: 32...
  10. BSOD Critical_Process_Died

    in Windows 10 Software and Apps
    BSOD Critical_Process_Died: HelloI recently bought a PC with a Gigabyte Motherboard and the first day it worked perfectly. The next day when i started the Pc up and tried to play a game it gave me a BSOD with the message CRITICAL_PROCESS_DIED. Since then ive tried everything. Resetting the PC wich...