im not going to change clocks on my cpu everytime i want to play one specific game ... but using the setting " use cpu offset when running avx" did the same for me
changed my 7700k from 4,9ghz to -4 offset 4,5 standart boost clock and didnt crash since then
Mine crashed w/o OC
crash:
{
msvcrt: 000000000002A9E6
EXCEPTION_ACCESS_VIOLATION(write): 0000000000000000
}
cpu: "Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz"
ram: 64 // GB
callstack:
{
KERNELBASE: 000000000008667C
ntdll: 00000000000A810B
ntdll: 000000000008FD56
ntdll: 00000000000A46AF
ntdll: 0000000000004BEF
ntdll: 00000000000A341E
msvcrt: 000000000002A9E6
sapi_onecore: 000000000011CA8F
sapi_onecore: 000000000011CAC9
sapi_onecore: 000000000003F4D1
sapi_onecore: 000000000015E8C7
sapi_onecore: 0000000000026C30
sapi_onecore: 0000000000026BE4
sapi_onecore: 0000000000026B7B
module@00007FFEA05E0000: 000000000009759D
module@00007FFEA05E0000: 00000000000978CF
module@00007FFEA05E0000: 0000000000097C5C
ntdll: 0000000000048F07
ntdll: 00000000000435BC
ntdll: 0000000000066DCD
KERNEL32: 000000000001D62A
R5Apex: 0000000001241584
R5Apex: 0000000001241520
R5Apex: 00000000004AE602
R5Apex: 0000000001202656
Activation64: 0000000000011050
Activation64: 0000000000008F82
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 0
rbx = 0x00000035FBDAEA10
rcx = 0x013FFC2AA8F00000
rdx = 0
rsp = 0x00000035FBDAE9A0
rbp = 0x000001553C7C6F80
rsi = -1 // 0xFFFFFFFF
rdi = 0x000001553C792800
r8 = 0
r9 = 0x00000035FBDADFB0
r10 = 0x00007FFED9D81DC4
r11 = 0x00000035FBDAE3E0
r12 = 0x000001553C7C6F80
r13 = 0
r14 = 0x00000035FBDAEA08
r15 = 0x00007FFEB2E54070
rip = 0x00007FFED7D3A9E6
xmm0 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm1 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm2 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
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: 1554860081
EA Staff (Retired)@Kaz3ee, you didn't get the usual Intel crash. Instead, your program crashed in Microsoft's C runtime DLL (msvcrt.dll) when shutting down Microsoft's speech API DLL (sapi_onecore.dll) when you were exiting the game. I've seen this 3 other times, but I'm not too hopeful that we'll fix it ourselves, since it happens in Microsoft's code when Apex has almost finished exiting. Do you have any info about what you were doing when this happened that might narrow it down, such as quitting while speech was playing?
I was killed and the screen just froze. Wasn't quitting the game.
EA Staff (Retired)@Kaz3ee, that's really interesting. That sounds like a freeze, not a crash, but often the game freezes for a few seconds before finally crashing. Crashes and freezes are basically the same from a user's perspective (the game suddenly and frustratingly stops working), but they are actually different underlying problems.
In a crash, the program did something the CPU doesn't allow, such as trying to read from memory you don't have read access to. Because of that, the OS completely kills the program.
In a freeze, the program is still running, but it's stuck. This comes in two basic kinds. One is the "infinite loop", where the program keeps doing the same thing over and over, but never actually makes any progress so that it can stop doing it. It's basically stuck running in circles rather than running toward the finish line. The other is "deadlock", where thing A is waiting for thing B, but thing B is waiting for thing A, so neither will ever go first and the game just stops. This is basically two guys both wanting to go the finish line, but each insists "no, you go first", so that neither takes a step ever again.
When you get a freeze, you have to kill the program yourself. Apex won't generate an apex_crash.txt for a freeze, because it doesn't know it happened. It only generates the apex_crash.txt for the crash.
So, there are two basic ways to know if this apex_crash.txt goes with this crash or an earlier one:
Thanks for your help!
The one I posted is the crashed after I get killed, and I have to kill the program myself.
The one that I killed someone and I have to terminate the program doesn't gives out any crash log.
