How to fix: video_tdr_failure (116) - failure_bucket_id: 0x116_IMAGE_nvlddmkm.sys

Question

How to fix: video_tdr_failure (116) - failure_bucket_id: 0x116_IMAGE_nvlddmkm.sys

LwobeLTzweL Ryan 20

Hello to everyone !

I have an issue, when i try play a game my pc restart, i can`t play more than 15 minutes, i tryed alot of settings, i used DDU in SAFE MODE , and alot of settings and settings.

My problem start with 6 months ago, i change alot of components in pc case, and nothing, diferents ram memory, Corsair, Kingston, 2666Mhz, 3200Mhz, i change my PSU, was a Corsair 750HXi, proccessors, i3, i5 and now i9, i change the SSD's, bios update motherboard, bios update video card, and can't fix this .......

BTW, The windows 11 64bit was reinstal 5-6 times until now ...

Please help me fix this problem !

And many thanks in advance !

This is my Black-Screen Report:

ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:
ExtensionGallery ExtensionRepository: Implicit

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*

************* 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.390 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Active memory is 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 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 26100.1.amd64fre.ge_release.240331-1435
Kernel base = 0xfffff806`e9200000 PsLoadedModuleList = 0xfffff806`ea0f5040
Debug session time: Sun Feb 15 17:49:40.346 2026 (UTC + 2:00)
System Uptime: 0 days 0:35:23.072
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols

Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`e96fb8c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe382`f6df7190=0000000000000116
10: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols

Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff970b44ed2360, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8069490fff0, 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_dispi.inf_amd64_adc55ecfca814224\nvlddmkm.sys, Win32 error 0n2
Page 2d2a0e not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2875

    Key  : Analysis.Elapsed.mSec
    Value: 7815

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x116

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116

    Key  : Bugcheck.Code.TargetModel
    Value: 0x116

    Key  : Dump.Attributes.AsUlong
    Value: 0x21040

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.FilterDumpFile
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_nvlddmkm.sys

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8069490fff0

    Key  : Failure.Exception.IP.Module
    Value: nvlddmkm

    Key  : Failure.Exception.IP.Offset
    Value: 0x19afff0

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

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

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

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0


BUGCHECK_CODE:  116

BUGCHECK_P1: ffff970b44ed2360

BUGCHECK_P2: fffff8069490fff0

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB:  MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x21040
  Filter Dump

FAULTING_THREAD:  ffff970b40d82040

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
nvlddmkm+19afff0
fffff806`9490fff0 488b05892b81ff  mov     rax,qword ptr [nvlddmkm+0x11c2b80 (fffff806`94122b80)]

STACK_TEXT:  
ffffe382`f6df7188 fffff806`7b196d5d     : 00000000`00000116 ffff970b`44ed2360 fffff806`9490fff0 ffffffff`c000009a : nt!KeBugCheckEx
ffffe382`f6df7190 fffff806`7b402c94     : fffff806`9490fff0 ffff970b`3e1282b0 00000000`00002000 ffff970b`3e128370 : dxgkrnl!TdrBugcheckOnTimeout+0x101
ffffe382`f6df71d0 fffff806`7b1a59d6     : ffff970b`3e18f000 00000000`00000000 00000000`00000004 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x220
ffffe382`f6df7200 fffff806`7b1e0455     : ffff970b`00000100 00000000`00000000 ffffe382`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x58a
ffffe382`f6df7290 fffff806`7b1e05b2     : ffff8901`80005720 ffff970b`146bb500 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe382`f6df72c0 fffff806`e9515a9b     : ffff970b`40d82040 ffff970b`14823ae0 fffff806`ea038b00 ffff970b`14823ae0 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffffe382`f6df7300 fffff806`e968966a     : ffff970b`40d82040 ffff970b`40d82040 fffff806`e95155e0 ffff970b`14823ae0 : nt!ExpWorkerThread+0x4bb
ffffe382`f6df74b0 fffff806`e98ab774     : ffffe581`6f683180 ffff970b`40d82040 fffff806`e9689610 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffffe382`f6df7500 00000000`00000000     : ffffe382`f6df8000 ffffe382`f6df1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nvlddmkm+19afff0

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffff970b146d0040; .thread 0xffff970b40d82040 ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi LwobeLTzweL Ryan,

Welcome to the Microsoft Q&A forum.

Based on the crash analysis you provided, the system is encountering a display timeout recovery (TDR) event, where Windows attempts to reset the graphics driver after it becomes unresponsive. When that recovery does not complete successfully, the system may show a black screen or restart to protect overall stability.

Please try the possible checking steps below to help stabilize the system:

1, Disable virtualization‑related features

Press Win + R > type optionalfeatures
Turn off:
- Hyper‑V
- Windows Hypervisor Platform
- Virtual Machine Platform
- Windows Subsystem for Linux (if enabled)
Restart the PC
Open Windows Security > Device Security > Core isolation
- Turn Memory integrity Off
- Restart again

2, Set PCIe mode manually in BIOS

Enter BIOS/UEFI
Set PCIe Link Speed to Gen 3
Temporarily disable:
- Above 4G Decoding
- Resizable BAR
Save and reboot

3, Reduce GPU boost behavior

Open MSI Afterburner (or equivalent app)
Reset to defaults, then apply:
- Power Limit: 90%
- Core Clock: ‑100 MHz
- Memory Clock: ‑200 MHz
Apply and test again

4, Reinstall NVIDIA driver

Install the NVIDIA Studio Driver (not Game Ready)
Choose Custom install
Install Driver + PhysX only
Do not install GeForce Experience

If the issue persists after completing all steps, the system is still protected and functioning as designed, and further hardware‑level diagnostics would be the appropriate next direction.

Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

LwobeLTzweL Ryan 20 Reputation points

2026-02-16T21:54:17.6+00:00

Thank you very much Hendrix-V for your help and support !!!!

STEP 2 is the key, “Set PCIe Link Speed to Gen 3”

STEP 1 and 3 have done before !

BTW i made and STEP 4 to be sure !

I played one hour and fifteen minutes with Very High settings, DLSS: ON, NVIDIA Reflex Low Latency: ON and VSync: ON and NO “BLACK-SCREEN” .

Now i want to activate XMP, and all settings at maximum, and play again to be sure !
Hendrix-V 11,355 Reputation points Microsoft External Staff Moderator

2026-02-19T00:32:29.55+00:00

Hi LwobeLTzweL Ryan,

I'm relieved to know that you made a great decision and everything is good to go on your side. I hope the insights shared in the forum help address your concerns effectively. And thank you for accepting my answer since accepting it helps others with similar concerns can find useful information.

You’ve already done the hard part. The fact that the system ran 1h15m at Very High + DLSS + Reflex + VSync with zero black screens after forcing PCIe Gen 3 is a very strong stability signal.

At this point, you can consider enabling XMP but keeping PCIe set to Gen 3 and all other settings unchanged to test gaming again.

If you have any updates or further questions, please feel free to share them with us.

Share via

How to fix: video_tdr_failure (116) - failure_bucket_id: 0x116_IMAGE_nvlddmkm.sys

0 additional answers

Your answer