I made an adjustment to my OC on my PC and played 7 hours without a single crash.
Current Rig:
i7-8700K
MSI GTX 1080
32GB G.Skill RAM
I’ve ran a fixed overclock @ 5GHz since I built the machine. I’ve never had an issue with any other games crashing including Apex Legends, until their most recent two patches. Since I could barely play the game cause I’d crash every other game, I changed my BIOS back to default settings. I set a fixed overclock @ 4.4GHz with EIST and Turbo Boost disabled. I left everything else at stock settings. I have yet to crash and have played roughly 7-8 hours. Clearly something in the newer patches is triggering the crash when the CPU is overclocked pretty high even if it’s a stable overclock. My gaming rig is cooled very well and @ 5GHz it would top out around 65c when under heavy load. Never had issues with anything (software, hardware, games, etc) until Apex Legends and the newest two patches. I run a 240Hz monitor so the drop in overclock has dropped my frame rate by a noticeable amount. In the jump ship I’d average roughly 140-150fps, I now average 95-115fps. Nothing earth shattering, but sucks that the game is having issues with high clocks. I used to run close to 240fps throughout most of the areas in the game, but now I range anywhere from 160-240fps depending on the area. Again I’d rather lose the frame rate then crash every other game. Haven’t taken the time to mess with the overclock and see if I could bump it up more, might just leave it since I have yet to crash. Hope a fix/solution is found so we can all run our higher clocks without crashes. Hope this helps some of you out. If anything changes or a crash happens I will be sure to post an update.
Fellas, this is your OVERCLOCK. Revert to factory and your problem will be solved. This has worked for 3 different people who I play with who have had similar issues. I have a 9900k that was clocked at 5.0. Crashed randomly since the release. Reverted back to stock 3.6, played 6 hours with no crash. There's something screwy with overclocking. I am a IT Engineer myself, and I cannot understand how voltage levels by itself can crash a game. It could be, in my opinon that this game prefers lower clock speeds. I've had 3 different software engineers look at my rig for a solution, none suggested it was an overclock issue.
There is nothing more frustrating than fixing IT issues for a living and having an issue you can't solve on your PC. If there is someone above my expertise that can explain this, I'd love to learn. Thanks!!
Removed the overclock on my cpu and haven't crashed since. Its the overclock guys. I have an i3-8350K oc to 4.8 and i reverted it back to base clock.
@McQuak wrote:Fellas, this is your OVERCLOCK. Revert to factory and your problem will be solved. This has worked for 3 different people who I play with who have had similar issues. I have a 9900k that was clocked at 5.0. Crashed randomly since the release. Reverted back to stock 3.6, played 6 hours with no crash. There's something screwy with overclocking. I am a IT Engineer myself, and I cannot understand how voltage levels by itself can crash a game. It could be, in my opinon that this game prefers lower clock speeds. I've had 3 different software engineers look at my rig for a solution, none suggested it was an overclock issue.
There is nothing more frustrating than fixing IT issues for a living and having an issue you can't solve on your PC. If there is someone above my expertise that can explain this, I'd love to learn. Thanks!!It's the AVX instructions the game is using, most probably. Just for the record - I play on 5.1Ghz Metro Exodus + BFV and I have never crashed. Apex is the only game that it's handling avx instructions that bad.
2019 will be the year of buggy games - Apex has problems with drivers + cpu avx instructions, battlefield V still has a problem with DXR enabled... hilarious how EA is pushing the teams to launch a game that it's not yet ready and then trying to fix it after the launch.
@_S7ORM-BRINGR The game isn't using AVX instructions. Ohiostorm (the programmer) said that it uses SSE2 instructions. AVX instructions don't cause this type of error. The game is generating "CPU Internal Parity Errors" (WHEA correctable) when overclocked and voltage isn't high enough. The correctable errors aren't making the game crash. It's the -uncorrectable- error that crashes the game (or the error that doesn't get caught).
I've been unable to make any other stress test or program generate an "Internal parity error". It either BSOD's (clock watchdog timeout--meaning an actual core froze, system service exception, iRQ_L not less or equal, etc) at unstable voltage settings, or generates a "CPU Cache L0 error" (high stress programs/prime95/realbench 2.56) when temps get too high if voltage isn't high enough. Never, ever an "internal parity error" on a core. Even prime95 with AVX disabled (uses SSE2) doesn't do that.
We also don't know if easyanticheat is affecting or causing it somehow as well.
@Falkentyne wrote:@_S7ORM-BRINGR The game isn't using AVX instructions. Ohiostorm (the programmer) said that it uses SSE2 instructions. AVX instructions don't cause this type of error. The game is generating "CPU Internal Parity Errors" (WHEA correctable) when overclocked and voltage isn't high enough. The correctable errors aren't making the game crash. It's the -uncorrectable- error that crashes the game (or the error that doesn't get caught).
I've been unable to make any other stress test or program generate an "Internal parity error". It either BSOD's (clock watchdog timeout--meaning an actual core froze, system service exception, iRQ_L not less or equal, etc) at unstable voltage settings, or generates a "CPU Cache L0 error" (high stress programs/prime95/realbench 2.56) when temps get too high if voltage isn't high enough. Never, ever an "internal parity error" on a core. Even prime95 with AVX disabled (uses SSE2) doesn't do that.
We also don't know if easyanticheat is affecting or causing it somehow as well.
Yes, it is using avx instructions as well as battlefield 5. Don’t know what devs are you quoting, but you can test that by yourself by simply putting an avx offset in the bios.
Community Manager
