· GPUStores

War Thunder and Adrenalin 26.9.2: check your Radeon generation first

A War Thunder fix in the release notes is not enough to choose a driver. Start with your exact Radeon model and the settings used when the problem happens.

Document-based analysis. GPUStores has not tested this driver or measured its performance. Original analysis October 5, 2026; 26.11.2 follow-up checked November 19, 2026.

Editorial illustration of software data paths around a graphics processor
GPUStores illustration, not a test capture.

Follow-up: Adrenalin 26.11.2, November 18, 2026

The AMD 26.11.2 notes list War Thunder timeouts on RX 5000 as fixed, without a stated DX12 or capture restriction. They also fix excessive idle disk writes on RX 5000/6000 under Windows 10. Caution: Crimson Desert may fail to launch on RX 6000; AMD recommends 26.11.1 for that issue. GPUStores has not tested these fixes. The 26.9.2 context below remains historical.

Security: check before rolling back

AMD’s November 10 bulletin AMD-SB-6028 separates mitigations by GPU family, operating system and vulnerability; several predate November. AMD plans no fix for CVE-2026-0457 on RX 5000 and RX 6000. Before returning to an older driver for War Thunder, check the row for your hardware. A recommendation for that game does not guarantee coverage of every vulnerability. GPUStores has not tested these fixes.

Historical context: the two 26.9.2 cases

AMD’s September 29 release notes distinguish these cases:

RX 6000 · Stated fix
War Thunder in DirectX 12 with Instant Replay and Borderless Region Capture enabled: the driver timeout is listed as fixed.
RX 5000 · Known issue
Timeouts remain listed. AMD recommends 26.9.1 for affected users; that entry is not restricted to DX12 or capture settings.

These recommendations describe the 26.9.2 situation, not today’s driver choice. Start with the follow-up above, your exact model and the affected games. Do not return to 26.9.1 solely because of this historical passage.

Before changing anything, make a symptom record

Search for “System” in AMD Software to find hardware and installed driver details. AMD’s identification guide shows where to look; labels can vary with the application language.

Also record the game’s graphics API, resolution, preset, capture options and the scene that triggers the problem. Distinguish a game closing, a driver-timeout message and a complete system freeze. That short record gives you something useful to compare after restarting.

Choose one change to evaluate. Updating the driver, BIOS, overclock and several game settings together would make it difficult to identify what helped.

Prepare a rollback you can actually verify

Version 26.9.1 is dated September 3 and lists RX 5000 compatibility. Still check your exact model and Windows version before downloading. AMD’s previous-driver instructions start from the product page; keep the intended installer before removing the current driver.

AMD recommends its cleanup utility when downgrading. The AMD Cleanup Utility guide recommends Safe Mode and requires a restart. It removes AMD graphics and audio components while leaving chipset drivers intact. Let any active Windows Update finish and make sure you can reach the PC directly.

Then follow AMD’s installation instructions. Take care with Factory Reset: AMD says it removes previous packages and prevents rolling back to the previously installed driver through that mechanism. Do not select it automatically. For a laptop or all-in-one PC, also check the system manufacturer’s guidance.

Afterward, repeat the same scenario

Confirm the version actually installed, then revisit the same scene using the settings you recorded. Use a comparable session length, especially if the problem appeared only after extended play. One successful session cannot establish that an intermittent crash is gone.

AMD also lists Smart Access Memory becoming disabled after installation on Windows 10 as fixed in 26.11.2. Its graphics-settings guide shows the SAM control where supported. Record the before-and-after state; this check does not require a BIOS change.

If the fault remains reproducible, keep your versions, settings and reproduction steps for support. A persistent crash alone is insufficient evidence that the card needs replacing. For a genuine performance limit, our CPU-or-GPU upgrade method helps prepare a separate buying decision.

Scope: the War Thunder driver decision on Radeon under Windows. AMD’s full notes cover other games and issues. No FPS gain or guaranteed troubleshooting outcome is claimed.

Share