Game crash with "The description for Event ID 0 from source nvlddmkm cannot be found"

We are in the same boat. I have tried everything you did as well. Have you fixed the problem? I am still trying figure it out myself.

oddly enough, the second error happens sometimes when i open the start menu. The screen goes black for a second and comes back with the wrong color calibration.

I'm using Windows 11 Insider Preview 23475.1000 (ni_prerelease), but this has happened many times before too.

I have the same error. And I checked my ram completely and it certainly healthy. The amazing thing that i understood is that When I plug in my 3 power cables of 3 hdd hards to PSU and turn on the computer it crashes after a few seconds of working. and it usually occurs after make computer out from sleep. Memory dump file analyze result:************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true

-- 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: 36

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

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

Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff80758a00000 PsLoadedModuleList = 0xfffff8075962a2d0 Debug session time: Thu Jun 22 09:26:05.609 2023 (UTC - 7:00) System Uptime: 0 days 0:11:16.263 Loading Kernel Symbols ............................................................... ...Page 300c0b not present in the dump file. Type ".hh dbgerr004" for details ............................................................. .................................................... Loading User Symbols

Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff80758dfc030 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8b08c4e5aa20=0000000000000116 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

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

Debugging Details:

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_777742171a918a50\nvlddmkm.sys, Win32 error 0n2 Page 25dd67 not present in the dump file. Type ".hh dbgerr004" for details *** WARNING: Check Image - Checksum mismatch - Dump: 0x3aff59, File: 0x3ab4c9 - C:\ProgramData\Dbg\sym\dxgkrnl.sys\0F2DDF593aa000\dxgkrnl.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3000

Key  : Analysis.Elapsed.mSec
Value: 7965

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

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

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

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

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

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

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x116

Key  : Bugcheck.Code.LegacyAPI
Value: 0x116

Key  : Failure.Bucket
Value: 0x116\_IMAGE\_nvlddmkm.sys

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

Key  : Hypervisor.Enlightenments.Value
Value: 0

Key  : Hypervisor.Enlightenments.ValueHex
Value: 0

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key  : Hypervisor.Flags.ApicEnlightened
Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 0

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 0

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key  : Hypervisor.Flags.Phase0InitDone
Value: 0

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 0

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 0

Key  : Hypervisor.Flags.ValueHex
Value: 0

Key  : Hypervisor.Flags.VpAssistPage
Value: 0

Key  : Hypervisor.Flags.VsmAvailable
Value: 0

Key  : Hypervisor.RootFlags.AccessStats
Value: 0

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 0

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key  : Hypervisor.RootFlags.Value
Value: 0

Key  : Hypervisor.RootFlags.ValueHex
Value: 0

Key  : SecureKernel.HalpHvciEnabled
Value: 0

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffbe8df2a5b010

BUGCHECK_P2: fffff807771cad40

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB: MEMORY.DMP

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8b08c4e5aa18 fffff80763cb65be : 0000000000000116 ffffbe8df2a5b010 fffff807771cad40 ffffffffc000009a : nt!KeBugCheckEx ffff8b08c4e5aa20 fffff80763c66b64 : fffff807771cad40 ffffbe8defa3c010 0000000000002000 ffffbe8defa3c0d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffff8b08c4e5aa60 fffff80763c5f69c : ffffbe8defa34000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174 ffff8b08c4e5aa90 fffff80763cb5ce5 : 0000000000000100 ffffbe8defa34a70 00000000f167b040 0000000000000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc ffff8b08c4e5ab10 fffff80763cb5e57 : fffff80759725440 0000000000000000 0000000000000000 0000000000000300 : dxgkrnl!TdrResetFromTimeout+0x15 ffff8b08c4e5ab40 fffff80758c8e5c5 : ffffbe8df3519040 fffff80763cb5e30 ffffbe8deb2a1010 ffffbe8d00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27 ffff8b08c4e5ab70 fffff80758d268f5 : ffffbe8df3519040 0000000000000080 ffffbe8deb28e040 000fa425bd9bbfff : nt!ExpWorkerThread+0x105 ffff8b08c4e5ac10 fffff80758e04c68 : fffff80754f15180 ffffbe8df3519040 fffff80758d268a0 0000000000000000 : nt!PspSystemThreadStartup+0x55 ffff8b08c4e5ac60 0000000000000000 : ffff8b08c4e5b000 ffff8b08c4e55000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nvlddmkm+108ad40

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

How old is your PSU? It is rare for a PSU to cause this issue but have you checked the power cable connections into your drives? I found out the hard way as the SATA connection was loose from all the changing around I been doing causing transmissions to cut in and out intermittently on a data pin. SSD's are hot-swappable (safe if no windows DIRS are linked) but Windows 10 used a temp DIR on D whilst installing for some reason and that was my issue.

Remove any storage drives, Use stock clocks, Make sure your BIOS is updated as there are a some new ones that have just been released but caution with ASUS as there is plenty of info on the BIOS updates which are auto over-volting your CPU, Disconnect from the net and re-install the package file from the website - Not an updater. Do a clean install.

This part may help when you un-install but restart and then re-install your chipset drivers before your graphics and restart each time.

Once done, open Device Manager, click on Display Adapters, then update driver but search for the .inf file manually to make sure it installed correctly if you have any doubts.

There are many options to get this done or search for the file with 'hidden sys files showing' and copy the missing file into the System32 folder.

Install the latest C++ Pack (big archive but installs all versions.

Good Luck.