BF6 Null Pointer Access Violation (0xC0000005) Mid-Game Crashes
Got ChatGPT to write up report below - have tried everything to fix this issue with some results giving slight improvements but mostly to no avail - I did get it to play for 2 hours fully once but it deteriorated quickly again after. Please help!
BF6 repeated access violation crashes with code 0xC0000005. Crashes occur mid match after 5 to 30 minutes. The game instantly closes to desktop with no error message. This happens consistently across sessions.
Windows Error Reporting and WinDbg show access violation crashes caused by null pointer reads or writes inside bf6.exe. All crashes point to the same internal Frostbite functions, mostly ffxFsr2ResourceIsNull and isGlimpseEnabled. The faulting instructions attempt to read or write memory at address 0 or at FFFFFFFFFFFFFFFF which indicates a null pointer dereference inside the game engine. No driver or system level modules ever appear in the call stack.
Crash pattern:
The game runs normally until a single large stutter occurs. Immediately after the stutter, the game closes to desktop. Task Manager shows bf6.exe immediately terminated. No freeze and no Windows errors.
Other games on this system are fully stable including Fortnite, Darktide, Helldivers 2 and Battlefield 2042. These titles previously had instability but were fully resolved through GPU tuning and cache rebuilds. Battlefield 6 is the only game still crashing.
Typical crash details from WinDbg:
Exception code: c0000005 access violation
Cause: null pointer read or null pointer write
Module: bf6.exe
Functions involved: ffxFsr2ResourceIsNull, isGlimpseEnabled
Address accessed: either 0000000000000000 or FFFFFFFFFFFFFFFF
Thread context: always in a Frostbite threaded job during rendering or asset streaming.
Examples of exception info:
Attempt to read from address FFFFFFFFFFFFFFFF at bf6.exe offset 458fe128
Attempt to read from address FFFFFFFFFFFFFFFF at bf6.exe offset 44ac4000
Attempt to read from address 0000000000000000 at bf6.exe offset 421a523e
These patterns all point to null pointer usage inside the engine code.
Steps already taken:
Full rebuild of Frostbite caches including shader cache, pipeline cache, compiled shaders, DirectX cache, ProgramData EA cache, and LocalAppData Frostbite cache.
Full reinstall of BF6.
Reset configuration files including PROFSAVE_profile.
Tested lowest, medium and high graphics presets.
Disabled ambient occlusion, DX12, frame generation, ray tracing, future frame rendering, Nvidia and AMD low latency options, and all upscalers.
Tried fullscreen, borderless and windowed modes.
Underclocked GPU and tested at stock voltage.
Disabled all overlays including Steam, Discord and AMD.
Disabled MPO and verified HAGS off.
Verified Secure Boot and TPM enabled.
Confirmed no RAM overclock. RAM is running JEDEC.
System passes OCCT, Memtest and long gaming sessions in all other games.
Conclusion:
All crash dumps consistently show null pointer dereferences inside bf6.exe. There is no evidence of GPU driver failure, DirectX failure, or system instability. This appears to be a BF6 engine level bug within Frostbite rendering or AMD FSR2 resource handling.
I can provide multiple crash dumps, DxDiag with personal info removed, and Event Viewer logs on request.
Request:
Please investigate repeated null pointer dereferences in ffxFsr2ResourceIsNull and isGlimpseEnabled within bf6.exe during mid match rendering. This crash only affects Battlefield 6 and has been reproduced more than thirty times.
Thank you.
