New bugs in 2026
After renewing my EA Play subscription, I returned to Battlefield 2042, but since then, I haven't been able to enter a single 2042 session. Every time I try, my network card crashes. I've tried updating my network card driver, motherboard BIOS, clearing the cache, updating and fixing anti-cheat measures, updating my NVIDIA graphics card driver, and using my phone's hotspot, but without exception, I get the same error message. I'm starting to believe that DICE is trying to drive players to Battlefield 6, but this will only drive players away. My IP address is in the US, so I'm sure it's not a VPN issue.
Help Needed (Error code: 1:4688822970: -4685921B) for BF2042
I consistently receive the following error code about five minutes into gameplay: 1:4688822970: -4685921B. I'm running a dual-boot system with Windows 10 (22H2) and Ubuntu. I've already tried switching DNS servers, reinstalling the anticheat software, reinstalling the game, enabled secure boot, and disabling background applications, but the issue persists. Any suggestions would be appreciated.
Do your job.
fix the matchmaking *snip*. fix the cheat *snip* with javelin is juvenile against make the game playable for full xo without without "official" breakthrough or conquest. Portal exists ands theres bots either way so whats the point? its an insult to have a conquest mode dedicated to less vehicles and more ground soldiers over a similar mode for breakthrough. Breakthrough chaos features maybe 4-5 maps played over and over that only had heavy vehicles. Ruined the whole thing. Look at the numbers. prior to discontinuing Chaos, most went back to regular breakthrough because there were more maps, some that included NO vehicles. The fact Dice doesnt understand how vehicles ruins some gameplay, such as rams against poorly balanced teams, tells me all I need to know about how much the people who make, produce and develop the game... actually play the game. also no game invokes an Nvidiacontainer error that crashes the game for Device Hung. Literally no other game, meaning no other platform. Its only EA games. Fishy how Chat GPT, Google AI and many typical sources blame NVidia FrameView,, Nvidia Drivers, and Windows despite every single error associated with those names sources way back to EA if you use the data provided by event viewer. The clear source of all these errors across many games is EA. UN-**snip*_Deniable. (CM: Edited to remove profanity. Please keep our forum rules in mind when engaging on the forums)1.ExitType 111 Invalid Image Hash 2. Failed to obtain Origin directory
Battlefield 2042 does not launch on PC due to EA AntiCheat kernel driver failing to load. The game shows the splash screen, EA AntiCheat service starts briefly, then crashes and stops. Windows Event Viewer reports: - EAAntiCheatService ExitType: 111 - Service Control Manager Event ID 7023 - STATUS_INVALID_IMAGE_HASH (%%4294901871) This is NOT a standard configuration issue. Secure Boot, TPM/fTPM, SVM, VBS, Core Isolation and Hyper-V have all been tested ON and OFF. Windows 11 is clean installed, BIOS and all drivers are up to date. Hardware: - AMD Ryzen 9 9600X (Zen 5) - Gigabyte B850M AORUS ELITE WIFI6E ICE (BIOS F7) - 64 GB DDR5 - RTX 2070 Super This appears to be an EA AntiCheat driver signature / Secure Boot CA compatibility issue. Please escalate this case to the EA AntiCheat engineering team. Before the EA AntiCheat service crashes with ExitType 111, the following error is logged: "EAAntiCheatService – Failed to obtain Origin directory" This happens during game launch while the splash screen is visible. The EA AntiCheat service starts, then immediately stops. EA App is installed cleanly in the default directory: C:\Program Files\Electronic Arts\EA Desktop\ Origin is not installed and no Origin registry entries remain. This indicates EA AntiCheat is failing to correctly detect the EA App installation path before the kernel driver load phase.
EAAntiCheatGameService being detected as a threat..... again.
Windows Defender detecting EAAntiCheatGameService creating a .tmp file that is considered a threat, again.... although it is being detected as winring0 now and not whatever it was before. I know this is now probably going to be fixed with an EA Anticheat update but still..... annoying.
