Please keep me posted.
And you were right. I had three hours of stability, but then suddenly the "internal parity errors" started happening again, and not long after, the random crashes.
The only fix was to increase CPU voltage -excessively- high.
Oriostorm, is Apex doing something timing related that is causing this instability?
Because it really should not be happening.
I set my cpu to 5.2 ghz (hyperthreading off) at 1.335v and I ran Battlefield 5 (Firestorm) for an hour. BF5 was using >75% of the CPU cores, temps and power draw were much higher, and there were no errors or crashes. I then ran the Blender Classroom render stress test (you can google this), and blender BMW stress test and both completed with flying colors. The only programs that had problems at this point were Apex Legends (those crashes and Internal Parity Error) and Prime95 AVX 1344K (clock watchdog timeout BSOD). Prime95 small FFT with AVX disabled ran forever. (Prime95 29.8 build 1).
Increasing CPU voltage to 1.385v completely stopped the Prime95 1344K AVX tests from crashing. These ran fine now.
But APEX legends was still randomly acting up (exception error, or CTD sometimes with no error, or internal parity error (no crash).
1.395v-1.40v was needed to stop this--far far beyond what any other program or application needed! Something is really strange here.
And what's even worse---Apex Legends uses FAR FAR far less CPU resources than Blender, Battlefield 5, Prime95 (AVX disabled), etc.
Oriostorm, is there any way, if you have time, to write a very small 'stress test' code sample that can extensively test some of the instructions you are using for Apex Legends, in a repeated intense loop of cycles, so that we can run the executable program and it can catch any SSE2 error in a bugtrap? This may help track down the problem. This might also help determine why some users with stock clocks are also getting these crashes (in most cases, pure stock clocks prevent these problems). It shouldn't take that long to write a code sample that we can download, and it may help determine what's going on.
It really is inconceivable that Apex is needing far more voltage than something like Blender or Prime95....
Could EasyAntiCheat be causing these timing errors?
By the way, this "bizarre" behavior seems to get reversed (meaning things start acting properly) if you run at base clocks (4.7 ghz) and then downvolt the CPU enough so it's unstable.
Doing this and Apex Legends runs nice and happily while Prime95 with AVX disabled generates a BSOD crash. This happened at about 4.7 ghz (HT enabled) at 1.065v.
You have to go even lower on the voltage before Apex starts generating parity errors.
Thanks for doing this. I've got 3 crash logs for you; the first two are from patch 1.1.0 and the third is just last night from 1.1.1. I've got about 20 more if you want to see them - hex error codes are 2F2BB0, 2F20B6, 2F239A, 2F20C1, 2F23C5. The latest ones are 2F2E2A and two that have 2F2DCA.
History of my crashes - I picked up the game in the first week of release and didn't have a single crash until the patch that fixed the revive bug - The bug where a revived character still moved super slowly as if they were still down and wounded. After that patch, I started crashing anywhere from a couple times every few days to eleven times in one day. It was random, and it was super frustrating, but I kept going regardless because I really liked the game. The crashes came at all times - most were in-game, but a couple of them happened while I was still in the character select screen. None of them seemed to have anything in common with each other - I crashed in gunfights, I crashed in peaceful fields, I crashed with apps like Discord open, I crashed with just Apex open, and a dozen other random situations it would take too long to recount here.
But with the 1.1.0 patch, everything went to hell. I crash every single game now, every single time, usually within less than five minutes. I don't know what changed, but whatever my problem is, the 1.1.0 patch kicked it into overdrive. I can't play at all now, haven't touched the game at all since the day 1.1.0 dropped aside from last night so I could generate a fresh crash log for you. Crashed about 3 minutes into the game, just like I knew I would. I hope you manage to figure out what's going on; I still like Apex, but the game has made it clear it doesn't want me playing it.
System information - Intel i7-9700k overclocked to 4.9 gHZ, voltage at 1.235
Ram - 16 GB overclocked to 3200
Graphics Card - Nvidia 1080, stock timings
Types of crashes - I get three different types of crashes, detailed below:
The typical crash - The visuals freeze, audio may or may not keep going, and after about 2 - 4 seconds the game crashes to desktop. This crash hits me about 45% of the time and DOES GENERATE A CRASH LOG.
The atypical crash - The visuals freeze, audio may or may not keep going, and after about 2 - 4 seconds the game crashes to desktop. This crash hits me about 50% of the time and DOES NOT GENERATE A CRASH LOG. I have no idea why this crash doesn't generate a log. I assume something is breaking that isn't being accounted for in your logging process, or Windows or possibly Easy Anti-Cheat is somehow preventing log generation. If I had a log for every crash, I'd have somewhere north of 50 by now.
The "Instant" crash - One second I'm in the game. The next second I'm staring at my desktop. No transition whatsoever between the two - it's that fast. No audio or visual freezing, no screen tear, just instant transition to desktop with the game mysteriously closed. Obviously, THIS CRASH DOES NOT GENERATE A CRASH LOG. It only happens about 5% of the time, but it sure makes a hell of an impression when it does.
Finally, one crash I had that might help you - don't think it generated a log: One time, about 3 weeks ago, so before 1.1.0, I had a situation in-game where I thought I crashed - The screen froze, audio kept going, and I thought welp, there goes this game. But then, for some mysterious reason, after about three seconds the game snapped back and resumed normal play. I could run around, shoot, hear everything normally for about five seconds. THEN the game did an "Instant" crash - straight to desktop with no transition at all. I have no idea what it meant - perhaps the function somehow managed to correct itself briefly? Or some other code process interceded? But it was weird enough that it stuck out and made me want to mention it.
Hope all this information helps you. I really want to play Apex without wondering when the game is going to kick me out of it.
I’d like to add that all of these crash types you’ve explained are happening almost identically for me. I get all three types of those crashes. I have yet to see the 2F2DCA crash since the newest patch, though I haven’t played a whole lot since the patch dropped. I did crash multiple times with and without crash logs and posted a log from the new patch. The crashes I’ve got are the EXCEPTION_ACCESS_VIOLATION(write) and EXCEPTION_ACCESS_VIOLATION(read). I don’t have the error codes handy at the moment. I’ll definitely post more logs as I get them.
Also want to thank @OrioStorm for all the input and support on these crashes. It’s rare to get this kind of insight and help on forums nowadays from devs. So thank you for taking time out of your day to respond, educate, and help solve these issues. Thanks to everyone else as well who’s continuing to test and provide information. I really hope a solution is found soon. Keep providing as much info as you can.
Community Manager
