9900k, crashed at stock clocks but not stock settings (xmp enabled, power limits bumped).
I find a reason for crush - its about number of threads in your cpu. If it is more than 8 - its causes game for crash. My config is ryzen 1700 and nvidia 1070, after upgrade from intel 3470k i have always crashes almost every game. I changed with my settings with ryzen master - 16 threads to 8 threads(multithreading disabled) and my crashes ended, i tested 4 cores(4 cores disabled) with multithreading(8 threads)its ok, no crashes. If i start game with 16 threads and option -threads 16 it works fine,
if you have 6 core cpu with 12 threads you have to use -threads 12.
Game mostly uses 4 threads, optimal use 4 cores with overlocking to boost your cpu performance, using more threads better only if you using discord or some background apps.
Analysing everyones here crash logs, it looks like overflow error - every log have register with around e^30 variable, it could be 2 types of problem in code of apex: thread safety(more threads than 8 cases crash somehow, maybee some kind of deadlock, or race condition) or its overflow error, caused by number of threads. Or maybee, its KOMBO of thread lock and overflow or undefined behaouvor of game cased by reading variables in async, if i use +fps_max 60 it cases crash game very rare(every 6 games).
Also, i tested, if performance of processor related to crashes: if you have 100% processor load on 4 core processor, its fine, if you overlock you cpu its will not result in system crashes, if system stable in this mode(test by linx avx for 5 min stability and it would be fine). Its not related to memory clock rate of memory - i tested from 3000Mhz to 3466 Mhz(xmp profile of my memory) it works same. My game start up option looks like +fps_max 144 -refresh 144 -threads 16(g-sync monitor). My crash log if i start game without comand line option included.
Hope my post help solve smbs problem. If developers need help with it, Russian rocket scienstist ready to help you:D
@madfugas wrote:I find a reason for crush - its about number of threads in your cpu. If it is more than 8 - its causes game for crash. My config is ryzen 1700 and nvidia 1070, after upgrade from intel 3470k i have always crashes almost every game. I changed with my settings with ryzen master - 16 threads to 8 threads(multithreading disabled) and my crashes ended, i tested 4 cores(4 cores disabled) with multithreading(8 threads)its ok, no crashes. If i start game with 16 threads and option -threads 16 it works fine,
if you have 6 core cpu with 12 threads you have to use -threads 12.
Game mostly uses 4 threads, optimal use 4 cores with overlocking to boost your cpu performance, using more threads better only if you using discord or some background apps.
Analysing everyones here crash logs, it looks like overflow error - every log have register with around e^30 variable, it could be 2 types of problem in code of apex: thread safety(more threads than 8 cases crash somehow, maybee some kind of deadlock, or race condition) or its overflow error, caused by number of threads. Or maybee, its KOMBO of thread lock and overflow or undefined behaouvor of game cased by reading variables in async, if i use +fps_max 60 it cases crash game very rare(every 6 games).
Also, i tested, if performance of processor related to crashes: if you have 100% processor load on 4 core processor, its fine, if you overlock you cpu its will not result in system crashes, if system stable in this mode(test by linx avx for 5 min stability and it would be fine). Its not related to memory clock rate of memory - i tested from 3000Mhz to 3466 Mhz(xmp profile of my memory) it works same. My game start up option looks like +fps_max 144 -refresh 144 -threads 16(g-sync monitor). My crash log if i start game without comand line option included.
Hope my post help solve smbs problem. If developers need help with it, Russian rocket scienstist ready to help you:D
Maybe it's a coincidence, but I put that -threads 12 (I use a 8700k) at the Origin's Apex properties and the crashes stopped! I played more than 10 matches, before this change I couldn't make past 2 matches without a crash. But maybe it's a coincidence, as I said, but I hope not.
If my crashes return and it was just luck/coincidence/a bug in the matrix I'll edit this post.
@RascabuchesCH Does the -threads parameter even work? How?
I tried -threads 1 through -threads 16 and there was zero difference, like the option did absolutely nothing. There was also no difference in CPU usage either(9900K).
@Falkentyne wrote:@RascabuchesCH Does the -threads parameter even work? How?
I tried -threads 1 through -threads 16 and there was zero difference, like the option did absolutely nothing. There was also no difference in CPU usage either(9900K).
It worked here though. I didn't changed anything else since last time where I crashed all the time. Maybe it was luck, I was playing until now with no crashes (the game was open for more than 4 hours). Tonight I'll make a new test and see if I still don't crash. Maybe Windows updated and changed something? I don't remember new updates.
Community Manager
