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.
Community ManagerThanks 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.
