War Thunder AMD RX 5000 driver timeout remains a known issue in Adrenalin Edition 26.10.2. AMD’s official recommendation for affected Radeon RX 5000 players is to use driver version 26.9.1 instead of assuming the newest optional update will correct the problem.
A driver timeout is different from losing your connection to a match or seeing low frame rates. If the picture freezes, the screen goes black or Windows reports a graphics-driver recovery, compare that with AMD’s reported fault.
War Thunder AMD RX 5000 driver timeout: what AMD says
AMD’s 30 October 2026 notes list an intermittent driver timeout while playing War Thunder on RX 5000 series graphics. It appears under Known Issues, not Fixed Issues, and the entry says affected users are recommended to use AMD Software: Adrenalin Edition 26.9.1.
That wording matters. Other problems are fixed in 26.10.2, but this War Thunder issue is not among them. Installing 26.10.2 for a War Thunder timeout on RX 5000 is the opposite of AMD’s stated workaround for the condition.
The War Thunder AMD RX 5000 driver timeout is specific to Radeon hardware. Intel Arc graphics use different drivers, so Intel rendering workarounds don’t apply to this problem.
Confirm your RX 5000 card and driver
Open AMD Software on Windows and search for System Settings. The Hardware & Drivers section lists your Radeon product and AMD Software version. Write down the exact model, Windows build and installed driver before changing anything.
The AMD note applies to RX 5000 graphics, which includes supported products in the RX 5700, RX 5600 and RX 5500 families. Don’t assume the same recommendation automatically applies to RX 6000, RX 7000 or RX 9000 hardware.
For War Thunder AMD RX 5000 driver timeout, keep a brief note of the symptoms as well. Did the game disappear, did the screen briefly go black, or did a driver recovery message appear? That makes it easier to tell whether your failure matches AMD’s report.
How to go back to AMD Adrenalin 26.9.1
Before downgrading, save your work and preserve any important AMD tuning settings. Obtain a genuine AMD Adrenalin 26.9.1 installer that supports your exact card and version of Windows. Avoid unknown third-party driver bundles that merely advertise the right number.
AMD recommends using its Cleanup Utility when downgrading to an earlier Adrenalin release. Follow AMD’s own guidance and precautions, remove the current graphics driver, then install the compatible 26.9.1 package. Restart as requested and confirm the installed version in AMD Software.
For War Thunder AMD RX 5000 driver timeout, try the same mode and graphics settings after returning to 26.9.1. That gives you a meaningful comparison without changing unrelated options.
What if War Thunder still times out?
A persistent timeout after moving to 26.9.1 deserves a more specific investigation. Record the graphics card, driver version, Windows build, game version and exact scene or action that triggered the fault. If possible, note the recovery error text.
Check for relevant game updates, then report the remaining issue to AMD or Gaijin. The driver note doesn’t establish that every War Thunder crash comes from the same defect, and it doesn’t justify deleting saved games or altering Windows registry settings.
War Thunder AMD RX 5000 driver timeout troubleshooting should stay separate from connection issues, matchmaker delays and Intel Arc rendering reports. Those problems need different evidence and vendor-specific fixes.
Should you install 26.10.2 for other AMD fixes?
Adrenalin 26.10.2 fixes a range of other problems, including Valor Mortis timeouts, Steam startup crashes and certain RX 9000 FSR hangs. Read our full AMD Adrenalin 26.10.2 coverage before deciding. The presence of other fixes does not override the 26.9.1 recommendation for this War Thunder case.
If you’re experiencing War Thunder AMD RX 5000 driver timeout, AMD recommends version 26.9.1. Follow its cleanup and installation guidance, keep a record of the result and check later release notes for a confirmed fix.
Official AMD source: Adrenalin 26.10.2 release notes.
