Question Computer started BSODing or CTDing only in games randomly last week, feeling lost

[radioactivejawa]

Hello everyone, I hope you can help me figure this one out, because it's come out of nowhere and I'm feeling a bit tired already.

My specs are:

RTX 4070Ti

Ryzen 7800X3D

32 GB of RAM at 6000Mhz

The good news is that the computer isn't acting up during normal work, but I kinda need to play PC games due to my work. Due to the nature of the crashes (either CTD or BSOD), I'm leaning towards this being GPU-related or a driver mess, but I've already DDU'd and tried Nvidia drivers previous to last week's. Also rolled back the last couple of major W11 updates. Otherwise, nothing has changed, software or hardware. That's why I'm a bit confused.

• Checked RAM through Windows' test. All good, no errors.
• Ran OCCT, CPU+RAM as well as GPU tests came out good.
• /sfc, DISM, chkdsk all good, no errors there either.

XDefiant is crashing to desktop after 1-2 matches. Unreal Engine-based games, such as Predecessor, Hellblade 2, and Lords of the Fallen can all crash to desktop with a variety of errors, such as LowLevelFatalError. However, Hellblade 2 (also 1, which I replayed a few days ago) can trigger BSODs too. Here's a memdump which points to dxgmms2.sys:

************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories

----> Repository : LocalInstalled, Enabled: true

----> Repository : UserExtensions, Enabled: true

************* Waiting for Debugger Extensions Gallery to Initialize **************

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 41

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidumps\052224-17453-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22621 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0xfffff806`0ce00000 PsLoadedModuleList = 0xfffff806`0da13130

Debug session time: Wed May 22 13:51:53.521 2024 (UTC + 2:00)

System Uptime: 0 days 0:18:02.128

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.................

Loading User Symbols

PEB is paged out (Peb.Ldr = 000000e7`1c529018). Type ".hh dbgerr001" for details

Loading unloaded module list

............

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff806`0d217f80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff958b`c8b8ea80=0000000000000139

8: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)

A kernel component has corrupted a critical data structure. The corruption

could potentially allow a malicious user to gain control of this machine.

Arguments:

Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).

Arg2: ffff958bc8b8eda0, Address of the trap frame for the exception that caused the BugCheck

Arg3: ffff958bc8b8ecf8, Address of the exception record for the exception that caused the BugCheck

Arg4: 0000000000000000, Reserved

Debugging Details:

*** WARNING: Check Image - Checksum mismatch - Dump: 0x210d9b, File: 0x210ec3 - C:\ProgramData\Dbg\sym\BTHport.sys\FE108757203000\BTHport.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 1436

Key : Analysis.Elapsed.mSec

Value: 1523

Key : Analysis.IO.Other.Mb

Value: 0

Key : Analysis.IO.Read.Mb

Value: 0

Key : Analysis.IO.Write.Mb

Value: 0

Key : Analysis.Init.CPU.mSec

Value: 233

Key : Analysis.Init.Elapsed.mSec

Value: 18881

Key : Analysis.Memory.CommitPeak.Mb

Value: 97

Key : Bugcheck.Code.LegacyAPI

Value: 0x139

Key : Bugcheck.Code.TargetModel

Value: 0x139

Key : Dump.Attributes.AsUlong

Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key : Dump.Attributes.ErrorCode

Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage

Value: 0

Key : FailFast.Name

Value: CORRUPT_LIST_ENTRY

Key : FailFast.Type

Value: 3

Key : Failure.Bucket

Value: 0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!VidSchiInterlockedRemoveHeadListIfExist

Key : Failure.Hash

Value: {205f16eb-23f7-9cb6-6b18-dd9368af9984}

BUGCHECK_CODE: 139

BUGCHECK_P1: 3

BUGCHECK_P2: ffff958bc8b8eda0

BUGCHECK_P3: ffff958bc8b8ecf8

BUGCHECK_P4: 0

FILE_IN_CAB: 052224-17453-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

TRAP_FRAME: ffff958bc8b8eda0 -- (.trap 0xffff958bc8b8eda0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffff97031f187018 rbx=0000000000000000 rcx=0000000000000003

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8067e8f6239 rsp=ffff958bc8b8ef30 rbp=ffff9703114da6c8

r8=ffff9703114da6c8 r9=0000000000000070 r10=fffff8060d0f7f20

r11=ffff958bc8b8f0e8 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz ac po cy

dxgmms2!VidSchiInterlockedRemoveHeadListIfExist+0x89:

fffff806`7e8f6239 cd29 int 29h

Resetting default scope

EXCEPTION_RECORD: ffff958bc8b8ecf8 -- (.exr 0xffff958bc8b8ecf8)

ExceptionAddress: fffff8067e8f6239 (dxgmms2!VidSchiInterlockedRemoveHeadListIfExist+0x0000000000000089)

ExceptionCode: c0000409 (Security check failure or stack buffer overrun)

ExceptionFlags: 00000001

NumberParameters: 1

Parameter[0]: 0000000000000003

Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Hellblade2-Win

ERROR_CODE: (NTSTATUS) 0xc0000409 - El sistema detect una saturaci n de un b fer basado en pilas en esta aplicaci n. Esta saturaci n podr a permitir que un usuario malintencionado tome el control de la aplicaci n.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

EXCEPTION_STR: 0xc0000409

STACK_TEXT:

ffff958b`c8b8ea78 fffff806`0d22de29 : 00000000`00000139 00000000`00000003 ffff958b`c8b8eda0 ffff958b`c8b8ecf8 : nt!KeBugCheckEx

ffff958b`c8b8ea80 fffff806`0d22e3f2 : ffff9703`00a76320 ffff958b`c8b8f080 ffff9703`00a76320 00000000`00000000 : nt!KiBugCheckDispatch+0x69

ffff958b`c8b8ebc0 fffff806`0d22c0db : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xb2

ffff958b`c8b8eda0 fffff806`7e8f6239 : ffff958b`c8b8f080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x35b

ffff958b`c8b8ef30 fffff806`7e9b1e86 : 00000000`00000cc0 ffff9703`1c987020 00000000`00000000 ffff958b`c8b8f230 : dxgmms2!VidSchiInterlockedRemoveHeadListIfExist+0x89

ffff958b`c8b8ef80 fffff806`7e934f99 : ffff9703`1eecdce0 00000000`0001cc54 ffff9703`1e903200 fffff806`00000000 : dxgmms2!VidSchiAllocateHwQueuePacket+0x84

ffff958b`c8b8f070 fffff806`3f699fcc : ffff9703`1eecdce0 ffff958b`c8b8f4e0 ffffbb81`b7313050 ffff958b`c8b8f228 : dxgmms2!VidSchSubmitWaitToHwQueue+0x59

ffff958b`c8b8f0f0 fffff806`3f59b537 : ffff958b`c8b8f3b8 00000000`00000000 ffff9703`114d8000 ffffbb81`b7313050 : dxgkrnl!SubmitWaitForSyncObjectsFromGpu+0xae8

ffff958b`c8b8f340 fffff806`3f69cf8b : 00000000`00000004 ffff9703`13f6c080 00007ffb`85318858 ffff6ffb`e4400000 : dxgkrnl!DxgkSubmitWaitForSyncObjectsToHwQueueInternal+0x34f

ffff958b`c8b8f430 fffff806`0d22d508 : ffff9703`13f6c080 00000000`00000000 00000000`00000000 ffff9703`152fe110 : dxgkrnl!DxgkSubmitWaitForSyncObjectsToHwQueue+0xb

ffff958b`c8b8f460 00007ffc`17136014 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

000000e7`4bd9ee68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`17136014

SYMBOL_NAME: dxgmms2!VidSchiInterlockedRemoveHeadListIfExist+89

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.22621.3593

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 89

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!VidSchiInterlockedRemoveHeadListIfExist

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {205f16eb-23f7-9cb6-6b18-dd9368af9984}

Followup: MachineOwner

 

[Ralston18]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

= = = =

Look in Reliability History/Monitor and Event Viewer. Either one or both tools may be capturing some error codes, warnings, or even informational events just before or at the time of the BS?ODs.

Reliabilty History/Monitor is end-user friendly and the timeline presentation may reveal patterns.

Event Viewer requires more time and effort to navigate and understand. To help with Event Viewer:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Any given entries can be clicked for additional details. The details may or may not be helpful.