[Crash] Battlefield 6 Open Beta – Access Violation in FSR2 Thread (bf6event.exe)
The game frequently crashes to desktop without any error message.
Nothing shows up in Windows Event Viewer. The only evidence are the Battlefield-generated crash dumps, which consistently show Access Violations (0xc0000005) in the functions ffxFsr2ResourceIsNull or ffxFsr2ContextGenerateReactiveMask.
This happens even when Upscaling is OFF or when DLSS/DLAA is used instead of FSR2.
→ It seems the FSR2 pipeline is still initialized and crashes due to an invalid resource/pointer.
Steps to reproduce:
Launch Battlefield 6 Open Beta.
Play for several minutes (doesn’t matter if Upscaling is OFF, DLSS, or DLAA).
Game crashes back to desktop, no Windows error dialog.
Technical details:
Crashdump snippet:
ExceptionCode: c0000005 (Access violation) Module: bf6event.exe Function: ffxFsr2ResourceIsNull ReadAddress: ffffffffffffffff
GPU: RTX 4080 (latest WHQL driver, tested with 551.86)
CPU: i7-12700K
RAM: 32 GB DDR5-6000 (also reproducible with 5600 MHz)
OS: Windows 11 Pro 24H2 (26100.1)
Monitors: Dual setup (144 Hz + 180 Hz)
Already tested (no success):
Upscaling OFF
DLSS Quality / DLAA
HDR off, second monitor disconnected
NVIDIA Reflex: "On" instead of "On + Boost"
Future Frame Rendering toggled
HAGS on/off
GPU driver clean reinstall via DDU
RAM at lower clocks
Conclusion:
The crash most likely occurs in the FSR2/Reactive Mask implementation in the Frostbite engine, as the callstack always ends there regardless of whether FSR2 is enabled in the settings.
Please investigate and fix so the game runs stable with DLSS/DLAA as well.
ExceptionCode: c0000005 (Access violation)
Process: bf6event.exe
Instruction: bf6event!ffxFsr2ResourceIsNull+0x2f9b10f
Faulting address: 00000000000000a0
Stack trace:
> bf6event!ffxFsr2ResourceIsNull+0x2f9b10f
bf6event!ffxFsr2ResourceIsNull+0x2f9bed7
bf6event!ffxFsr2ResourceIsNull+0x1148149
bf6event!ffxFsr2ResourceIsNull+0x114f941
...
ucrtbase!thread_start
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
