The screen goes black for a few seconds, comes back, and Windows announces that the display driver stopped responding and has recovered. The first time it is startling; the tenth time it is infuriating, especially mid-game or mid-project. This error is Windows Timeout Detection and Recovery doing its job, forcibly restarting a graphics driver it believes has hung.
TDR crashes have a wide range of triggers, which is why generic advice rarely helps. The cause could be a buggy driver release, a GPU running too hot, an unstable factory overclock, a dying graphics card, or even a Windows power setting starving the GPU. Diagnosis means narrowing that list before changing anything.
This guide follows the order a technician uses: stabilize the driver, rule out heat and clocks, adjust the TDR behavior, then test the hardware. Related display problems like second-monitor detection failures and USB-C charging quirks often share driver roots with TDR crashes.
Why this happens
- Buggy graphics driver release: a new driver version can introduce TDR crashes on specific GPU and game combinations.
- Corrupted driver installation: leftover files from previous installs conflict with the current driver and destabilize it.
- GPU overheating: dust-clogged fans or dried thermal paste let temperatures spike until the driver hangs.
- Unstable overclock: factory or manual overclocks on the GPU core or memory can fail under sustained load.
- TDR timeout too aggressive: the default two-second timeout can trip on heavy workloads that a healthy GPU would finish given more time.
- Insufficient or unstable power: an aging charger or battery on a laptop can starve the GPU during boost clocks.
- Conflicting background software: overlays, recording tools, and aggressive antivirus hooks can interfere with the driver.
- Failing GPU hardware: degrading VRAM or GPU silicon produces crashes that no software change fixes.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Note when the crashes happen
Diagnosis first. Whether crashes happen only in one game, only under heavy load, or even at idle points at completely different causes. Spend five minutes characterizing the pattern before changing anything.
- Write down exactly what you were doing for the last three crashes.
- Check whether crashes happen at idle, in one specific game, or in all 3D loads.
- Open Event Viewer and look under System for nvlddmkm or amdkmdap errors with timestamps.
- Note whether the screen shows artifacts like colored blocks before crashing.
- This pattern determines which of the fixes below matters most.
Fix 2: Clean-install the graphics driver
A proper clean install eliminates corrupted driver state, which is the most common software cause. Use the manufacturer’s installer with its clean-install option rather than relying on Windows Update’s driver.
- Download the latest driver for your exact GPU from NVIDIA, AMD, or Intel.
- Run the installer and choose Custom or Clean installation when offered.
- For NVIDIA, check Perform a clean installation in the installer options.
- Restart the laptop after installation completes.
- Test with the workload that previously crashed.
Fix 3: Use DDU for a truly clean driver sweep
When a standard clean install does not stop the crashes, Display Driver Uninstaller removes driver remnants that normal uninstallers leave behind. Run it in Safe Mode for the full effect.
- Download DDU and the new graphics driver before starting.
- Disconnect from the internet to stop Windows installing a driver mid-process.
- Boot into Safe Mode and run DDU, choosing Clean and restart.
- After reboot, install the downloaded driver normally.
- Reconnect to the internet and test stability.
Fix 4: Check temperatures and clean the cooling
Heat is the leading hardware cause of TDR crashes on laptops. A GPU that thermal-throttles hard can hang badly enough to trip detection. Monitoring temps during the crash workload tells you immediately.
- Install HWMonitor or HWiNFO and watch GPU temperature during the crashing workload.
- Sustained temperatures above 90C on a laptop GPU indicate a cooling problem.
- Blow compressed air through the vents to clear dust buildup.
- Use a cooling pad and make sure vents are not blocked on soft surfaces.
- If the laptop is old, consider a professional repaste of CPU and GPU.
Fix 5: Remove overclocks and test at stock settings
Even factory overclocks on gaming laptops can become unstable as silicon ages or drivers change. Returning everything to stock clocks isolates clock instability as a cause.
- Close MSI Afterburner or any overclocking utility and reset to defaults.
- In the GPU control panel, disable any automatic overclock or boost features.
- Set the Windows power plan to Balanced rather than a maximum-performance custom plan.
- Retest the crashing workload at fully stock settings.
- If crashes stop, any overclock must be re-tuned conservatively.
Fix 6: Increase the TDR delay in the registry
Giving the GPU more time before Windows declares a hang helps workloads that are heavy but legitimate. This is a workaround, not a cure, so use it alongside the real fixes above.
- Press Windows + R, type regedit, and press Enter.
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers.
- Create a new DWORD 32-bit value named TdrDelay and set it to 8.
- Optionally create TdrDdiDelay set to 8 as well.
- Restart and test; remove these values if they make no difference.
Fix 7: Test the GPU hardware and check official drivers
If software steps fail, verify the hardware. A stress test that crashes at low temperatures with stock clocks points at failing silicon, and official driver sources may carry a fixed release.
- Run a GPU stress test like FurMark briefly while watching temperatures.
- Crashes at low temperatures suggest hardware failure rather than heat.
- Check NVIDIA driver downloads or AMD driver support for a newer release.
- Try one driver version older than current to rule out a bad new release.
- If hardware failure is indicated, check warranty status before it expires.
Closing
Display driver crashes feel random but they follow logic: bad driver state, heat, unstable clocks, or dying hardware, in that order of likelihood. Work the list from software to hardware and you will either fix the crashes or arrive at a confident hardware diagnosis instead of guessing.
