Video TDR Timeout - 0x116 + 0x117

[jcgriff2]

Video Timeout Detection and Recovery (TDR)

There are two bugchecks usually associated with Video TDR -

1. 0X116 - VIDEO_TDR_ERROR​

2. 0X117 - VIDEO_TDR_TIMEOUT_DETECTED​

0x116 and 0x117 are very similar = Video driver was unable to reset within the allotted time (usually 30000ms = 30 seconds). The difference between them:

0x116 = video driver is unable to recover; system BSODs​

0x117 = video driver ultimately does recover; records a "Live Kernel Event"​

​

Windows Vista and later operating systems attempt to detect situations in which computers appear to be completely "frozen". They then attempt to dynamically recover from the frozen situations so that their desktops are responsive again. This process of detection and recovery is known as timeout detection and recovery (TDR).

​

In the TDR process, the operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to reinitialize the driver and reset the GPU. Therefore, end users are not required to reboot the operating system, which greatly enhances their experience.​

​

The only visible artifact from the hang detection to the recovery is a screen flicker. This screen flicker results when the operating system resets some portions of the graphics stack, which causes a screen redraw.​

​

Some legacy DirectX applications (for example, those DirectX applications that conform to DirectX versions earlier than 9.0) might render to a black screen at the end of this recovery. The end user would have to restart these applications.​

​

.... Timeout Detection and Recovery - Microsoft MSDN Library​

​

​

A 0x116 BSOD generates a kernel memory dump file, depending on system crash settings
- Full kernel dump = \windows\memory.dmp
- Mini kernel dump - \windows\minidump

A 0x117 Live Kernel Event generates a WATCHDOG memory dump file
- \windows\LiveKernelReports\watchdog

Timeout Detection and Recovery (TDR) (Windows Drivers)

There are 3 solutions to a TDR Timeout -
1. Update video drivers
2. Roll-back video drivers
3. Replace video card if Desktop PC

 

[usasma]

STOP 0x116/0x117 Troubleshooting
Can also be used to troubleshoot other video errors.
​

If overclocking, please stop and reset the system to stock values while we're troubleshooting. Feel free to resume the overclock once the system is stabilized (once the BSOD's have stopped)

More info on the STOP 0x116 error here: BSOD Index - STOP 0x116
More info on the STOP 0x117 error here: BSOD Index - STOP 0x117

ATI troubleshooting (thanks to Cap'n Jack): How to troubleshoot ?Display driver stopped responding and has recovered?, ATIKMDAG.sys type errors
nVidia troubleshooting (thanks to Vir Gnarus): http://forums.nvidia.com/index.php?showtopic=65161 (link broken at present, but expected to come back up)
Microsoft TDR error troubleshooting KB article: "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista
In general the articles apply to any make/model of video card (so advice from the ATI link may be applicable to nVidia/Intel/other video cards)

Also, try the video stress tests listed here: Additional Hardware Diagnostics

Best advice that I've seen about this error (from here: BSOD - Windows 7 Help Forums )

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling." - H2SO4

When fiddling with drivers, try the DRIVER ONLY installation instructions here:
ATI - ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums
nVidia - nVidia Video Cards - DRIVER ONLY installation procedure - Sysnative Forums

Final suggestion is to try another video card. If you don't have one to try it with, I'd suggest purchasing one from a shop that will allow you to return it for a full refund if you don't need it.

**********************************************************************
Further troubleshooting suggestions - my comments are in RED. This was extracted from this post - ( Moved: Misc tasks, screen freezes, video driver unloads, BSOD atikmpag - Page 3 - Windows 7 Help Forums )

From this link ( Support Forums | Community ):

The following hardware issues are examples that can cause a TDR event:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: Memory Diagnostics and Additional Hardware Diagnostics )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( Hard Drive Diagnostic Procedure ), reset your pagefile)

Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

and run the System File Checker

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!))
- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

The following software issues are examples that can cause a TDR event:
-Incompatible drivers of any sort (either GPU, sound, etc) Windows Compatibility Center: Find Updates, Drivers, & Downloads for Windows 8, Windows RT and Windows 7
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for Win7 - but in early to mid-2012 there were some reported issues w/ATI drivers)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for Win7)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Win7)

Extracted and updated from this topic: STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Help Forums

 

[jcgriff2]

From Microsoft - Timeout detection and recovery (TDR) - Windows drivers | Microsoft Docs

John