ANTICHEAT - CTD

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.