If Forza Horizon 6 started throwing mid-race crashes, false out-of-VRAM warnings on a 16 GB card, or giant black rectangles where tire smoke should be, your GPU isn’t dying — AMD’s October driver branch broke it, and neither November patch touched the problem.

TL;DR

  • The broken branch: AMD Software: Adrenalin Edition 26.10.1 (released October 20, 2026) and 26.10.2 introduced mid-gameplay driver timeouts (FHC01), false VRAM exhaustion errors (FHD01), and screen-blocking smoke and dirt artifacts in Forza Horizon 6.
  • The thing most people get wrong: Updating to November 12’s Adrenalin 26.11.1 won’t rescue you — its release notes only address an idle SSD-write bug on RX 7000+ cards, and Playground’s November 5 Hotfix 1 (3.483.970.0) only fixed Drift Zone scoring and a Saleen S7 bumper.
  • Which driver actually works: Community consensus splits by GPU generation — Adrenalin 26.8.1 WHQL (August 20) is the safest universal baseline for RX 6000 and RX 7000 cards, while 26.9.1 Optional (September 3) is the cleanest pick on RX 9000 series GPUs like the RX 9070 XT.
  • Why dirt glitches survive a rollback: Downgrading the driver without purging both the AMD and Windows DirectX shader caches leaves 26.10.1‘s compiled particle blobs sitting on disk.
  • If another game locks you onto 26.10.1+: Closing hardware-accelerated web browsers reclaims 1–2 GB of contested VRAM, and dropping Particle Effects Quality from Extreme/Ultra to High stops the tire-smoke buffer spike.

Updating to 26.11.1 won’t save you: why the October branch broke FH6

Before you touch your drivers, make sure you are diagnosing the right crash. Forza Horizon 6 on PC currently has three completely separate failure modes that get lumped together in support threads: dying before the title screen (which needs our Forza Horizon 6 Steam startup crash fix), silently vanishing with exit code 0 ninety seconds into the shader pass (caused by the D3D12 shader upload-heap leak we tracked in July), and crashing during normal driving on recent AMD Radeon drivers.

If your game boots fine, lets you drive out of the festival site, and then either hard-locks with an FHC01 driver timeout, throws an FHD01 (“Out of Video Memory”) warning on a 16 GB or 24 GB card, or turns tire smoke and off-road dust into giant black, green, or pixelated blocks that tank your frame rate — that’s Adrenalin 26.10.1.

AMD shipped 26.10.1 on October 20 to add support for Call of Duty: Modern Warfare 4 and expand FSR 4.1 upscaling to RX 6000 GPUs. Nothing in the notes touched Forza Horizon 6 (whose official profile and native FSR 4.1 support landed months ago in 26.5.2), yet players on r/ForzaHorizon6 immediately began reporting severe VRAM budget spikes and alpha-particle corruption — worst of all during sustained tire smoke in tandem runs in Drift Attack at Shimanoyama or high-speed town streaming.

“On 26.10.1 I kept crashing during regular gameplay. Ever since I rollbacked to 26.8.1 I haven’t had a single issue or any hiccups.” — u/Christian5220 on r/ForzaHorizon6 (November 2, 2026)

The part people get wrong: assuming the November updates quietly cleaned this up. AMD’s Adrenalin 26.11.1 Optional hotfix (November 12) exists for one narrow reason — stopping excessive system-drive SSD writes while idle or resizing windows on RX 7000 and RX 9000 cards. On the studio side, Playground’s November 5 Hotfix 1 (3.483.970.0 / Steam 1.483.970.0) patched Series 7’s FPS-dependent Drift Zone scoring bug and left PC memory allocation untouched. Waiting on 26.11.1 leaves you on the exact same broken October branch.

26.8.1 vs. 26.9.1: the right rollback depends on which Radeon card you run

Epistemic status: this split is community consensus across independent reports, not official AMD telemetry. Read any troubleshooting thread from the past two weeks and you’ll see players recommending two different rollback targets. Both work — for different cards.

In the same November 3 r/ForzaHorizon6 thread, u/GeorgeEne95 reported rolling back to 26.8.1 to stop screen-filling smoke blowouts, while u/KillerSpectre21 noted that “26.9.1 has been the most stable for me so far on a 9070 XT, got rid of both the crashes and artifacts.” Checking AMD’s release notes explains why that split exists: 26.9.1 Optional (September 3) shipped targeted intermittent-crash fixes specifically for Radeon RX 9000 series (RDNA 4) hardware before 26.10.1 introduced the FH6 regression.

Driver VersionRelease DateFH6 StatusWho Should Run It
Adrenalin 26.8.1 (WHQL)Aug 20, 2026StableRX 6000 & RX 7000 series — broadest WHQL baseline; fallback for RX 9000
Adrenalin 26.9.1 (Optional)Sept 3, 2026StableRX 9000 series (RX 9070 / 9070 XT) — includes RDNA 4 crash fixes
Adrenalin 26.10.1 / 26.10.2Oct 20, 2026BrokenAvoid for FH6 (FHC01 timeouts, FHD01 VRAM spikes, smoke blocks)
Adrenalin 26.11.1 (Optional)Nov 12, 2026UnfixedFixes RX 7000+ idle SSD writes only; carries 26.10.x FH6 bugs forward

If you’re on an RX 9070 or 9070 XT, try 26.9.1 first and keep 26.8.1 in reserve. On RX 7900 XTX/XT, RX 7800 XT, or RX 6000 series cards, go straight to 26.8.1 WHQL.

Why dirt artifacts survive a rollback: purge the shader cache, not just the driver

Notice a telling detail in u/GeorgeEne95’s November 3 report: rolling back to 26.8.1 killed the crashes and the FPS-tanking smoke wall, but minor dirt artifacts remained. That happens when you swap the driver over top of compiled shader blobs that 26.10.1 already wrote to disk. Do the rollback in five steps so nothing carries over:

  1. Download the offline installer first. Grab 26.9.1 (RX 9000) or 26.8.1 (RX 6000/7000) from AMD’s Previous Drivers archive for your exact GPU model before uninstalling anything.
  2. Wipe 26.10.x cleanly. Run the AMD Cleanup Utility (or Display Driver Uninstaller (DDU) in Windows Safe Mode) so broken registry keys and driver-store remnants don’t survive the downgrade.
  3. Install and disable Auto-Update. Run your 26.8.1 or 26.9.1 installer, then immediately open Adrenalin Settings → System and toggle Check for Updates to Manual so Windows or Adrenalin doesn’t push 26.10.1+ back overnight. (If you still hit FHC01 during event transitions, toggle In-Game Overlay off under Preferences.)
  4. Purge both shader caches. In Adrenalin, go to Gaming → Graphics → Advanced → Reset Shader Cache. Then open Windows Disk Cleanup on C:, check DirectX Shader Cache, run it, and reboot before launching Forza Horizon 6.
  5. Windows 10 check — verify Smart Access Memory. Both AMD’s 26.8.1 and 26.9.1 official Known Issues warn that AMD Smart Access Memory (SAM) can silently toggle off during driver installation on Windows 10 systems. Check Gaming → Tune / Smart Technology after rebooting and flip it back on if the installer disabled it.

Stuck on 26.10.1 for another game: how to keep VRAM below the tripwire

If you actively play Call of Duty: Modern Warfare 4 or another late-October release that forces you to stay on 26.10.1 or 26.11.1, you can’t eliminate the driver bug — but you can keep Forza Horizon 6 below the memory ceiling where it trips.

First, close Chromium browsers and background overlays before launching. Community testing backs up why shutting down Chrome, Edge, Discord’s overlay, Steam Overlay, and RivaTuner Statistics Server (RTSS) buys hours of stability. Forza Horizon 6 already holds roughly 9.5 GB of VRAM at baseline on a 16 GB card — a number we measured directly in why Forza Horizon 6 dies three minutes in — and community testing indicates the engine sizes its streaming pool after subtracting whatever background apps have reserved rather than evicting them. Handing 1.5 GB of VRAM to hardware-accelerated browser tabs pushes 26.10.1‘s leaky particle buffers straight into an FHD01 crash.

Second, adjust the four in-game settings that feed the spike:

  • Particle Effects Quality & Volumetric Fog: Drop from Extreme or Ultra down to High. Tire smoke, dust, and debris buffers are the primary trigger for both the screen-blocking alpha glitches and sudden VRAM jumps.
  • Ray-Traced Reflections: Turn Off and rely on Screen Space Reflections until AMD ships a fixed branch.
  • Environment Texture Quality: Cap at High (or Ultra on 16 GB+ cards; avoid Extreme, which accelerates streaming overflow).
  • Upscaling / Anti-Aliasing: If tire smoke still renders as blocky squares under FSR upscaling, test Native TAA to bypass transparency-upscaling artifacts.

Also verify you haven’t disabled your Windows Page File (sysdm.cpl → Advanced → Performance → Virtual Memory); leaving it System managed on an SSD prevents momentary VRAM spillover from becoming an instant desktop crash.

One thing to skip: third-party amd_ags_x64.dll proxy mods. Open-source DLL wrappers that intercept crashing particle allocations at the OS level have started circulating in community fix threads. Leave them alone — as we broke down in how Playground separates server-side errors from client tampering, dropping modified binaries into the game folder of a live-service Forza title carries real anti-cheat risk when a five-minute driver rollback solves the problem cleanly.

The Bottom Line

This isn’t dying silicon and it isn’t 16 GB of VRAM suddenly becoming obsolete overnight — it’s an October AMD driver regression that neither Adrenalin 26.11.1 nor Series 7’s first hotfix addressed. Waiting on automatic updates right now just keeps you on the broken branch.

Wipe 26.10.x with AMD Cleanup Utility or DDU, install 26.9.1 if you’re on an RX 9000 card or 26.8.1 WHQL on RX 6000/7000, purge both the Adrenalin and DirectX shader caches so old dirt artifacts don’t linger, and double-check Smart Access Memory if you’re still on Windows 10. Once your smoke renders like smoke again, jump into our Series 7 City Life playlist guide — playlist reward cars are 25% cheaper this month, and they’re a lot easier to unlock when you can actually see the corner exit.


Related on ApexSpeedCraft: The FH6 Shader Leak Survived the Patch | Why Forza Horizon 6 Dies Three Minutes In | FH6 Keeps Crashing on Startup: Steam Launch Fix | For Three Days, FH6 Scored Your Drifts by Frame Rate | FH6 Series 7 City Life Playlist Guide | Got the Italian Passion Cars Early? No, You’re Not Banned

Sources: AMD — Adrenalin 26.8.1 Release Notes | AMD — Adrenalin 26.9.1 Release Notes | AMD — Adrenalin 26.10.1 Release Notes | AMD — Adrenalin 26.11.1 Release Notes | Forza.net — Series 7 City Life Release Notes | Forza Support on X — Series 7 Hotfix 1 | r/ForzaHorizon6 — AMD 26.8.1 & 26.9.1 Community Reports

Reporting and verification by ApexSpeedCraft. Official release notes cross-checked against AMD Adrenalin builds 26.8.1 through 26.11.1 (as of November 15, 2026) and Forza Horizon 6 Series 7 Hotfix 1 (3.483.970.0). GPU-specific stability differences between 26.8.1 and 26.9.1 reflect independent community reports rather than studio or vendor telemetry.

Fediverse reactions

Leave a Reply

Trending