Apex Legends Crash no error - PC (apex_crash.txt)

@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.

@OrioStorm Increased my overclocking back to 5GHz several days ago and received an entirely new crash after several hours of gameplay. I've attached the crash file. Any thoughts?

crash:
{
module@00007FFCD7200000: 00000000007E0823
EXCEPTION_ACCESS_VIOLATION(write): 0000014A2303BE30
}
cpu: "Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 00000000000FF91A
ntdll: 00000000000A4AB2
ntdll: 000000000008C676
ntdll: 00000000000A119F
ntdll: 000000000006A229
ntdll: 000000000009FE0E
module@00007FFCD7200000: 00000000007E0823
module@00007FFCD7200000: 00000000007E1AE1
module@00007FFCD7200000: 00000000006B951A
module@00007FFCD7200000: 000000000053A553
module@00007FFCD7200000: 000000000053A5DF
module@00007FFCD7200000: 000000000046F9F1
module@00007FFCD7200000: 00000000003BFCCA
module@00007FFCD7200000: 00000000001C2F3A
module@00007FFCD7200000: 0000000000E2A4B2
module@00007FFCD7200000: 0000000000DA705B
module@00007FFCD7200000: 000000000037A529
module@00007FFCD7200000: 000000000019A8F6
module@00007FFCD7200000: 0000000000451D25
module@00007FFCD7200000: 00000000004EE5B7
module@00007FFCD7200000: 00000000012A066C
KERNEL32: 0000000000017BD4
ntdll: 000000000006CE71
}
registers:
{
rax = 0x0000014A2303BE30
rbx = 0x000000299999D640
rcx = 0
rdx = 0x50000030
rsp = 0x000000299999D560
rbp = 0x0000016A23119440
rsi = 0x0000016A2303BD18
rdi = 0x0000016A2303BD18
r8 = 0x0000016A23115C10
r9 = 0x0000016A23119690
r10 = 0x0000016A23006D08
r11 = 0
r12 = 0
r13 = 0x0000016A23031980
r14 = 0
r15 = 14
rip = 0x00007FFCD79E0823
xmm0 = [ [1.4993894e-43, 5.0727004e-43, 7.0930804e-18, 5.0727004e-43], [0x0000006B, 0x0000016A, 0x2302D820, 0x0000016A] ]
xmm1 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm2 = [ [2.6904931e-43, 5.0727004e-43, 7.107116e-18, 5.0727004e-43], [0x000000C0, 0x0000016A, 0x23031A68, 0x0000016A] ]
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

Looks like this is the new intel CPU crash, first time i've got this tho, game is a lot more stable with this update.

R5Apex: 00000000004C2EFD
EXCEPTION_ILLEGAL_INSTRUCTION: C000001D

@TrigrH increase CPU voltage by 5mv and test again.

@MrDakk, that's a crash in an unknown module, with no Apex code in the callstack. So I can't say for sure what is crashing, but it's most likely your video card driver, since it's crashing in its own thread. But really, it could be any DLL that is making its own thread.

@TrigrH, that is executing in the middle of an instruction. The only other time I've seen that is when @Falkentyne ran into it after he tried lowering his CPU voltage.

@OrioStorm , hello, just crashed, my first time after the patch. You will find the log attached.

@_S7ORM-BRINGR, the address of the next instruction to execute is in RIP. The address that gave the execute violation is in the crash report.

00007FF635AC5B39 -- RIP address

00007FF600005B39 -- execute violation address

Notice that the only difference is that some of the address bits have been zero'd out in the execute violation address. These addresses should always be the same if the CPU was working right. Were you overclocking when this happened?

We saw this sort of crash a lot before I "jiggled the handle" in patch 1.1.3. This is the first time I've seen this category of crash since then.

---

@OrioStorm wrote:

@_S7ORM-BRINGR, the address of the next instruction to execute is in RIP. The address that gave the execute violation is in the crash report.

00007FF635AC5B39 -- RIP address

00007FF600005B39 -- execute violation address

Notice that the only difference is that some of the address bits have been zero'd out in the execute violation address. These addresses should always be the same if the CPU was working right. Were you overclocking when this happened?

We saw this sort of crash a lot before I "jiggled the handle" in patch 1.1.3. This is the first time I've seen this category of crash since then.

---

Yes, it is overclocked - 5.0 GHZ at the moment. My first crash after the patch.

---

@_S7ORM-BRINGR wrote:

---

@OrioStorm wrote:

@_S7ORM-BRINGR, the address of the next instruction to execute is in RIP. The address that gave the execute violation is in the crash report.

00007FF635AC5B39 -- RIP address

00007FF600005B39 -- execute violation address

Notice that the only difference is that some of the address bits have been zero'd out in the execute violation address. These addresses should always be the same if the CPU was working right. Were you overclocking when this happened?

We saw this sort of crash a lot before I "jiggled the handle" in patch 1.1.3. This is the first time I've seen this category of crash since then.

---

Yes, it is overclocked - 5.0 GHZ at the moment. My first crash after the patch.

---

An just got another one.. ☹️

@_S7ORM-BRINGR 

Raise your CPU voltage by 10mv to 15mv.  (1.250v=1250mv, so that's 1265mv or 1.265v, for this random example).