[PC] Crash on Launch - bf6.exe Access Violation (ffxFsr2ResourceIsNull)

Update:

Confirmed that the crash also occurs with FSR fully disabled via EA App command-line flags, on RTX 4060 (NVIDIA) with DLSS enabled. The exception remains a NULL pointer write (0xC0000005) in ffxFsr2ResourcesIsNull, triggered during Exclusive Fullscreen initialization.

Borderless Windowed mode appears significantly more stable and avoids the crash in most cases.

This suggests an unconditionally executed FSR2 validation path, despite FSR being disabled by user settings.

Monnezzarolvlmax​ disable XMP memory overclocking in motherboard BIOS settings. See if this stops the crashing.

If I don't reply to your post then personal message me. Sometimes the forum fails to notify me when someone replies.

Thanks for the suggestion but XMP is not the issue here. I have already analyzed the Crash Dumps, and the data doesn't point to hardware instability or random memory corruption. The logs consistently report a specific Exception Access Violation (c0000005) inside ntdll.dll and KERNELBASE.dll

Monnezzarolvlmax​ here's what Google Gemini AI says about (c0000005).

Error code c0000005, also known as STATUS_ACCESS_VIOLATION, is a critical Windows exception indicating that a program attempted to read, write, or execute a memory address to which it does not have rights.

Common Causes

Hardware Issues: Faulty RAM is a primary driver, but unstable CPU settings (especially on newer Intel chips) can also trigger it.

Corrupt Files: Damaged system files or corrupted game/application installations.

Driver Conflicts: Outdated or incompatible graphics and motherboard drivers.

Third-Party Overlays: Software such as antivirus, game mods, or input device drivers (e.g., non-standard gamepads).

Recommended Fixes

Check System Files: Open Command Prompt as Administrator and run sfc /scannow. This tool scans and repairs missing or corrupted system files.

Test Your RAM: Use the Windows Memory Diagnostic tool (press Win + R, type mdsched.exe) to check for physical memory errors.

Update Graphics Drivers: Visit the official site for NVIDIA, AMD, or Intel to install the latest stable version of your GPU drivers.

Verify Application Files: If the error occurs in a specific game, use the "Verify Integrity" option in the game launcher (like Steam or Epic Games) to repair corrupted data.

Disable Background Apps: Perform a Clean Boot to determine if third-party software is interfering with the program.

Adjust CPU Settings (Advanced): For users with high-end Intel CPUs (like 13th/14th Gen) experiencing crashes, lowering the "Performance Core Ratio" by 1 in the Intel Extreme Tuning Utility (XTU) has resolved the issue for some.

I suggest disabling XMP memory overclocking and see if BF6 stops crashing.

- Oskool_007

Thanks but that's a generic AI answer. I have already tried every single step in that generic list (SFC /scannow, memory diagnostics, clean DDU driver install, Clean Boot, verifying game files, etc.) and none of them fixed the issue. Also, XMP is not the culprit here (I'm on a 9th Gen CPU, so the known 13th/14th Gen instability fixes don't apply) I have analyzed the Crash Dumps in depth, while initial logs pointed to FSR resource failures, even after a clean reinstall on an NTFS drive and a full registry reset, the crash persists as a generic Exception Access Violation (c0000005) inside ntdll.dll, specifically flagged by APPLICATION_VERIFIER_LOADED: 1. This happens even with FSR disabled/clean configs. The persistent AVRF flag on Windows Build 26100 (24H2) confirms this is an OS Kernel/Anti-Cheat conflict triggering system mitigations, not a hardware instability or a simple graphics setting, this is a core incompatibility that only the devs can fix

I'm having this same exact fault and it's very frustrating to say the least. Paying 80€ for a game i can't even play.
Also on RTX 40-series and debugging found the very same access violation for the function bf6!ffxFsr2ResourceIsNull.
Any ideas if the dev team has picked this up or if they are working on a fix for this? From the research i have done it seems to quite a large amount of people that have this exact issue on their system.

Absolutely agree with you, i'm convinced devs know about the BF6 crashes at launch on PC, the only thing i'm not sure is if they will be able to come up for a patch for season 2 in February.