Forum Discussion
24 Replies
- OCTunel23 days agoNewcomer
I had the same issue.
- EA_Shepard3 days ago
Community Manager
electronicpunk Hey, that is great! Thank you for letting us know on this one. Helps out a lot when the community lets us know it does work with these updates!
Appreciate it.
- electronicpunk4 days agoRising Novice
My game got an update today so gave it a go and noticed it downloading an update.
Low and behold - the game is now working with build 26300.9539
- EA_Shepard6 days ago
Community Manager
Hey, folks
Thank you to everyone who has replied to this one. We have seen other reports from the community and have passed the information over to the team.
We have put up a cool new sticky for this one here: [BFComms] Windows Insider Build is not currently working with EA Javelin
It has some cool info in it to help with this one. Once we get more updates, we will update y'all.
Hope these steps work for you and you get back on the Battlefield! - Tibo_GER7 days agoNewcomer
I am experiencing the exact same EAAntiCheatService error.
Service Control Manager, Event ID 7023
EAAntiCheatService terminated with error: %%4294944373Battlefield 6 crashes to desktop without a useful in-game error. The EA Javelin AntiCheat Application log also consistently produces Event ID 1000 with:
ExitType: 0xD9F6F9654DDA8675 (0xE7726BD6414F02C6)
I have already performed extensive troubleshooting.
Verified Battlefield 6 through Steam. Three corrupted files were found and reacquired.
Completely reinstalled EA Javelin AntiCheat.
Cleared the Battlefield 6 shader cache.
TPM 2.0 is enabled and ready.
Secure Boot is enabled and the system boots in UEFI mode.
DISM /RestoreHealth completed successfully.
SFC found corrupted Windows files and successfully repaired them.
Tested with Razer services and processes disabled.
Tested with TAP-Windows and TeamViewer VPN adapters disabled.
No permanent "Run as administrator" compatibility flags are enabled on BF6, Steam or EA App.
No CPU overclock is configured. CPU settings are on Auto.
No XMP or memory overclock is configured. DDR4 is currently running at 2133 MHz.
Updated ASUS PRIME Z370-A BIOS from version 2201 from 2019 to version 3005, including newer platform firmware and CPU microcode.
TPM 2.0 and Secure Boot were verified again after the BIOS update.Hardware:
Intel Core i7-9700K
ASUS PRIME Z370-A
NVIDIA GeForce RTX 3070 Ti
32 GB DDR4
Windows 11 Pro, build 26300.9539None of these steps resolved the issue. The same Javelin / EA AntiCheat crash still occurs.
Since the EAAntiCheatService itself is consistently terminating and another user is reporting the identical %%4294944373 error, could this please be escalated to the Javelin / AntiCheat team?
I can provide additional Event Viewer logs, DxDiag or MSInfo if required.
- EA_Kuba7 days ago
Community Manager
Thanks everyone for the additional reports.
I'm seeing several of you describe a very similar pattern.
There's also an interesting common point from rdrck around the recent Windows update KB5124010.
If you're experiencing this issue, could you please check Settings > Windows Update > Update history and let us know:
- Whether KB5124010 is installed
- Your Windows version/build
- Whether the crash started only after that update was installed
- If you've already removed KB5124010, whether Battlefield 6 started working again afterwards
- AyeurA7 days agoSeasoned Newcomer
Hi RGR, go to Windows Update, then Update history, then Uninstall updates, scroll to the bottom, then Uninstall, then reboot.
- RGR_Gaming10X7 days agoNew Adventurer
I removed 26H2 and it went back to 25H2 and is still doing it during shader recomp. I try to remove KB5124010 with command prompt and it says it won't let me because my PC needs it. AyeurA
- rdrck8 days agoRising Newcomer
Hope this works for you. In my case I noticed the same day that this occurred (EA Javelin anticheat closes the game after around 10 seconds) I did noticed the windows KB5124010 was installed, after uninstalling this KB I was able to play.
- Nobiliore9 days agoNew Novice
Thank you so much; the problem is resolved for now.