@OrioStorm Hi, I got a new crash today.
Any idea what this is?
Never seen this code before.
crash:
{
R5Apex: 00000000004C2EFD
EXCEPTION_ILLEGAL_INSTRUCTION: C000001D
}
cpu: "Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 0000000000006913
ntdll: 00000000000ADA9D
ntdll: 0000000000096476
ntdll: 00000000000AA08D
ntdll: 0000000000019C58
ntdll: 00000000000A910E
R5Apex: 00000000004C2EFD
R5Apex: 00000000004C35A7
R5Apex: 00000000004C1D47
R5Apex: 00000000004C3AE2
KERNEL32: 0000000000012774
ntdll: 0000000000070D61
}
registers:
{
rax = 0x40C6000000000000
rbx = 125
rcx = 0xFFC0000000000000
rdx = 125
rsp = 0x0000009343D1F630
rbp = 0x0140F0D2
rsi = 65535 // 0x0000FFFF
rdi = 0x00007FF7BF2DF100
r8 = 0x40C600007D00007D
r9 = 0
r10 = 0
r11 = 13
r12 = 20
r13 = 0
r14 = 0xFFFF000000000000
r15 = 0x40C0000000000000
rip = 0x00007FF7989A2EFD
xmm0 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm1 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm2 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm3 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm7 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm8 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm9 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm12 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm13 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm14 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1557879477
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
