Repeated kernel crash/reboot caused by eaanticheat.sys - confirmed via WinDbg
Battlefield 6 is repeatedly causing my PC to black-screen and hard-reboot during gameplay, with no crash-to-desktop and no visible BSOD text. I've analyzed all three crash dumps in WinDbg and confirmed the fault originates inside eaanticheat.sys, at the same exact offset every time.
**Summary of crashes:**
1st crash - Bugcheck 0xA (IRQL_NOT_LESS_OR_EQUAL), main menu after ~1 hour of play
2nd crash - Bugcheck 0xA (IRQL_NOT_LESS_OR_EQUAL), main menu after ~1 hour of play
3rd crash - Bugcheck 0x1E (KMODE_EXCEPTION_NOT_HANDLED), ~10 minutes into a match
All three share the identical symbol/offset and failure hash:
```
SYMBOL_NAME: eaanticheat+4b480f3
MODULE_NAME: eaanticheat
IMAGE_NAME: eaanticheat.sys
FAILURE_BUCKET_ID: AV_eaanticheat!unknown_function
Failure.Hash: {d544cf09-4735-e698-77c3-5df5924e5448}
PROCESS_NAME: bf6.exe
```
**Troubleshooting already completed (no change in outcome):**
- SFC /scannow - found and repaired corrupt files, re-ran clean afterward
- DISM /RestoreHealth - completed successfully
- Ran the EasyAntiCheat repair tool from the game's install folder
- Confirmed Secure Boot is enabled
- Enabled Virtualization-Based Security / Memory Integrity (had to first remove an unrelated incompatible legacy driver to allow this)
- Rolled back my NVIDIA driver from 610.88 (the version originally installed when crashes started) to 610.74, hoping it was driver-related - crash persisted identically, ruling out this specific GPU driver version as the cause
- Windows fully up to date
Despite all of the above, the crash recurs at the same driver offset every session.
**System specs:**
- OS: Windows 11 (build 26100)
- CPU: Intel Core i7-13700K
- GPU: NVIDIA GeForce RTX 4080 Super, driver version 610.74
- RAM: Corsair Vengeance DDR5 (2x16GB), 6000 MHz
**Attached:**
- BF6_crash_dumps.zip (contains all three .dmp files: 080226-8921-01.dmp, 080226-9546-01.dmp, 080226-14765-01.dmp)
Happy to provide any further logs or run additional diagnostics if it helps get this resolved. This appears to match other reports of the same `eaanticheat+4b480f3` crash signature on this forum - please escalate to the anti-cheat engineering team if possible.
