How to fix nvlddmkm.sys BSOD VIDEO_TDR_FAILURE on my Windows PC?

Василий 0 Reputation points
2023-06-11T18:47:38.0366667+00:00

got a Blue Screen of Death. How do I resolve this and what does the contents of the dump file mean? Below are the contents of the dump file

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffba89c3f30010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff804aa4e3ac0, 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\nvltig.inf_amd64_d02a3ec451b2dba6\nvlddmkm.sys, Win32 error 0n2
*** 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: 3015

    Key  : Analysis.Elapsed.mSec
    Value: 4521

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

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

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

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

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 417cf9c

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  116

BUGCHECK_P1: ffffba89c3f30010

BUGCHECK_P2: fffff804aa4e3ac0

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB:  MEMORY.DMP

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffba89c3f30010
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:  
fffffd02`033c68f8 fffff804`78c665be     : 00000000`00000116 ffffba89`c3f30010 fffff804`aa4e3ac0 ffffffff`c000009a : nt!KeBugCheckEx
fffffd02`033c6900 fffff804`78c16b64     : fffff804`aa4e3ac0 ffffba89`bd0b1620 00000000`00002000 ffffba89`bd0b16e0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffffd02`033c6940 fffff804`78c0f69c     : ffffba89`bd3ec000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
fffffd02`033c6970 fffff804`78c65ce5     : fffffd02`00000109 ffffba89`bd3eca70 ffffcf91`00000000 ffffba89`bd3ec000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
fffffd02`033c69f0 fffff804`78c65e57     : ffffa88b`820da230 ffffba89`bd3ec000 ffffba89`b8497110 00000000`00000002 : dxgkrnl!TdrResetFromTimeout+0x15
fffffd02`033c6a20 fffff804`78bf26b9     : ffffba89`bd3ec000 00000000`00000004 00000000`00000000 00000000`00000021 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
fffffd02`033c6a50 fffff804`78c095a9     : ffffba89`b8497050 00000000`00000000 00000000`00000000 ffffba89`b8497050 : dxgkrnl!DXGADAPTER::ApplyCoreSyncAction+0x7f8a5
fffffd02`033c6ab0 fffff804`5f7265f5     : ffffba89`b848a080 00000000`00000080 fffff804`78b96770 000fa46f`b19bbfff : dxgkrnl!DpiPowerArbiterThread+0x72e39
fffffd02`033c6b10 fffff804`5f8048d8     : ffffcb00`41aec180 ffffba89`b848a080 fffff804`5f7265a0 fdbffdbe`fdbdfdbc : nt!PspSystemThreadStartup+0x55
fffffd02`033c6b60 00000000`00000000     : fffffd02`033c7000 fffffd02`033c0000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm!nvDumpConfig+570c10

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

In addition to the aforementioned error, there were two other errors related to nvlddmkm.sys. All 3 types are documented with the v2 log here:
https://drive.google.com/drive/folders/1FwTggX5O5TaxBTBS3BlK1CTmXUWxpvIC?usp=sharing

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Docs 16,226 Reputation points
    2023-06-11T20:28:41.8266667+00:00

    Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    .

    .

    .

    --Please don't forget to upvote and Accept as answer if the reply is helpful--

    .

    .

    .


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.