Forum Discussion

Balazs57's avatar
Balazs57
Seasoned Novice
23 days ago
Solved

EA Javelin AntiCheat repeatedly crashes with identical NX fault / 0xC0000005

College Football 27 repeatedly fails to launch because EA Javelin AntiCheat itself crashes. I have reproduced the issue multiple times and analyzed multiple EA AntiCheat crash dumps with WinDbg. Dum...
  • Balazs57's avatar
    22 days ago

    I think I may have finally found a workaround, although I don't want to call this a confirmed permanent fix yet. As you know, my original problem was a recurring crash of eaanticheat.gameservice.exe (Javelin) while launching College Football 27. The crash dumps consistently showed 0xc0000005 / SOFTWARE\_NX\_FAULT.

    After a lot of troubleshooting, this is what appears to have changed the behaviour:

    1.) Open Registry Editor (regedit).
    2.)Navigate to:

    HKEY\_CURRENT\_USER\Software\EA\AC

    3.) Export the entire AC key first so you have a backup. Do not skip this because later you need it.
    4.) Delete the AC key.
    5.) Launch the game.

    In my case, this did not immediately fix the problem. Instead, the behaviour changed: the game got past the point where Javelin normally crashed and reached the main menu, but then CollegeFB27.exe itself crashed. I then restored the EA\AC registry key from the backup I had just made. I launched the game again — without even rebooting Windows — and it worked.

     Since restoring the key, I have successfully launched the game four times in a row, including two successful launches after a full Windows restart. 1 or 2 hours later seems work. The EA App was also running during the post-reboot tests, so simply having the EA App open does not appear to be the cause.

    So, strangely, the sequence that currently appears to have helped was: Back up HKCU\Software\EA\AC → delete it → launch the game → restore the original key → launch again. I don't yet know why this changed anything. It may have forced EA AntiCheat/Javelin to regenerate or resynchronise some per-user/session state, that's only my hypothesis. I also tested removing Windows update KB5121003 earlier, and that did not fix the original problem, so I currently don't believe that update was the cause in my case.

    I recommend to make a registry backup before trying this. I'll update this again if the problem returns. For now, though, this is the first time I've had repeated successful launches, including across some reboot and shutdown.