VIDEO_TDR_FAILURE: When the Graphics Driver Cannot Recover

What causes VIDEO_TDR_FAILURE

• The display driver needs an update: Microsoft says you may need the latest one "so it properly supports the TDR process".
• Hardware that keeps the card from working properly. Microsoft lists overclocked components, wrong memory configuration and timings, insufficient cooling, insufficient power and defective parts.
• Visual effects, or too many programs running in the background, slowing the PC so the card cannot respond in time.

How to fix VIDEO_TDR_FAILURE, safest step first

The steps come from Microsoft's guidance, with the reversible ones first. Each one says how to put back what it changed. If Windows cannot start normally, Microsoft's basic steps say to start in safe mode and continue from there.

1. 01

   Write down the stop code and the file the screen names

   Microsoft Support says the stop code appears at the bottom of the screen and, when Windows knows it, so does the name of the module that was running. If the screen went by too fast, the command under Check it yourself lists the stop codes Windows recorded, and Event Viewer > Windows Logs > System shows the errors logged around the restart.

   To undo: Nothing to undo: this only reads information.

2. 02

   Before you change anything: note the driver and make a restore point

   Open the device's Properties > Driver tab and write down the driver provider, date and version. Then select Start, type Create a restore point, open it, and on the System Protection tab choose Create. Microsoft notes that System Protection is not turned on by default; if Create is greyed out, choose Configure and turn it on for the system drive first.

   To undo: A restore point changes nothing by itself. To go back later, run System Restore and pick it: Microsoft says it reverts system files, the registry and installed programs, and leaves your personal files alone.

3. 03

   Install the current graphics driver

   An out-of-date display driver is the first reason on Microsoft's list. Get the driver for your exact graphics card from its maker, or from the PC maker's support page for a laptop, and install it.

   To undo: Open the display adapter's Properties > Driver tab in Device Manager and choose Roll Back Driver, or apply the restore point.

4. 04

   If it started after a driver update, roll the driver back

   In Device Manager, right-click the device, choose Properties, open the Driver tab and select Roll Back Driver, then give a reason and confirm. Microsoft notes that you need administrator rights, and that going back to the previous driver often fixes a problem that appeared after an update. The button is greyed out when Windows kept no earlier driver for the device.

   To undo: Rolling back is the undo for the update. To return to the newer driver, install it again with Update driver or from the manufacturer's package.

5. 05

   Rule out heat, power and overclocking

   Microsoft lists hardware reasons a graphics card stops answering in time: overclocked components, wrong memory configuration and timings, insufficient cooling, insufficient power and defective parts. Set any overclock back to stock, check that the card's fans spin and its power cables are seated, and test again.

   To undo: Apply your previous clock and fan settings again if they made no difference.

6. 06

   Lighten the load

   Close programs running in the background and try the game or app again at lower settings. Microsoft notes that visual effects or too many background programs can slow the PC enough that the card misses the deadline.

   To undo: Start the programs again and set the game's options back.

7. 07

   Install the latest Windows updates

   Select Start > Settings > Windows Update and choose Check for updates. It is one of Microsoft's basic steps for a stop code that keeps returning, and it is how new versions of Windows' own drivers arrive.

   To undo: If the crashes get worse after an update, apply the restore point from the earlier step.

Check it yourself

1. 01

   List the stop codes Windows recorded (PowerShell)

   Each entry gives the date, the stop code as a hexadecimal number with its four parameters, and where the dump file was saved. On the test PC, Windows 11 build 26300, this ran without administrator rights. An error saying no events were found means Windows recorded none. This stop code appears there as 0x00000116.

   Get-WinEvent -FilterHashtable @{ LogName='System'; Id=1001;
     ProviderName='Microsoft-Windows-WER-SystemErrorReporting' } -MaxEvents 5 |
     Format-List TimeCreated, Message

   PowerShellCopy
2. 02

   List the driver packages installed on the PC

   Shows every third-party driver package with its provider, class, version and date, so you can see what was installed around the first crash. Nothing is changed.

   pnputil /enum-drivers

   cmdCopy