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!!
@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.
That doesn't mean that the game is using AVX instructions.
A Gigabyte bios engineer responded to this query.
He said on a brand new windows install (No updates, microsoft patches, C++ updates, etc etc), the CPU was not downclocking via AVX offset randomly unless an AVX application was running (e.g. Prime95, BF5).
Question for you.
Does Overwatch use AVX instructions?
No, it doesn't.
Yet I get an "AVX" downclock in Overwatch randomly, at the same intervals as in Apex Legends, even when I'm sitting around on the *training room* doing absolutely nothing.
Oriostorm explained that AVX instructions can look similar to SSE2 instructions (he also explained that they are related).
Read his posts in this thread and you will see that Apex does NOT use AVX instructions on its own.
Don't mean to be a * but I think a head programmer knows what instructions he's using.
Please read his posts. I asked him directly.
Community Manager
