Battlefield 6 DirectX crashes can only be a problem with the game engine.
Battlefield 6 is crashing with DirectX errors on a wide range of systems. This has been happening since release and appears related to the game engine under heavy load. It needs an official fix. Many players are reporting the same behavior across different hardware and drivers. Some players say that the problem appears to have existed since Battlefield 2042. I can't confirm that myself, as I haven't played BF2042 for very long.
My system:
- CPU: [I7 14700K]
- GPU: [RTX 3090]
- RAM: [DDR5/ 64gb / 6400mhz]
- Storage: [M.2 SDD/NVme]
- Motherboard and BIOS: [MSI Z790 Carbon WiFi/latest]
- OS: Windows 11 [24H2] fully updated
- Display: [1440P/ultrawide]
- Driver: NVIDIA [latest] clean installed with DDU
Error codes:
- DXGI_ERROR_DEVICE_HUNG
- DXGI_ERROR_DEVICE_REMOVED
What happens:
- Crashes occur sporadically
- Sometimes only the game and open Steam processes die (most in my Case)
- Sometimes the entire PC reboots (for some players)
- there is no consistent pattern by map or time into the match
But there are repeated DirectX related crashes that are not fixed by normal maintenance or driver changes.
Steps to reproduce:
1. Launch the game normally from Steam or EA App
2. Join RedSec or Conquest mode
3. Played it through heavy action for a few minutes to tens of minutes or Sometimes over one hours
4. Crash with one of the codes above
Impact:
- Progress and match results are broken
- Time is wasted on failed troubleshooting
- This affects many players, not isolated edge cases
What I have already tried:
(None of the following resolved the issue)
- Drivers and OS:
- Clean driver installs with DDU for multiple versions
- Switching between Game Ready and Studio drivers
- Windows updates and optional cumulative updates
- Removing all overlays and capture tools
- Graphics API and launch options:
- Launching with -d3d11
- Disabling or enabling the different Anti-lag and upscaling ingame options.
- Forcing different shader cache settings in the driver
- BIOS and firmware:
- Enabling and disabling Resizable BAR
- Updating GPU VBIOS
- Updating motherboard BIOS and chipset drivers
- Power and stability:
- Returning CPU and GPU to stock clocks
- Disabling XMP or EXPO
- Raising power limits or lowering them to stock
- Checking PSU capacity and Performance
- disable PCI-Express - Link State Power Management on Windows
- set Windows PWR-Management to ultimate Performance
- Game files and cache:
- Verifying files via Steam
- Reinstalling the game on a different drive
- Deleting DX shader caches
- switching Graphics settings
- Dropping all settings Low
- Disabling Anti-lag and upscalers
- Reducing resolution to well below native
- Frame cap on and off (ingame and rtss)
- Vsync on and off
- disable Freesync/gsync
- Workarounds that are not solutions:
- Artificially throttling performance to keep GPU load very low (this seems to be working)
- Running windowed or borderless - (Not tested long enough yet)
- Disabling all background apps and services - (Not tested long enough yet)
Community signal:
Multiple reports show the same DirectX crash codes and the same failure of the usual fixes. The scope appears broad across GPUs from different vendors, multiple driver lines, and fully updated Windows systems.
-- All this points to an engine side stability issue under specific render or memory pressure conditions.--
What we need from EA and the dev team:
Official acknowledgement that this is being tracked as a top priority and a targeted hotfix or a detailed workaround that does not **bleep** performance.
If a driver side change is needed, coordinated guidance with NVIDIA and AMD.
Optional: a temporary toggle to disable the specific feature set that triggers the crash.
Clear communication on progress and an estimated timeline for a fix.
This is blocking normal play for many of us. A stable fix would go a long way for the community.
Thank you.
