DXGI_ERROR_DEVICE_HUNG in season4

Game is consistently crashing with the following message: 

SInce last update, my game is crashing regularly. I can't get thru a match 90% of the time. DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). GPU: "NVIDIA GeForce RTX 5090", Driver: 61074 This error is usually caused by the graphics driver crashing; try installing the latest drivers.

I have over 100 haves installed across 5 hard drives and this is the only one crashing. While this may end up being a driver issue, it is a driver issue impacting this game. 

(FIX)
I had the same device hung error, and the only fix that worked for me was turning off XMP in my BIOS. After disabling XMP, my RAM went back to default settings and the crashes stopped completely. 

All in all, it is NOT your GPU!!!!

It seems like the game was unstable with my memory profile enabled, so if you’re running XMP or any RAM overclock, it may be worth testing with it off first. Just go into BIOS/UEFI, disable XMP/DOCP/EXPO, save changes, reboot, and see if the game becomes stable.

Good Luck and enjoy!
-Lumpia 

[BUG REPORT] REDSEC-only DXGI_ERROR_DEVICE_HUNG at match start — RTX 5070 Ti — all hardware causes ruled out

Platform: PC (EA app) Mode affected: REDSEC only. Gauntlet and regular multiplayer have never crashed.

Symptoms Crash occurs consistently after selecting class, as the match is about to start. Error:

DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). GPU: "NVIDIA GeForce RTX 5070 Ti", Driver: 61074

Also seen earlier as 0x887a0006 (DXGI_ERROR_INVALID_CALL) in other titles on the same system, since resolved.

System

• CPU: AMD Ryzen 7 7800X3D
• GPU: NVIDIA RTX 5070 Ti 16GB
• RAM: 64GB DDR5 Kingston Fury Beast (EXPO disabled, running stock)
• Motherboard: ASUS Prime B650M-A AX6 II (BIOS updated)
• Storage: 2TB WD Blue SN580 NVMe Gen4
• PSU: 750W 80+ Gold
• OS: Windows 11 Home, fully updated

Troubleshooting already performed — none resolved the issue

1. DDU clean uninstall in Safe Mode, fresh driver from NVIDIA
2. EXPO/XMP disabled, RAM at stock JEDEC. PBO disabled
3. BIOS updated to latest
4. Game files repaired via EA app
5. NVIDIA shader cache reset to Driver Default (was Disabled)
6. Settings tested at Overkill, High, and Low — crashes at all levels
7. NVIDIA Reflex disabled — no change
8. Future Frame Rendering disabled — produced longer crash-free stretches but crash returned
9. DLSS/upscaling settings varied — no consistent effect
10. No overlays running (OBS, Discord, Steam all closed during test sessions)
11. FurMark burn-in, 20+ minutes at 2560x1440: no crash, no artifacts. Peak 75°C, 100.3% TDP, limits reported as power only (temp:0, volt:0). GPU is stable under sustained maximum load.

Key evidence this is not a hardware or VRAM issue

• In-game VRAM meter shows 5140 / 15995 MB during REDSEC on low settings — roughly one third utilized, nowhere near the ceiling. Crashes still occur.
• GPU passes extended stress testing without fault.
• Crash is exclusive to REDSEC. Gauntlet and multiplayer are stable on identical hardware, drivers, and settings.

Additional note The in-game performance overlay flags memory throughput (mp/s) in red even while idle in the menu. May be relevant to the render/memory subsystem involved.

Attachments: DxDiag, crash log

Hi there, I’ve merged your post into the main thread.

Please take a look at the pinned message.

Hi there, I’ve merged your post into the main thread.

Please take a look at the pinned message.

Hello,

Since the latest Battlefield 6 update (weekend patch), I have been experiencing consistent crashes whenever Frame Generation is enabled.

System Specifications

GPU: NVIDIA GeForce RTX 5080 (No overclock)

CPU: AMD Ryzen 7 9800X3D

RAM: DDR5-6000 EXPO Enabled (stable for months)

NVIDIA Driver: 610.74 (Released July 7, 2026)

Operating System: Windows 11 (fully updated)

Issue

The game runs perfectly without Frame Generation enabled.

- 200+ FPS

- Completely stable

- No crashes

- No stuttering

However, as soon as I enable Frame Generation (both Fixed 2x and Dynamic MFG), the game crashes with a DirectX error.

The issue is consistently reproducible and is especially easy to trigger on the newest map introduced in the latest update.

Error

NVIDIA Driver Version: 610.74

GetDeviceRemovedReason failed with:

DXGI_ERROR_DEVICE_HUNG

"The application's device failed due to badly formed commands sent by the application. This is a design-time issue that should be investigated and fixed."

Troubleshooting Already Performed

- Repaired the game files.

- GPU is running completely at stock settings (no overclock).

- DDR5 EXPO has been stable for months.

- Tested without Frame Generation (100% stable).

- Tested with Fixed 2x Frame Generation (crashes).

- Tested with Dynamic MFG (crashes).

- DLSS Performance preset.

- No hardware instability in any other games.

- Disabling Frame Generation completely eliminates the crashes.

Reproduction Steps

1. Launch Battlefield 6.

2. Enable Frame Generation (Fixed 2x or Dynamic MFG).

3. Join a multiplayer server (especially the newest map).

4. Within seconds or a few minutes, the game crashes with DXGI_ERROR_DEVICE_HUNG.

Expected Result

Frame Generation should work without causing the game to crash.

Actual Result

The game crashes with DXGI_ERROR_DEVICE_HUNG, forcing the application to close shortly after Frame Generation is enabled.

Additional Information

I have also seen reports from other RTX 50-series users experiencing similar DXGI_ERROR_DEVICE_HUNG crashes. This may indicate a broader issue related to Frame Generation or the current game version.

Disabling Frame Generation completely eliminates the issue. I can play for extended periods at over 200 FPS without any crashes. The crashes only occur when Frame Generation is enabled.

I have attached a screenshot of the DirectX error dialog showing the DXGI_ERROR_DEVICE_HUNG error.

Thank you for investigating this issue.

Hi there, I’ve merged your post into the main thread.

Please take a look at the pinned message.