BF6 Reproducible Crashes – Invalid Pointer / NX Execute Faults

POST

I’ve isolated a reproducible crash in Battlefield 6 that appears to be engine-side and mode-specific.

Summary
Battlefield 6 crashes to desktop with 0xC0000005 access violations involving invalid pointer reads and NX (non-executable memory) execute faults. All crashes occur inside Frostbite rendering code, specifically in isGlimpseEnabled and ffxFsr2ResourceIsNull / ffxFsr2ContextGenerateReactiveMask.

This only occurs in RedSec Gauntlet mode. Other modes have not reproduced the crash under the same conditions.

Environment
CPU: i7-13700KF
GPU: RTX 4070
RAM: DDR5-4800 (no XMP)
OS: Windows 11 (clean installs of 22H2 and 25H2)
GPU drivers tested: 581.80 and 591.59
DX11 and DX12 tested
HAGS OFF, HDR OFF
No overlays, no overclock
EA Anti-Cheat not involved

Reproduction notes
Crash occurs mid-match, often after extended play.
Only reproduces in RedSec Gauntlet mode.
Crash frequency increases when using a PS5 DualSense controller over USB-C.
Disabling Steam Input or using Bluetooth reduces frequency.
Crash stack does not change, suggesting the controller is a timing trigger, not the root cause.

Mitigation
Using the launch flag
-bEnableGlimpse 0
significantly reduces crash frequency but does not eliminate it and causes cursor issues. This strongly implicates the Glimpse or temporal rendering path.

Conclusion
All evidence points to a use-after-free or object lifetime bug in the Frostbite FSR2 or reactive mask or Glimpse subsystem, triggered by RedSec Gauntlet-specific gameplay or rendering behavior. This likely requires an engine-side fix.

Keywords
Frostbite, FSR2, Reactive Mask, Glimpse, Temporal Rendering, NX Fault, Invalid Pointer, RedSec Gauntlet, DualSense, Steam Input