FSR2 Implementation Causing Sudden Crash

Hi all,

I’m experiencing the same crash as reported by others in this thread. I’ve done a detailed analysis and would like to share my findings to help the devs and community.

System Specs

• CPU: AMD Ryzen 7 5700X
• GPU: NVIDIA RTX 5060 Ti 8GB
• RAM: 32GB DDR4
• OS: Windows 10 22H2 (Build 26100.1)
• Drivers: All up-to-date (NVIDIA, chipset, Windows)

Crash Details

• Crash Type: Access Violation (0xc0000005)
• Faulting Module: bf6.exe (Battlefield 6 main executable)
• Function: ffxFsr2ResourceIsNull (related to FidelityFX Super Resolution 2)
• Exception: INVALID_POINTER_READ (attempt to read from 0x0000000000014891)
• Stack Trace (WinDbg): ExceptionCode: c0000005 (Access violation) Faulting module: bf6.exe (ffxFsr2ResourceIsNull) Attempt to read from address 0x0000000000014891 Failure.Bucket: INVALID_POINTER_READ_c0000005_bf6.exe!Unknown

What I’ve Tried

• FSR is disabled, using DLSS
• Clean install of NVIDIA drivers (latest and previous versions).
• Disabled all overlays (MSI Afterburner, Steam, etc.).
• Verified game files (Steam/EA App).
• No mods, no Reshade, no third-party injectors.
• Monitored hardware:
  • No overheating (CPU/GPU temps well below throttle limits).
  • No RAM/VRAM exhaustion (plenty of headroom).
  • No disk or SMART errors.
• Windows Event Viewer: no related system errors at crash time.

WinDbg Output (Summary)

ExceptionCode: c0000005 (Access violation) Faulting module: bf6.exe (ffxFsr2ResourceIsNull) Attempt to read from address 0x0000000000014891 Stack trace: bf6!ffxFsr2ResourceIsNull+0x1c0bdb7 Failure.Bucket: INVALID_POINTER_READ_c0000005_bf6.exe!Unknown

• The crash occurs during a pointer dereference in the FSR2 resource handling code.
• The address being accessed is invalid, suggesting a null or dangling pointer.

Observations

• The crash is not hardware-specific (many users with different CPUs/GPUs report the same).
• The crash is not caused by overheating, RAM/VRAM exhaustion, or disk issues.
• The crash is not exclusive to FSR2 being enabled—i'm using DLSS 
• The crash is not resolved by disabling overlays or doing a clean driver install.

Request to EA/DICE

• Can you confirm if this is a known issue in the FSR2 resource management code?
• Is there a workaround or hotfix in the works?
• Is there any additional debug info or logging I can provide to help pinpoint the root cause?
• I am happy to provide the full crash dump and hardware logs if needed.

Thank you for investigating this! If anyone else has found a workaround or has additional technical info, please share.