EA Staff (Retired)@2Cavalier, thank you for that generous offer in time, effort and hardware!
It would be an interesting data point if other identical CPUs had the same problem, especially at stock settings (just to rule out the overclocking factor in the experiment). If only one chip fails, that'd indicate it's probably something in that particular chip. If they all fail, that'd indicate it's likely related to the CPU microarchitecture, or that somehow your other hardware is involved (motherboard etc.). That information could be helpful, but it probably won't immediately point us to a solution.
Still, not knowing your plans for those CPUs, I would hate for you to lose any value on them by opening their boxes for this test.
Regarding something in your previous post, I doubt the GPU matters, but it is possible. There's always the outside chance of some electrical or thermal communication. Also, different GPU and frame capping configurations can alter CPU timing, which can affect the CPU behavior.
EA Staff (Retired)As more general info, the crash is happening inside a loop to decide what LOD to use for a bunch of models, and whether they should fade out. Looking at @Benef1cient's apex_crash.txt, I see that iteration 883 crashed processing model 96651. Looking at @TEZZ0FIN0's crash, I see that iteration 450 crashed processing model 24032. Looking at @Vaestroo's crash, he made it to iteration 3768 and model 408479.
There's no way through the loop that doesn't hit the instruction that crashes, so we've had hundreds or even thousands of iterations that didn't crash before we hit one that did.
Third one today in ~15 games. 1660Ti
crash:
{
R5Apex: 00000000002F2DCA
EXCEPTION_BREAKPOINT: 80000003
}
cpu: "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz"
ram: 8 // GB
callstack:
{
KERNELBASE: 000000000008667C
ntdll: 00000000000A810B
ntdll: 000000000008FD56
ntdll: 00000000000A46AF
ntdll: 0000000000004BEF
ntdll: 00000000000A341E
R5Apex: 00000000002F2DCA
R5Apex: 00000000004C0B56
R5Apex: 00000000004C0F47
R5Apex: 00000000004BF767
R5Apex: 00000000004C1502
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 1
rbx = 0x0000006DD45BBB80
rcx = 0
rdx = 32
rsp = 0x0000006DD516F890
rbp = 298 // 0x0000012A
rsi = 0x000001DDD88336C0
rdi = 1914 // 0x0000077A
r8 = 0
r9 = 22965 // 0x000059B5
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x000001DB57632410
rip = 0x00007FF61F542DCA
xmm0 = [ [4.0952231e+14, 0, 0, 0], [0x57BA3AAC, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [1.9501056e+15, 0, 0, 0], [0x58DDB38B, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5.7619019, 0, 0, 0], [0x40B86180, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [2.3596274e+15, 0, 0, 0], [0x59062119, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [4.2811824e+08, 0, 0, 0], [0x4DCC2487, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [4.2811824e+08, 0, 0, 0], [0x4DCC2487, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [4284900, 11902500, 23328900, 57608100], [0x4A82C3C8, 0x4B359E24, 0x4BB1FC42, 0x4C5BC1E9] ]
xmm9 = [ [4.2848998e+08, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x4DCC51E8, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm13 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm14 = [ [13.8, 0, 0, 0], [0x415CCCCD, 0x00000000, 0x00000000, 0x00000000] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1553899726
Out of curiosity, would anything from Windows Event Viewer help in finding the cause to the crashes? If so, I could start posting the error from the Event Viewer alongside the crash it happened with.
EA Staff (Retired)The code I mentioned is actually LOD for the stationary models, not the characters that move around.
I think the bug in your screenshot is something else. We store lighting at various points in space. We use the closest sample point to light a character. Sometimes you're outside on a roof and the closest point is inside near a dark ceiling. We work hard to avoid this in how we automatically place the sample points, but it isn't perfect.
i have the same issue
crash:
{
R5Apex: 0000000000B0E44E
EXCEPTION_ACCESS_VIOLATION(read): FFFFFFFFFFFFFFFF
}
cpu: "AMD Ryzen 7 2700X Eight-Core Processor "
ram: 16 // GB
callstack:
{
SogouPy: 00000000001B13EA
PicFace64: 000000000018F416
KERNELBASE: 0000000000086B2C
ntdll: 00000000000A81CB
ntdll: 000000000008FD56
ntdll: 00000000000A477F
ntdll: 0000000000004BEF
ntdll: 00000000000A34EE
R5Apex: 0000000000B0E44E
R5Apex: 0000000000B0EB4D
R5Apex: 0000000000B0F656
R5Apex: 0000000000727BA2
R5Apex: 000000000072808C
R5Apex: 0000000000452936
R5Apex: 0000000000452D27
R5Apex: 00000000004515B7
R5Apex: 00000000004532E2
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 0x0018000001C42CCF
rbx = 0
rcx = 0x000001C570CF4E80
rdx = 19
rsp = 0x0000001E36E0F900
rbp = 1
rsi = 2783 // 0x00000ADF
rdi = 0x000001C570CF4E80
r8 = 1
r9 = 0xFFFFFEFF
r10 = 20
r11 = 0x0000001E36E0F978
r12 = 19
r13 = 0
r14 = 0
r15 = 1
rip = 0x00007FF789DAE44E
xmm0 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [219.89484, 0, 0, 0], [0x435BE514, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5.1623049, 0, 0, 0], [0x40A5319A, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [5, 0, 0, 0], [0x40A00000, 0x00000000, 0x00000000, 0x00000000] ]
xmm6 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm9 = [ [0.1, 0, 0, 0], [0x3DCCCCCD, 0x00000000, 0x00000000, 0x00000000] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [0.001, 0, 0, 0], [0x3A83126F, 0x00000000, 0x00000000, 0x00000000] ]
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: 1567116206
Wasn't going to post, but was thinking about it. Looked like my teammate, and then I, got the error while trying to go into a vaulting motion.
This crash is when i OC my I7 8700k at 5GHZ so turn the OC down it order not to get crashes any more R5Apex: 000000000029AD5F
EXCEPTION_ACCESS_VIOLATION(read): 000000000000024F
}
cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz"
ram: 16 // GB
Community Manager
