How do i fix VIDEO_TDR_FAILURE(116)?

Question

How do i fix VIDEO_TDR_FAILURE(116)?

Anonymous

Hi,

I've been having this error for a little while now since i updated to windows 11 from windows 10. The computer just instantly freezes when i am listening to songs or using chrome. It doesn't happen while i'm playing games. Then i just lose control of my mouse and keyboard and the monitor just turns black.

MY PC SPECS:

CPU- Intel i5 11400f

GPU- INNO3D NVIDIA RTX 2060

MOBO-MSI H510M-A-PRO
RAM-8GBX2 ADATA XPG D30 3200mhz

STORAGE- 256 GB ANT ESPORTS 690 NEO PRO+WD 1 TB harddrive

PSU-DEEPCOOL PF650 650W

I checked the event viewer for more details about the problem, apparently its a kernel power 41 error with bugcheck code 278.

5 answers

Answer 1

Hi

Welcome to Microsoft community.

I carefully examined the log files and found that your issue was caused by a conflict between Defender and the NVIDIA graphics card driver, resulting in the crash.

At the same time, I also see it from your error message VIDEO_TDR_FAILURE (116) error. This error often occurs when the Timeout Detection and Recovery (TDR) feature in Windows detects that the Graphics card has not responded within the permitted time, then the display driver is restarted to prevent the need to reboot.

Here are some steps you can follow to resolve this issue:

Update Graphics Driver: The first thing you should do is ensure that your Nvidia RTX 2060 graphics driver is up-to-date. Visit Nvidia's official website, download the latest driver for your graphics card, and install it. Choose the "Clean Installation" option during the installation to remove the old driver and settings.
Perform a clean boot. To exclude the interference of the vast majority of applications.
Run Windows Defender Offline Scan: As you mentioned a conflict between Defender and the Nvidia graphics driver, conducting an offline scan might help. Go to Windows Security settings > Virus & threat protection > Scan options > Windows Defender Offline Scan. This will restart your PC and take about 15 minutes to run.
Adjust the TDR settings: You can try increasing the TDR delay which may help if your system is just taking longer than expected to respond. This involves editing the Windows Registry, so proceed with caution. Here's how you can do it:
- Press the Windows key + R, type "regedit" into the Run box, and press Enter to open the Registry Editor.
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
- Right-click on the right pane and select New > DWORD (32-bit) Value or QWORD (64-bit) Value. Name it "TdrDelay".
- Double-click on TdrDelay and set the value data to 8 (for 8 seconds).
- Click OK and restart your computer. Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article.
Check Hardware: Overheating or faulty hardware could also cause this error. Check if your GPU and other components are properly seated and clean. Make sure your PC is not overheating.

Please feel free to let me know if you have any further updates, thanks.

Best regards

Derrick Qian | Microsoft Community Support Specialist

Answer 2

Anonymous

Thanks a lot for helping, I will do as you say and I will let you know if any problem persists.

Regards

Answer 3

Hi,
I tried everything you asked me to do but i still faced the error today. I suppose the problem was due to the gpu driver again. Should i try reinstalling windows or going back to using windows 10 instead of 11?
The latest dump file:

https://drive.google.com/file/d/1xlpsht5vTIpW0sRYpQqja2M46JMrag5z/view?usp=sharing

Thanks

Answer 4

Hi

Thanks for your reply.

The latest log error indicates that there is a conflict between your NVIDIA driver and the Intel Ethernet driver. The specific file involved is e1i68x64.sys. You can check for the relevant drivers and try uninstalling and reinstalling them.

Here is the related article.

Answer 5

Hi Derrick,

I am having a very similar issue.

I've recently updated drivers & performed a reboot.

Can you please help me to understand my minidump? :(

Thanks,
Dan.

************* 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.172 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 [C:\Windows\Minidump\080924-11296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff803`31e00000 PsLoadedModuleList = 0xfffff803`32a13510
Debug session time: Fri Aug  9 23:13:34.399 2024 (UTC + 9:30)
System Uptime: 0 days 3:28:14.038
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols

Loading unloaded module list
............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`32215df0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbf8f`d5b27130=0000000000000116
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffa38bb14cc010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80360920100, 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_1196b342b24df5d1\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1671

    Key  : Analysis.Elapsed.mSec
    Value: 12323

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116

    Key  : Bugcheck.Code.TargetModel
    Value: 0x116

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_nvlddmkm.sys

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

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  116

BUGCHECK_P1: ffffa38bb14cc010

BUGCHECK_P2: fffff80360920100

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB:  080924-11296-01.dmp

FAULTING_THREAD:  ffffa38babe46040

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffbf8f`d5b27128 fffff803`483eb00e     : 00000000`00000116 ffffa38b`b14cc010 fffff803`60920100 ffffffff`c000009a : nt!KeBugCheckEx
ffffbf8f`d5b27130 fffff803`4839ce32     : fffff803`60920100 ffffa38b`a5286050 00000000`00000080 ffffa38b`a5286110 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffbf8f`d5b27170 fffff803`483953a9     : ffffa38b`a5c98000 ffffa38b`abe46040 ffffa38b`a5c98b50 ffffa38b`a5c98b50 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a
ffffbf8f`d5b271a0 fffff803`483ea765     : 00000000`99910180 ffffa38b`abe46040 00000000`00000000 ffffa38b`b14eb430 : dxgkrnl!DXGADAPTER::Reset+0x60d
ffffbf8f`d5b27250 fffff803`483ea8c2     : 00000000`00000000 fffff803`32a13ca0 ffffa38b`9cd57000 fffff803`32b49ac0 : dxgkrnl!TdrResetFromTimeout+0x15
ffffbf8f`d5b27280 fffff803`321064f5     : ffffa38b`abe46040 ffffa38b`9991bc80 ffffa38b`00000000 fffff803`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffffbf8f`d5b272c0 fffff803`32079ca7     : ffffa38b`abe46040 00000000`0000011e ffffa38b`abe46040 fffff803`321063a0 : nt!ExpWorkerThread+0x155
ffffbf8f`d5b274b0 fffff803`3221af64     : ffffd580`59177180 ffffa38b`abe46040 fffff803`32079c50 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffbf8f`d5b27500 00000000`00000000     : ffffbf8f`d5b28000 ffffbf8f`d5b21000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  nvlddmkm+1620100

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .process /r /p 0xffffa38b998fc040; .thread 0xffffa38babe46040 ; 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
---------

4: kd> !process 4 3
Searching for Process with Cid == 4
fffff80332a40000: Unable to get value of ObpTypeObjectType
Cannot resolve nt!_EPROCESS object type
4: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff803`5f300000 fffff803`638bc000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1196b342b24df5d1\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Thu Jul 11 03:24:30 2024 (668ECAD6)
    CheckSum:         04469EB1
    ImageSize:        045BC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Share via

How do i fix VIDEO_TDR_FAILURE(116)?

5 answers