Battlefield 6 - Repeated BSODs caused by EA Anti-Cheat (Intel i7-14700K)
Hi everyone,
I'm posting this in the hope that EA can investigate this issue, as I've spent days troubleshooting and have ruled out many common causes.
System Specifications:
CPU: Intel Core i7-14700K
GPU: Sapphire Nitro+ Radeon RX 7800 XT
Motherboard: ASUS TUF Gaming B760M-PLUS WIFI II
RAM: 32GB Corsair DDR5 5600MHz
Storage: Windows on C: drive, Battlefield 6 on a separate NVMe SSD (D: drive)
PSU: Gigabyte UD850W (850W)
Cooler: Corsair Titan 360 RX AIO
Windows 11 (fully updated)
Latest AMD GPU drivers
Latest motherboard BIOS
The Issue:
Around 28th-30th July, Battlefield 6 suddenly started crashing my entire PC with Blue Screens of Death. Before then, the game had been working normally. Nothing changed with my hardware or BIOS configuration immediately before the issue began, yet the crashes started completely out of nowhere.
This is not a normal game crash—it completely crashes Windows and forces the PC to reboot.
The crashes are inconsistent. On some occasions I can play a full match before the system blue screens, while on others the PC crashes within 5–10 minutes and even when I'm idling in the menu. I have not found any consistent action or point in the match that triggers the crash.
I also tested today's Battlefield 6 update as soon as it became available, but it did not resolve the issue. The game continues to trigger the same BSODs on my system.
Crash Analysis:
I've analysed multiple minidumps using WinDbg.
Every dump consistently points to:
IMAGE_NAME: eaanticheat.sys
FAILURE_BUCKET_ID: AV_eaanticheat!unknown_function
SYMBOL_NAME: eaanticheat+4b480f3
Every crash dump I've analysed points back to the EA Anti-Cheat kernel driver, with the stack trace consistently ending inside eaanticheat.sys.
Troubleshooting Already Performed
Over the last several days I have tried:
Completely uninstalling and reinstalling EA Anti-Cheat.
Repairing EA Anti-Cheat multiple times.
Running the EA Anti-Cheat installer and launcher as Administrator.
Verifying the Battlefield 6 game files.
Updating Windows.
Updating my motherboard BIOS.
Updated Intel Chipset Driver, Intel Management Engine Interface and Intel Serial IO.
Updating to the latest AMD graphics drivers.
Using DDU (Display Driver Uninstaller) to completely remove my GPU drivers before installing the latest AMD driver.
Testing with XMP both enabled and disabled (the PC still crashes after roughly 10-20 minutes either way).
Disabling third-party antivirus.
Adding Battlefield and EA Anti-Cheat to Windows Exploit Protection exclusions.
Disabling as many third-party kernel-level applications and background software as possible.
Restarting between troubleshooting attempts.
Performed CPU and RAM stability testing (including OCCT) to check for hardware instability. Those tests did not reproduce the Battlefield 6 BSODs, suggesting the crashes are specific to Battlefield 6 and/or EA Anti-Cheat rather than occurring under general system load.
One interesting thing happened after repairing EA Anti-Cheat. The game crashed to desktop instead of blue screening my PC, and I managed to finish a full match beforehand. I initially thought this had resolved the issue, but after repeating the exact same repair process, the crashes returned and my entire PC blue screened again.
I have also tested Battlefield 1 on the same system without any crashes, BSODs or unexpected reboots, suggesting the issue is specific to Battlefield 6 rather than gaming in general.
Request:
Has anyone with a similar system, particularly an Intel 13th or 14th generation CPU, experienced this?
If anyone from EA is reading this, could this please be investigated? Multiple crash dumps consistently identify eaanticheat.sys, and despite extensive troubleshooting the issue persists. A game crashing is frustrating enough, but software causing repeated kernel-level BSODs is a much more serious problem.
At this point, I feel I've exhausted the troubleshooting that can reasonably be performed on my end, which is why I'm raising this in the hope that EA can investigate it further.
I'm happy to provide crash dumps, WinDbg output, Event Viewer logs, or any additional diagnostic information if it helps identify the cause.
