Ten EAAntiCheatService terminations on 24-25 August: 11:38, 12:05, 13:29, 13:53, 16:19, 17:10, 17:11, 17:27, and 01:27 F1_25.exe never records a fault. WER LocalDumps was configured for it and C:\D...
Ideas
ANTICHEAT - CTD
er605ay6v5n8
2 months agoNew Spectator
EA_Barry Hi Barry,
Before I change BIOS/chipset components, I wanted to give you an important update because I have now captured the actual failure with Windows Performance Recorder and found EA AntiCheat's own crash dumps.
The failure sequence is now confirmed:
EAAntiCheat.GameService.dll exits first, with status 0x00000000.
About 0.8 ms later, eaanticheat.gameservice.exe exits with status 0x0000DEAD.
About 1.28 seconds later, F1_25.exe exits with status 0xE0AC0001.
Service Control Manager then records:
"The EAAntiCheatService service terminated unexpectedly."
So F1 itself is not crashing first. The anti-cheat fails first and F1 is then terminated as a consequence.
I also discovered that EAAC has been generating its own crash dumps in:
C:\ProgramData\eaanticheat\Crashdumps
I have 8 EAAC dumps from separate failures.
Analysis of all 8 shows the same pattern:
Exception: 0xC0000005 (access violation)
Fault inside eaanticheat.gameservice.exe
Same relative fault offset on every run: +0x09F88800
Invalid read address: 0xFFFFFFFFFFFFFFFF
Because ASLR changes the module base on each launch but the relative fault offset is identical across all 8 crashes, this appears highly repeatable rather than random hardware instability.
One potentially important lead has also emerged.
Process Lasso / ProcessGovernor was installed on the failing PC.
It is NOT installed on the second near-identical PC which can run F1 25 for 15+ hours without a failure.
Process Lasso has now been completely uninstalled and both ProcessLasso.exe and ProcessGovernor.exe are confirmed absent.
I have also uninstalled TeamViewer because its hook process was active in the WPR trace.
I am rebooting now before retesting, so that neither Process Lasso nor TeamViewer has any remaining process/service/component loaded.
I therefore plan to do one controlled post-reboot F1 test BEFORE changing BIOS/chipset, with everything else unchanged.
If EAAC still crashes, I will then proceed with your chipset/DxDiag suggestion.
For reference, the motherboard BIOS is ASUS ROG MAXIMUS Z790 DARK HERO BIOS 2107 dated 28/11/025, which I had already checked as current when I opened the report.
If useful to the EA/Javelin team, I can provide:
EAAC PACKER_*.dmp files
The WPR/ETL trace
The exact process termination timeline
A newly generated DxDiag
The EAAC dumps may be particularly useful because they reproduce the same access violation at the same relative code offset on every failure.
One additional point which may be significant: Process Lasso is not installed on the known-good near-identical PC, so this gives us a concrete software difference between the two machines.
I'll report back after the clean post-reboot test.
Thanks.