Forum Discussion
This is still on-going for thousands of players EA, can we get an update?
Happened twice during the first 35 hours of play, that I can live with.
Then 5 times over 4 hours.
Now it's every 2-20 minutes. I can't play the game anymore. I can't finish a match.
Tried every solution Ive come across so far, reinstalled the game, direct X, swapped drivers,
installed/uninstalled windows updates, resizable bar on/off, DCOP/XMP on/off, PBO fiddling and on/off, page file sizes, shader caches both for the game and dx, all in-game settings wiped, from off/low to overkill etc. etc.
Im at my wits end here and I put in a refund request to Steam and I suggest others do as well until this is fixed since the game is just broken on a technical level at the moment.
- siles20045 months agoSeasoned Novice
Do you guys have AMD CPU and EXPO enabled?
IF SO, then download OCCT, run CPU+RAM Test if it fails, disable EXPO in BIOS and try BF6 again.
Even if you don't have EXPO but XMP, the same deal.
Download OCCT run the tests, if it fails and you also tried without XMP, then you may have an actual hardware error.- Zevered5 months agoSeasoned Adventurer
Appreciate it my dude, but it's literally thousands of players over both AMD, Intel and Nvidia experiencing this and in this game only. You can check this thread which I suppose is only a fraction of the people actually experiencing this and even as the EA rep said he saw a lot of these posts on Steam as well.
https://forums.ea.com/discussions/battlefield-6-technical-issues-en/dxgi-error-device-removed-or-dxgi-error-device-hung/12737991
- Zevered5 months agoSeasoned Adventurer
Ran the CPU + RAM test for 1 hour without issues.
- siles20045 months agoSeasoned Novice
I can only talk out of my own experience. I have been troubleshooting my issues for 4 days and solved them 100% today with disabling EXPO.
Maybe the EXPO issue is only with Ryzen 7000 on B650 Boards, but I'd rather tell and maybe help another then saying nothing.- Zevered5 months agoSeasoned Adventurer
Also RIP my xp boosts...
- 4htbocriik915 months agoSeasoned Newcomer
voce conseguiu resolver? ja tentei de tudo tambem e até agora nada
- NomadicX5 months agoSeasoned Newcomer
Seems to happen to me if I change game settings after installing drivers. Now, if I change the games settings to what I want then use ddu to uninstall nVidia driver and do a clean install of the driver I wont' get the errors at all unless I go back in and mess with the games graphics settings. I've been error free for 3 days after doing this. This only seems to happen in the graphics sections of game settings, going back in to change keybinds and other things doesn't trigger the error or require a reinstall of the driver
- TheGaiel5 months agoSeasoned Newcomer
i've been getting a inconsistent DXGI_ERROR_DEVICE_HUNG when launching the game,
The game encounters a DirectX error with the message: "DirectX function 'Hang Detected in waitForFrameFences. Timed out after 8000 ms. Waiting for SignalId: 116. Last Signaled Fence Value: 117. Unsignaled Fences: CGraphics stopped at 115), failed with 'The GPU will not respond to more commands'). GPU: NVIDIA GeForce RTX 4070, Driver: 58157. This error is usually caused by the graphics driver crashing; try installing the latest drivers."
The error occurs approximately 1 out of 3 times when launching the game.
Game Version: v1.0.1.0
Platform: PC (EA App)
OS: Windows 10
GPU: NVIDIA GeForce RTX 4070
GPU Driver: 581.57
CPU: AMD Ryzen 7 5700X
RAM: 32 GB- DJGamer485 months agoRising Novice
I get the same error when trying to multi-task while waiting for the match to fill before start.
- FrozenPlasma5 months agoRising Newcomer
Same error after alt-tabbing and clicking back into the game. Happens with both fullscreen and borderless.
- Fearless_FrieS5 months agoSeasoned Newcomer
I'm encountering this error too. It's triggered by Alt+Tab and then browsing the web for about a few minutes to half an hour, and then the error appears😂
- ShowNoMercy_Tv5 months agoSeasoned Novice
Τhe game consistently crashes after 5–15 minutes of play, no matter what settings I use.
The issue started on the second day after launch — on day one I could play for ~10 hours straight without a single crash. Since then, the game crashes every session with either:"DirectX function GetDeviceRemovedReason failed with DXGI_ERROR_DEVICE_HUNG", or
Access Violation (0xC0000005) pointing to RenderCore2.PlatformPcDx12.dll or RenderCore2.PlatformPcDx11.dll.I have multiple .mdmp crash dumps confirming that the crash happens inside Frostbite RenderCore2 — specifically during GPU command submission, not in the driver layer.
System Specs
CPU: AMD Ryzen 9 9800X3D
GPU: NVIDIA GeForce RTX 3080 (EVGA XC3)
Motherboard: MSI B650 Tomahawk MAX
RAM: 32 GB DDR5 6000 MHz CL30
PSU: Lian Li 1000 W Gold
Storage: NVMe Gen4 SSD
OS: Windows 11 Pro 64-bit, fully updated
GPU Driver: NVIDIA 552.44 WHQL (tried 581.57 and 537.58 too)
Monitor: 1440p / 240 Hz G-SyncError Details from Crash Dumps
DX12 mode: DXGI_ERROR_DEVICE_HUNG inside
RenderCore2.PlatformPcDx12.dll → D3D12Core.dll → nvldumdx.dll.
DX11 mode: Access Violation (0xC0000005) inside
RenderCore2.PlatformPcDx11.dll → D3D11.dll.
DRED data shows:
AllocationName: Frostbite::Render::DX12CommandQueue
→ Indicates the engine lost its GPU device context or invalidated its command buffer.
No overlays, overclocks, or third-party DLL hooks active.
Crash address is always the same (0x...66CA), confirming deterministic bug inside RenderCore2.Troubleshooting Already Tried
I’ve already tested every known fix and still get the same result:Drivers & Windows
- Clean driver install with DDU in Safe Mode.
- Tried 581.08, 552.44 WHQL, 581.57 and 537.58 WHQL (same issue).
- Windows fully updated, GPU firmware up to date.System stability
- No overclock on CPU/GPU/RAM (tested also with –50 MHz core / –200 MHz memory).
- GPU temps under 60 °C, VRAM < 60 °C.
- MemTest64 and OCCT show 0 errors.
- PSU 1000 W Gold, stable voltages.Settings & Engine
- Disabled HAGS, Game Mode, ReBAR, iGPU.
- Tried both DX12 and DX11 (same crash).
- Reset and deleted all game config and shader cache folders.
- Disabled Ray Tracing, DLSS, Reflex Boost, On-Demand Texture Streaming.
- Capped FPS to 165 Hz, V-Sync Off.
- Disabled all overlays (EA, Steam, Discord, Afterburner, RTSS).
- Attempted -RenderDevice.RenderAheadLimit 1 and -RenderDevice.Dx12Enable 0.
- Disabled Windows MPO via registry.Hardware isolation
- Tested with undervolt (0.900 V @ 1850 MHz) and stock — identical results.
- No other games crash (COD, Cyberpunk, Valorant, etc. all stable).All crash dumps show the same pattern:
Frostbite RenderCore2 triggers a GPU device hang or memory access violation inside the DX12/DX11 command queue layer.This strongly suggests a regression introduced with patch v2.2.0 affecting RTX 30-series GPUs and X3D CPUs (high frame-time variance).
It’s not caused by drivers or hardware — it’s an internal synchronization or memory-corruption bug inside the RenderCore2 module.I attach a Google Drive folder with some of my crashes:
https://drive.google.com/drive/folders/1bUSGO48XkK-4WSGIsDYzd87tw1p-nAoF?usp=sharing - Infortunio5 months agoRising Novice
The game is broken, this is not related to XMP profiles or whatever... EA, pls fix.
- bySkriK5 months agoNew Rookie
Hi everyone,
I'm creating my own post about the DXGI error because, although I've seen others mentioning it, I want to share my specific case and findings. After (maybe) 100 crashes since launch — and even back in the Beta — I think I’ve gathered enough consistent data that might help identify what’s happening.While this issue may vary slightly from player to player, my crashes are 100% reproducible under certain conditions. I believe it’s worth documenting here, hoping it might reach the devs at EA/DICE for further investigation.
Short summary
It seems there’s a potential bug in the FSR2 implementation, where the game passes a null or invalid texture/buffer to FSR2. When FSR2 tries to access that invalid resource, DXGI triggers a crash.
Why I believe this:
1. Crashes usually occur when swapping sights quickly or when there’s a zoom event — e.g., 3x scopes, RPGs, vehicle weapons, etc. Not always, but ~99% of the time.
2. Every crash dump shows the same call stack reference:
bf6!ffxFsr2ResourceIsNull+0x22ad1a0 bf6!ffxFsr2ResourceIsNull+0x22ad834
The crash is always a Device Hung (0x887A0006), suggesting the GPU is processing invalid data coming from FSR2.So in summary:
- Game passes FSR2 a null resource
- DirectX tries to process it
- GPU hangs → Windows terminates the process → crash
Things I’ve tested (none fixed it)
- Disabled FSR as much as possible → tried TAA, no upscaling, no AMD frame generation → same crash.
- Launch options: -dx12 -noasync → no effect.
- Re-tested FSR on/off and various AA modes → crashes happen faster with FSR enabled.
- Cleared shader/cache files between tests.
- Disabled all overlays (Radeon, Discord, Steam, etc.).
- Edited TDR registry values (Delay and DdiDelay) → no stable improvement.
- Underclocked GPU core frequency → no change.
- Many more smaller tests with same results.
Key debug extract (WinDbg !analyze -v)EXCEPTION_CODE: 0x887A0006 (DXGI_ERROR_DEVICE_HUNG) PROCESS_NAME: bf6.exe MODULE_NAME: bf6 FAULTING_FUNCTION: bf6!ffxFsr2ResourceIsNull STACK (top frames): bf6!ffxFsr2ResourceIsNull+... KERNELBASE!RaiseException+...
Failure indicates FSR2 attempted to access an invalid/null resource during frame reconstruction.
System
GPU: AMD RX Vega 64
Driver: Adrenalin 25.8.1 (clean install via DDU, last driver available for the Vega)
CPU: Ryzen 5 3600X
OS: Windows 10 22H2
API: DirectX 12If anyone else is facing the same issue, especially with AMD GPUs, please share your crash stack or reproduction pattern — the more data we gather, the better the chances EA/DICE can identify it.
Summary
“This is a consistent, reproducible crash seemingly caused by an invalid FSR2 resource being passed to DirectX during zoom/scope transitions. Requires dev-side fix.”
- PolyMorris5 months agoNew Novice
Adding onto this:
My Crashdump is the following:FILE_IN_CAB: CrashDump_2025.10.18_22.15.31.828.mdmp
COMMENT: Frostbite MiniDump. Address: 1449567de (In Windbg type: .ecxr)
[EOF]NTGLOBALFLAG: 0
CONTEXT: (.ecxr)
rax=000000000007025d rbx=0000001e2d90c2b0 rcx=0000001e2d90c2b0
rdx=0000000000000000 rsi=000000007dd8fec8 rdi=3fae40f14109ffff
rip=00000001449567de rsp=000000007dd8fca0 rbp=000000007dd8fda0
r8=0000001e2d90c2b0 r9=0000001e2d90c2b0 r10=0000001e2dc3955b
r11=000000007dd8fe48 r12=000000000007025d r13=3fae40f1410a01a7
r14=0000000000000010 r15=000000007dd8fe98
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
bf6!ffxFsr2ResourceIsNull+0x21534ee:
00000001`449567de 418b4d10 mov ecx,dword ptr [r13+10h] ds:3fae40f1`410a01b7=????????
Resetting default scopeEXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00000001449567de (bf6!ffxFsr2ResourceIsNull+0x00000000021534ee)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffffPROCESS_NAME: bf6.exe
READ_ADDRESS: ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
No event log, also no device hung error is reported, the only source here for me is the crashdump, windows itself doesnt even report the crash in the even log.
Sadly I dont have an AMD GPU maybe that is why the crash and logs look a bit different.
In addition to that, if I keep trying to play the game, eventually its a reboot not just a crash to desktop.
I have not payed attention to whether or not it happens during scoping or not sadly.
But it usually happens after the next match loads and then about 15 mins into that second match.
So basically I can play one game plus 15 mins.- Rixtn4 months agoSeasoned Adventurer
PolyMorris It has nothing to do with your GPU not being from AMD.
I’m getting the same crash dump report, and I do have an AMD GPU (7900XTX).
Silent crash to desktop, no error message, no event log.
It’s strange that you can play for a while before it crashes. For me, it crashes as soon as I try to load a map. I’ve never even got my boots on the ground in-game. It was the same issue during the beta weekends. Really thought they would have fixed it by now.
- budekim5 months agoRising Rookie
Chiming in to say I'm having the same exact error as you on a 9060 XT. And I played fine for an entire week without this happening, just started today.
- Rixtn4 months agoSeasoned Adventurer
+1
"bf6!ffxFsr2ResourceIsNull"
I'm with you guys... let's hope for a fix soon.
- FelizNaveedad5 months agoRising Newcomer
Rest of Error:
("The GPU will not respond to more commands"). GPU: "NVIDIA GeForce RTX 3080", Driver: 58157. This error is usually caused by the graphics driver crashing; try installing the latest drivers.
Game is optimized and on latest driver. This game keeps crashing every 5 minutes, making the game unplayable.
In a cross-play party with an xbox friend.
- Glowreus5 months agoRising Newcomer
I am having this issue as well
- Raiiny_D5 months agoRising Novice
I still get DXGI_ERROR_DEVICE_HUNG crashes every 15 minutes. I see many people complaining about this and there seems to be no word of progress on wether they are looking into this or not?
Can someone on the EA team be more vocal on this issue, it makes the game unplayable. Its so frustrating, no other game i play crashes like this.
- Hasand0503915 months agoNew Adventurer
https://www.intel.com/content/www/us/en/download/17881/intel-extreme-tuning-utility-intel-xtu.html
dowload this end maybe fix work for me =D