Simple Anti-Cheat BSOD solutions
Simple Anti-Cheat BSOD solutions
This morning I opened the game Crossout, after about 20 seconds I got a "kernel mode heap corruption" BSOD. Restarted, opened the game again, this time a "cache manager" BSOD. Tried some other games and Furmark, no issue there. Updated my GPU drivers, still happens but only on this one game. Used the verify integrity button on Steam and aforementioned issue still occured. My RAM is fine, GPU is probably fine, Windows isn't corrupted, no devices have the exclaimation mark next to them in Device Manager. Doesn't happen with this game on my laptop. Any clues what could be going on here? Specs: Xeon E5-2690, EVGA GTX 980 SC, 32gb DDR3 ECC, game is loaded from 1tb Hynix SATA SSD on port 2 (AHCI)
It's a strange BSOD alert! The message suggests an issue with the kernel handling. It might be related to Easy Anti-Cheat, and you could test other games that don't trigger it.
Open the event viewer and navigate to Windows logs under system. You’ll find more details about the BSOD. It might show crashes that trigger the error. Also, check the application logs within the event viewer.
The request has been clarified. I will remove any filtering to provide a more comprehensive response.
Someone mentioned restarting after a bug check. It seems unclear from the context, as I was opening Fortnite while checking the event viewer and it crashed again. Likely related to anti-cheat issues. Found a suggestion online about removing easyanticheat.sys, which I plan to try.
Removing easyanticheat.sys from C:\program files (x86)/EasyAntiCheat didn't resolve the issue but extended the crash by another ten seconds. It's unclear what to do next. The EasyAntiCheat app has been deleted, and a reinstallation might be considered.
I fixed it by updating the GPU drivers, reinstalling Visual Studio, removing all EasyAntiCheat files from game and Windows folders, and repairing each game from its launcher. It stopped crashing in Fortnite now. Still puzzling why it worked last night, but Windows seems to be handling it. Crossout is functioning properly!
I've faced the same issue since June. My memory issues keep reporting Easyanticheat.sys. In June I waited two days, tried Crossout again and played smoothly until last Friday (August 5th), which made me suspect it wasn't my machine. Meanwhile, BSODs with EasyAntiCheat have started again. I'm planning to wait a few days and try once more; it seems some updates to EasyAntiCheat cause the crashes, as others report. From what I've seen online, this problem appears only with EasyAntiCheat and isn't linked to Crossout. Have you been playing Crossout since June 20th without any further BSODs?