"Display driver stopped responding" while a video plays on a Radeon RX 7000 card
If you are on a Radeon RX 7000 card running Windows 11 and the screen blanks or flickers for a moment while a video plays, AMD has acknowledged exactly this: a driver timeout during video playback with Hardware-Accelerated GPU Scheduling enabled, listed as fixed in Adrenalin 26.10.2 of 30 October 2026. Install that driver first - it is an optional release, so an updater set to recommended drivers only will not offer it. Do not raise TdrDelay in the registry: Microsoft says end users should not touch those keys, and a longer timeout hides the hang instead of fixing it.
Start here
The message you are seeing is not AMD's. It is Windows' own Timeout Detection and Recovery notice, and it appears whenever any GPU misses its deadline - so almost every page that ranks for it is a generic list of remedies written for no particular cause. This page is about one specific cause that AMD has written down and fixed, and about how to tell whether it is yours.
Symptoms
- The screen goes black or flickers for about a second while a video plays in a browser or a media player, then comes back on its own
- Windows shows the notification "Display driver stopped responding and has recovered"
- The same message appears in Event Viewer for the moment it happened
- It happens during video playback rather than in a game
- A game or other DirectX application that was already open may render black afterwards and need restarting
- You have a Radeon RX 7000 series card and Hardware-accelerated GPU scheduling is on
Why this happens
AMD's acknowledged video-playback timeout on Radeon RX 7000 with HAGS enabled
AMD's Adrenalin 26.10.2 release notes list, under Fixed Issues, an intermittent driver timeout while playing video on Windows 11 with Hardware-Accelerated GPU Scheduling enabled on Radeon RX 7000 series graphics products. All four conditions are part of AMD's own wording: the RX 7000 generation, Windows 11, video playback, and HAGS switched on. If your situation matches all four, this is the cause, and the fix is a driver update rather than anything you change on your machine.
Check whether your case matches all four conditions AMD names · Install Adrenalin 26.10.2 or later - from AMD's page, not the in-app updater · Turn Hardware-accelerated GPU scheduling off if you cannot take the optional driver
What the message itself means, whatever caused it
Timeout Detection and Recovery is a Windows feature, not a driver fault message. The GPU scheduler inside Dxgkrnl.sys watches how long the GPU takes on a task and tries to preempt one that overruns; the wait on that preempt is the timeout, and Microsoft documents the default as two seconds. If the GPU neither finishes nor yields in time, Windows decides the GPU is frozen, resets the graphics stack, purges video memory, redraws the desktop - which is the flicker you see - and then shows you the recovery message. So the notice tells you a reset happened, and nothing at all about why.
Fixes
Check whether your case matches all four conditions AMD names
about 5 minAMD's wording is narrow on purpose. If any one of the four conditions does not hold, a driver update is not the answer and you are looking at a different problem with the same message.
Applies to: Radeon RX 7000 series on Windows 11
- Find your graphics card: press Ctrl+Shift+Esc, open the Performance tab and read the GPU entry, or open Device Manager and expand Display adapters. AMD's note covers the Radeon RX 7000 series only.
- Check your Windows version: press Windows+R, type winver and press Enter. AMD's note names Windows 11 only.
- Check whether Hardware-accelerated GPU scheduling is on, in Settings > System > Display > Graphics, under Advanced graphics settings. Microsoft notes the toggle appears only on systems with a supporting GPU and the necessary display drivers.
- Note what you were doing. AMD's entry is specifically about video playback. If your resets happen in games instead, this page is not your answer.
Confirmed by the vendor.
Install Adrenalin 26.10.2 or later - from AMD's page, not the in-app updater
about 20 minThis is the release that carries AMD's fix. It matters where you get it from: 26.10.2 is an optional driver, and the previous releases had a bug where AMD's own Install Manager failed to find optional drivers at all.
Applies to: Windows 11 version 21H2 and later, Windows 10 64-bit version 21H2 and later
- Check what you are running now: open Device Manager, expand Display adapters, open your Radeon card's Properties and read the Driver tab. AMD gives 26.10.2 as driver version 26.20.15.12, with Windows Driver Store version 32.0.32015.12012.
- If you are on anything earlier, download 26.10.2 from AMD's own release-notes page for that version rather than relying on a driver check inside Adrenalin. AMD lists "AMD Install Manager fails to locate optional drivers for AMD Software: Adrenalin Edition when Recommended + Optional is selected" as a bug fixed in 26.10.2 itself, so the updater you would use to find it is the thing that was broken.
- Install it and restart. Afterwards, re-check the Driver tab and confirm the version actually changed - an install that silently failed is the usual reason a driver fix appears not to work.
- Play the video that triggered it before changing anything else, so you know whether the update alone settled it.
Confirmed by the vendor.
Source: AMD, Igor's Lab
Turn Hardware-accelerated GPU scheduling off if you cannot take the optional driver
about 10 minHAGS being enabled is one of the conditions AMD states for this bug, so switching it off removes a condition. It is a stop-gap, not AMD's fix, and it is also the cleanest way to confirm the diagnosis.
Applies to: Windows 11, Systems where the HAGS toggle is present
- Open Settings > System > Display > Graphics, then open Advanced graphics settings.
- Switch Hardware-accelerated GPU scheduling off. If the toggle is not there at all, your GPU or driver does not support the feature, which means HAGS cannot be your cause.
- Restart the PC - the setting does not take effect until you do.
- Play the same video again. If the resets stop, that is good evidence you had AMD's bug, and worth noting: once you are on 26.10.2 or later you can turn HAGS back on.
Confirmed by the vendor.
Known issues
Fixed by AMD. Adrenalin 26.10.2, last updated 30 October 2026, lists "Intermittent driver timeout may be observed while playing video on Windows 11 with Hardware-Accelerated GPU Scheduling (HAGS) enabled on Radeon RX 7000 series graphics products" under Fixed Issues. Independent coverage on 2 November 2026 reports the same entry. The next release, 26.11.1 of 12 November 2026, does not list it again under Known Issues, so the fix holds.
Affects Radeon RX 7000 series, Windows 11, Adrenalin releases before 26.10.2, Fix still holding in Adrenalin 26.11.1 · Status: fixed
The fix is in AMD's optional channel, and until this same release the updater could not find optional drivers. AMD's 26.10.2 page is titled "Optional Driver Release Notes", and the same release fixes "AMD Install Manager fails to locate optional drivers for AMD Software: Adrenalin Edition when Recommended + Optional is selected". That is a catch: the fix for the updater ships in the optional driver the broken updater could not find. Download it from AMD's page directly.
Affects AMD Software: Adrenalin Edition 26.10.2 Optional (30 October 2026) · Status: fixed
AMD does not say which earlier drivers carried the bug. The entry appears only in the 26.10.2 fixed-issues list, with no first affected version and no date it was opened, so this page cannot tell you whether the driver you are on today is one of the affected ones - only that 26.10.2 and later are not.
Affects Adrenalin releases before 26.10.2 · Status: fixed
No independent confirmation that AMD's fix clears it in practice. AMD's release note is the only source, and a re-check on 16 November 2026 for readers reporting the timeout still happening after installing 26.10.2 or 26.11.1 found nothing either way. This page rests on AMD's own statement, which is why the update step is first and the confirmation step asks you to test the same video afterwards.
Affects AMD Software: Adrenalin Edition 26.10.2 Optional (30 October 2026), AMD Software: Adrenalin Edition 26.11.1 (12 November 2026) · Status: unknown
AMD names Radeon RX 7000 only. Driver resets during video playback happen on other hardware too, including other Radeon generations and GeForce cards, but those are different faults with different fixes and AMD's entry does not cover them.
Affects Radeon RX 7000 series · Status: open
A separate Radeon RX 7000 known issue is still open in 26.11.1: an intermittent application crash or driver timeout while playing Assassin's Creed Black Flag Resynced. If your resets happen in that game rather than during video, that is the entry that applies to you.
Affects Radeon RX 7000 series, AMD Software: Adrenalin Edition 26.10.2 and 26.11.1 · Status: open
Not the same bug as the NVIDIA one that looks identical. NVIDIA fixed a separate video-playback freeze and black screen introduced by its 621.01 driver, on GeForce RTX 50 Series and RTX Spark, in hotfix 621.12 of 27 October 2026 and then in WHQL Game Ready 621.14 of 4 November 2026 (bug 6979343). Two vendors shipped unrelated video-playback display faults within weeks of each other.
Affects NVIDIA GeForce Game Ready 621.01, NVIDIA GeForce/RTX Spark Hotfix 621.12 (27 October 2026), NVIDIA GeForce Game Ready 621.14 WHQL (4 November 2026) · Status: fixed
If none of this worked
This page covers one documented cause of one Windows message, and the message has many. If your card is not an RX 7000, if you are on Windows 10, or if the resets happen in games rather than during video playback, AMD's entry does not apply and updating to 26.10.2 is unlikely to change anything. Two signs you are somewhere else entirely: if the machine blue-screens instead of recovering, Windows is bug-checking after five or more GPU hangs inside a minute, which points at hardware or a far more serious driver fault than this one; and Windows treats an engine timeout differently from an adapter timeout - for an engine timeout it blocks the one misbehaving process from the GPU and logs that, instead of resetting the whole adapter, so a single application dying repeatedly is that application's problem rather than your driver's. Game-specific Radeon timeouts are their own faults with their own vendor entries - the War Thunder and Assassin's Creed Black Flag Resynced pages here cover two that AMD documents separately.
Common questions
- Should I increase TdrDelay in the registry?
- No. Microsoft's own documentation for those keys says to use them "for testing or debugging purposes only during the driver development process", and carries an Important note reading "End users shouldn't manipulate these registry keys". TdrDelay is the timeout threshold, two seconds by default; raising it means Windows waits longer before resetting a GPU that has already stopped responding, so the notification goes away while the stall it was reporting gets longer. Setting TdrLevel to 0 is worse - that disables detection altogether, which turns a one-second flicker you recover from into a frozen desktop. This advice appears on most pages that rank for the error message, and it is not a fix for anything.
- Does turning off Hardware-accelerated GPU scheduling cost me performance?
- Microsoft's position is that you should not notice. The DirectX team introduced the feature saying the transition should be transparent and that users should not notice any significant changes, because most applications already hide scheduling costs by buffering their work. It is a latency feature rather than a frame-rate feature, so leaving it off while you wait for a driver is a cheap trade. There is a fuller discussion on our page about whether HAGS improves performance.
- Why doesn't Adrenalin offer me 26.10.2?
- Because it is an optional release, not a recommended one, so an updater configured for recommended drivers will not surface it. There is a second reason too: AMD lists a bug in which the Install Manager failed to locate optional drivers even when "Recommended + Optional" was selected, and the release that fixes that bug is 26.10.2 itself. Download it from AMD's release-notes page for 26.10.2 rather than waiting for the in-app check to find it.
- Is this the same bug as the NVIDIA video-playback black screen?
- No, though the symptom looks identical. NVIDIA acknowledged and fixed a separate video-playback freeze and black screen introduced by its 621.01 driver, affecting GeForce RTX 50 Series and RTX Spark systems, in hotfix 621.12. Two vendors shipped unrelated video-playback display bugs within weeks of each other; the fix you need depends on which card you have, and our 621.01 page covers the NVIDIA one.
- Can I just roll back to an older driver instead?
- Rolling back is the wrong direction here, because the fix is in the newer driver, not the older one. AMD does not say which earlier releases carried this bug, so going backwards is a guess. If you do need to downgrade an AMD driver for some other reason, AMD recommends using its Cleanup Utility first.
- Does the message mean my graphics card is failing?
- Not by itself. Timeout Detection and Recovery exists precisely so that a GPU which overruns its deadline gets reset instead of hanging the whole machine, and Microsoft describes the visible result as a screen flicker followed by an informational message. A single recovery traceable to a known driver bug is a software problem. Repeated recoveries that end in a blue screen are a different matter: Windows bug-checks after five or more hangs within a minute, and at that point hardware is worth investigating.
Did this fix work?
If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.
Report a problem with this pageRelated problems
- Does Hardware-Accelerated GPU Scheduling Improve Performance?
- War Thunder driver timeout on Radeon: RX 5000, RX 6000 and RX 9000 need opposite fixes
- Radeon driver timeout or crash when opening an overlay with the AMD metrics overlay enabled
- Assassin's Creed Black Flag Resynced crashes with DX12 error 0x887A0006
- Video stutters or the screen goes black in Chrome after the NVIDIA 621.01 driver
- Smart Access Memory Turns Itself Off After an AMD Driver Update on Windows 10
Sources
AMD · Release notes · checked Nov 16, 2026
- AMD lists "Intermittent driver timeout may be observed while playing video on Windows 11 with Hardware-Accelerated GPU Scheduling (HAGS) enabled on Radeon RX 7000 series graphics products" under Fixed Issues for Adrenalin 26.10.2
- The page is titled "Optional Driver Release Notes" and is last updated 30 October 2026, so this fix ships in AMD's optional channel rather than the recommended one
- AMD lists "AMD Install Manager fails to locate optional drivers for AMD Software: Adrenalin Edition when Recommended + Optional is selected" under Fixed Issues for the same 26.10.2 release
- Packaged Contents give Adrenalin 26.10.2 as driver version 26.20.15.12, Windows Driver Store version 32.0.32015.12012
- Compatible operating systems are listed as Windows 11 version 21H2 and later and Windows 10 64-bit version 21H2 and later
- The Known Issues list for 26.10.2 names no remaining video-playback or HAGS timeout, and names Radeon RX 7000 only for an Assassin's Creed Black Flag Resynced crash
- AMD recommends the AMD Cleanup Utility when downgrading to a previous version of Adrenalin
Microsoft · Documentation · checked Nov 16, 2026
- "The default timeout period in Windows is two seconds" for the GPU scheduler's preempt wait, which is the actual TDR timeout
- On a successful recovery Windows "Displays an informational message to the end user, saying 'Display driver stopped responding and has recovered.'" and logs the same message in Event Viewer
- "The only visible artifact from hang detection to recovery is a screen flicker"
- "By default, the OS bug-checks the computer on the sixth (or more) GPU hang when it detects that five (5) or more GPU hangs (0x117) and subsequent recoveries occur within one (1) minute"
- Engine timeouts (0x141) do not contribute to the GPU hang count, and the system logs 0x142 when a malfunctioning process is blocked from GPU access instead of bug-checking
- "Some legacy DirectX applications might just render black at the end of this recovery, which requires the end user to restart these applications"
- TDR resets the graphics card when it takes longer than expected to complete an operation, to stop the whole system becoming unresponsive
Microsoft · Documentation · checked Nov 16, 2026
- Microsoft says to use the TDR-related registry keys "for testing or debugging purposes only during the driver development process"
- Microsoft's Important note states "End users shouldn't manipulate these registry keys"
- TdrDelay "is effectively the timeout threshold" and "The default value is 2 seconds"
- TdrLevel value TdrLevelOff (0) disables timeout detection altogether, and TdrLevelRecover (3) is the default
Microsoft · Documentation · checked Nov 16, 2026
- Microsoft states "Windows can now offload most of GPU scheduling to a dedicated GPU-based scheduling processor", with high-frequency work such as quanta management and context switching moving to the GPU
- Microsoft states "The transition should be transparent, and users should not notice any significant changes" and "We do not expect customers to experience performance regressions"
- The feature requires "recent GPUs that have the necessary hardware, combined with a WDDMv2.7 driver that exposes this support to Windows"
- The toggle is reached at "Settings -> System -> Display -> Graphics Settings" and appears only if both the GPU and driver support it
- The feature is opt-in and off by default
Microsoft · Documentation · checked Nov 16, 2026
- Hardware-accelerated GPU scheduling is one of three settings listed under "Advanced graphics settings" on the redesigned graphics page in Settings
- "This setting will only appear if your system has one or more supporting GPUs and the necessary display drivers"
- Microsoft describes Advanced graphics settings as aimed at knowledgeable users who want to further modify their graphics performance
NVIDIA · Release notes · checked Nov 16, 2026
- NVIDIA lists "Fixed an issue where video playback may freeze or black screen on some GeForce RTX 50 Series GPUs/RTX Spark" after updating to GRD 621.01 [6979343], confirming the NVIDIA video-playback bug is a separate fault from AMD's
- NVIDIA states "these Hotfix drivers are beta, optional and provided as-is" and that "The safest option is to wait for the next WHQL certified driver"
- The page was updated 10/27/2026 and does not mention Advanced Shader Delivery
AMD · Release notes · checked Nov 16, 2026
- Newest Adrenalin release, notes last updated 12 November 2026.
- The HAGS video-playback driver timeout on Radeon RX 7000 does not appear under Known Issues for this release, so the fix AMD shipped in 26.10.2 is still holding one release on.
- Known Issues still list the Assassin's Creed Black Flag Resynced crash or driver timeout on Radeon RX 7000 series graphics products.
- Fixed Issues for 26.11.1 name only the excessive writes to the system drive at idle and while moving or resizing windows.
Igor's Lab · News · checked Nov 16, 2026
- Independent coverage published 2 November 2026 lists "Driver timeouts during video playback with HAGS" for "Radeon RX 7000 / Windows 11" among the issues 26.10.2 fixes
- Adrenalin 26.10.2 is described as an optional driver released 30 October 2026, and users without these specific issues are told they do not need to update immediately
- The article reports no earlier driver as having carried this fix and describes no regression