---------------------------
Apex Crash - Overclocked/Overheated?
---------------------------
Apex crashed in a way usually caused by a CPU that is overclocked or overheating.
Specifically, the CPU reported that it couldn't execute an instruction it didn't want to execute. More precisely, the CPU's memory controller said it didn't have permission to execute one address, but the CPU's registers said it wanted to execute a different address.
More technical information should be available in "apex_crash.txt" in your Documents folder.
Ctrl+C in this window will copy this message so you can paste it as text.
Got the same message. Temperatures were perfectly fine and this happened after I downclocked my 100% stable overclock by 100mhz.
@EA_Atic wrote:Hey everyone,I wrote this in another thread also.One of our developers recommending, quoting him below:Those that get R5apex crash, listed at the top of the apex_crash.txt (Example; R5Apex: 00000000003A7BF6).Please mention if you've overclocked your system. If you are able to and know your system bios,set the AVX offset to 1 or 2 regardless of overclock to see if the R5Apex crash stops. Please report back if the issue seems resolved after that. !!Do not tinker with BIOS if you're not comfortable with it!!/Atic
This is not a fix, this is a cheap workaround. Apex is using AVX instructions almost 100% of the time so it basically means you have to run your CPU 100-200mhz lower the whole time after you set the AVX offset to 1 or 2. The problem are obviously not the cpu overclocks, but the poorly implemented AVX instructions in the game.
Sometimes I think my PC does the same
5GHZ OC - Tried with AVX offset 1-2. Both causes crashes and bluescreen. Tried ramping voltages up by 0.04 and still same thing happens. Tried with only boos which is 4.7ghz and still crashes.
crash:
{
R5Apex: 000000000029BC2F
EXCEPTION_ACCESS_VIOLATION(execute): 00007FF60000BC30
}
cpu: "Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 00000000000FF67A
ntdll: 00000000000A4AF2
ntdll: 000000000008C6E6
ntdll: 00000000000A120F
ntdll: 000000000006A299
ntdll: 000000000009FE7E
R5Apex: 000000000029BC2F
R5Apex: 0000000000458F06
R5Apex: 00000000004592F7
R5Apex: 0000000000457B87
R5Apex: 00000000004598B2
KERNEL32: 0000000000017BD4
ntdll: 000000000006CEE1
}
registers:
{
rax = 0x03E30000
rbx = 246
rcx = 246
rdx = 5965 // 0x0000174D
rsp = 0x000000632C058860
rbp = 0x000000632C05E500
rsi = 23
rdi = 0x000001673DAFE9C0
r8 = 0x000000632C059040
r9 = 0x000001665A237970
r10 = 995 // 0x000003E3
r11 = 0
r12 = 246
r13 = 0x000001665A23F998
r14 = 0x000001665A500330
r15 = 0x000001665A260A04
rip = 0x00007FF6544CBC2F
xmm0 = [ [9641025, 0, 0, 0], [0x4B131C41, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [9641025, 0, 0, 0], [0x4B131C41, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [3413419.5, 3413419.5, 18531.611, 18531.611], [0x4A5056AE, 0x4A5056AE, 0x4690C739, 0x4690C739] ]
xmm3 = [ [9641025, 0, 0, 0], [0x4B131C41, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [2024616, 0, 0, 0], [0x49F72540, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [3431951, 0, 0, 0], [0x4A51783C, 0x00000000, 0x00000000, 0x00000000] ]
xmm6 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [3431951, 3431951, 3431951, 3431951], [0x4A51783C, 0x4A51783C, 0x4A51783C, 0x4A51783C] ]
xmm8 = [ [3431951, 3431951, 3431951, 3431951], [0x4A51783C, 0x4A51783C, 0x4A51783C, 0x4A51783C] ]
xmm9 = [ [7757.2192, -17920.604, -3503.8691, 0], [0x45F269C1, 0xC68C0135, 0xC55AFDE8, 0x00000000] ]
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: 1569284646
My game literally just crashes and freezes and i have to task manager out. This is starting to really annoy me!
crash:
{
mileswin64: 0000000000027971
EXCEPTION_ACCESS_VIOLATION(write): 0000000000000080
}
cpu: "Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000FF92A
ntdll: 00000000000A4AB2
ntdll: 000000000008C676
ntdll: 00000000000A119F
ntdll: 000000000006A229
ntdll: 000000000009FE0E
mileswin64: 0000000000027971
mileswin64: 00000000000225A6
mileswin64: 00000000000260DB
mileswin64: 000000000001636A
mileswin64: 0000000000006B5C
mileswin64: 0000000000007395
R5Apex: 00000000009519BA
R5Apex: 0000000000458F06
R5Apex: 00000000004592F7
R5Apex: 0000000000457B87
R5Apex: 00000000004598B2
KERNEL32: 0000000000017944
ntdll: 000000000006CE71
}
registers:
{
rax = 0
rbx = 0x0000023F43CC2A10
rcx = 0
rdx = 0x0000023F43CC2A10
rsp = 0x0000006E1E00E640
rbp = 0x0000006E1E00E790
rsi = 67
rdi = 0x0000023F48D7C640
r8 = 0x00000240240F6400
r9 = 0
r10 = 0x0000023F48D7C640
r11 = 0x0000023F41DD4010
r12 = 2
r13 = 0
r14 = 0x0000023F3EAC5C10
r15 = 0x0000023F48D7C640
rip = 0x00007FF9EF3A7971
xmm0 = [ [342974.72, 0, 0, 0], [0x48A777D7, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm2 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [24, 0, 0, 0], [0x41C00000, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [750, 0, 0, 0], [0x443B8000, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [-1.663039e+38, -1.9232867, 0, 0], [0xFEFA39EF, 0xBFF62E42, 0x00000000, 0x00000000] ]
xmm6 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1.6666666, 0, 0, 0], [0x3FD55555, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
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: 1569284646
A bit better workaround then turning off half of CPU cores:
Setting the affinity to 4 threads did not work for me. Took a little longer to freeze, but eventually it happened on my 4th game about 30-45 min. I verified that only 4 cores were working by using Speed Fan. This showed that I had all 8 cores available, but only 4 of them were doing any work.
Only fix for me on an i7-9700k is to disable 4 cores in the bios.
Community Manager
