Question BSOD "Critical_Process_Died" caused by opening two games simultaneously ?

[DimkaTsv]

Looking for help in identifying an underlying trickaroo
BSOD Cause - Just open specific 2 games, don't minimize their windows and wait.
BSOD Proc rate - 100% in around 15 minutes of having these 2 games opened.

System:
CPU - AMD R5 5600X
GPU - AMD RX 6750XT
RAM - 32 GB 3800 16-20-20
SSD - 2x NVME + 1x SSD + 1xHDD
(not that it matters, because from own search it definitely isn't Drive, CPU, GPU or RAM fault)

Link for memory dump (not just mini one, but not full dump either) - https://drive.google.com/file/d/1HsZqrGd2UrdpNYGKx_OayXojxmA0lwSP/view?usp=sharing

Dump log from WinDbg also applied below (in spoiler)
I just want to know, how and what specific driver/app/request causes system that quite consistent and serious memory integrity fail.

Spoiler: Dump log

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffff800b7abe7100, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000, The process object that initiated the termination.
Arg4: 0000000000000000

Debugging Details:
------------------

Page 8063d6 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2687

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2677

    Key  : Analysis.Init.CPU.mSec
    Value: 562

    Key  : Analysis.Init.Elapsed.mSec
    Value: 55215

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xef

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xef

    Key  : Bugcheck.Code.Register
    Value: 0xef

    Key  : CriticalProcessDied.ExceptionCode
    Value: 812aa080

    Key  : CriticalProcessDied.ImageName
    Value: ntdll.dll

    Key  : CriticalProcessDied.ImageOffset
    Value: 52e21

    Key  : CriticalProcessDied.ImageSize
    Value: 1f8000

    Key  : CriticalProcessDied.ImageTimestamp
    Value: 1000a5b9

    Key  : CriticalProcessDied.Process
    Value: svchost.exe

    Key  : CriticalProcessDied.Symbol
    Value: ntdll.dll!TppWorkerThread

    Key  : CriticalProcessDied.WERReportId
    Value: 93eb2c63-8eb7-4a0f-94e0-05f6ed7bf73e

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  ef

BUGCHECK_P1: ffff800b7abe7100

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

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

CRITICAL_PROCESS_REPORTGUID:  {93eb2c63-8eb7-4a0f-94e0-05f6ed7bf73e}

IMAGE_NAME:  ntdll.dll

MODULE_NAME: ntdll

FAULTING_MODULE: 00007ffa82d30000 ntdll

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

STACK_TEXT:
ffffb803`b261f8f8 fffff805`36908af2     : 00000000`000000ef ffff800b`7abe7100 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffb803`b261f900 fffff805`3681041b     : 00000000`00000000 fffff805`363446c9 00000000`00000002 fffff805`3633012f : nt!PspCatchCriticalBreak+0x10e
ffffb803`b261f9a0 fffff805`36677f8c     : ffff800b`00000000 00000000`00000000 ffff800b`7abe7100 ffff800b`7abe7538 : nt!PspTerminateAllThreads+0x198f8f
ffffb803`b261fa10 fffff805`366fcfcc     : ffff800b`7abe7100 00000000`00000000 00000000`00000016 00000206`ee9c0000 : nt!PspTerminateProcess+0xe0
ffffb803`b261fa50 fffff805`3640a2b8     : ffff800b`7abe7100 ffff800b`812aa080 ffffb803`b261fb40 ffff800b`7abe7100 : nt!NtTerminateProcess+0x9c
ffffb803`b261fac0 00007ffa`82dcd4c4     : 00007ffa`82e43024 00000000`00000000 0000000a`04a7f58c 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000000a`04a7e568 00007ffa`82e43024     : 00000000`00000000 0000000a`04a7f58c 00000000`00000000 00007ffa`82d30000 : ntdll!NtTerminateProcess+0x14
0000000a`04a7e570 00007ffa`82dd5718     : 00007ffa`82e77720 00007ffa`82d61040 00007ffa`82d30000 00007ffa`82d82e21 : ntdll!TppWorkerpOuterExceptionFilter+0x38
0000000a`04a7e5a0 00007ffa`82dbc766     : 0000000a`04a7e648 0000000a`04a7e688 00007ffa`82d82e21 00000000`00000001 : ntdll!TppWorkerThread$filt$11+0x12
0000000a`04a7e5e0 00007ffa`82dccb2e     : 00007ffa`82e777e0 0000000a`04a7f330 0000000a`04a7f550 0000000a`04a7ec80 : ntdll!_C_specific_handler+0x96
0000000a`04a7e650 00007ffa`82dd229f     : 00000000`00000000 0000000a`04a7ec70 0000000a`04a7f330 00000000`00000000 : ntdll!_GSHandlerCheck_SEH+0x6a
0000000a`04a7e680 00007ffa`82d81454     : 00000000`00000000 0000000a`04a7ec70 0000000a`04a7f330 00000000`00000000 : ntdll!RtlpExecuteHandlerForException+0xf
0000000a`04a7e6b0 00007ffa`82dd0dce     : 00000000`00000000 00000000`00000000 00000206`ef05d210 00000000`00000000 : ntdll!RtlDispatchException+0x244
0000000a`04a7ee40 00007ffa`82d82e21     : 00000000`00000000 00000000`00000000 00000206`ee0c5a40 00000206`ef05d210 : ntdll!KiUserExceptionDispatch+0x2e
0000000a`04a7f550 00007ffa`82487034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x351
0000000a`04a7f850 00007ffa`82d82651     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14
0000000a`04a7f880 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


SYMBOL_NAME:  ntdll!NtTerminateProcess+14

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  14

FAILURE_BUCKET_ID:  0xEF_svchost.exe_DcomLaunch_BUGCHECK_CRITICAL_PROCESS_812aa080_ntdll.dll!TppWorkerThread_ntdll!NtTerminateProcess

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {27f77f41-e971-e190-2504-a8f638f62ad3}

Followup:     MachineOwner
---------

 

[Colif]

why are you running 2 games at same time?

can you set up for minidumps as well? unless you lucky and one guy is still around, a 1.3gb memory dump is too large for a friend of mine to download, so if/when it happens again I can ask him to do the smaller dump


critical process died can only happen if a windows system file crashes. Service host is one such process. Its cause is not simple question as there are about 71 service hosts running at any one time.

try checking windows out:

right click start button

choose powershell (admin)

copy/paste this command into window:

Repair-WindowsImage -Online -RestoreHealth

and press enter

Then type SFC /scannow

and press enter

Restart PC if SFC fixes any files as some fixes require a restart to be implemented

First command repairs the files SFC uses to clean files, and SFC fixes system files

SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

SSD - 2x NVME + 1x SSD + 1xHDD

what are the make/model of the drives as it could be a drive causing it. Only as you loading 2 games at once.

 

[DimkaTsv]

why are you running 2 games at same time?

MMO life... Doing stuff in background, while playing with friend in turn based strategy. And not just 2 games (even though it isn't a problem even when i need to run 3 games for me at some times), but 2 SPECIFIC games. Not just any, but exactly these 2 (if interested, BDO and Total war: Warhammer II)

Repair-WindowsImage -Online -RestoreHealth
and press enter
Then type SFC /scannow
and press enter

Yeah, yeah. my system is healthy if i should believe these things. It is one of first things i tried. This BSOD is a bit too consistent

what are the make/model of the drives as it could be a drive causing it. Only as you loading 2 games at once.

That is definitely not a fault point there, or i would've known about any issues much earlier. System is on other drive from games anyways. (Kingston KC 2500 500GB and 1TB, if there are still questions)

can you set up for minidumps as well? unless you lucky and one guy is still around, a 1.3gb memory dump is too large for a friend of mine to download, so if/when it happens again I can ask him to do the smaller dump

Sure, but as MMO right now have maintenance for few hours and i go to sleep, i will only be able to generate one later.

 

[DimkaTsv]

Here you go...
3 minidumps
https://drive.google.com/drive/folders/1iIAHZV8t_k--BVUkM8biceppjdECRbBH?usp=sharing

Strangely BSOD now began to not just be caused by same exact [ntdll.dll _ svchost.exe _dcomlaunch], but by [ntkrnlmp.exe _ services.exe] instead
But i attempted to "reinstall" windows this morning, so i may have touched some core level dlls

Because that's, like, only difference i can see

Spoiler

Also, this BSOD is not just for me, but for my friend too. With same 2 games (we play them both)

 

[PsychoPsyops]

Hmm...MMOs can kill one's health and one's pc. Who would've thought...

 

[DimkaTsv]

Hmm...MMOs can kill one's health and one's pc. Who would've thought...

Well, tbh anticheats and/or DRM protections are much more under suspicion there than games by themselves.
And it is not MMO specific thing. Any game can have those