Help us improve Answers HQ! Take Survey No, Thanks

Apex Legends Crash no error - PC (apex_crash.txt)

by KaolinAngel_TTV
Reply

Original Post

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

@OrioStorm 

Thanks for doing this. I've got 3 crash logs for you; the first two are from patch 1.1.0 and the third is just last night from 1.1.1. I've got about 20 more if you want to see them - hex error codes are 2F2BB0, 2F20B6, 2F239A, 2F20C1, 2F23C5. The latest ones are 2F2E2A and two that have 2F2DCA.

 

History of my crashes - I picked up the game in the first week of release and didn't have a single crash until the patch that fixed the revive bug - The bug where a revived character still moved super slowly as if they were still down and wounded. After that patch, I started crashing anywhere from a couple times every few days to eleven times in one day. It was random, and it was super frustrating, but I kept going regardless because I really liked the game. The crashes came at all times - most were in-game, but a couple of them happened while I was still in the character select screen. None of them seemed to have anything in common with each other - I crashed in gunfights, I crashed in peaceful fields, I crashed with apps like Discord open, I crashed with just Apex open, and a dozen other random situations it would take too long to recount here.

 

But with the 1.1.0 patch, everything went to hell. I crash every single game now, every single time, usually within less than five minutes. I don't know what changed, but whatever my problem is, the 1.1.0 patch kicked it into overdrive. I can't play at all now, haven't touched the game at all since the day 1.1.0 dropped aside from last night so I could generate a fresh crash log for you. Crashed about 3 minutes into the game, just like I knew I would. I hope you manage to figure out what's going on; I still like Apex, but the game has made it clear it doesn't want me playing it.

 

System information - Intel i7-9700k overclocked to 4.9 gHZ, voltage at 1.235

Ram - 16 GB overclocked to 3200

Graphics Card - Nvidia 1080, stock timings

 

Types of crashes - I get three different types of crashes, detailed below:

The typical crash - The visuals freeze, audio may or may not keep going, and after about 2 - 4 seconds the game crashes to desktop. This crash hits me about 45% of the time and DOES GENERATE A CRASH LOG.

The atypical crash - The visuals freeze, audio may or may not keep going, and after about 2 - 4 seconds the game crashes to desktop. This crash hits me about 50% of the time and DOES NOT GENERATE A CRASH LOG. I have no idea why this crash doesn't generate a log. I assume something is breaking that isn't being accounted for in your logging process, or Windows or possibly Easy Anti-Cheat is somehow preventing log generation. If I had a log for every crash, I'd have somewhere north of 50 by now.

The "Instant" crash - One second I'm in the game. The next second I'm staring at my desktop. No transition whatsoever between the two - it's that fast. No audio or visual freezing, no screen tear, just instant transition to desktop with the game mysteriously closed. Obviously, THIS CRASH DOES NOT GENERATE A CRASH LOG. It only happens about 5% of the time, but it sure makes a hell of an impression when it does.

 

Finally, one crash I had that might help you - don't think it generated a log: One time, about 3 weeks ago, so before 1.1.0, I had a situation in-game where I thought I crashed - The screen froze, audio kept going, and I thought welp, there goes this game. But then, for some mysterious reason, after about three seconds the game snapped back and resumed normal play. I could run around, shoot, hear everything normally for about five seconds. THEN the game did an "Instant" crash - straight to desktop with no transition at all. I have no idea what it meant - perhaps the function somehow managed to correct itself briefly? Or some other code process interceded? But it was weird enough that it stuck out and made me want to mention it.

 

Hope all this information helps you. I really want to play Apex without wondering when the game is going to kick me out of it.

Message 81 of 532 (706 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★ Apprentice

@OrioStorm Thank you very much.  I would be happy to do these tests for you (after all it's what we people over on overclock.net do, spend all day running stability tests!).

 

I just did something very interesting on my laptop.  

It is a 7820HK (MSI) laptop, and I set it to a speed which I know is unstable:

4800 mhz (cache: 4400 mhz), and 1.260v.

This laptop does not have loadline calibration so there is voltage vdroop, but there is no "live" Vcore sensor, just VID, so real vdroop is impossible to measure.

Anyway:


This laptop is highly overclocked to its max absolute limits.

 

At 4800 mhz, 1.260v, Apex Legends generated three CPU errors but did not crash:

1 x Internal Parity Error on thread #4

2x Cache Hierarchy Errors on threads #6 and #3. (the threads go from 0 to 7, one physical core+1 logical core, so threads 0 and 1 are for the first core, etc).

 

This was a 1 hour play session.

 

This is exactly what I would expect an unstable CPU to do.  

These cache hierarchy errors are also what Realbench 2.56 and Prime95 (AVX disabled) do on my desktop when they are unstable.  So this is properly expected.

 

Apex Legends did NOT crash however!  But the fact that I got *both* internal parity and Cache L0 errors (instruction register corruption basically)--but they were corrected, means that the "Unstable" CPU is actually acting as expected.

 

1.265v did not generate anything but I didn't test that long enough.

 

The 9900K desktop, when overclocked is performing completely different however, although desktops do have a loadline calibration setting to lower CPU vdroop.

Instead of throwing any L0 cache errors in Apex, it just throws out Internal Parity Errors, or just exception error crashes Apex, while every other stress test or program (like more intensive stuff like Battlefield 5, Blender, etc) runs all day (except small FFT AVX prime95. which is a 200 amp 100C temp power virus; 1344K AVX prime is more realistic).  Small FFT prime with AVX disabled also runs fine.

 

My gut is screaming "Microcode bug" but unfortunately, disabling loadline calibration on the desktop wouldn't work too well. as then you would need unsafe voltages to be stable with <>200mv of voltage droop.  I may try disabling 4 cores (e.g. turn my 9900K into a 7700K) and then overclock and disable LLC (Loadline calibration) later, and test, but this is very time consuming.  

 

I would enjoy doing any small code testing for you.  If you have a more convenient way I can contact you or where you can post anything to test, let me know.  I'm always available.

Message 82 of 532 (685 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

I’d like to add that all of these crash types you’ve explained are happening almost identically for me. I get all three types of those crashes. I have yet to see the 2F2DCA crash since the newest patch, though I haven’t played a whole lot since the patch dropped. I did crash multiple times with and without crash logs and posted a log from the new patch. The crashes I’ve got are the EXCEPTION_ACCESS_VIOLATION(write) and EXCEPTION_ACCESS_VIOLATION(read). I don’t have the error codes handy at the moment. I’ll definitely post more logs as I get them. 

 

Also want to thank @OrioStorm for all the input and support on these crashes. It’s rare to get this kind of insight and help on forums nowadays from devs. So thank you for taking time out of your day to respond, educate, and help solve these issues. Thanks to everyone else as well who’s continuing to test and provide information. I really hope a solution is found soon. Keep providing as much info as you can.

Message 83 of 532 (676 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

Same

 

crash:
{
R5Apex: 00000000002F2DCA
EXCEPTION_BREAKPOINT: 80000003
}
cpu: "Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 00000000000EBDD0
ntdll: 00000000000A3167
ntdll: 000000000008B5E6
ntdll: 000000000009F7DD
ntdll: 000000000000D856
ntdll: 000000000009E70E
R5Apex: 00000000002F2DCA
R5Apex: 00000000004C0B56
R5Apex: 00000000004C0F47
R5Apex: 00000000004BF767
R5Apex: 00000000004C1502
KERNEL32: 0000000000014034
ntdll: 0000000000073691
}
registers:
{
rax = 1
rbx = 0x000000437E8BBCC0
rcx = 0
rdx = 1
rsp = 0x000000437FC1F6E0
rbp = 1057 // 0x00000421
rsi = 0x00000236A6E10C60
rdi = 1113 // 0x00000459
r8 = 0
r9 = 61538 // 0x0000F062
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x00000232CCB35E10
rip = 0x00007FF77D892DCA
xmm0 = [ [210000, 0, 0, 0], [0x484D1400, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [1000000, 0, 0, 0], [0x49742400, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [4.9630308, 0, 0, 0], [0x409ED126, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [1042236.5, 0, 0, 0], [0x497E73C8, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [167763.47, 0, 0, 0], [0x4823D4DE, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [167763.47, 0, 0, 0], [0x4823D4DE, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 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

Message 84 of 532 (668 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

my game crashes every second to third round ..

crash:
{
R5Apex: 00000000002F2E2A
EXCEPTION_ACCESS_VIOLATION(write): 0000000000000664
}
cpu: "Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000EBDD0
ntdll: 00000000000A3167
ntdll: 000000000008B5E6
ntdll: 000000000009F7DD
ntdll: 000000000000D856
ntdll: 000000000009E70E
R5Apex: 00000000002F2E2A
!!!unknown-module!!!: 0000028CB5EC6E4C
}
registers:
{
rax = 201830 // 0x00031466
rbx = 0x000000CE4B8AF7C0
rcx = 0
rdx = 4
rsp = 0x000000CE57DDF8E0
rbp = 2050 // 0x00000802
rsi = 0x0000028DF9CA4C80
rdi = 1633 // 0x00000661
r8 = 0
r9 = 100963 // 0x00018A63
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x0000028CC0B21C90
rip = 0x00007FF66D542E2A
xmm0 = [ [2.1000008e+11, 0, 0, 0], [0x524393EC, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [1e+12, 0, 0, 0], [0x5368D4A5, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5.7614908, 0, 0, 0], [0x40B85E22, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [1.2099136e+12, 0, 0, 0], [0x538CDA3C, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [86498304, 0, 0, 0], [0x4CA4FB80, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [86498304, 0, 0, 0], [0x4CA4FB80, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 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 = [ [0.80000001, 0, 0, 0], [0x3F4CCCCD, 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


Message 85 of 532 (577 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

I strongly advise everyone in here to revert their overclocking CPU settings back to default,

and disabling Intel SpeedstepTM in their BIOS.

I am pretty sure this has solved my problem as no longer do I have these crashes with logs.

Before it used to be all the time, now I can go for days without a single crash.

 

As I read here, since the problem was CPU related I tried different things.

But as mentioned over, im 99% this has solved my problem completely.

im using 7700k and 1080 ti, if any others at least try stock clock speeds and disabling Intel Speedstep,

it would be very interesting to see if the crashes are actually stopping.

 

Message 86 of 532 (531 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

@TEZZ0FIN0 

 

My crashing stopped as well, I'm using an i9-9900K. I was stable at 4.7GHz (Turbo Boost) so I just introduced overclocking back and went to 4.8GHz to see if I'm stable. I'll report back soon.

Message 87 of 532 (518 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★ Newbie

I am using i9-9900k overclock at 5Ghz and RTX 2080 Ti.

I had the same issues before (Exception breakpoint / Exceotion access violation / no crash report)

It was my CPU problem, My CPU's voltage was so high (more than 1.5 V) because of my overclock setup and cause APEX to crash. 

I set my CPU without overclock and no crash after that. Now I set my overclock to 5 Ghz with the safest setup, and no crash until now.

Try to check your CPU's voltage and temp when your game crash, if it goes so high, I think that is the problem. 

I hope it helps. 

Message 88 of 532 (466 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

i have the same  issue

crash:
{
R5Apex: 00000000002F2E2A
EXCEPTION_ACCESS_VIOLATION(write): 0000000000000004
}
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
R5Apex: 00000000004C0B56
R5Apex: 00000000004C0F47
R5Apex: 00000000004BF767
R5Apex: 00000000004C1502
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 49546 // 0x0000C18A
rbx = 0x000000227FDCBE40
rcx = 255
rdx = 32
rsp = 0x000000227E50F930
rbp = 249
rsi = 0x0000016DC7C818C0
rdi = 1
r8 = 0x0000016CA0F14600
r9 = 249
r10 = 1
r11 = 0x00007FF7F5E45B80
r12 = 249
r13 = 447828 // 0x0006D554
r14 = 1
r15 = 0x0000016CA0F14730
rip = 0x00007FF7D1242E2A
xmm0 = [ [0, -nan, -nan, -nan], [0, -1, -1, -1] ]
xmm1 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm2 = [ [8.2800007, 0, 0, 0], [0x41047AE2, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [9.2172891e+14, 0, 0, 0], [0x585193AF, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [7.4120614e+08, 0, 0, 0], [0x4E30B7A2, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [-nan, 0, 0, 0], [-1, 0, 0, 0] ]
xmm6 = [ [1.8530154e+08, 0, 0, 0], [0x4D30B7A2, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [685584.13, 1542564.3, 2742336.5, 4284901], [0x49276102, 0x49BC4D22, 0x4A276102, 0x4A82C3CA] ]
xmm9 = [ [68558416, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x4C82C3CA, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [0.60000002, 0, 0, 0], [0x3F19999A, 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

 

 

no way to play

Message 89 of 532 (450 Views)

Re: Apex Legends Crash no error - PC (apex_crash.txt)

★★★★ Novice

@Siiega I have the SAME set up exactly. Would you mind sharing your OC settings with me setting by setting. I'd GREATLY appreciate it!

Message 90 of 532 (582 Views)

fifa-20-promo-splash

Having trouble connecting to your game?

Try these steps first to clear up any problems you may have when connecting to an EA game.

Troubleshoot and test your connection

ea-help-promo

Forget your EA Account ID or password?

Reset, update, or link your account information.

View More on EA Help