FSR2 Implementation Causing Sudden Crash

Hi Battlefield Team,

I want to fully support 'gnomecannon' who posted about the FSR2 implementation causing sudden crashes to desktop. I am experiencing the exact same crash, consistently producing the same crash dump as described in the original post.

Issue:

Battlefield 6 abruptly closes to desktop with no in-game error.

Windows Event Viewer logs Application Error 1000 for bf6.exe with ExceptionCode c0000005.

WinDbg analysis of my minidump points to bf6!ffxFsr2ResourceIsNull, which attempts to read an invalid pointer even when FSR is disabled in the game settings.

I have followed all standard troubleshooting steps:

- Verified integrity of game files on Steam - repair on EA app.

- Clean-installed/DDU: GPU drivers (NVIDIA 591.44, RTX 4090)

- Disabled all overlays (Steam, Discord, every possible overlay) nothing is running in the background.

- Set FSR off 

- Tested Fullscreen, Window mode and Borderless

 - BIOS and all drivers fully updated

- No overclocking active

- Reinstalled everything...

Etc, etc, etc.

Despite this, the crash occurs repeatedly mid-game and is reproducible. This is not an isolated issue — many users report the same problem across forums.

After around 100 hours of gameplay, it is extremely frustrating that such a technical issue persists. 

DICE & EA can you please prioritize investigating the FSR2 integration in Battlefield 6, specifically how FSR2 resources are handled, so we can finally have stable gameplay. After so many hours of gameplay, we should not have to deal with this kind of crash.

Thank you for taking this seriously.

Hope we sooner or later can visit the battlefields again with the full experience.

Best regards - Ezra

PC Specs:

CPU i9: 13900k - GPU: 4090 Asus Rog Strix - Motherboard: Asus Maximus Hero z790 - DDR5 RAM G.Skill 32GBx2 6000 MT/s - PSU: Seasonic Vortex GX-1200 80 Plus Gold - SSD 990 PRO 1TB - CPU Cooler: Artic liquid freezer iii pro. Screen:  26.5" Asus Rog Strix OLED XG27ACDNG - 2560x1440 QHD - 360 Hz - QD-OLED.

Hello Team,

 I want to fully support 'Ezra-Nu7ella' who posted about the FSR2 implementation causing sudden crashes to desktop. I am experiencing the exact same crash, consistently producing the same crash dump as described in the original post. 

dealing with this same exact issue

1660 super

AMD Ryzen 5 2600 Six-Core Processor (3.40 GHz) Windows 11 Pro version 25H2

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.

Same issue as above, scoured many pages of hundreds of people reporting similar issues. Please can someone investigate and inform the best resolution, plenty of people paying good money for this game!

Hi there team, 

Exact same issue stated. Started since early December. 

Crashdump files show this :

CONTEXT: (.ecxr) rax=0000000000000000 rbx=00000000365f1bd0 rcx=0000000000000000 rdx=0000000000010280 rsi=0000000049033450 rdi=0000000036653d90 rip=0000000144cd4364 rsp=000000005bc4fb40 rbp=00000000800701b1 r8=7ffffffffffffffc r9=000000000037e000 r10=00007ffcd3d90000 r11=00007ffcd3da13f1 r12=0000000000200000 r13=000000001137b585 r14=0000000000000000 r15=0000000036fa14f0 iopl=0 nv up ei pl nz na pe nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 bf6!ffxFsr2ResourceIsNull+0x23b9ec4: 00000001`44cd4364 448930 mov dword ptr [rax],r14d ds:00000000`00000000=???????? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 0000000144cd4364 (bf6!ffxFsr2ResourceIsNull+0x00000000023b9ec4) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000000 Attempt to write to address 0000000000000000

EA chat support as been telling a number of fix that dont work 

Specs : 

CPU : 12th Gen Intel(R) Core(TM) i7-12700K

OS: Windows 11 (64 bit)

GPU : NVIDIA GeForce RTX 4080

Please EA, acknowledge this issue and fix it as I we cannot play the game or battlepass we fully paid for  

Hello everyone,

Today I've experienced exactly the same problem. It started happening after I updated BIOS to the newest version. Just like you, I can play maybe one or two games and the game crashes without any error BUT with Crash Dump file that through WinDbg goes exactly like yours:

CONTEXT: (.ecxr)

rax=0000000000000003 rbx=0000000149a4c9c8 rcx=0000000000000003 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000005794898 rip=0000000143a781d4 rsp=000000007309fb00 rbp=7309fa9000000005 r8=0000ffffffffffff r9=000000004a540200 r10=000000004a4d9cc0 r11=000000004a540240 r12=0000138636b07c39 r13=ffffffffffffffff r14=000000007309fd50 r15=0000000000000000

 iopl=0 nv up ei pl nz na pe nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202

 bf6!ffxFsr2ResourceIsNull+0x115cf64: 00000001`43a781d4 488b7d00 mov rdi,qword ptr [rbp] ss:7309fa90`00000005=????????????????

 Resetting default scope

 EXCEPTION_RECORD: (.exr -1)

 ExceptionAddress: 0000000143a781d4 (bf6!ffxFsr2ResourceIsNull+0x000000000115cf64)

 ExceptionCode: c0000005 (Access violation)

 ExceptionFlags: 00000000

 NumberParameters: 2

Parameter[0]: 0000000000000003 

Parameter[1]: 0000000000000000 Attempt to write to address 0000000000000000 PROCESS_NAME: bf6.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja w 0x%p odwo a a si do pami ci pod adresem 0x%p. Pami nie mo e by %s. 

EXCEPTION_CODE_STR: c0000005 

EXCEPTION_PARAMETER1: 0000000000000003 

EXCEPTION_PARAMETER2: 0000000000000000

My specs:

MB - Gigabyte Z790 Aorus Elite AX DDR4

CPU - I7 13700K

GPU - RTX 4070TI

RAM - 32GB DDR4 3200Mhz

OS - Win 10

Can you downgrade the BIOS?

And did you Load Bios Defaults before and after update?

Yup I was on Bios defaults both before and after the update. Will try downgrading the Bios to the version I had, however I noticed that its not only related to fsr2 but in general to upscaling and anti aliasing because after changing in game options i've got different results with the same error code:

• Upscaling - DLAA - Ends with FSR2 related error 0xc0000005 Access Violation
• Upscaling - OFF, Anti-Aliasing - DLAA - Ends with Nvidia error related to 

  nvwgf2umx.dll file (same error code)

• Upscaling - OFF, Anti-Aliasing - TAA - Ends with the same error code but it doesn't even show now what it is related to, only this gibberish:

CONTEXT: (.ecxr)

rax=0000000001e2f89c rbx=0000000000000000 rcx=0000000000000000 rdx=000000004a545080 rsi=0000000001e2f89c rdi=000000004a545080 rip=0000000000000000 rsp=000000007217f918 rbp=000000007217f968 r8=0000000000000000 r9=000000004a6b7b30 r10=000000004a5dd5c0 r11=000000004a6b7b30 r12=0000000000000000 r13=000000004a5d8480 r14=0000000000000000 r15=0000000000000000 

iopl=0 nv up ei pl zr na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246 00000000`00000000 ?? ???

Resetting default scope

EXCEPTION_RECORD: (.exr -1)

ExceptionAddress: 0000000000000000

ExceptionCode: c0000005 (Access violation)

I also noticed  that the same error is happening when I run a multi core stress test on Cinebench r23 with a CTD, but I managed to fix(?) that and perform full test without any CTD by doing as follows:

• manually setting power limits of PL1 and PL2 to 253W
• setting IccMax to 307A
• manually setting CPU Temp Protection to 100 degrees celsius
• changing CPU Vcore Loadline Calibration from "Auto" to "Medium"
• changing CPU V core from "Auto" to "Normal"
• changing dynamic V Core to -0.050V (undervolting)

Unfortunately these BIOS settings only worked out with Cinebench. In BF6 the problem still persists.

The game probably doesn't "like" it that you run it with a 12 core CPU. Try to limit the game to only use one of your two CCD's and see how that runs, if you haven't tried that already.

Put that in a .txt file you call "user.cfg" make sure it really turns into a ".cfg" file.

Thread.ProcessorCount 6

Thread.MaxProcessorCount 6

Thread.MinFreeProcessorCount 0

Thread.JobThreadPriority 0

GstRender.Thread.MaxProcessorCount 12

And then just copy paste it into the mainfolder of Battlefield 6. And try to play without V-Sync and use a RTSS FPS limit instead, if you have a G-Sync/Freesync monitor. I use a FPS limit of 138 that works fine. The game's V-Sync is broken it has been broken since release. And the latest Nvidia drivers also broke V-Sync in other games, you get horrible microstuttering if V-Sync+G-Sync is enabled at the same time lately. The last good driver was 581.94 iirc. But you need newer drivers for latest games and DLSS 4.5 and such, it's so annoying.

You know... I think you might be onto something, cause after I copied these commands 3 hours passed and not a single CTD. Although having to limit the CPU in order to play normally isn't ideal It should be enough until they fix that problem completely... unless they won't, and the problem is related to hardware/firmware...

Further testing is required to completely eliminate the thought that problem still exist but as for now nothing unusual happened. Ill notify you if the crash will occur again.

In case if anyone want to know what settings I choose while testing the commands I went with

Upscaling - OFF and AA - TAA