FC 25 launch BSOD in eaanticheat.sys: same +0x18905d9 crash as FC 26 report
EA SPORTS FC 25 on Steam now causes a reproducible Windows blue screen on two PCs that used the game successfully for about a year. Both show SYSTEM_SERVICE_EXCEPTION (0x3B) naming eaanticheat.sys. The failures began at roughly the same time.
On one PC I analyzed four minidumps (10 and 15 September 2026) with WinDbg. All four show exception 0xC0000005 at eaanticheat.sys+0x18905d9 and failure hash {ba758836-7880-e66a-acd0-8452c9260e6f}. The driver image in the dumps is timestamped 31 August 2026. The faulting instruction reads address 0x30 from r14=0x28.
I preserved the modded game folders as backups, restored original Data and Patch folders, verified all 54.6 GB of game files through Steam, and Steam replaced one failed file. The active installation had no mod markers or mods.txt and no Steam launch options. I also reinstalled EA Javelin anticheat and stopped MSI Afterburner, RivaTuner, and RTCore64. The next FC 25 launch still produced the identical BSOD. I will not repeat the launch until a meaningful change is available because each test forces a Windows restart.
This FC 26 report shows exactly the same driver offset, instruction, and failure hash on different hardware after an anticheat reinstall and clean boot:
https://forums.ea.com/discussions/fc-26-technical-issues-en/reproducible-bsod-caused-by-eaanticheat-sys-%E2%80%93-system-service-exception-0x3b/13702508
EA_Barry, could you pass this additional FC 25 cross-title reproduction to the EA Javelin engineering team and advise whether a supported driver fix or safe workaround is available? I can provide the raw minidumps and WinDbg output privately on request.
