ANTICHEAT - CTD

Adding that the Motherboard bios is up to date (14900 intel cpu had issues when first released)

adding current report code MRPX-BMRLRLTV-BPDD  (not crashed yet - note this session doesnt have resize racoon running and game is windowed on one screen. i made those logs during this session

TITLE: F1 25 - EAAntiCheatService terminates repeatedly, game closes to desktop with no error

Platform: PC (Steam)

Report Code: *(paste the code from the Pause menu, bottom left, from a session that crashed)*

SUMMARY

F1 25 closes to desktop with no error message, repeatedly, 25 to 90 minutes into a session.

The game process itself never faults. Windows records no crash for F1_25.exe. What

terminates is EAAntiCheatService, and the game goes down with it. This happened ten

times in roughly fifteen hours.

WHAT WINDOWS RECORDS

Every occurrence produces one identical System log entry and nothing else:

The EAAntiCheatService service terminated unexpectedly.

Timestamps (24–25 August 2026):

11:38:54 · 12:05:23 · 13:29:53 · 13:53:34 · 16:19:14 · 17:10:52 · 17:11:40 · 17:27:11 · 01:27:33

No bugcheck. No WHEA event. No display driver timeout (no event 4101). No Code Integrity

block. The machine stays up; only the game disappears.

THE GAME PROCESS NEVER FAULTS

I configured WER LocalDumps for F1_25.exe pointing at C:\Dumps. The registry key was

verified as correctly registered. After ten crashes, C:\Dumps is empty. The game is

being terminated rather than crashing.

One earlier fault was recorded for the anti-cheat launcher itself:

Faulting application: EAAntiCheat.GameServiceLauncher.exe, version 1.0.64026.0

Faulting module name: unknown, version 0.0.0.0

Exception code: 0xc0000005

Fault offset: 0x00007ffd92332a9e

Bucket: PCH_88_FROM_unknown

The WER report for that fault lists only two non-Microsoft modules loaded in the process:

EAAntiCheat.GameServiceLauncher.exe and preloader_l.dll. Both are EA's own files.

Nothing third-party was injected into it.

WHAT I HAVE ALREADY ELIMINATED BY DIRECT TEST

Each of these was removed or disabled, and the crash still occurred:

- NVIDIA App overlay (processes killed, NvContainer service stopped)

- DisplayFusion (uninstalled)

- Resize Raccoon (closed; also tested on a single screen with it not running)

- AutoHotkey (removed)

- Triple-screen span (tested on a single 2560x1440 display)

- Second GPU, an NVIDIA T1000, disabled in Device Manager

- EA Anti-Cheat reinstalled twice via EAAntiCheat.Installer.exe

- F1 25 fully uninstalled and reinstalled from Steam (~81 GB)

- Windows Defender exclusions added for the game folder, C:\Program Files\EA\AC, and both

EAAC executables

- "Optimizations for windowed games" turned off

- Default high performance GPU forced to the RTX 5090

Platform state verified as normal: Secure Boot On, Kernel DMA Protection On,

WDAC usermode enforcement not enabled, mandatory ASLR not set, no second antivirus.

TWO CONTROLS THAT ISOLATE THIS TO THE ANTI-CHEAT

1. Another Codemasters title runs fine on the same machine. DiRT Rally 2.0 ran for

hours on the same PC, same three screens, same window tooling, same GPU load, with no

crash. Same engine lineage, no kernel anti-cheat.

2. A near-identical second PC runs F1 25 for 15 hours without a single failure. Same

game, same Resize Raccoon setup, same triple-screen span, at a higher resolution

(triple 4K vs triple 1440p). The differences are that this machine has a second GPU (a

T1000, which was disabled during testing and made no difference) and a 14900K rather than

a 14900KS.

SYSTEM

- Windows 11 Pro 10.0.26100

- ASUS ROG MAXIMUS Z790 DARK HERO, BIOS 2107 (28/11/2025)

- Intel Core i9-14900K

- 64 GB RAM

- NVIDIA GeForce RTX 5090, driver 32.0.16.1088 (22/07/2026)

- Secondary NVIDIA T1000 8GB (disabled during testing)

- Triple 2560x1440, played at 7680x1440

- Game on a separate drive: E:\SteamLibrary

No overclocking. No shader cache or driver tuning changes. Machine restarted many times

during testing.

ATTACHED

- dxdiag.txt

- hardwaresettings/ (hardware settings XMLs)

- F1_25.exe.*.running (renamed to .txt)

- EAAntiCheat-service-terminations.txt — the ten System log entries

- no-game-fault-evidence.txt — empty C:\Dumps plus the registry key proving capture was configured

- application-crash-records.txt

- eaac-versions.txt

- platform-state.txt

er605ay6v5n8​ 

Can you check if you have Windows Update KB5121003 installed? If so, please rollback/uninstall that update and then reboot and retry playing. Let us know if this has any effect please. Thank you. EA_Barry.

EA_Barry​ Hi Barry, thanks for the quick reply.

KB5121003 is not installed on this machine. I verified three separate ways:

• DISM /Online /Get-Packages /Format:Table returns no match for 5121003 (this reads the component store directly, so it catches cumulative updates that Get-HotFix and wmic qfe miss)
• The generated WindowsUpdate.log contains no reference to it
• It does not appear in Settings > Windows Update > Update history

For reference, OS build is 10.0.26100.7623, Windows 11 Pro. Happy to send the DISM package list if that would help confirm.

Update on the report code I posted earlier  MRPX-BMRLRLTV-BPDD . I said at the time that MRPX-BMRLRLTV-BPDD was from a session that hadn't crashed yet. It has since crashed, so that code is now tied to a failed session and should be usable for your telemetry. I was using resize racoon so triple screen.

Timeline for it:

• Launched approximately 01:45 on 25 August (from the F1_25.exe.18664.running file timestamp)
• Graphics settings saved in-game at 02:03:53 (applying resize racoon).
• EAAntiCheatService terminated at 02:20:22
• Roughly 35 minutes, in line with every other occurrence
• The PC itself stayed up throughout. I found it sitting at the Windows desktop this morning, no reboot, no bugcheck

One correction to my earlier comment: I described that  previouis session as single-screen windowed without Resize Raccoon. That is correct, and worth noting because it crashed in exactly the same way and on the same timescale as the triple-screen sessions with Raccoon running. The display configuration makes no difference to the failure.

That brings the total to ten terminations. Please add 02:20:22 on 25 August to the list in my original post.

Additional steps taken since I first posted, all of which the crashes survived:

• Fully uninstalled and reinstalled F1 25 from Steam (~81 GB, fresh download)
• Reinstalled EA Anti-Cheat a second time via EAAntiCheat.Installer.exe
• Disabled the secondary NVIDIA T1000 in Device Manager
• Forced the default high-performance GPU to the RTX 5090 in Windows graphics settings
• Turned off "Optimizations for windowed games"

The 01:27:33 and 02:20:22 crashes both occurred after all of the above, on a completely fresh game install.

At this point every third-party component, the display configuration, the second GPU, and the game files themselves have been eliminated by direct test. Let me know what else would be useful and I'll run it.

One thing from Update history that may be relevant: on 26/05/2026 Windows Update installed two NVIDIA display drivers (32.0.15.7688 and 30.0.14.7247), and both also show failed install attempts the same day with error 0x80240016. There is additionally an Intel display driver from 23/01/2026 for the iGPU. So this machine has had three graphics driver stacks present, with a history of failed driver installs. The current NVIDIA driver is 32.0.16.1088 dated 22/07/2026, installed manually CLEAN INSTALL with no errors.

while waiting for your reply i just ticked these 2 boxes in AC installer, updated then same boxes tickec on anticheat launcher exe, gave it a go (with and without F1 exe with same boxes ticked). It made things worse i felt CTD would arrive sooner with ACL on admin but it could be random. At this time, i dont know what to do (Im happy to run some powershell commands on the working computer that has almost the same config, again there is that second gpu on this PC (actually there are 3  5090, T1000 then the onboard intel gpu and i disabled the T1000 in device manager, not intel on board gpu) 

er605ay6v5n8​ 

Thanks for the detailed info. If you feel confident in your abilities, it may be worthwhile to check for a BIOS and/or chipset update. A newly generated Dxdiag may also be useful here.

DXDIAG

EA_Barry.

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.

EA_Barry​ 

Hi Barry,

Quick but important update.

I followed your BIOS/chipset suggestion and went further by performing a complete clean Windows reinstall.

Current test configuration:

ASUS ROG MAXIMUS Z790 DARK HERO

BIOS 2202

Current Intel chipset, ME, Serial IO and Thunderbolt drivers

Windows 11 Pro 25H2 build 26200.9168

Secure Boot enabled

Fresh NVIDIA driver environment

F1 25 verified/repaired through Steam after the clean Windows installation

64 GB DDR5, 2x32 GB in A2/B2, XMP I at 6400

No Resize Raccoon

No iCUE, MSI Afterburner, NVIDIA App, Discord or other usual background utilities

Unfortunately, the original failure reproduced again on the completely fresh Windows installation.

Failed session report code:

DRZV-SLCP-GBSM-2KJD

F1 started at approximately 02:08:52 and CTD occurred at 02:32:58, roughly 24 minutes later. This is the second occurrence of the CTD since the clean Windows installation.

A new EA AntiCheat dump was generated at the exact crash time:

PACKER_1578500_16948.dmp

The dump shows the same recurring GameService signature as before:

eaanticheat.gameservice.exe

Exception 0xC0000005

READ access violation

Attempted address 0xFFFFFFFFFFFFFFFF

Same relative fault offset: +0x09F88800

So this appears to be the same deterministic EA AntiCheat GameService failure that occurred before the Windows reinstall.

Regarding KB5121003: it was not installed when the original crashes began. I later installed it on the previous Windows installation specifically as a test, and the same EAAC crash still occurred, so installing KB5121003 did not change the behaviour.

I am attaching a fresh diagnostic ZIP containing the new DxDiag, system and driver information and relevant logs, together with PACKER_1578500_16948.dmp from this failed session.

One other observation may be worth mentioning. During testing I temporarily removed one of the two 32 GB RAM modules and tested different RAM and BIOS configurations. At one point EA Javelin AntiCheat repeatedly failed even to start. F1 25 started loading normally again after I restored both original 32 GB DIMMs to A2/B2 and restored XMP I at 6400.

I do not know whether that behaviour is relevant, so I do not want to draw conclusions from it, but I thought it was worth reporting.

Other demanding applications remain stable. MSFS 2024, DiRT Rally 2.0 and GPU-heavy workloads can run for hours without reproducing the F1 behaviour.

I have a sim-racing event from Friday to Saturday and one of the stations is currently unusable for F1 25. I have spent considerably more time troubleshooting this than I expected and I am now running out of useful things to test.

The strongest finding so far is that a BIOS update, current chipset drivers and a complete Windows wipe/reinstall did not eliminate the original EA AntiCheat GameService crash.

If the AntiCheat/game team wants a specific trace, dump or diagnostic capture, I am happy to run it.

Thanks for your help.

EA_Barry​ 

Hi Barry,

Quick but important update.

I followed your BIOS/chipset suggestion and went further by performing a complete clean Windows reinstall.

Current test configuration:

ASUS ROG MAXIMUS Z790 DARK HERO

BIOS 2202

Current Intel chipset, ME, Serial IO and Thunderbolt drivers

Windows 11 Pro 25H2 build 26200.9168

Secure Boot enabled

Fresh NVIDIA driver environment

F1 25 verified/repaired through Steam after the clean Windows installation

64 GB DDR5, 2x32 GB in A2/B2, XMP I at 6400

No Resize Raccoon

No iCUE, MSI Afterburner, NVIDIA App, Discord or other usual background utilities

Unfortunately, the original failure reproduced again on the completely fresh Windows installation.

Failed session report code:

DRZV-SLCP-GBSM-2KJD

F1 started at approximately 02:08:52 and CTD occurred at 02:32:58, roughly 24 minutes later. This is the second occurrence of the CTD since the clean Windows installation.

A new EA AntiCheat dump was generated at the exact crash time:

PACKER_1578500_16948.dmp

The dump shows the same recurring GameService signature as before:

eaanticheat.gameservice.exe

Exception 0xC0000005

READ access violation

Attempted address 0xFFFFFFFFFFFFFFFF

Same relative fault offset: +0x09F88800

So this appears to be the same deterministic EA AntiCheat GameService failure that occurred before the Windows reinstall.

Regarding KB5121003: it was not installed when the original crashes began. I later installed it on the previous Windows installation specifically as a test, and the same EAAC crash still occurred, so installing KB5121003 did not change the behaviour.

I am attaching a fresh diagnostic ZIP containing the new DxDiag, system and driver information and relevant logs, together with PACKER_1578500_16948.dmp from this failed session.

One other observation may be worth mentioning. During testing I temporarily removed one of the two 32 GB RAM modules and tested different RAM and BIOS configurations. At one point EA Javelin AntiCheat repeatedly failed even to start. F1 25 started loading normally again after I restored both original 32 GB DIMMs to A2/B2 and restored XMP I at 6400.

I do not know whether that behaviour is relevant, so I do not want to draw conclusions from it, but I thought it was worth reporting.

Other demanding applications remain stable. MSFS 2024, DiRT Rally 2.0 and GPU-heavy workloads can run for hours without reproducing the F1 behaviour.

I have a sim-racing event from Friday to Saturday and one of the stations is currently unusable for F1 25. I have spent considerably more time troubleshooting this than I expected and I am now running out of useful things to test.

The strongest finding so far is that a BIOS update, current chipset drivers and a complete Windows wipe/reinstall did not eliminate the original EA AntiCheat GameService crash.

If the AntiCheat/game team wants a specific trace, dump or diagnostic capture, I am happy to run it.

Thanks for your help.