crash report [ Edited ]

[Men4n]

crash report

[Zerrone1]

I had crashes since i got my new pc, i think it is mostly cause of my RTX 2070 but now it says its cause of my CPU dont really get it sadly.

Still hoping someone smart can help me out. 

[Panda5_OG]

try setting avx offset to 1 or 2 in bios.... Seems to be stopping the crashes for me... Well so far. 

[EA_Atic]

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 

[CroL0co]

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

[TheBigglyOof]

No overclock, changed AVX offset but still freezing mid game. I have to force quit and task manager shows Apex running at near 100% cpu. 

i7 9700k
RTX 2080 

[pikathar]

SAME HERE !

WTF

8700k + 1080ti + 16gb ram

crash:
{
R5Apex: 000000000029BD37
EXCEPTION_ACCESS_VIOLATION(execute): 00007FF6C451BD37
}
cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000FF67A
ntdll: 00000000000A4AF2
ntdll: 000000000008C6E6
ntdll: 00000000000A120F
ntdll: 000000000006A299
ntdll: 000000000009FE7E
R5Apex: 000000000029BD37
R5Apex: 0000000000458F06
R5Apex: 00000000004592F7
R5Apex: 0000000000457B87
R5Apex: 00000000004598B2
KERNEL32: 0000000000017BD4
ntdll: 000000000006CEE1
}
registers:
{
rax = 0x08F80000
rbx = 440 // 0x000001B8
rcx = 440 // 0x000001B8
rdx = 58596 // 0x0000E4E4
rsp = 0x0000005C1EF68DB0
rbp = 0x0000005C1EF6E580
rsi = 43
rdi = 0x000001C872C89CA0
r8 = 0x0000005C1EF69BA0
r9 = 0x000001C5C21611D0
r10 = 2296 // 0x000008F8
r11 = 0
r12 = 440 // 0x000001B8
r13 = 0x000001C5C21691F8
r14 = 0x000001C5C24A2700
r15 = 0x000001C5C218AE84
rip = 0x00007FF6EC51BD37
xmm0 = [ [5.76081e+09, 0, 0, 0], [0x4FABAF7E, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [5.76081e+09, 0, 0, 0], [0x4FABAF7E, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [62049888, 62049888, 20021.766, 20021.766], [0x4C6CB398, 0x4C6CB398, 0x469C6B88, 0x469C6B88] ]
xmm3 = [ [5.76081e+09, 0, 0, 0], [0x4FABAF7E, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [1.2097705e+09, 0, 0, 0], [0x4E903744, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [62069908, 0, 0, 0], [0x4C6CC725, 0x00000000, 0x00000000, 0x00000000] ]
xmm6 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [62069908, 62069908, 62069908, 62069908], [0x4C6CC725, 0x4C6CC725, 0x4C6CC725, 0x4C6CC725] ]
xmm8 = [ [62069908, 62069908, 62069908, 62069908], [0x4C6CC725, 0x4C6CC725, 0x4C6CC725, 0x4C6CC725] ]
xmm9 = [ [-14384.817, 30726.949, -4079.5017, 0], [0xC660C345, 0x46F00DE6, 0xC57EF807, 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

[LoK_PT]

@CroL0co Exactly! I've got a 4.9ghz oc without AVX offset perfectly stable after passing overnight OCCT with AVX instructions + zero problems in Battlefield V that also uses avx which also detects oc instability really fast.

That fix is bull****

[OmegaChipz]

crash:
{
R5Apex: 000000000029BD37
EXCEPTION_ACCESS_VIOLATION(execute): 00007FF70010BD37
}
cpu: "Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 00000000000FF67A
ntdll: 00000000000A4AF2
ntdll: 000000000008C6E6
ntdll: 00000000000A120F
ntdll: 000000000006A299
ntdll: 000000000009FE7E
R5Apex: 000000000029BD37
R5Apex: 0000000000458F06
R5Apex: 00000000004592F7
R5Apex: 0000000000457B87
R5Apex: 00000000004598B2
KERNEL32: 0000000000017BD4
ntdll: 000000000006CEE1
}
registers:
{
rax = 0x08F60003
rbx = 425 // 0x000001A9
rcx = 425 // 0x000001A9
rdx = 61684 // 0x0000F0F4
rsp = 0x000000BA6B05B3A0
rbp = 0x000000BA6B05E5F0
rsi = 31
rdi = 0x00000229DF331EA0
r8 = 0x000000BA6B05C118
r9 = 0x00000228FBFA7B10
r10 = 2294 // 0x000008F6
r11 = 3
r12 = 425 // 0x000001A9
r13 = 0x00000228FBFAFB38
r14 = 0x00000228FC278790
r15 = 0x00000228FBFD16D4
rip = 0x00007FF7D0B7BD37
xmm0 = [ [2.3043239e+12, 0, 0, 0], [0x5406211A, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [2.3043239e+12, 0, 0, 0], [0x5406211A, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [3.8968845e+08, 3.8968845e+08, 7013824, 7013824], [0x4DB9D164, 0x4DB9D164, 0x4AD60B80, 0x4AD60B80] ]
xmm3 = [ [2.3043239e+12, 0, 0, 0], [0x5406211A, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [4.8390812e+11, 0, 0, 0], [0x52E15658, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [3.9670227e+08, 0, 0, 0], [0x4DBD2992, 0x00000000, 0x00000000, 0x00000000] ]
xmm6 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [3.9670227e+08, 3.9670227e+08, 3.9670227e+08, 3.9670227e+08], [0x4DBD2992, 0x4DBD2992, 0x4DBD2992, 0x4DBD2992] ]
xmm8 = [ [3.9670227e+08, 3.9670227e+08, 3.9670227e+08, 3.9670227e+08], [0x4DBD2992, 0x4DBD2992, 0x4DBD2992, 0x4DBD2992] ]
xmm9 = [ [-11939.694, 4875.7358, -3434.3506, 0], [0xC63A8EC7, 0x45985DE3, 0xC556A59C, 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

[M4pleLeaf]

Hello,

My game crashed as soon as I started shooting at a drone. I don't know if it helps, but I was playing Bloodhound, and was using an R-99. My crash file is attached.