Display driver stopped responding and has recovered

Fix 'Display driver stopped responding and has recovered' on Windows 10/11

When your screen freezes, flickers, or goes black and then this error pops up, the GPU driver hit a timeout. Here's why and how to fix it for good.

You're mid-game or maybe just scrolling through a web page with hardware acceleration enabled, and suddenly the screen freezes. A few seconds later everything goes black, your monitor loses signal, and then Windows chimes and a balloon appears: "Display driver stopped responding and has recovered". Sometimes the screen just flickers once. If you're on Windows 10 or 11, this is the classic TDR (Timeout Detection and Recovery) event.

What's actually happening here is that your GPU took longer than two seconds to respond to a command from the operating system. Windows has a built-in watchdog—a timer—that expects the display driver to finish its current operation within that window. If the GPU is bogged down, hung on a bad instruction, or the driver itself is locked up, the watchdog assumes the driver is dead and forces a reset. The driver then reloads, and you get that message. It's not a crash of the whole system, but it's a sign that something is frustratingly wrong.

The root cause is almost always one of these three: a buggy or outdated graphics driver, an unstable GPU overclock (including factory overclocks that are too aggressive), or a power/thermal issue that causes the GPU to throttle or lock up. Less common but real: the TDR timeout value in the registry is set too low by some applications, or you have a corrupted DirectX shader cache.

The Fix: Steps That Actually Work

  1. Update your graphics driver—but do it right. Skip the "check for updates" button. Go to the manufacturer's site directly. For NVIDIA, that's nvidia.com/drivers. For AMD, amd.com/support. Download the latest driver for your exact GPU model and Windows version. Then use Display Driver Uninstaller (DDU) in Safe Mode to wipe the old driver completely. Reboot, then install the new one. This removes any leftover registry entries or files that might be causing conflicts.
  2. Check your GPU temperature and clock speeds. Download HWiNFO64 (free) and look at the GPU core temperature, hot spot temp, and memory junction temp if you're on an AMD card. If your GPU hits 90°C or higher under load, that's your problem. Clean the dust out of your case, check your fans, and if you're on a laptop, make sure the vents aren't blocked. Overheating causes the GPU to throttle, and throttling can cause the driver to miss its deadline.
  3. Remove any overclock—including factory ones. If you're using MSI Afterburner or EVGA Precision X1, set the core clock and memory clock back to stock. Even if you didn't overclock manually, some factory overclocked cards (like ASUS ROG Strix or MSI Gaming X) are unstable out of the box. Test at stock settings first. If the error stops, you know it's a stability issue. Then you can try a mild undervolt instead—it often makes the card more stable and cooler.
  4. Increase the TDR timeout (registry hack). This doesn't fix the root cause, but it gives your GPU more time before Windows kills the driver. It's a stopgap, not a cure. If you're constantly getting the error every few minutes, it can get you past a game session. Open Registry Editor (regedit) and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers

Create a new DWORD (32-bit) value named TdrDelay and set it to 10 (decimal). That's 10 seconds instead of the default 2. Reboot. If the error persists after 10 seconds, then it's not a matter of timing—the driver is truly hung.

What Else Could It Be?

If you've updated the driver, verified thermals, and removed overclocks, and it's still happening, look at your power supply. A dying or underpowered PSU can cause voltage drops that make the GPU crash randomly. This is especially common with high-end cards like an RTX 3080 that draw sudden power spikes. Check your PSU's wattage and age—if it's over five years old, consider replacing it.

Also, check the Windows Event Viewer for the exact error. Open Event Viewer, go to Windows Logs > System, and look for Event ID 4101 for the TDR event. If you see additional errors like Event ID 14 or 13 from the display driver, that gives you a clue. For NVIDIA, the error might reference nvlddmkm.sys; for AMD, it's atikmpag.sys. Those filenames tell you the driver is the culprit, not the hardware.

Still Failing? Try These

  • Clean install older driver. Sometimes the newest driver is the buggy one. Known good versions exist for every GPU. Search "best driver for [your GPU] stability" and install that.
  • Disable hardware acceleration in your browser (Chrome/Edge: Settings > System > Use hardware acceleration when available). Also disable it in Discord, Slack, or any Electron app. That's a common fix if the error only happens when you're not gaming.
  • Run a GPU stress test like FurMark or OCCT to see if the error triggers under a controlled load. If it does, it's almost certainly a hardware instability—either thermal or power.
  • Check the GPU physically. Reseat the card in the PCIe slot, and make sure the power connector is fully clicked in. Sounds silly, but a loose connector causes random resets.

The TDR error is a symptom, not a disease. The steps above address the three most common causes, and in my experience, step 1 (clean driver install) fixes it for 60% of people. The rest usually have a thermal or power issue. If you've done all of this and the error still appears, the GPU itself may be dying—especially if it's an older card. In that case, start saving for a replacement.

Related Errors in Software – Games & Drivers
The program can't start because MSVCR120.dll is missing "MSVCR120.dll missing" error in Windows games – fix it Game Won't Launch on Windows 11? Fix the Top 3 Causes DirectX Runtime Error Fix DirectX Runtime Error at Game Launch on Windows 11 0xc000007b Fix 'The application was unable to start correctly (0xc000007b)' on game launch

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.