Fix GPU Driver Crashes (2026): NVIDIA & AMD Timeout Errors

A recovered display-driver timeout records a graphics stall and a reset. It does not tell you which component caused it.

Start by saving the exact event, driver version and the change that preceded the first failure. A driver regression remains possible, alongside unstable settings or a hardware problem. The next steps are comparisons: use the same workload after each change so that a quiet afternoon does not become proof that an intermittent fault is fixed. Keep those records when asking the component or system maker for help. The guide below explains Windows recovery, then works through supported driver and tuning checks. Leave the TDR registry timeout alone; Microsoft’s instructions reserve those controls for driver development.

If you have a Radeon card and started getting driver timeouts in late August or September 2026, see what AMD and Microsoft have and haven’t published about them first.

Which message do you have?

Three messages people search for are one Windows mechanism with different outcomes. Find yours in the table.

Microsoft’s archived Event ID 4101 page, written for Windows Vista and 7, gives the message as “Display driver %1 stopped responding and has successfully recovered,” logged as Event ID 4101 from the source Display. The %1 is the driver module.

On NVIDIA it is nvlddmkm, which NVIDIA’s own security bulletin calls the “kernel mode layer (nvlddmkm.sys)” of its display driver; on AMD it shows up as names such as amdwddmg, as in this Microsoft Q&A report.

The AMD window comes from AMD Software’s Issue Detection, which the AMD Bug Report Tool page says is on by default and launches the tool “when BSOD, TDR, or device installation error is detected.” The same page says you can turn Issue Detection off. That hides the window.

The timeout stays.

Use the message to preserve the right evidence. Repeated failures deserve investigation, but a recovered flicker and a failed reset do not assign a probability to a hardware versus software cause. Work through the comparisons below and keep the exact result of each.

What is happening: TDR explained

Windows has a built-in safety feature called Timeout Detection and Recovery, or TDR. According to Microsoft’s documentation, TDR detects when the GPU takes longer than expected to complete an operation, then resets the graphics card so the entire system does not hang.

The GPU scheduler inside the DirectX graphics kernel (Dxgkrnl.sys) notices the stall and tries to preempt the stuck task. The wait time on that preempt operation is the TDR timeout.

That timeout is short. The default TDR timeout period in Windows is two seconds. If the GPU cannot finish or preempt the current task within that window, the OS decides the GPU is frozen and resets it.

When the reset succeeds, the only visible artifact is a brief screen flicker as the OS redraws the desktop, plus the informational message “Display driver stopped responding and has recovered,” which Windows also logs in Event Viewer. That recovery is a good outcome.

The bad outcome is bug check 0x116, VIDEO_TDR_FAILURE, which Microsoft defines as an attempt to reset the display driver and recover that failed. Windows also bug-checks the whole machine by default on the sixth GPU hang inside one minute, controlled by TdrLimitCount (default 5) and TdrLimitTime (default 60 seconds).

There is one useful nuance. Microsoft’s TDR page describes engine timeouts (0x141), which reset one part of the GPU. When they repeat, Windows blocks GPU access for the process causing them and logs 0x142, so “the malfunctioning process doesn’t bug-check the system.”

So an engine timeout can end one program’s access to the GPU while the rest of the desktop keeps running, instead of the entire screen flickering at once.

If a game closes without a recovered-driver message, inspect its error and Windows logs before assigning it to this TDR path. Application failure, device removal and graphics recovery can leave different records.

What the timeout identifies

Microsoft’s 0x116 reference lists driver updates, incompatible settings, overclocking, inadequate cooling or power, defective parts and background workload among the possibilities. Microsoft does not rank their frequency. Counting bullets cannot establish that most cases are hardware faults. Keep the module name: it helps support correlate the failure with the graphics stack, but a named display-driver module does not prove either a driver defect or a healthy driver. The next comparison needs the workload and preceding change as well as the stop code.

For a load-only failure, record whether it occurs in one game or across several, and whether the screen recovers or the whole PC restarts. Those patterns choose tests. They do not replace them.

The fix path, in order

The order is mine. It starts with reversible software comparisons and follows Microsoft’s possibilities and AMD’s stability checklist. Keep the same reproducing workload and test after each step.

1. Do a DDU clean reinstall in Safe Mode

I start here because it costs nothing but time and it clears the most frustrating case, where a new Game Ready or Adrenalin driver broke something that worked fine before. A rollback or an over-install can leave enough state behind to keep the bug alive, which is why a clean wipe comes first.

On a Radeon card, AMD’s own checklist gives two routes: the Factory Reset option during the driver’s setup, or the AMD Cleanup Utility before installing. Display Driver Uninstaller (DDU) from Wagnardsoft is the third-party tool for either brand.

Its official guidance is to run it in Safe Mode (strongly recommended), use the “Clean and restart” option, and disconnect the internet or block Windows Update until your new driver is installed, so Windows does not silently reinstall an old driver behind your back.

Download the latest driver straight from NVIDIA or AMD first, then run DDU, then install the fresh driver. As one community write-up puts it, the leftover registry and driver-store entries that survive an over-install are exactly what keep regression bugs alive.

Intel prescribed the same fix when one of its driver updates left monitors unrecognized and blank. Its support article says to uninstall with DDU, then install the latest driver in Safe Mode.

2. Separate user tuning from the factory profile

Save the current settings. Reset user overclocking or undervolting in the tool that applied it, then stop that tool from reapplying the profile during the test. AMD’s stability guidance recommends restoring defaults and removing third-party tuning/monitoring variables while investigating. That does not necessarily remove a factory overclock. A board sold as an OC edition can retain its supplied profile after the utility is reset. “I pressed Reset” is insufficient evidence. Check which profile the board is using before calling it a reference-clock comparison.

For supported NVIDIA configurations, NVIDIA documents Debug Mode as a way to use reference clocks, disabling factory and user overclocking for diagnosis. Its NVIDIA App path is System → Advanced → Debug Mode. Use the option only where the installed software exposes it, record the change and repeat the failing workload. If that comparison changes the result, take both runs to the board maker. It identifies sensitivity to the tested configuration; it is not a population claim about OC cards.

For another GPU or a missing option, request the exact board’s supported diagnostic procedure instead of guessing clock offsets, voltage settings or a different firmware image.

3. Clear overlays and shader caches

Disable in-game and app overlays from Discord, Steam, and Adrenalin, and clear the shader cache.

Overlays inject themselves into the render path, and a stale shader cache can replay a corrupt state every launch.

This is also a common fix for game-specific crashes, which overlap with anti-cheat conflicts; if a single protected game is the one crashing, our Easy Anti-Cheat fix guide covers that adjacent failure mode in depth.

4. Update Windows and BIOS, then test with XMP/EXPO off

Update Windows and your motherboard chipset and BIOS, set the BIOS to optimized defaults, and test with your memory profile (XMP, EXPO, or DOCP) turned off. Memory instability is one of Microsoft’s named causes, and a too-tight or marginal memory profile is a classic source of TDR.

AMD’s guidance also recommends verifying the BIOS is on optimized factory defaults, setting “Power Supply Idle Control” to Typical, and — to rule out RAM — installing one module at a time and scanning memory with MemTest86. Repeat the workload at the supported default memory configuration. Improvement makes the old configuration worth investigating; one clean day cannot clear an intermittent memory fault.

5. Check power delivery and reseat the GPU

If crashes persist, inspect the physical layer. Check that PSU cables are fully seated, pay special attention to a 12VHPWR connector if your card uses one, and reseat the GPU in its PCIe slot. Insufficient power is one of Microsoft’s listed possibilities. Follow the card and PSU makers’ connection instructions, then repeat the workload before deciding whether a PSU replacement is justified.

6. Disable MPO with NVIDIA’s official registry file

NVIDIA publishes a registry file that disables MPO — mpo_disable.reg, with mpo_restore.reg to put it back — and both require a restart to take effect.

That page, revised September 28, describes MPO neutrally, as a feature that “can improve performance and reduce power consumption by offloading certain composition tasks from the desktop window manager to dedicated hardware,” and gives the disable and restore steps. It does not attribute flickering or stuttering to MPO.

That is new: an archived copy shows the same answer in February 2021 titled “After updating to NVIDIA Game Ready Driver 461.09 or newer, some desktop apps may flicker or stutter when resizing the window,” with these files as the workaround.

The current revision adds that from Release 610 drivers, MPO works on all monitors in multi-monitor setups on Blackwell GPUs, and asks for Windows build 26100.7705 or 26200.7705 or later.

So flicker when you drag or resize a window is the case NVIDIA wrote these files for. The common third-party method, a DWORD named OverlayTestMode set to 5 under the DWM key, may no longer reliably disable MPO on Windows 11 24H2 and later, so NVIDIA’s own file is the authoritative route.

The TdrDelay myth: do not do this

Search “fix driver stopped responding” and you will find dozens of pages telling you to raise the TdrDelay value in the registry.

The exact keys live under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers, and Microsoft documents the defaults: TdrLevel is 3, TdrDelay is 2 seconds, TdrDdiDelay is 5 seconds, TdrLimitCount is 5, and TdrLimitTime is 60 seconds.

Microsoft’s page is written for driver developers, and it says “End users shouldn’t manipulate these registry keys.” The old Windows 7 era Event ID 4101 page linked above still suggests raising the timeout. The current developer page is the one to follow. Raising TdrDelay only gives a hung GPU more time before Windows resets or bug-checks it.

You get fewer recovery popups and a delayed blue screen, but the unstable overclock, faulty memory, weak power, or broken driver that caused the stall is still there. It is the equivalent of taping over a check-engine light. Fix the cause from the ordered list above instead.

Radeon driver timeouts in September 2026

At the end of September 2026, r/AMDHelp had a run of driver-timeout threads, enough that one poster proposed a megathread and another ran a poll on how many people were getting them. The cards named run from the RX 5700 XT to the RX 9070 XT. Some posters suspect a Windows update; others suspect AMD’s drivers.

None of AMD’s or Microsoft’s pages I read names a cause for the wider run of reports. Here is what those pages said when I read them on September 28, 2026.

AMD. For its two newest drivers, the only AMD statement about a timeout I found is a reply further down AMD’s 26.8.1 release-notes thread on its forum.

In it AMD_Matt, the account marked (AMD) that posts the release notes there, wrote that AMD was investigating an issue with Adrenalin 26.8.1 that brings “a driver timeout/hang” in Apex Legends and War Thunder under DX12. The reply was last edited August 26.

The workaround he gave is to roll back to the previous driver or use DX11 mode if the game has it. The 26.8.1 release notes don’t list it.

The optional 26.9.1, dated September 3, lists an intermittent Apex Legends crash on RX 9000 cards as fixed. War Thunder isn’t mentioned. No driver timeout appears among its known issues, and I found no later release note on AMD’s site.

On September 9 the same account told one poster with an RX 9070 XT and another with an RX 7800 XT, both with games crashing on driver errors, to update to 26.9.1, which “did address some stability issues in DX12 apps”.

He didn’t mention timeouts.

Microsoft lists nothing for AMD.

Its known-issues pages for Windows 11 25H2 and 24H2 name no AMD or Radeon problem for the September 8 security update (KB5124008), the September 14 out-of-band fix (KB5129195) or the September 22 preview (KB5124010).

The one black-screen entry there, about the desktop failing to load after sign-in, began with the August 27 preview (KB5120998), and Microsoft has seen it mainly on Azure Virtual Desktop hosts using FSLogix.

What I would do, in order:

1. If the timeouts come in Apex Legends or War Thunder under DX12 on 26.8.1, switch the game to DX11 if it offers that. AMD lists it beside rolling back, and I would try it first because you keep your driver.
2. Still timing out, or crashing in other DX12 games? Install 26.9.1, the driver AMD pointed those September posters to. Its notes also list an intermittent Apex crash on RX 9000 cards as fixed, though AMD hasn’t said either fix covers the timeout above.
3. If 26.9.1 doesn’t clear it, roll back to 26.7.1, the release AMD’s 26.8.1 notes sent RX 9000 owners back to for a Starfield crash. Its own notes list one timeout, in Battlefield 6 on the Ryzen AI 9 HX 370. Remove the driver you’re on before installing it. AMD recommends its Cleanup Utility when you downgrade, and DDU, covered in the fix path above, is the third-party tool for the same removal.
4. If none of that clears it, or the timeouts come on the desktop or in a browser, nothing I found from AMD or Microsoft addresses them. Work the ordered fix path above from the clean install down.

When it really is the driver (and when it is hardware)

Sometimes a specific driver build genuinely is broken, and a fresh update is the fix.

AMD’s release notes for Adrenalin 26.6.2 list one “intermittent application crash or driver timeout” as fixed (RoadCraft on RX 7000 cards) and another as a known issue (Battlefield 6 on the Ryzen AI 9 HX 370).

On the NVIDIA side, Tom’s Hardware reported on February 27, 2025 that black screens, “alongside BSODs and various game crashes,” had plagued the RTX 50-series since the RTX 5090’s January launch, that Game Ready driver 572.60 fixed “various black screen issues,” and that NVIDIA confirmed vBIOS updates as an alternative route to the same fix.

So updating to a fixed build, or rolling back to a known-good one when a new release regressed, is sometimes exactly right.

If crashes survive those comparisons, I would investigate hardware while keeping unresolved driver, game and compatibility issues open. Preserve the logs and test a known-good component only where the maker supports that procedure. Persistence after several software changes is not proof that a GPU or PSU has failed.

If the card is throwing visual corruption — colored lines, snow, or garbled textures — rather than clean crashes, that’s a related but distinct symptom; our guide to GPU artifacts shows how to tell a dying card from a bad cable or an unstable overclock.

And if the card has stopped being detected altogether — gone from Device Manager, or absent from the BIOS screen — that’s a separate diagnostic path; see graphics card not detected to find where it disappears before assuming the card is dead.

If you suspect the card itself is on the way out and you are weighing a replacement, our 2026 GPU hierarchy ranks current cards by real performance tier, and the GPU comparison tool lets you put two specific cards side by side so you can size an upgrade sensibly rather than guessing.

Next steps and related tools

Keep the evidence together. Compare the clean driver installation and user-tuning defaults, then use a supported factory-profile test where appropriate. Follow the remaining clues if the failure returns. Leave TdrDelay unchanged; increasing a recovery timeout does not identify the cause of the stall. If a single anti-cheat-protected game is what crashes rather than your whole desktop, read the Easy Anti-Cheat fix guide next. If your testing points at a dying card and you need an upgrade, the 2026 GPU hierarchy and the GPU comparison tool will help you pick the right replacement without overspending.