Battlefield 6 DirectX Error Fix: 12 Ways to Stop DXGI_DEVICE_HUNG and DEVICE_REMOVED Crashes

There is no single universal fix for Battlefield 6 DirectX crashes. A DXGI_ERROR_DEVICE_HUNG, DXGI_ERROR_DEVICE_REMOVED, DXGI_ERROR_DEVICE_RESET, GetDeviceRemovedReason, or m_submitFencePlat->GetCompletedValue() message usually means that the game lost access to the graphics device or Windows recovered from a GPU timeout. It does not automatically mean DirectX is missing or that your graphics card is physically defective.

Start with the low-risk sequence: restart Windows, update Battlefield 6, repair the game files, reset its local settings, clean-install or roll back the graphics driver, return overclocked hardware to stock settings, disable overlays, and cap the frame rate. The correct order matters because a game bug, driver regression, corrupted profile, unstable hardware, or background hook can produce nearly identical messages.

What does a Battlefield 6 DirectX error actually mean?

These are graphics-device errors reported by the game through Microsoft’s DXGI layer. Microsoft defines DXGI_ERROR_DEVICE_HUNG (0x887A0006) as a device failure associated with badly formed commands, while DXGI_ERROR_DEVICE_REMOVED (0x887A0005) means that the graphics device was removed or reset. DXGI_ERROR_DEVICE_RESET (0x887A0007) indicates that the device could not continue in its current state. The definitions are documented in the DXGI error reference.

From a player’s point of view, the same failure can be caused by a Battlefield 6 bug, an incompatible or damaged driver, a GPU timeout, unstable overclocking or undervolting, excessive temperature or power demand, overlays and capture hooks, corrupted shader or settings data, or memory pressure. Windows’ timeout detection and recovery system normally gives a graphics operation about two seconds to finish before it attempts recovery, so a stalled render command can become a device-hung or device-removed crash even when the hardware is not permanently damaged. Microsoft describes that process in its WDDM timeout-detection documentation.

The exact wording is more useful than the generic word DirectX. A missing DLL, a Javelin Anti-Cheat message, a black-screen reboot, and a normal device-hung crash need different remedies. Copy the complete error text before changing anything.

Is this a DirectX installation problem?

Usually, no. Battlefield 6 requires DirectX 12, which is part of supported Windows versions. Microsoft’s DirectX End-User Runtime installer supplies optional legacy components for older games; it does not upgrade the installed DirectX 12 graphics runtime. Installing it can help when an older title reports a missing legacy DLL, but it is not the normal remedy for a DXGI device-hung or device-removed crash.

Do not download individual DLL files from random sites, edit TDR registry values as a first step, or assume that reinstalling DirectX will repair a driver timeout. Repair the game, the driver, and the system conditions that can make the device unavailable.

What are the current Battlefield 6 PC requirements?

Use EA’s dedicated Battlefield 6 system-requirements page rather than older FAQ figures. The current page lists DirectX 12 for both tiers.

Requirement	Minimum	Recommended
Operating system	Windows 10	Windows 11
CPU	Intel Core i5-8400 or AMD Ryzen 5 2600	Intel Core i7-10700 or AMD Ryzen 7 3700X
RAM	16 GB	16 GB
GPU	NVIDIA RTX 2060, AMD RX 5600 XT 6GB, or Intel Arc A380	NVIDIA RTX 3060 Ti, AMD RX 6700 XT, or Intel Arc B580
VRAM	6 GB	8 GB
DirectX	DX12	DX12
Storage	55 GiB HDD	80 GiB SSD
Other	TPM 2.0, UEFI Secure Boot, HVCI/VBS capability	TPM 2.0, UEFI Secure Boot, HVCI/VBS capability

EA’s separate FAQ has displayed older 60 GB and 90 GB storage figures, so use the dedicated requirements page for the current values. Meeting the minimum specification does not guarantee stability; drivers, cooling, power delivery, game updates, and background software can still cause a device timeout.

Did the latest Battlefield 6 update fix the crash?

Only one documented class of crash was addressed. As of August 10, 2026, EA’s latest official update reference was Game Update 1.4.1.5, announced August 3 and released August 4, 2026. Its PC stability fix covered certain NVIDIA GPUs that could crash when changing attachments on the SOR-300SC, using Custom Search, or playing on maps with large bodies of water. Read the official update notes.

Update through Steam, the EA app, or the Epic Games Store before deeper troubleshooting. If your crash matches one of those triggers, test the patched version first. The update does not establish that every remaining DXGI error has been fixed, so record the game version and exact trigger if the problem continues.

How can I fix Battlefield 6 DXGI_DEVICE_HUNG and DEVICE_REMOVED crashes?

Follow these fixes in order. Each step changes a different cause and is reversible unless noted. Test the game long enough to reproduce the original trigger after each change instead of repeatedly launching it without recording what changed.

1. Fully restart the PC

Exit Battlefield 6 and its launcher, then choose Start > Power > Restart. Do not rely on closing the game window: a stuck background process or partially recovered graphics driver can remain active until Windows reboots. EA lists a full restart as first-line advice for DXGI_ERROR_ and DEVICE_HUNG messages in its Battlefield 6 error guidance.

Expected result: the game reaches the menu and completes the activity that previously crashed. If the same error returns, continue to the update and file checks rather than performing multiple identical relaunches.

2. Update the game and compare the trigger with known issues

Open the launcher’s download or update queue and allow Battlefield 6 to finish patching. Then note whether the crash happens while changing SOR-300SC attachments, opening Custom Search, or entering a water-heavy map. Those symptoms overlap the NVIDIA issue addressed in update 1.4.1.5.

If the crash started immediately after a game update, keep the exact build number, map, weapon, and menu action in your notes. A timing change can indicate a post-update interaction rather than a missing Windows component. If the patched scenario still fails, continue with requirements and driver testing.

3. Confirm the PC and driver meet the current requirements

Use Windows’ diagnostic report before changing hardware settings:

1. Press Windows + R.
2. Enter dxdiag and press Enter.
3. Review the operating system, processor, memory, DirectX information, display adapter, and driver date.
4. Select Save All Information if you need to attach the report to EA support.

Compare the GPU, VRAM, RAM, and Windows edition with EA’s current table. The minimum tier requires 16 GB of RAM and a DX12-capable GPU at least in the RTX 2060, RX 5600 XT 6GB, or Arc A380 class. A qualifying PC can still crash because of a driver regression, temperature, power issue, unstable clock, or game defect; requirements checks eliminate an incompatibility but do not prove stability.

4. Repair the game files

Damaged or incomplete files can fail while the game loads shaders, opens the menu, or enters a map.

EA app

1. Open the EA app and select Library.
2. Find Battlefield 6 and open its Manage icon or three-dot menu.
3. Choose Repair.
4. Wait for the scan and replacement process to finish before launching.

EA documents this procedure for games that will not load or crash in its download, install, and load troubleshooting guide.

Steam

1. Restart Windows, then open Steam.
2. Right-click Battlefield 6 in the Library, or select its gear icon.
3. Choose Properties, then Installed Files.
4. Select Verify integrity of game files.

Steam notes that some files can fail verification because they are local configuration files. That warning can be normal; it does not necessarily mean the repair failed. See Steam’s verification instructions.

5. Reset only the Battlefield 6 settings folder

A corrupted graphics profile or shader-related setting can crash the game at startup, during compilation, or when changing options. Back up the folder before renaming it:

1. Close Battlefield 6 and its launcher.
2. Open C:Users<YourName>DocumentsBattlefield 6.
3. Copy the settings folder to another location.
4. Rename the original folder to settings_old.
5. Launch the game and let it create fresh defaults.

For Steam installations, the profile can be under C:Users<YourName>DocumentsBattlefield 6settingssteam. The PROFSAVE_profile file contains graphics and control configuration, so preserve the backup. A settings reset does not equal deleting online progression, and renaming the entire Documents folder is unnecessarily broad. The profile path and backup considerations are described by GameWatcher’s Battlefield 6 config guide.

Expected result: the game starts with default graphics and controls. If the crash remains, restore the backup and move to driver testing.

6. Perform a clean graphics-driver installation

Standard updates can leave old profiles or damaged components behind. Download the package for the exact GPU model from the manufacturer before removing anything.

NVIDIA

1. Start the official driver installer.
2. Choose Custom (Advanced).
3. Select Perform a clean installation.
4. Restart Windows and test Battlefield 6 before restoring tuning profiles.

The clean-install option is shown in NVIDIA’s documentation. Driver numbers change frequently; do not treat a particular release as permanently correct for every GPU.

AMD

1. Download AMD Cleanup Utility from AMD.
2. Run it and allow the recommended Safe Mode restart.
3. Let the cleanup complete, then restart Windows.
4. Install the current driver from AMD’s support site.

AMD says Safe Mode is recommended and that a restart is required. Its procedure is available at AMD Cleanup Utility. Laptop owners should check the computer maker’s driver first because OEM packages can include display, power, mux, or hybrid-GPU customizations.

7. Test the previous driver when the crash follows an update

Latest is not always best when a regression has just been introduced. Use this rule:

• If the crash existed before the driver update, clean-install the current package.
• If it began immediately afterward, test the previous known-good package for your exact GPU.
• If only Battlefield 6 crashes while other demanding games remain stable, suspect a game-and-driver interaction before declaring the hardware defective.

AMD’s system-stability guidance recommends checking release notes and reverting when a known driver issue has no available fix. Do not choose a rollback version solely because another player reported success on different hardware.

8. Return CPU, GPU, and memory to stock settings

Temporarily disable GPU overclocks, undervolts, CPU overclocks, XMP or EXPO memory profiles, automatic tuning utilities, custom voltage settings, and power-limit changes. Then check:

• GPU and CPU temperatures during a match
• GPU power cables and PSU capacity
• Whether the graphics card is fully seated
• Whether other demanding games also crash

Microsoft lists overclocking, incorrect memory configuration, insufficient cooling, insufficient power, and defective components among contributors to video timeout failures in its Bug Check 0x117 guidance. Stock settings may reduce performance temporarily, but they test system stability. If the game becomes reliable, the result points to tuning or power conditions rather than DirectX itself.

9. Reduce rendering stress and cap the frame rate

EA recommends frame-rate limiting and V-Sync when troubleshooting crashes or freezes. Set a cap below the monitor’s maximum refresh rate and enable V-Sync, then test conservative settings:

• Lower texture, effects, mesh, and post-processing quality.
• Reduce resolution or render scale.
• Disable Frame Generation.
• Disable or change upscaling.
• Turn HDR off temporarily.
• Disable ray-tracing-related features if they are available in the current build.

The last four are diagnostic tests, not guaranteed EA fixes. If disabling one feature stops the crash, re-enable features one at a time and record the combination that remains stable. A change that helps indicates a rendering-path or driver interaction, not proof that a particular vendor or feature is universally defective. EA’s general guidance is at Troubleshoot PC, PlayStation, and Xbox crashing or freezing.

10. Disable overlays, capture hooks, and background applications

Turn off overlays and monitoring tools for one test session:

• Discord, Steam, EA, NVIDIA App, and AMD overlays
• Xbox Game Bar
• MSI Afterburner or RivaTuner on-screen displays
• OBS capture hooks
• RGB and peripheral-control utilities
• VPNs and unnecessary monitoring programs

For a clean-boot test:

1. Press Windows + R, type msconfig, and press Enter.
2. Open Services, check Hide all Microsoft services, and select Disable all.
3. Open Task Manager from the Startup tab and disable nonessential startup items.
4. Restart Windows and test Battlefield 6.
5. Restore normal startup services after the test.

A clean boot is diagnostic, not a permanent gaming configuration. If the crash disappears, re-enable services in groups until the conflicting program is identified.

11. Force the game to use the dedicated GPU

This is most useful on laptops and hybrid-graphics systems, where Windows can assign a game to an integrated adapter.

1. Open Settings > System > Display > Graphics.
2. Add the Battlefield 6 executable if it is not listed.
3. Select it, choose Options, and set High performance.
4. Save and relaunch the game.

Microsoft explains GPU selection in its GPU guidance. If the option is missing or ineffective, use the laptop manufacturer’s control panel or BIOS/mux-switch setting. A desktop with one discrete adapter generally has no integrated-GPU assignment problem.

12. Repair runtimes, anti-cheat components, or reinstall as a last resort

Missing DLL or launch message

For a specific missing-runtime error, install or repair both the x64 and x86 Microsoft Visual C++ Redistributables. Microsoft’s latest supported Visual C++ Redistributable page explains the architecture requirements. This addresses missing runtime libraries; it is not a general remedy for a device-hung crash.

EA Javelin Anti-Cheat message

Battlefield 6 uses EA Javelin Anti-Cheat, not Easy Anti-Cheat. For a Javelin error, EA’s current steps include restarting the EA app as administrator, launching through the EA app, and reinstalling Javelin when required. Follow the Battlefield 6 error-code guidance. Those steps do not prove a fix for an ordinary DXGI_ERROR_DEVICE_HUNG crash.

Reinstall only after targeted tests

1. Back up the Battlefield 6 Documents settings folder.
2. Uninstall Battlefield 6.
3. Restart Windows.
4. Reinstall the game and allow all updates to finish.
5. Repair or reinstall the EA app if applicable.
6. Confirm that the clean installation launches before restoring old settings.

EA includes game and app reinstallation among escalation steps for persistent crashing. Reinstalling is time-consuming and will not correct unstable hardware or a current game-and-driver defect.

Should I force DX11 with a launch option?

Not as a standard fix. EA lists DX12 for both Battlefield 6 requirement tiers, and it does not document DX11 flags as a supported troubleshooting method. Community posts have reported experimental options such as -dx11, -d3d11, or -RenderDevice.Dx11Enable 1, but reports are inconsistent: some players describe temporary improvement, while others see no change or a launch failure.

If you test one, treat it as an unsupported experiment, not a recommendation:

-dx11

-RenderDevice.Dx11Enable 1

Remove the option immediately if the game will not start, and return to driver, file-repair, settings, and stability checks. The community discussion is available at EA Forums.

Which fix should I try first for my symptom?

Symptom	Start with
Crash while changing SOR-300SC attachments	Update Battlefield 6 to 1.4.1.5 or newer
Crash on maps with large bodies of water	Update, test the graphics driver, and disable overlays
Crash while opening Custom Search	Update Battlefield 6 before changing system settings
Crash at the menu or during shader compilation	Repair files, reset the settings folder, and disable overlays
Crash after 30–60 minutes	Return clocks to stock, check temperatures and power, and cap FPS
Laptop appears to use integrated graphics	Set Battlefield 6 to High performance in Windows Graphics settings
Missing DLL message	Repair the Visual C++ runtime or, for an older legacy component, the DirectX End-User Runtime
EA Javelin error	Use EA’s Javelin repair and launch steps
Black screen, reboot, or BSOD	Stop game tweaks and investigate drivers, temperatures, power, BIOS, and Windows logs

What should I do if the crash is specific to AMD or NVIDIA hardware?

A vendor-specific pattern narrows the test but does not prove a vendor-wide defect. For example, one EA forum report associated DXGI_ERROR_DEVICE_HUNG with a Desktop Window Manager crash inside amdxx64.dll, an older AMD driver, and outdated audio or peripheral drivers. That is a single diagnostic report, not evidence that every AMD crash has the same cause. Collect a current DxDiag, update related system drivers, and compare a clean current driver with the last known-good version.

For NVIDIA systems, first compare your trigger with the 1.4.1.5 SOR-300SC, Custom Search, and water-map fix. If it does not match, use the same neutral sequence: clean driver installation, stock settings, overlays off, and controlled graphics reductions.

What changes should I avoid?

• Do not disable every Exploit Protection mitigation. That lowers Windows security without establishing that a mitigation caused the crash.
• Do not apply arbitrary pagefile formulas. The often-repeated 1.5-times-RAM initial and 3-times-RAM maximum rule is not a Battlefield 6 requirement. Leave Windows-managed virtual memory enabled and keep adequate free space on the system drive.
• Do not edit TDR registry keys casually. Microsoft describes them as testing and debugging controls and says end users should not manipulate them as a routine fix. See TDR Registry Keys.
• Do not use Easy Anti-Cheat repair instructions. Battlefield 6 uses EA Javelin Anti-Cheat.
• Do not delete the entire Documents folder without a backup. Rename the settings folder first and preserve PROFSAVE_profile.
• Do not assume the newest driver is always best. A rollback can be the correct test when the crash began immediately after an update.
• Do not treat a DX11 flag as official support. Remove it if the game fails to launch.

When should I treat this as a hardware or system problem?

A normal game crash is different from a full black screen, forced reboot, system freeze, or blue screen. If the entire PC fails, inspect Reliability Monitor and Event Viewer for display-driver, Kernel-Power, or hardware events; monitor CPU and GPU temperatures; check the PSU and cables; and review recent BIOS, Windows, chipset, and driver changes. Test another demanding game at stock settings. Repeated system-level failures warrant hardware or driver diagnosis instead of more Battlefield launch options.

If Battlefield 6 alone crashes after repaired files, a fresh settings folder, a clean current or previous driver, stock hardware, disabled overlays, and conservative graphics settings, an unresolved game-and-driver interaction is plausible. That conclusion is different from proving that the GPU is defective.

What information should I send to EA if nothing works?

Give support a reproducible description instead of only saying DirectX crashed. Include:

• The complete error string and any numeric code
• GPU model, CPU, RAM amount, and Windows version/build
• Graphics-driver version and whether it was clean-installed or rolled back
• EA app, Steam, or Epic Games Store platform
• Battlefield 6 game version
• Map, mode, weapon, menu action, or time elapsed before the crash
• Whether Frame Generation, upscaling, HDR, overlays, or overclocking are enabled
• A saved DxDiag report
• Reliability Monitor or Event Viewer evidence
• Whether other demanding games also fail

This information helps distinguish a reproducible game bug from a driver regression, a local profile problem, or system instability. Use EA Help and the Battlefield forums after completing the safe checks above.

Frequently Asked Questions

Can a Battlefield 6 DirectX crash damage my graphics card?

A DXGI device error alone does not establish physical GPU damage. Windows may reset the graphics device after a timeout; concern rises when crashes occur in several demanding applications, temperatures or power delivery are abnormal, or the computer also freezes, reboots, or blue-screens.

Will deleting the Battlefield 6 settings folder erase my online progress?

Renaming the local settings folder primarily resets graphics and control configuration. Back it up first because files such as PROFSAVE_profile contain personal settings; do not delete the entire Documents directory as a precaution.

Why does Battlefield 6 crash only after a long session?

A delayed failure points more strongly toward temperature, power, VRAM pressure, unstable clocks, or a driver timeout than a missing DirectX component. Monitor temperatures, return tuning to stock, cap the frame rate, and compare another demanding game.

Should I reinstall Windows for DXGI_ERROR_DEVICE_HUNG?

A Windows reinstall is not a first-line response. Complete game repair, settings reset, clean driver testing, stock-hardware checks, overlay isolation, and log review first; reinstalling Windows will not fix a current game bug or unstable power and cooling.