Battlefield 6 – Black Screen on Launch and Silent Exit
Battlefield 6 – Black Screen on Launch and Silent Exit
Hello,
I am experiencing a persistent launch issue with Battlefield 6 on PC and have already carried out extensive troubleshooting.
ISSUE
When I launch Battlefield 6 through the EA app, EA Javelin Anti-Cheat launches normally and EAAntiCheatService starts successfully.
The Battlefield 6 splash screen appears. BF6 then opens as a small/windowed black screen in the top-left area of my primary monitor. The BF6 icon is visible on the Windows taskbar.
The black window remains for approximately 1–2 minutes without progressing. It then closes completely, the BF6 taskbar icon disappears, and the EA app returns to the foreground.
No error message or error code is displayed.
This happens consistently on every launch attempt.
PC SPECIFICATIONS
- OS: Windows 11 Pro 25H2
- OS Build: 26200.8655
- CPU: AMD Ryzen 7 7800X3D
- GPU: NVIDIA GeForce RTX 3070
- RAM: 32 GB
- Motherboard: MSI B650 Gaming Plus WiFi (MS-7E26)
- BIOS: American Megatrends 1.80, dated 15/12/2023
- BIOS Mode: UEFI
- Secure Boot: ON
- Virtualization-Based Security: Running
- Hypervisor-Enforced Code Integrity / Memory Integrity: Running
- I am not enrolled in the Windows Insider Program.
EA ANTI-CHEAT STATUS
I checked EAAntiCheatService from Command Prompt while the Battlefield 6 black window was still open.
The service reported:
SERVICE_NAME: EAAntiCheatService
TYPE: 10 WIN32_OWN_PROCESS
STATE: 4 RUNNING
WIN32_EXIT_CODE: 0 (0x0)
SERVICE_EXIT_CODE: 0 (0x0)
CHECKPOINT: 0x0
WAIT_HINT: 0x0
Therefore, EA Anti-Cheat appears to successfully reach the RUNNING state before Battlefield 6 eventually exits.
TROUBLESHOOTING ALREADY COMPLETED
- I have confirmed the BIOS is running in UEFI mode and Secure Boot is enabled.
- I have confirmed VBS/HVCI is running.
- I have rebooted the PC multiple times.
- I have run the EA app as Administrator.
- I have confirmed EA Background Service is running.
- I have confirmed EA Javelin/EA Anti-Cheat launches successfully.
- I have confirmed EAAntiCheatService reaches STATE 4 RUNNING with exit code 0 while BF6 is running.
- I have closed/disabled third-party applications and utilities.
- I have ensured AutoHotkey/macro-related applications are not running.
- I performed a Windows clean boot with all non-Microsoft services disabled. I manually enabled EABackgroundService so the EA app could launch and then tested BF6 in this clean-boot environment. The exact same issue occurred.
- I checked Windows Event Viewer. No corresponding BF6 application crash/error was recorded.
- I checked Windows Reliability Monitor. No Battlefield 6 failure was recorded when BF6 silently exited.
- I checked the Windows CrashDumps directory. No bf6.exe crash dump was generated.
- I also discovered that Windows Exploit Protection had a specific bf6.exe entry containing 23 system overrides. I removed the BF6-specific Exploit Protection profile, rebooted and tested again. This made no difference.
IMPORTANT DIAGNOSTIC BEHAVIOUR
- This does not appear to behave like a conventional application crash.
- Battlefield 6 successfully creates its window and remains running on a black screen for approximately 1–2 minutes.
- During this period, EAAntiCheatService is fully RUNNING and reports no service error.
- BF6 then appears to terminate silently.
- There is no BF6 error message.
- There is no EA/Javelin error code.
- There is no BSOD.
- There is no BF6 Event Viewer application crash.
- There is no BF6 Reliability Monitor crash.
- There is no bf6.exe crash dump.
- The EA app simply returns after BF6 disappears.
REQUEST FOR ASSISTANCE
Could this please be investigated as a potential Battlefield 6/Javelin compatibility or initialization issue?
I am particularly interested in whether there are known issues involving Windows 11 25H2 build 26200.x.
Could you also advise where I can obtain EA Javelin Anti-Cheat logs, Battlefield 6 launch logs or other diagnostic logs that may show why bf6.exe is being terminated?
If necessary, I would appreciate this case being escalated beyond the standard Secure Boot and clean-boot troubleshooting, as those steps have already been completed and the EA Anti-Cheat service has been verified as successfully reaching the RUNNING state during the failed launch.
Thank you.