I just bought Battlefield 6 and tried playing it. It has already CRASHED 8 TIMES, and it's not just the game crashing, MY ENTIRE PC CRASHES INTO A BSOD.
I've tried every single fix on the forums and nothing works. Please don't reply with generic troubleshooting steps like doing a clean driver install, secure boot, disabling XMP, etc. I've already tried all of them to no avail.
ERROR DETAILS:
- Stop-code: IRQL NOT LESS OR EQUAL(0xA)
- What failed: ntoskrnl . exe
I have seen TONS of other players with this exact same issue, all seemingly pointing to your garbage anti-cheat. It's making people refund the game because they literally can't play it.
Please fix this and give me an actual workaround so i can play. I spent my own money on this just to not be able to play LOL.
Specs:
Rtx 4070 ti super
Intel i7 14700kf
32gb of ram ddr 5
Install the latest drivers for your graphics card, network card, and motherboard chipset. Run the built-in Windows Memory Diagnostic tool from your start menu to test your memory chips. Repair System Files: Open Command Prompt as an administrator and run sfc /scannow followed by dism /online /cleanup-image /restorehealth.
My drivers, network card and motherboard chipset are up to date. The Windows Memory Diagnostic tool found zero errors, and I have also done SFC/DISM prompt within admin CMD multiple times and found zero errors.
My solution was for the Stop-code: IRQL NOT LESS OR EQUAL.
F4cepalm Thanks for letting me know. Was your IRQL_NOT_LESS_OR_EQUAL also consistently pointing to eaanticheat.sys in WinDbg, or was it caused by a different driver? If it was EA Anti-Cheat, I’d be really interested to know exactly what fixed it.
UPDATING DRIVERS DOES NOT FIX THIS..........stop trolling people. This issue is far deeper than a driver.
I agree. Stop telling people it is drivers causing the issue. Stop telling people it is their operating system. EA designed their anti cheat to operate in kernel and intercept all legitimate things on the system causing false positives and degrading performance. It is something that Microslop should have never allowed. I hope they remove kernel access in future versions of Windows.
