EA Staff (Retired)@Falkentyne that's executing the middle of an instruction. The instructions start at 4C2EF6 and 4C2EFE. The state of the registers is inconsistent with it having recently executed the instructions immediately before here. The most likely causes of jumping to the middle of an instruction are ⚽ a function pointer being corrupt, 🏈 the return address on the stack getting clobbered, or 🏀 a computed jump (sometimes used to implement a switch statement) had an invalid input. But I don't see anything in the registers that would point me to any of these three having happened.
So, I can't really dig in any further. This is the only time I've seen this crash location also. If it starts to be common, we'll invest more effort.
On the bright side, our crash rate appears to be really down now. From my limited sampling, most actual crashes are now in 3rd party DLLs.
@OrioStorm I think it's just from me decreasing my CPU Voltage too low.
Was at 1.270v (Loadline calibration level 6) @ 5 ghz. Went to 1.265v (5mv lower) and got that crash.
So back to 1.270v I go !
tl;dr; Trying to find my minimum stable voltage where Apex won't generate any errors or crashes post patch.
I already know 1.275v is stable so been doing 1.270v then went to 1.265v just now.
Pre-patch it was 1.315v (Loadline calibration=turbo/level 6)
Can second this, at least for now. Around 15hrs of uninterrupted gaming since patch. i7 8700k 5ghz at my initially stable voltage.
Community Manager
