Game causes PC to randomly Blue Screen with CRITICAL_PROCESS_DIED

If I leave the game open overnight theres pretty much a 100% chance that my game will cause me to bluescreen with the error code "CRITICAL_PROCESS_DIED". Only happens while I have PSO2 NA open. Also seems to happen faster with higher graphics settings.

Sometimes this will happen after a few hours too, but it happens guaranteed the longer I have the game open. I've even had it happen while playing 3 times now.

Check your computer's error logs. It will tell you what process died and that can be used to help identify the problem for the developers to fix. It could also just be a case of running out of RAM and the system cutting a required process in order to free up RAM.

This post is deleted!

Yeah, just checked this now. svchost.exe died. It appears that it's being killed by Gameguard....

Here's the last minidump file that I have being read through WinDbg.

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffff928ffa2694c0, 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:
------------------

ETW minidump data unavailable

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1S0N1RS

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 8

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 78

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  ef

BUGCHECK_P1: ffff928ffa2694c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

ERROR_CODE: (NTSTATUS) 0xc2240c0 - <Unable to get error code text>

CRITICAL_PROCESS_REPORTGUID:  {b2970ac3-3b93-468e-afe0-2117476d478d}

IMAGE_NAME:  npggNT64.des

MODULE_NAME: npggNT64

FAULTING_MODULE: 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:  
ffffe386`72e2f838 fffff805`16acb6c9 : 00000000`000000ef ffff928f`fa2694c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffe386`72e2f840 fffff805`169ecd27 : ffff928f`fa2694c0 fffff805`16288065 ffff928f`fa2694c0 fffff805`162880e0 : nt!PspCatchCriticalBreak+0x115
ffffe386`72e2f8e0 fffff805`16870330 : ffff928f`00000000 00000000`00000000 ffff928f`fa2694c0 ffff928f`fa2694c0 : nt!PspTerminateAllThreads+0x17b06b
ffffe386`72e2f950 fffff805`1686ff59 : ffffffff`ffffffff ffffe386`72e2fa80 ffff928f`fe5770c0 00000000`00000f01 : nt!PspTerminateProcess+0xe0
ffffe386`72e2f990 fffff805`163d3c15 : ffff9280`000002ec ffff9280`0c2240c0 ffff928f`fa2694c0 00007ffc`e0eecb68 : nt!NtTerminateProcess+0xa9
ffffe386`72e2fa00 00007ffd`0333c5f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000fa`769fef68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`0333c5f4


STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c2240c0_npggNT64.des!_IMAGE_npggNT64.des

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {40ffc060-4628-b581-063b-6dff96494a12}

Followup:     MachineOwner

If I'm not mistaken, npggNT64 is gameguard.

@Theuberclips That process is nProtect GameGuard. It shouldn't be killing a critical Windows process, though, which is what SVChost is. The only reason it should be killing it is if there is something that it is doing that it shouldn't be. Typically, this would only occur if a virus took it over, but Microsoft may have altered it in a recent update to where it works in a way GameGuard doesn't expect it to. The first step to rule out a potential virus would be to open a Command Prompt as an admin and use the command "sfc /scannow". If a critical windows component got modified, it should reacquire it automatically with that scan.

Looks like it repaired "something" except the log file at the end said nothing was repaired. Confusing. I'll update later if something changed.

I also reinstalled Gameguard stuff through PSO2 tweaker, as apparently this same issue existed a few years back for some people on JP and that's how they fixed it. I'll see if it happens again later, as I have to basically AFK in casino for titles anyways.