SOLVED!
I suddenly was unable to play BF5. I could still play BF2042 and other non-EA games just fine.
Was getting this Security Violation popup (after BFV splash image, sometimes after game window would show for a few seconds) with:
"EA AntiCheat Service encountered an error. Please restart the game. (114)".
I had very same issue for last week or two and was going crazy trying everything:
- latest Windows 10 updates (now on Version 10.0.19045 Build 19045)
- latest Nvidia drivers (now on GeForce 565.90 - released 10/01/2024)
- clear EA APP cache
- uninstall EA Anticheat (for all games)
- Repair BFV game
- re-install BF5 game
- ran Dism++ and other file/cache clearing tools
- disk/memory checks (all clear)
- setting EA anticheat exe file permissions
- and more
Nothing worked.
I think after upgrading the EA Anticheat to the latest version the BFV splash image started showing the error on the bottom/top of the splash image itself.
Then I started to see something a bit different in the Windows Event log - there wasn't much there before apart from EAAnticheatService crash text. But now I got:
"The following information was included with the event:
EAAntiCheatService
ExitType: 104 (asahci64.sys)
"
From that sys driver file clue I was able to find this info:
"asahci64.sys is part of Asmedia 106x SATA Host Controller Driver and developed by Asmedia Technology".
From looking at my motherboard specs, I could see I had a mix of Intel and AsMedia SATA ports. One of more of my HDD's might be plugged into one of those AsMedia ports.
I was going to try moving all my HDD drives to those Intel SATA ports in desperate hope that bypassing anything to do with that AsMedia driver.
BUT just before doing that I decided to see if taking the sys driver file out of action would maybe help my situation.
Warning: I was certain that my bootable Windows SSD was plugged into an Intel port, so I felt comfortable that it would not affect the Intel driver. I would not advocate messing with sys driver files without taking these things into consideration.
Anyway, that driver file was here: C:\Windows\System32\drivers\asahci64.sys
So I simply renamed it to: asahci64.sys.tmp
I fired up BFV and instantly for the first time in 2 weeks it roared back to life. Happy days.
I don't fully understand why EA Anticheat would crash with that only for BF5 but there you have it.
You may not have exact same issue, but maybe you might similar clues to get you over the line.
Good luck.
