“Display driver stopped responding and has recovered”: what to check

A game freezes, the screen flashes, and the desktop returns with the message “Display driver stopped responding and has recovered.” Windows has detected a graphics timeout and recovered the desktop. The message confirms that recovery succeeded; it does not identify why the graphics work stopped responding.

Start by separating three outcomes: a brief flicker with the desktop back, one game that stays black after Windows returns, or a Windows restart with a stop code. They call for different next steps. This guide uses Windows 11 settings and Microsoft's documented graphics behaviour; it cannot diagnose a particular PC from the message alone.

What Windows is recovering

Windows uses timeout detection and recovery (TDR) to respond when graphics work stops making progress. The Windows Display Driver Model's GPU scheduler tries to pre-empt work that is taking too long. Microsoft's driver documentation gives two seconds as the default wait timeout for that pre-emption request. If the work cannot finish or be pre-empted in time, Windows treats the GPU as unresponsive and attempts to reset the graphics stack.

A short screen flicker can appear while the display is redrawn. After a successful recovery, Windows shows the message above and records it in Event Viewer. Some older DirectX applications may stay black after the reset and need to be restarted. These are details of the recovery process, not a diagnosis of its cause. Microsoft lists several possibilities, including driver problems, heavy background work, overclocked or incompatible component settings, insufficient cooling or power, and defective hardware.

Identify which outcome you saw

• The screen flickered once and the desktop is responsive again. Note the time and what was open. If the issue does not return, you do not need to change several settings in response to one recovered event.
• Windows returned, but one game stayed black or stopped responding. Save if the game still accepts input, then close and reopen that game. Some applications do not recover cleanly after the graphics device resets. Check that game's update notes or support page if the same title triggers the problem again.
• The whole PC restarted with a stop code. Write down the exact code. VIDEO_TDR_FAILURE (0x116) means Windows' attempt to reset the display driver and recover from a timeout failed. That is different from the successful “has recovered” message. Repeated stop-code restarts deserve a closer look at the driver and hardware.

A blank screen without a recovered message or stop code is not enough to identify a TDR. Treat it as a separate display problem and follow the relevant instructions from your PC or display maker.

Record the event before changing drivers

Write down the exact time, the game or app, what you were doing, whether other apps were affected, and whether this began after a confirmed driver, Windows or game update. A small timeline can make a pattern visible without changing several variables at once.

To check Windows' record, open Event Viewer, choose Windows Logs → System, and look near the time of the flicker or restart for display-related entries. Read the event's source, time and message together. Microsoft's TDR documentation says a successful recovery is logged in Event Viewer; the log gives you another clue to share, not a verdict that a graphics card has failed.

If it began after a display-driver update

When the problem began immediately after a display-driver update, consider rolling back that adapter's driver before reinstalling everything:

1. Search for and open Device Manager.
2. Expand Display adapters.
3. Right-click the affected adapter and choose Properties.
4. Open the Driver tab and choose Roll Back Driver, then confirm.
5. Restart Windows and check the same game or workload again.

Microsoft notes that Roll Back Driver is unavailable when Windows has no previous driver version stored. If there is no rollback option, check the exact PC or graphics-adapter maker's support page for a compatible driver and follow its installation instructions. Avoid third-party driver-updater downloads.

Change one thing at a time and compare the same activity. If you recently changed GPU or memory clocks, return only that change to the last stable setting before testing. Do not raise voltages or alter several firmware settings to chase a timeout.

Leave TDR registry settings alone

You may find advice to increase TdrDelay or edit other graphics-driver registry values. Microsoft documents these TDR keys for testing and debugging during driver development and says end users should not manipulate them. A longer timeout changes how Windows handles detection; it does not explain why the graphics work stalled or establish that the underlying problem is fixed.

When to ask for hardware support

If timeouts recur across different games and apps, continue after a driver change is reversed, or end in repeated stop-code restarts, collect the event time, exact message or code, PC model, graphics adapter, driver version and recent changes. Share that record with the PC maker or graphics-adapter maker. Their support route can account for the exact hardware and provide its diagnostics.

A recovered flicker is a useful signal. Use it to narrow down whether the issue follows one app, one recent driver change or several graphics workloads. That gives your next step a reason to exist.

Sources

• Microsoft Learn, WDDM support for timeout detection and recovery (TDR) — updated 5 November 2025.
• Microsoft Learn, Bug Check 0x116: VIDEO_TDR_FAILURE — updated 22 December 2022.
• Microsoft Learn, Testing and debugging TDR during driver development — updated 7 November 2025.
• Microsoft Support, Troubleshoot screen flickering in Windows — driver rollback steps and availability notes.