Constant Game Crash (World of Warcraft DX12)

pete05uk · 7 Sep 2024 at 17:38

Not sure if anyone has come across a solution for this but World of Warcraft crashes after a few black screens, the game recovers then it begins to stutter and freeze until it eventually crashes to desktop with an error wow.exe was unable to start up 3d acceleration. The windows event log has an error about the display driver being recovered.

My PC has an i9 13900k on an ASUS ROG Maximus Z690 Extreme Glacial and ASUS RTX4090, fully liquid cooled and 32GB ram.

I have tried everything I can think of including disabling overclocking and XMP, updating to thee latest BIOS (my Graphics are not overclocked nor do I have any overclocking software installed, changing power management settings and a full, clean reinstall of the last 6 versions of the nvidia drivers and finally a couple of full windows reinstalls.

Along with this I have run full memtests, CPU and GPU testing/stress tests with no issues and temperatures within norm. The only “workaround” is switching the game to run in DX11.

I have other games that run DX12 that don’t have the crashing problem. I have come across other posts with similar problems but does anyone know what the issue is and what the fix might be (Other than the DX11 workaround)

Thanks in advance.

Emlyn_Dewar · 8 Sep 2024 at 03:47

Could be CPU degradation on that 13900K. :/

Rroff · 8 Sep 2024 at 06:24

What cable are you using with the 4090? the symptoms are consistent with the 4090 power cable/connector melting issue and I'd definitely check for that before anything else - albeit that will usually fail in stress tests as well.

Dunno how far you went back but I'd try rolling nvidia drivers back to something older like 551.76 which are usually very stable.

I'd try downloading the Black Myth:Wukong benchmark as well (shows under Tools rather than Games in Steam Library) as apparently if you have a degraded 13th or 14th gen CPU there is a high chance it will crash on the shader compiling part on start up on that.

pete05uk · 8 Sep 2024 at 07:07

Emlyn_Dewar said:
Could be CPU degradation on that 13900K. :/

Is there any tests that I can do to check ? To be fair I upgraded from a 12900k when I did some cosmetic changes to my case and at the time, this was a know issue and the bios was set to enforce all intel limits.

freddie64 · 8 Sep 2024 at 08:07

pete05uk said:
i9 13900k on an ASUS ROG Maximus Z690 Extreme Glacial

Are you on the latest bios version?

ROG MAXIMUS Z690 EXTREME GLACIAL BIOS 3802

Version 3802
13.32 MB 2024/08/09
"1.The new BIOS includes Intel microcode 0x129 to enhance the stability of Intel Core 13th and 14th Gen processors.
2.The factory default settings are set to Intel Default Settings, which now include non-K processors (the K series were already included in previous versions).

Updating this BIOS will simultaneously update the corresponding intel ME to version 16.1.30.2307. Please note after you update this BIOS, the ME version remains the updated one even if you roll back to an older BIOS later.

Before running the USB BIOS Flashback tool, please rename the BIOS file (MZ690EG.CAP) using BIOSRenamer."

pete05uk · 8 Sep 2024 at 08:32

Rroff said:
What cable are you using with the 4090? the symptoms are consistent with the 4090 power cable/connector melting issue and I'd definitely check for that before anything else - albeit that will usually fail in stress tests as well.

Dunno how far you went back but I'd try rolling nvidia drivers back to something older like 551.76 which are usually very stable.

I'd try downloading the Black Myth:Wukong benchmark as well (shows under Tools rather than Games in Steam Library) as apparently if you have a degraded 13th or 14th gen CPU there is a high chance it will crash on the shader compiling part on start up on that.

Thanks - I have checked the cables and no apparent issues. Will

pete05uk · 8 Sep 2024 at 08:34

I have also (following a guide from Nvidia) set the TDRLevel to 1 so that windows does not attempt to recover but initiates a bugcheck, output from the memory.dmp file:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

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

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Primary dump contents written successfully

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff807`0c600000 PsLoadedModuleList = 0xfffff807`0d2134f0
Debug session time: Sun Sep 8 08:28:04.331 2024 (UTC + 1:00)
System Uptime: 0 days 0:02:49.971
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................................................
Loading User Symbols

Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`0ca15cb0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd30a`6b26f7c0=0000000000000116
14: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff8f84cb3ee220, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8073ce30d80, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000001, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_78cd02ab022cd554\nvlddmkm.sys, Win32 error 0n2
Page 15ee32 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1578

Key : Analysis.Elapsed.mSec
Value: 3590

Key : Analysis.IO.Other.Mb
Value: 3

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 10

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x116

Key : Bugcheck.Code.LegacyAPI
Value: 0x116

Key : Bugcheck.Code.TargetModel
Value: 0x116

Key : Dump.Attributes.AsUlong
Value: 1800

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 100

Key : Failure.Bucket
Value: 0x116_IMAGE_nvlddmkm.sys

Key : Failure.Hash
Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 21631230

Key : Hypervisor.Flags.ValueHex
Value: 14a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : SecureKernel.HalpHvciEnabled
Value: 1

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff8f84cb3ee220

BUGCHECK_P2: fffff8073ce30d80

BUGCHECK_P3: 0

BUGCHECK_P4: 1

FILE_IN_CAB: MEMORY.DMP

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1800

FAULTING_THREAD: ffff8f84bd167480

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff8f84cb3ee220
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000001

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd30a`6b26f7b8 fffff807`2610b00e : 00000000`00000116 ffff8f84`cb3ee220 fffff807`3ce30d80 00000000`00000000 : nt!KeBugCheckEx
ffffd30a`6b26f7c0 fffff807`26109292 : fffff807`3ce30d80 ffff8f84`cb3ee220 00000000`00000001 00000000`00000001 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffd30a`6b26f800 fffff807`26ac675e : ffff8f84`bd168000 ffffd30a`00000001 00000000`00000000 00000000`00000000 : dxgkrnl!TdrAllowToDebugEngineTimeout+0x1f2
ffffd30a`6b26f830 fffff807`26a93ced : ffff8f84`bd0c1000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0x36
ffffd30a`6b26f880 fffff807`26a65919 : 00000000`00000000 00000000`00000000 00000000`00002a30 00000000`00989680 : dxgmms2!VidSchiCheckHwProgress+0x2e3ad
ffffd30a`6b26f900 fffff807`269c6ae1 : 00000000`00000000 ffff8f84`bd0c1000 ffffd30a`6b26fa39 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x389
ffffd30a`6b26f9d0 fffff807`26a7a405 : ffff8f84`d42ef200 ffff8f84`bd0c1000 ffff8f84`d42ef290 ffff8f84`bd110860 : dxgmms2!VidSchiScheduleCommandToRun+0x291
ffffd30a`6b26faa0 fffff807`26a7a37a : 00000000`00000000 fffff807`26a7a2b0 ffff8f84`bd0c1000 00000000`00050246 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffd30a`6b26faf0 fffff807`0c954d07 : ffff8f84`bd167480 fffff807`00000001 ffff8f84`bd0c1000 006fe47f`b19bbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffd30a`6b26fb30 fffff807`0ca1ae24 : fffff807`06291180 ffff8f84`bd167480 fffff807`0c954cb0 0eba0020`24648348 : nt!PspSystemThreadStartup+0x57
ffffd30a`6b26fb80 00000000`00000000 : ffffd30a`6b270000 ffffd30a`6b269000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nvlddmkm+1620d80

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffff8f849d34f040; .thread 0xffff8f84bd167480 ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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

Tetras · 8 Sep 2024 at 15:08

pete05uk said:
Is there any tests that I can do to check ?

The ones I'm aware of are:
Cinebench (don't run this without the limits imposed)
Games which require compiling shaders.
Unreal 5 games.
Installing the nvidia drivers.

Emlyn_Dewar · 9 Sep 2024 at 04:50

The whole issue makes troubleshooting issues on the higher end 13/14th gen CPUs pretty awkward, as there's always the thought "is this just another broken Intel CPU?"
Might not even be that, but there's little point assuming anything else.

JNZ · 10 Sep 2024 at 13:15

13/14th gen. die slowly or quickly, depending on operating conditions, however, once the process of them failing has begun, there is no stopping it.

That said, your problem sounds like a GPU issue. I'd check the power going to the card, check the pins/connector and look for signs of burning, and replace the cable if you haven't already.

Do you have another recent nVidia GPU you could try, just to see if it perists with a different card? Quickest way to out-rule the 4090 hardware at least.