FC 26 on PC causes BSOD: eaanticheat.sys KMODE_EXCEPTION_NOT_HANDLED (0x1E)

Hi EA_Barry, thanks for following up. Just to clarify - the DxDiag I sent already showed "No problems found" for Display, Sound, and Input, so I don't think DxDiag-based troubleshooting will find anything new here.

The actual issue is a kernel-level crash (BSOD) inside eaanticheat.sys itself, which I've documented in detail with WinDbg analysis across 4 separate crash dumps (including a fully controlled retest with all third-party software disabled). This isn't something DxDiag can diagnose or fix, since it's a bug in the anti-cheat driver's own code, not a graphics/sound/input driver issue.

Could someone from the Javelin Anticheat engineering team take a direct look at the minidumps and WinDbg output I provided? I'm happy to answer any technical questions or provide additional data if needed.

abedi51488​ 

Thanks for your efforts here. There is still a chance that we can resolve this with troubleshooting using the info in your Dxdiag file. Thank you. EA_Barry.

Update: minutes after my last crash, a DIFFERENT bugcheck occurred on the next launch - not a repeat of the previous "jmp rax" fault.

Bugcheck 0x50 (PAGE_FAULT_IN_NONPAGED_AREA). Fault originates from eaanticheat+0x519245 (different offset than before), which called nt!MmCopyMemory -> nt!MiCopySinglePage, then faulted reading an invalid memory address. Same driver build as all previous crashes (Timestamp Aug 7 2026). Dump: 082326-11343-01.dmp

This shows eaanticheat.sys has at least two separate bugs in this build: (1) an indirect jump through a bad pointer (my first 3 crashes), and (2) an unsafe memory copy from an invalid address, likely in the anti-cheat's memory-scanning code. This points to a broader stability issue in this driver build, not one isolated defect. Please pass this along too.

Update: I performed a fully controlled retest today. I completely uninstalled and freshly reinstalled EA Javelin Anticheat via its official installer, rebooted, and stopped every ASUS Armoury Crate service plus its kernel driver (AsIO3.sys) before testing - eliminating every variable I could think of.

The game launched successfully this time (past the point where it always crashed before) and I played Career mode for a bit. On the next launch, the exact same BSOD occurred again:

Bugcheck 0x1E, fault at eaanticheat+0x2a60f04 - the IDENTICAL offset as my first crash on Aug 15 - same instruction (jmp rax), same driver build (Timestamp Aug 7 2026). Dump: 082326-11203-01.dmp

This rules out any third-party software (Armoury Crate, AsIO3, etc.) as a factor. With every variable removed, the identical fault at the identical offset in eaanticheat.sys still happened - the bug is fully self-contained in the anticheat driver. Please escalate to engineering - happy to provide this new dump too.

Hi EA_Barry, thanks for the reply.

I already generated a full DxDiag report as part of this investigation (attached to my EA Help case #252887023). The relevant summary from it: "Display Tab 1: No problems found. Display Tab 2: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Input Tab: No problems found." So DxDiag itself confirms this isn't a graphics/sound/input driver issue.

Since posting it, I went further and ran a full WinDbg kernel debugger analysis on both minidumps (not just header inspection). Both crashes fault on the identical instruction pattern "jmp rax" (an indirect jump through a bad register value) inside eaanticheat.sys itself, from the exact same driver build (Timestamp: Fri Aug 7 21:42:31 2026). Full stack trace: nt!KeBugCheckEx <- nt!KiDispatchException <- nt!KiGeneralProtectionFault <- eaanticheat.sys.

I'm also a long-time FC customer (played FC 23/24/25 on this same PC with no issues) - this only started with FC 26's anticheat build.

Could this be escalated directly to the Javelin Anticheat engineering team? I can share the raw minidumps or full WinDbg output privately if useful.

abedi51488​ 

There is error reporting in a Dxdiag report that we can use to diagnose your specific issue. Please generate this report and post it here and we can take a look for you.

DXDIAG

Thank you. EA_Barry.