I’m getting repeat Battlefield 6 crashes with an ACCESS_VIOLATION (0xC0000005) error, usually pointing to bf6!isGlimpseEnabledand bf6!ffxFsr2ResourceIsNull. The crash reports show an invalid pointer read (e.g., trying to read from address 0x0000006A), which looks like the game is accessing a null or badly initialized FSR2-related resource and then exits to desktop.
Tried every fix imaginable, EA, please help or fix this.
timber_1507 disable EXPO/XMP memory overclocking in motherboard BIOS settings.
OskooI_007 List of troubleshoot trials....
Uninstall / Reinstall HD Textures - no
Disable integrated graphics in BIOS - no
Clear DirectX shader cache - no
Launch flags in Steam to force DX11 - no
Turn on/off DX12 in PROFSAVE_profile file - no
Launch flags in Steam to disable FSR2 - no
Launch flags in Steam for EnableGlimpse - no
Underclocking GPU - no
Underclocking RAM - no
Disable XMP/EXPO in BIOS - no
Disable all Nvidia 'extras' - no
In game graphics set to 'Low' - no
BIOS update - no
Uninstall / Reinstall game - no
Delete /battlefild6/settings directory - no
Fresh Windows install - no
Clean graphics driver install (DDU) - no
Graphics driver rollback - no
Graphics driver update - no
Update chipset driver - no
Stress test all hardware - no errors
Windows exploit protection bypass - no
Run anti-cheat and bf6.exe as admin - no
Repair EA anti-cheat - no
Turn debug mode on in Nvidia control panel - no
Turn off 'Threaded Optimization' 'Vertical Sync' in Nvidia control panel - no
Set 'OpenGL rendering' to my GPU specifically in Nvidia control panel - no
Set 'Power management mode' to 'Prefer maximum performance' in Nvidia control panel - no
Clear the following caches in /users/<username>/AppData/Local and then reboot: - no
/Temp/Battlefield6/httpcache
/battlefield/cache
/D3DSCache
/steam/htmlcache/ShaderCache
/steam/htmlcache/GrShaderCache
/Nvidia Corperation/Nvidia App/CefCache/GrShaderCache
/Nvidia Corperation/Nvidia App/CefCache/ShaderCache
Clamp GPU memory in ProfSave_profile - no
Change frame rate limit in ProfSave_profile - no
Lower resolution scale (1.00 -> 0.85) in ProfSave_profile - no
Disable shadows and enlighten in ProfSave_profile - no
Disable Hardware-accelerated GPU scheduling in System>Display>Graphics>Advanced Graphics Settings (and a system restart) - no
Clear Steam download cache - no
Remove and 'AMD phantom GPU drivers in Device Manager - no
Renaming amd_fidelityfx_*.dll -> amd_fidelityfx*.dll.bak in /steamapps/common/Battlefield 6 - no
Change System>Display>Graphics>Custom setting for applications>Battlefield 6>Specific GPU 1 - no
Change System>Display>Graphics>Custom setting for applications>Battlefield 6>Power Saving - no
Switch Monitors (noticed one had MPO = 4 and the other MPO = 1) - no
Delete all 'levels' directories and have Steam repair - no
so yah...
timber_1507 what's your CPU?
What fixed it for me was enabling frame rate limit and setting the cap to 75, may be different for you. Disabling XMP also worked for me, it's just a more round about way of gimping the game performance. The game simply doesn't run well on some systems, seems completely random who is affected.
OskooI_007 Ryzen 7 7700X , RTX 4060Ti , 32GB DDR5 (XMP OFF) , TUF GAMING B650m + WIFI
Gone through every hoop there is to jump through. Was able to log about 80 hours before the issues started up. At launch, I had the same issue, dropped in-game graphics to 'Low' and was fine for 80 hours, and now, nonstop CTD.
timber_1507 ACCESS_VIOLATION (0xC0000005) is usually caused by memory errors.
Run HCI MemTest overnight while you sleep to test for memory errors.
Since you have a 16 thread CPU you want to open 16 MemTest windows to really stress test the memory controller, CPU, and memory sticks. You should see the CPU usage close to 100% in Windows Task Manager with 16 MemTest windows running.
https://hcidesign.com/memtest/
Open Windows Task Manager and check how much available memory there is.
Open multiple MemTest windows. Have each MemTest window scan 2000MB of memory.
Never let the available memory in Windows Task Manager reach 0. Always leave at least 1GB of available memory because if it reaches 0 then MemTest will start testing the Windows page file on the SSD.
OskooI_007
Thanks for the advice, but all hardware tests came back clean. Ran MemTest86 overnight, no issues. Stress test GPU and VRAM usage, clean. Since my last post, I’ve done a full windows drive wipe in installed a different windows OS version so that everything was back to defaults. Still getting the crash consistently. Same error code
timber_1507 MemTest86 misses a lot of memory errors compared to HCI MemTest. I've used both and HCI MemTest is much better.
