Persistent DX12 FSR2 Crash
Battlefield 6 consistently crashes or freezes during the “Match Found” loading screen when using DX12, even with all upscaling, frame generation, and overlays disabled.
Every crash dump points to the same FSR2 function (ffxFsr2ResourceIsNull) inside bf6.exe, with an Access Violation (0xC0000005).
The game must be force-closed through Task Manager.
SYSTEM SPECS:
GPU: RTX 4060 (stock clocks, latest NVIDIA driver)
CPU: Intel Core i5-13400F
RAM: 32 GB DDR4 3600 MHz
OS: Windows 11 Pro (latest update)
CRASH DETAILS:
Exception: Access Violation (0xC0000005)
Function: bf6.exe → ffxFsr2ResourceIsNull
Sometimes: VCRUNTIME140.dll!memcpy_avx_ermsb_Intel
Read Address: FFFFFFFFFFFFFFFF
Failure Hash: {c6607993-a4db-3511-7d47-8a7ce6e5a44c}
Typical WER Entry: INVALID_POINTER_READ_c0000005_bf6.exe!Unknown
CRASH DUMP EXCERPT (WinDbg):
EXCEPTION_CODE: 0xC0000005 (Access Violation)
FAULTING_MODULE: bf6.exe
FAULTING_FUNCTION: ffxFsr2ResourceIsNull+0x11515c7
READ_ADDRESS: 0xFFFFFFFFFFFFFFFF
PROCESS_NAME: bf6.exe
IMAGE_VERSION: 1.0.388.5459
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_bf6.exe!Unknown
FAILURE_HASH: {c6607993-a4db-3511-7d47-8a7ce6e5a44c}
STACK_TOP: bf6!ffxFsr2ResourceIsNull → bf6!isGlimpseEnabled → bf6!ffxFsr2ResourceIsNull
Even when FSR2 and all upscaling features are disabled, the call stack still enters the FSR2 module.
This suggests a use-after-free or invalid resource pointer in the DX12 + FSR2 path.
The issue appears independent of overlays, drivers, or hardware.
Attached text file contains the full WinDbg output for the crash dump.
