AMD’s Adrenalin 26.11.1 optional driver fixes excessive writes to the system drive, according to its release notes, last updated on November 12. It covers two cases of the same fault: writes while the system sits idle on RX 7000 series cards and newer, and writes while application windows are moved or resized, for which no card range is given.
Both fixes concern writes to the system drive, and no game fixes are included
The previous driver, 26.10.2 from October 30, fixed ten issues, from Valor Mortis shutdowns to overlay crashes. 26.11.1 lists only the two write problems as fixed, so none of the game crashes that remain open appear to be addressed.
RX 6000 cards are on the compatibility list, but the fix names RX 7000 and newer
The driver is compatible with the RX 9070, 9060 and 9050 series, the Radeon AI PRO R9700, R9700S and R9600D, and the RX 7900 to RX 7600 and RX 6900 to RX 6400 families. The idle-write fix applies to RX 7000 series products and above, and the window-resize fix appears to have no stated range.
Known issues carry over from 26.10.2, including a Smart Access Memory warning for Windows 10
Assassin’s Creed Black Flag Resynced can crash or time out on RX 7000 cards, and War Thunder can time out on RX 5000 cards, where users are pointed back to 26.9.1. Cyberpunk 2077 can crash on some RX 9000 cards with FSR, Anti-Lag and in-game frame generation enabled during video playback on a second display, and turning off in-game frame generation is the suggested workaround. Call of Duty: Modern Warfare Remastered shows black corruption on RX 9000 cards and can become unresponsive on Alt+Tab on Ryzen AI Max PRO 400 processors, and Gears of War: Reloaded can show a black screen on Ryzen AI 9 400 processors.
Smart Access Memory may become disabled after installation on Windows 10, and AI Bundle installs can fail in regions with limited access to HuggingFace and GitHub. The Phantom Blade Zero entry now covers only hair corruption on RX 9000 cards, while 26.10.2 also included the sky, and the sky does not appear among the fixes.
No figure for the amount written or the driver where the fault began is given
No figure appears for how much data the driver wrote, and the version that introduced the fault does not appear to be named. The problem was not among the 26.10.2 known issues either, so an owner who saw heavy writes likely cannot tell from the notes which driver caused them.