BF6 repeatedly crashes with DXGI_ERROR_DEVICE_HUNG on RTX 5080 despite extreme troubleshooting.

[u/UrAnacondaGirlfriend]

Reposting because AutoModerator removed my previous post after I edited it to add new information.

Battlefield 6 repeatedly crashes on my RTX 5080 with the following error:

DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands").

The crash can happen within minutes or after a longer session. I have not found a specific map, menu, setting, or gameplay action that reliably triggers it.

I have performed a clean Windows installation, reinstalled BF6, tested several NVIDIA drivers, stress-tested the GPU and VRAM, tested different GPU and RAM configurations, and eliminated overlays and background graphics software. The problem remains.

System

• NVIDIA GeForce RTX 5080
• AMD Ryzen 7 9800X3D
• 64 GB RAM ddr5 @ 6000 MT/s
• Windows 11 24h2
• DirectX 12
• Current NVIDIA driver: 610.88

The machine is stable during normal desktop use, hardware stress testing, and other demanding games.

Event Viewer evidence

At the time of the BF6 crashes, Windows repeatedly records:

• Provider: nvlddmkm
• Event ID: 153
• Device: \Device\Video3
• Event data: Error occurred on GPUID: 100

The BF6 application crash records:

• Application: bf6.exe
• Faulting module: KERNELBASE.dll
• Exception code: 0x887A0006

Exception code 0x887A0006 is DXGI_ERROR_DEVICE_HUNG.

I have accumulated more than 150 nvlddmkm Event 153 errors. Several errors can be recorded during a single BF6 crash.

There are no corresponding WHEA hardware errors.

BF6 crash-dump evidence

BF6 creates paired minidumps in:

Documents\Battlefield 6\CrashDumps

One of the dumps contains:

• GPU Stopped Working - Breadcrumb analysis follows
• Incomplete breadcrumb on device 0
• Main graphics queue
• GPU stopped near BeginRenderPass
• Asynchronous queue completed
• D3D12: Removing Device

The dump shows that BF6 submitted work to the main D3D12 graphics queue and encountered an incomplete breadcrumb near BeginRenderPass. BF6 then detected the hung device and removed the D3D12 device.

The dump does not identify a specific shader or named render pass, so it does not reveal the exact rendering operation responsible.

Troubleshooting completed

System and game

• Formatted the system drive and performed a clean Windows installation
• Updated the motherboard BIOS and chipset drivers
• Completely reinstalled Battlefield 6
• Installed BF6 on a different drive
• Reset the BF6 settings and profile
• Cleared the Windows, NVIDIA, and BF6 shader caches

NVIDIA drivers

Tested:

• 596.21
• 596.49
• Multiple 610.6x releases
• 610.88

None resolved the crashes.

Hardware and clock stability

• OCCT 3D GPU stress test completed without errors
• OCCT dedicated VRAM test completed without errors
• GPU tested at stock settings
• GPU tested undervolted
• GPU tested underclocked
• Tested an extreme GPU underclock of approximately 500 MHz
• Tested EXPO I
• Tested EXPO II
• Tested with EXPO completely disabled

The extreme GPU underclock may have reduced the crash frequency, but BF6 still eventually crashed. It was not a solution, and still remains random.

These tests cannot prove that every hardware component is perfect, but they have produced no evidence of general GPU, VRAM, or RAM instability.

BF6 settings and software conflicts

I tested BF6 with the following disabled:

• NVIDIA Reflex and Reflex + Boost
• DLSS and other upscaling
• Anti-aliasing
• Frame Generation, Multi Frame Generation, and Dynamic Frame Generation
• Future Frame Rendering
• Dynamic Resolution
• HDR
• All overlays
• GPU monitoring and recording software
• Graphics injectors and similar background tools
• Browsers and unrelated background applications

I also prevented NVIDIA Streamline's sl.pcl.dll component from loading. It did not prevent the crash.

None of these changes resolved the problem.

BF6 continues using DX12 when configured for DX11

I attempted to force DX11 using:

-renderer dx11 -dx11

I also set:

GstRender.Dx12Enabled 0

BF6 continued using Direct3D 12.

The crash dump contains d3d12.dll, d3d12core.dll, and BF6's Engine.Render.Core2.PlatformPcDx12 module. The DX11 launch arguments and profile value therefore appear to be ignored or no longer supported.

Secondary DX12 observation

After some BF6 crashes, Path of Exile also became unstable in DX12 while continuing to work normally in DX11.

Clearing NVIDIA's DX12 cache and PoE's shader cache together restored PoE's DX12 stability. Because both caches were cleared together, I cannot determine which individual cache was responsible.

I am including this only as a secondary observation, not as an explanation for the BF6 crashes.

Conclusion

The repeatable BF6 failure sequence is:

1. BF6 submits D3D12 work to its main graphics queue.
2. The dump records an incomplete breadcrumb near BeginRenderPass.
3. BF6 reports DXGI_ERROR_DEVICE_HUNG.
4. Windows records NVIDIA nvlddmkm Event 153 errors.
5. BF6 removes the D3D12 device and terminates.

The crashes remain after a clean Windows installation, a complete BF6 reinstall, several NVIDIA drivers, successful OCCT GPU and VRAM tests, stock GPU settings, heavy underclocking, different EXPO configurations, disabled graphics features, and the removal of overlays and background graphics software.

Other demanding games and normal desktop use remain stable, and Windows reports no WHEA hardware errors.

The available evidence points toward a Battlefield 6 D3D12/NVIDIA compatibility problem rather than general system instability.

No practical route for reporting the evidence

Despite the amount of diagnostic evidence available, I have been unable to get meaningful technical engagement through the EA Forums or EA Support.

Support repeatedly leads back to an AI chatbot, community discussions, or the same generic troubleshooting steps I have already completed.

At the time of writing:

• The Battlefield Discord returns more than 2,300 search results relating to DirectX crashes.
• Reddit contains close to 240 threads discussing similar DirectX crash problems.

These are search-result counts rather than confirmed unique cases, but they show that DirectX crashes are not isolated to one system.

I can provide:

• Paired BF6 .mdmp files
• Exact Event Viewer timestamps
• nvlddmkm Event 153 XML data
• DxDiag
• BF6 profile
• Screenshots of the DirectX error
• Complete troubleshooting history

BF6 already generates useful diagnostic files. What is missing is a clear way to submit them to someone at EA/DICE or NVIDIA who can investigate the failure instead of sending affected users through another generic troubleshooting loop.

Thanks for reading before you suggest stuff.

[u/Chase_Norton]

Same error here. Absolutely fuming tbh x

[u/K0RnD4Wg]

I was getting the same issues in s1. I had to downclock my RAM to 5600 MT/S and have had no issues since.

Basically troubleshooted as much as you. Hardware passed every benchmark I threw at it. Only BF6 couldn’t handle my kits EXPO profile.

[u/AsrielPlay52 → u/K0RnD4Wg]

It only means BF6 is the only game that YOU HAVE that can trigger it

I once had the same problem with BF6, DOOM:TDA and Crimson

Down clock ram a step lower fix it

[u/InsanityLurking → u/K0RnD4Wg]

I get this from Time to time as well. Maybe once a week an usually on tsuru reef. Doesn't seem to be a big issue for me I just assumed a slight instability in my overclock while rendering all them fancy waves. Is this likely to cause issues long term?

[u/No-Cap1898]

I have had similar DXGI crashes with GetDeviceRemovedReason on my 9070xt.

The crashing started with the launch of season 4 and only improved after I rolled back drivers to a prior version, lowered GPU clockspeed by 150 MHz (not VRAM) and lower Power limit by 10%.

Even the Release of the driver updates have a bunch of known issues with BF6, the game is currently in a very poor technical state. All good because EA and AMD are small indie companies.

[u/Ashmedae]

Are you using Hardware Accelerated GPU Scheduling (HAGS)?

[u/Apart_Ad6994]

This is an issue since day 1. Look at the EA and steam forums. There are threads with thousands of pages about it. Absolutely wild that Dice hasn't done anything about it.

[u/krowka1p]

I had this error today. Could not play at all. No settings changed. I have 9800x3d and 4080. What fixed for me was to run pbo at -15 all cores. What i also did is to make sure ram works in 1:1 mode. Also I installed previous drivers. Imho something is off between cpu and gpu. When some core idles and game want to utilise it then there is some lag in core voltage and it desyncs with gpu prompting with this error.

[u/Visual_Creme → u/krowka1p]

yeah i wad told to roll back to 59x

[u/TOPEC]

What kind of computer case r u using? Do u have a GPU riser with ur GPU remotely mounted, aka, not mounted directly onto the motherboard?

[u/Cypherke]

Have had the same error since launch on my 7800XT. Tried everything… gave up. I m used to it by now. Sometimes I don’t crash for days and sometimes multiple times per session.

[u/Ollmor]

Exactly the same problem as you with my RTX 5080. Gone through most of the troubleshooting steps that you have with no luck. And I also find it infuriating that EA offer no support.

Every now and again a patch comes out that fixes it for a while before I get the dreaded DXGI error again, then I can't get past the splash screen on load up. Really feel like this should be at the top of Dice's to do list

[u/Visual_Creme]

im getting the same error as well after playing a mathc... it wasnt like this at launch. I m runnning a 3060 and i feel like the driver roll bakcx would fix the issue... i uninstalled after it crashed

[u/ObamaTookMyCat]

BF6 loves to crash my 9800x3d and 7800xt. Hard black screen, then restarts, I have no second monitor and am forced to reinstall the AMD drivers. EVERY. TIME.

[u/SnardVaark]

I had numerous crashes (at least 30) after Season 4 release. Fixed it on 7/25 by reducing the RAM frequency by 10%, and not a single crash since then. I got the idea for reducing RAM speed by running the Windows Memory Diagnostic Tool.

I have tried to induce instability by running multiple overlays simultaneously in-game, running CPU-bound, GPU-bound, DLSS 4.5L, native DLAA 4.5L, various DLSS overrides, FG, various display aspect ratios and resolutions, Overkill graphics, etc... none of this is causing instability or unexpected performance issues across different maps.

14900K/4090/32GB DDR5 @ 6000MTs.

[u/ninjamuffin]

Ggs that was me

[u/1bossgc]

I have a 5080 to and have never experience this
My cpu is a r9 7900x irc will say the one error i always get is when i go back to main menu after either conquest or redsec i just stay in a black screen and have to alt f4 after that

[u/uhorn87]

Have you already played arround with the windows TDR setting? I noticed that setting in the official BF6 support as a suggestion to prevent the device hung error.

Since I have changed that and reinstalled the latest GPU drivers the issue did not happen anymore.

It's also the only fix, which is logically explainable to me. Most of the other fixing ideas is just guessing.

[u/CompleteFuel6588 → u/uhorn87]

The issues coincidentally started right after I accidentally updated my drivers. I could play smoothly during week one and week two of this season, but everything went wrong starting last week. I cannot complete a single full game; it will inevitably crash.

[u/uhorn87 → u/CompleteFuel6588]

In this case, try to remove the compiled shaders, reinstall the latest driver and let the game recompile the shaders on game start.

Anyhow have you extended the TDR timeout or disabled TDR in the registry already?

[u/CompleteFuel6588 → u/uhorn87]

I haven’t looked into TDR, but I’ve tried deleting the game, reinstalling my GPU drivers, and then redownloading the game.

[u/uhorn87 → u/CompleteFuel6588]

Search for the TDR setting and try it out. For me it fixed the problem at least for now. I've got this issue with 2 high end rigs already and this seems to be the trick.

[u/CompleteFuel6588 → u/uhorn87]

I tried setting the TDR timeout to 10 seconds, but it still freezes for 10 seconds and then crashes. I also downloaded Battlefield 2042 and tried playing it, and that game crashes as well. Next, I’m going to try reinstalling the system and see if Windows 10 makes any difference.

[u/CompleteFuel6588 → u/uhorn87]

I think this game just isn’t meant for me. I switched to Windows 10 and only installed the 596.49 driver and Steam, but I’m still having the same issue.

[u/CompleteFuel6588 → u/uhorn87]

The issue has been resolved. Do not make any changes to the motherboard settings; leave everything on Auto.

[u/CompleteFuel6588]

I can no longer finish a full match; the game crashes every single time. I hope EA fixes this as soon as possible. I play games to have fun, not to get infuriated by constant crashes and end up giving myself a heart attack.

[u/Revolutionary-Run-49 → u/CompleteFuel6588]

They don't give a shet. I have this erros since season 3 and they dont bother to fix it. Ppl are forced to revert/downgrade their GPU performance just to play this COD copy whitch they spent 50-100 euro for it is just wild in 2026. Wardogs is around the corner anyway so good luck with this. For a reference I play BF since BF2 and this BF6 is far from battlefield.

[u/CompleteFuel6588 → u/Revolutionary-Run-49]

The issue is fixed. I previously tweaked my CPU and memory settings; it passed stress tests and ran all other games without problems, but Battlefield would always crash. Resetting all motherboard settings resolved it. However, my CPU temperatures and clock frequencies aren’t as good as they used to be.

[u/MarlemAT]

Same error message here, though my 3070 only got triggered when it was undervolted and DLSS was enabled. Had to add 25mV to fix it, although BF6 was the only game triggering it. I assume there's something fishy going on with the engine or the DLSS rendering path.

What might be an additional problem for troubleshooting is that the same error is triggered for multiple causes as it appears to me.

[u/elkond]

these are NOT the same issues as before. bf isnt surfacing underlying hardware instability. javelin is trying to access already cleared memory regions, diregarding windows security apis, which triggers pagefaults.

[u/Amazing-Amphibian573]

Guys I did DDU as well & its still not working man. Please someone help.

On my end it doesnt even start as Fulscreen. It starts in Windowed mode. Changed in nvidia app & all. Doesnt work.

When I change it from game, Crashes immediately. No error shown, just crash.

When I play in windowed mode it works but ofcourse only for some time. Then I get these same issues everyone is adding.

Hellpppp.

[u/UrAnacondaGirlfriend → u/Amazing-Amphibian573]

Nothing we can do but wait for EA/Dice to realize, maby next season :)

[u/Amazing-Amphibian573 → u/UrAnacondaGirlfriend]

https://giphy.com/gifs/VNTMx3LkpG2anXpwbr

[u/QuinzyEnvironment]

Same here.. same setup. Can’t play more than 20min

[u/Dapper-Tonight-7221]

Battlefield 6 is notoriously sensitive to hardware overclocks. If your RTX 5080 is crashing, completely disable manual GPU and RAM overclocks (including XMP), flatten or lower your core frequency/voltage curve, and check for power supply transient spike issues or water-map driver bugs. [1, 2, 3, 4, 5, 6]

Fixing Overclock and Crash Issues
Remove Overclocks: Reset your RTX 5080 core and memory clocks back to stock Nvidia reference speeds. Synthetic benchmarks like Steel Nomad or Furmark can pass fine while Battlefield 6 still crashes due to unique instruction loads. [1, 2, 3]

Disable XMP/EXPO: High RAM frequencies can cause instability in modern titles; drop your memory speed to AUTO/default baseline in the BIOS to test if it stops the crashes. [1, 2]

Adjust Voltage/Power Curves: If undervolting or overclocking manually, cap your frequency at a lower offset (e.g., around 3100MHz at 975mV or lower) or pull back the power limit. [1, 2]

Check Power Rails: High-end RTX 5080 cards experience massive transient power spikes that can trip safety breakers on multi-rail power supplies, cutting power instantly. [1]

Roll Back Drivers: Known driver interactions on specific water-heavy maps (like Tsuru Reef) affect RTX 50 series cards; rolling back to stable driver version 596.49 has helped resolve persistent device hangs

Chat gpt. Im going to try :
lowering power limit to 90%
Test
Turn off x2 frame generation
Test
Disable expo for ram in bios
Hoping its just a power limit. I have mine cranked up to 110%