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