Battlefield 6 Season 3 BSOD Restart Crash PC

What is the Battlefield 6 Season 3 BSOD restart crash?

Since the Season 3 patch (build 1.3.1.0, released May 12, 2026), a wave of Battlefield 6 players on Windows 11 24H2 are hitting a hard black-screen freeze followed by an automatic PC restart — usually mid-match on Operation Firestorm or Siege of Cairo. The Windows Event Viewer logs a BugCheck 0x117 VIDEO_TDR_TIMEOUT_DETECTED or 0x124 WHEA_UNCORRECTABLE_ERROR, and the EA crash dump shows the signature bf6!ffxFsr2ResourceIsNull+209c790 — pointing directly at the new FidelityFX Super Resolution 2 (FSR2) upscaler module shipped with the Season 3 build.

When does it occur?

• 5 to 25 minutes into a multiplayer match, especially when FSR2 Quality or Balanced is active
• Right after the engine streams in a new biome (Cairo sandstorm, Firestorm volcanic ash)
• When alt-tabbing out of the game with HDR enabled on a 4K display
• During the Season 3 intro cinematic on first launch after the patch
• On rigs using NVIDIA 555.xx Game Ready or AMD Adrenalin 26.5.1 / 26.5.2 drivers

Common causes

• FSR2 v2.3 module in 1.3.1.0 reuses GPU memory pages flagged as null by recent drivers
• NVIDIA 555.85 / 555.99 Game Ready ships a known TDR regression with DX12 mesh shaders
• AMD Adrenalin 26.5.1 leaks descriptor heap entries when FSR2 + Anti-Lag 2 are both on
• Windows 11 24H2 Hardware-Accelerated GPU Scheduling (HAGS) conflicting with the new BF6 frame pacer
• Resizable BAR being auto-disabled by the May Patch Tuesday rollup (KB5089573)
• Overclocked VRAM (XMP/EXPO + GPU OC) drifting under thermal load
• Corrupted shader cache from upgrading mid-season without a clean reinstall

Step-by-step fixes

1. Disable FSR2 immediately — In game, open Settings -> Video -> Upscaling and switch from FSR2 to either DLSS (NVIDIA), XeSS, or Native + TAA. This bypasses the ffxFsr2ResourceIsNull crash path entirely.
2. Roll NVIDIA drivers back to 552.44 or update to 556.12 Hotfix — Uninstall current driver with DDU in Safe Mode, then install 552.44 WHQL or the 556.12 Hotfix that EA confirmed in the May 22 forum post.
3. AMD users: install Adrenalin 26.5.3 Optional — 26.5.3 fixes the descriptor heap leak. In Adrenalin -> Gaming -> Battlefield 6, also force "Anti-Lag 2" to Off until the next stable release.
4. Read the Event Viewer to confirm the cause — Press Win+R, type eventvwr.msc, expand Windows Logs -> System, filter by Source nvlddmkm, amdkmdag, or WHEA-Logger. A timestamp matching your crash with TDR or 0x117 confirms the GPU path.
5. Turn off Hardware-Accelerated GPU Scheduling — Settings -> System -> Display -> Graphics -> Change default graphics settings -> toggle HAGS Off. Reboot. This stops the new frame pacer from racing with the kernel scheduler.
6. Clear the BF6 shader cache — Close the game, delete %LOCALAPPDATA%\Battlefield 6\cache\shaders and %PROGRAMDATA%\Electronic Arts\Battlefield 6\PSO. Relaunch — the first match will stutter while caches rebuild, then crashes stop.
7. Re-enable Resizable BAR / Above 4G Decoding — Reboot into UEFI, confirm Re-Size BAR Support = Enabled and Above 4G Decoding = Enabled. KB5089573 silently flipped these on several MSI and ASUS boards.
8. Pull back XMP / EXPO and GPU overclock — Set RAM to JEDEC 4800/5600 for one test session and remove any MSI Afterburner / AMD Adrenalin GPU OC. If crashes vanish, your previous OC was marginal under the new shader load.

If it still doesn't work

Generate a full DxDiag (Win+R -> dxdiag -> Save All Information) and attach it to a thread on the EA Answers HQ Battlefield 6 board with the exact bf6!ffxFsr2ResourceIsNull signature from your C:\Users\<you>\Documents\Battlefield 6\crashdumps .dmp file. EA's QA team is publicly tracking the FSR2 regression under ticket BF6-S3-FSR2-117 and is pushing a hotfix targeted at the June 9, 2026 Patch Tuesday window. If you cannot wait, players have reported full stability by switching the game launcher to DX12 Compatibility Mode (Settings -> Video -> Graphics API -> "DX12 Compatibility") which disables the new mesh-shader path entirely at a ~15% FPS cost.

BF6 player slang glossary: when teammates say they got "cooked" mid-firefight, "crashed out" after a wipe, or "mogged" by a sniper, that's the community vocabulary you'll see flooding chat after a crash wave like this one.