none
VIDEO_TDR_FAILURE(116) RRS feed

  • Question

  • Hello, my computer from months crashes when i game and in event visualizer i see this error : Kernel_Power 41 (63) with bugcheck 278. So i tried to debug the dump file and it gives me that :

    Microsoft (R) Windows Debugger Version 10.0.18914.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\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: Missing image name, possible paged-out or corrupt data. *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Windows 10 Kernel Version 18362 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Kernel base = 0xfffff807`36800000 PsLoadedModuleList = 0xfffff807`36c432f0 Debug session time: Sun Jul 14 18:23:16.378 2019 (UTC + 2:00) System Uptime: 0 days 0:41:03.071 Missing image name, possible paged-out or corrupt data. *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Loading Kernel Symbols Missing image name, possible paged-out or corrupt data. .*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - HRESULT 0x80004002 Loading unloaded module list ...... WARNING: .reload failed, module list may be incomplete For analysis of this file, run !analyze -v fffff807`369bc900 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb90b`caaeda10=0000000000000116 0: kd> !symfix 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffe205e22ef010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff80743a20578, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000003, Optional internal context dependent data. Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 0 Key : Analysis.Elapsed.Sec Value: 0 Key : Analysis.Memory.CommitPeak.Mb Value: 44 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202 DUMP_TYPE: 1 BUGCHECK_P1: ffffe205e22ef010 BUGCHECK_P2: fffff80743a20578 BUGCHECK_P3: ffffffffc0000001 BUGCHECK_P4: 3 FAULTING_IP: +0 fffff807`43a20578 48895c2408 mov qword ptr [rsp+8],rbx DEFAULT_BUCKET_ID: CORRUPT_MODULELIST_0x116 CPU_COUNT: c CPU_MHZ: d48 CPU_VENDOR: AuthenticAMD CPU_FAMILY: 17 CPU_MODEL: 8 CPU_STEPPING: 2 BUGCHECK_STR: 0x116 CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: DESKTOP-7785VJV ANALYSIS_SESSION_TIME: 07-14-2019 18:49:31.0544 ANALYSIS_VERSION: 10.0.18914.1001 amd64fre STACK_TEXT: ffffb90b`caaeda08 fffff807`4308fa2a : 00000000`00000116 ffffe205`e22ef010 fffff807`43a20578 ffffffff`c0000001 : 0xfffff807`369bc900 ffffb90b`caaeda10 00000000`00000116 : ffffe205`e22ef010 fffff807`43a20578 ffffffff`c0000001 00000000`00000003 : 0xfffff807`4308fa2a ffffb90b`caaeda18 ffffe205`e22ef010 : fffff807`43a20578 ffffffff`c0000001 00000000`00000003 00000000`00002000 : 0x116 ffffb90b`caaeda20 fffff807`43a20578 : ffffffff`c0000001 00000000`00000003 00000000`00002000 ffffe205`e22ef010 : 0xffffe205`e22ef010 ffffb90b`caaeda28 ffffffff`c0000001 : 00000000`00000003 00000000`00002000 ffffe205`e22ef010 fffff807`4303eefb : 0xfffff807`43a20578 ffffb90b`caaeda30 00000000`00000003 : 00000000`00002000 ffffe205`e22ef010 fffff807`4303eefb fffff807`43a20578 : 0xffffffff`c0000001 ffffb90b`caaeda38 00000000`00002000 : ffffe205`e22ef010 fffff807`4303eefb fffff807`43a20578 ffffe205`db064000 : 0x3 ffffb90b`caaeda40 ffffe205`e22ef010 : fffff807`4303eefb fffff807`43a20578 ffffe205`db064000 ffffe205`db0640d8 : 0x2000 ffffb90b`caaeda48 fffff807`4303eefb : fffff807`43a20578 ffffe205`db064000 ffffe205`db0640d8 00000000`00000000 : 0xffffe205`e22ef010 ffffb90b`caaeda50 fffff807`43a20578 : ffffe205`db064000 ffffe205`db0640d8 00000000`00000000 ffffe205`e22ef010 : 0xfffff807`4303eefb ffffb90b`caaeda58 ffffe205`db064000 : ffffe205`db0640d8 00000000`00000000 ffffe205`e22ef010 00000000`00002000 : 0xfffff807`43a20578 ffffb90b`caaeda60 ffffe205`db0640d8 : 00000000`00000000 ffffe205`e22ef010 00000000`00002000 00000000`00000001 : 0xffffe205`db064000 ffffb90b`caaeda68 00000000`00000000 : ffffe205`e22ef010 00000000`00002000 00000000`00000001 ffffe205`db0649e0 : 0xffffe205`db0640d8 SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID: CORRUPT_MODULELIST_0x116 PRIMARY_PROBLEM_CLASS: CORRUPT_MODULELIST_0x116 FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x116 TARGET_TIME: 2019-07-14T16:23:16.000Z OSBUILD: 18362 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: unknown_date BUILDDATESTAMP_STR: 190318-1202 BUILDLAB_STR: 19h1_release BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202 ANALYSIS_SESSION_ELAPSED_TIME: 22 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:corrupt_modulelist_0x116 FAILURE_ID_HASH: {31ac3780-c5f2-d530-0d34-c94f8f38c68a} Followup: MachineOwner --------- WARNING: Unable to reset page directories

    this is the dump file so you can debug : it https://1drv.ms/u/s!Ap8bJO3qDAhthUD_mQVCFp_eD_yW?e=mUOrwz

    Sunday, July 14, 2019 6:06 PM

All replies

  • Hi,

    The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.

    I cannot find any useful information from the analysis you provided. Please check the following: 

    The GPU is taking more time than permitted to display graphics to your monitor. This behavior can occur for one or more of the following reasons:

    1. You may need to install the latest updates for your display driver, so that it properly supports the TDR process.

    2. Hardware issues that impact the ability of the video card to operate properly, including:
       a. Over-clocked components, such as the motherboard
       b. Incorrect component compatibility and settings (especially memory configuration and timings)
       c. Insufficient system cooling
       d. Insufficient system power
       f. Defective parts (memory modules, motherboards, etc.)
    3. Visual effects, or too many programs running in the background may be slowing your PC down so that the video card can not respond as necessary.

    Besides, check the symptom in safe mode.

    Best regards,

    Yilia 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 15, 2019 7:24 AM
    Moderator
  • Hi,

    Is there anything I can do for you?

    If you have any problems or concerns, please feel free to post here. 

    Best regards,

    Yilia


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 22, 2019 7:55 AM
    Moderator