|
Problem description: When I launch certain games like PUBG or Apex Legends, my computer reboots. No bluescreen, no minidump, even the Event Viewer gives me only EventID 41"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." with an EventID 161 "Dump file creation failed due to error during dump creation." just before it. Attempted fixes:
None of these things have changed it. I get why people would think GPU but my machine plays things like Destiny 2 Forsaken without issue. The PUBG crash is actually upon installing the Battleye client. The Apex Legends crash is upon first time start and I can't help but notice there's a "secured with Easycheat" or whatever. Could anti-cheat kernel driver/rootkits be causing this issue? Recent changes: This has plagued me since my build in the fall of 2018. Operating system: Windows 10 Pro Build 17763 (1809 Feature Update) System specs:
Location: United States I have Googled and read the FAQ: Yes I'm open to any suggestions at this point, I'm about to bow out of PC gaming otherwise. Hed fucked around with this message at 22:55 on Feb 23, 2019 |
# ? Feb 23, 2019 22:52 |
|
|
# ? May 2, 2024 21:48 |
|
After I turned on driver verification and tried my iGPU, I actually got a bluescreen and a minidump! Ran the crash dump through windbg and "easyanticheat.sys" was definitely the culprit. Really not sure why easy anticheat and the BattlEye installer are causing these issues. I suck too much to be using cheaters anyway.
|
# ? Feb 24, 2019 21:41 |
|
Got another crash trying to run PUBG, immediately after UAC escalation to install the BattlEye client for the first time. Luckily this produced another minidump:code:
Why the gently caress do the Easy Anti Cheat and BattlEye drivers crash my system? Ran memtest86 all last night, 0 errors. Time to flatten and reinstall?
|
# ? Feb 25, 2019 12:11 |
|
I finally wrote an error report with stack traces to BattlEye and EAC especially since the latter's stack trace absolutely indicted their driver going down a code path that it shouldn't have. Since no one cares about me liveblogging my troubleshooting I'll close the thread and play Destiny 2 or BF 5 or CoD 4 instead.
|
# ? Feb 26, 2019 12:19 |