WinDbg analysis shows a NULL pointer write:
Attempt to write to address 0x0000000000000000
Crash location: bf6!ffxFsr2ResourceIsNull
Exception offset: 0x4f5bfa4
The crash appears related to FSR2/render resource initialization or shader/resource handling. The stack also contains HRESULT 0x80070017 (CRC/data error), which may indicate corrupted shader cache or invalid render resources.
The crash consistently happens on the map “Railway to Golmud” near objective F.
Game version: 1.0.424.48767
OS: Windows 11 26200
Dump
[drive.google.com]
file available.

I already cleared the NVIDIA shader cache:
%localappdata%\NVIDIA\DXCache
%localappdata%\NVIDIA\GLCache
I also verified the game files in Steam. Steam reports:
“10 files failed to validate and will be reacquired”,
but the files are not being downloaded/reacquired afterward.
GPU driver version is 596.49 (May 12 release).
The crash still consistently happens on “Railway to Golmud” near objective E.
WinDbg dump shows a NULL pointer write inside:
bf6!ffxFsr2ResourceIsNull
This appears to be related to the rendering pipeline / FSR2 resource handling rather than a simple local cache issue.
Dump
[drive.google.com]

Hi and thanks for the detailed notes of this crash. Please try also the following steps and see if that helps:
1. Set the game to Borderless/Windowed, not Exclusive Fullscreen.
2. Clear Steam’s download cache, restart Steam, then verify BF6 files again.
3. Clear %LOCALAPPDATA%\BF6 shader/cache files and run Windows Disk Cleanup for DirectX Shader Cache.
4. Temporarily uninstall optional BF6 content such as HD Texture Pack / REDSEC / Single Player DLC if installed, then test Railway to Golmud again. Reinstall afterwards

Hi and thanks for the detailed notes of this crash. Please try also the following steps and see if that helps:
1. Set the game to Borderless/Windowed, not Exclusive Fullscreen.
2. Clear Steam’s download cache, restart Steam, then verify BF6 files again.
3. Clear %LOCALAPPDATA%\BF6 shader/cache files and run Windows Disk Cleanup for DirectX Shader Cache.
4. Temporarily uninstall optional BF6 content such as HD Texture Pack / REDSEC / Single Player DLC if installed, then test Railway to Golmud again. Reinstall afterwards
I have already tried:
- Windowed / borderless / fullscreen modes
- Clearing Steam download cache
- Deleting %LOCALAPPDATA%\BF6
- Full game reinstall (textures)
- Disabling DLSS, Frame Generation, and all NVIDIA upscaling
- Switching upscaling method to TAA
None of these resolved the issue. Both crash dumps point to the same root cause.
Exception: Access Violation (0xC0000005)
Type: NULL pointer write — attempt to write to address 0x0
Crash address: bf6.exe+0x4F5C944 (same in both dumps)
Faulting instruction:
mov dword ptr [rax], r14d ; rax=0x0, r14=0x0
- Crash occurs in a render worker thread, not the main thread
- HRESULT 0x80070017 (ERROR_NOT_READY) present in registers at crash time
- Multiple callers reach the same faulting address (confirmed across 2 dumps)
- This indicates a persistent null/freed resource tied to a specific
map object or trigger at Objective F, not a random race condition
Likely introduced in Season 3 Update 1.3.1.0 (May 12 2026) with the
Operation Golmud map. The bug is 100% tied to Objective F on this map.
Dump
[drive.google.com]

The crash occurs both on Brooklyn and Operation Golmud with the same pattern.

ExceptionCode : 0xC0000005 (Access Violation)
ExceptionAddress : 0x144f5c944 ←
Access type : WRITE
Target addr : 0x0 ←
This is the third dump in a row, all three fall into the same instruction in bf6.exe+0x4F5C944
The raw data of the dump contains readable lines directly from the game's memory:

Explosion marks render at wrong depth
Units icons, Units and building health bars are 2D
mass extraction icons render at wrong depth
Shadows from units and structures jitter while zooming camera
Shadows double render with separation...
Some objects render at wrong depth
Shadows are not rendered correctly
Go to options/video shadow complexity = low
Dump
[drive.google.com]

Hey did you manage to fix this? Having the same error

same issue here

Unfortunately, I did not win it... It just fixed itself at some point after the patches from EA.