Cannot launch game
I have seen threads on this already but I feel like I have exhausted all options this is what I have done so far. The support team directed me here after a long chat with them.
Here's the updated summary with the initial launch symptom added:
System: Windows 11, AMD RX 7900 XT, EA App + Steam version of Battlefield 6
Original symptom: On launch via Steam, the game proceeds through the EA anti-cheat (Javelin) initialization step — a black window appears displaying "BF6" — and then closes on its own before the game ever loads. No error message is shown to the user at this stage.
Summary: BF6 has failed to launch consistently across several days of troubleshooting, with the failure point shifting through multiple layers as fixes were applied.
Troubleshooting completed, in order:
- Verified game file integrity (Steam)
- Enabled Secure Boot, confirmed UEFI/GPT boot mode
- Reinstalled EA Anti-Cheat (Javelin) manually via installer, uninstall-all + reinstall, repair
- Applied Windows Exploit Protection overrides (disabled all) for both bf6.exe, anti cheat launcher, and the anti-cheat installer
- First crash signature: during the black "BF6" anti-cheat window described above — eaanticheat.gameservice.exe — STATUS_HEAP_CORRUPTION (0xc0000374) in ntdll.dll
- Ran clean boot (all third-party services/startup disabled) — ruled out overlay/injection software conflicts
- Reinstalled Microsoft Visual C++ Redistributables (x64 + x86, clean uninstall then fresh install)
- Attempted Windows file system transaction log reset (fsutil resource setautoreset)
- Checked Windows Firewall rules for anti-cheat/game exe — confirmed present
- Second symptom: intermittent behavior shift — the same black "BF6" window began hanging indefinitely (idle, no crash) instead of closing, then later reverted to closing on its own again
- Third crash signature: bf6.exe — Application Hang, "Top level window is idle"
- Performed clean AMD driver rollback to Adrenalin 26.3.1 via DDU in Safe Mode (matches a documented AMD/BF6 DX12 init conflict)
- Fourth crash signature (current): EALaunchHelper.exe (EA Desktop, v13.743.0.6256) — access violation 0xc0000005
- Cleared EA Desktop cache folders — no change
- Full clean reinstall of EA App (uninstall + manual folder deletion + fresh installer) — no change
- Tested launch under a new local Windows user profile — identical failure, ruling out profile-level corruption
- Confirmed .NET Framework 3.5 and 4.8 both enabled
Current state: Fails identically whether launched via Steam or directly through EA App, with EALaunchHelper.exe throwing an access violation. Full Event Viewer logs available for each crash signature listed above