April 2019 - last edited April 2019
@OrioStorm Thanks for looking into this for us!
However, I still cannot figure out why the game crashes almost every time after landing from the ship. All of the cores from my cpu will be in the 90% range before it happens. I've tried pretty much everything I could possibly think of, other than re-installing windows.
I haven't had a crash in ANY of the multiple games I've played in the past.
This is still very frustrating as I've made several purchases in this game and enjoy it a lot.
April 2019
@OrioStorm ok, i downgrade my cpu speed clock from 5ghz to 4.8ghz, i have now 0 crash in 20hours of game play.
i7 8700k @ 4.8ghz 1.35v
Thanks for your answer, i hope you will patch it.
Thanks for all ++
April 2019 - last edited April 2019
What are your CPU clock speeds? If you are running stock, I would just try increasing your vCore voltage until you get a stable game. For me it was 1.28v in the BIOS, and be sure not go to high.
If you are overclocking reduce your overclock some or go back to stock settings.
April 2019
Getting sick of Apex crashing nearly every game. Not sure what this error is, any help would be much appreciated.
crash:
{
R5Apex: 00000000002F2E2A
EXCEPTION_ACCESS_VIOLATION(write): 00000000000004BF
}
cpu: "Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 000000000008667C
ntdll: 00000000000A810B
ntdll: 000000000008FD56
ntdll: 00000000000A46AF
ntdll: 0000000000004BEF
ntdll: 00000000000A341E
R5Apex: 00000000002F2E2A
!!!unknown-module!!!: 000001EF8A03EF3C
}
registers:
{
rax = 323388 // 0x0004EF3C
rbx = 0x000000CCA4157000
rcx = 1
rdx = 4
rsp = 0x000000CCAD60F850
rbp = 662 // 0x00000296
rsi = 0x000001F1BE3EFB60
rdi = 1212 // 0x000004BC
r8 = 0
r9 = 161754 // 0x000277DA
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x000001EF94C54430
rip = 0x00007FF613AF2E2A
xmm0 = [ [1436334.5, 0, 0, 0], [0x49AF5574, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [6839687, 0, 0, 0], [0x4AD0BB0E, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [0.71091938, 0, 0, 0], [0x3F35FED0, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [1021118, 0, 0, 0], [0x49794BE0, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [7254903.5, 0, 0, 0], [0x4ADD66EF, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [-0.96401954, 0, 0, 0], [0xBF76C9FC, 0x00000000, 0x00000000, 0x00000000] ]
xmm6 = [ [7254903.5, 0, 0, 0], [0x4ADD66EF, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [0.71091938, 0, 0, 0], [0x3F35FED0, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [1218816, 2742336, 3.4028235e+38, 3.4028235e+38], [0x4994C800, 0x4A276100, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm9 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 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: 1554860081
April 2019
These are all the Intel crash (see post 1984) that is worked around by lowering clock speed. Unfortunately, I still don't know when a patch with a software workaround will go live:
@spackmanbr @pigfaceguy @GudLuckTurret @BartukTheGreat @solrflar @zzilis