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

@OrioStorm it's really hard to tell. Because there's also the season 2 patch in effect as well. So it's not apples to apples anymore.

I'll do more testing. I actually modded my bios (thanks to someone else) and inserted the BE microcode so I can't revert to AE anymore.

That being said, on the 'old' patch, with -force_old_gather_props installed, 5 ghz @ 1.270v + Turbo loadline calibration wasn't stable.

So far, on the new patch with BE Microcode, it is, at those settings (a few hours of play, no WHEA's), but I also temporarily reverted to AE microcode post flash (when I had updated it using VMWare) and it didn't crash either. But 5.2 ghz @ 1.335v (LLC Turbo+Hyperthreading disabled) logged a CPU internal parity error on the lobby load screen on AE. Going to test that again right now actually with BE.

To be honest since the patch version changed, I no longer have an apples to apples comparisoin anymore.

If i had to bet money on it, I'd say it was the patch itself that improved things with the old code path, not the microcode. I'll do a bit more testing though.

*Edit* played for another hour at 5.2 ghz @ 1.335v. No Internal Parity Errors. So I've had one (with BE microcode) in about 2 hours of play at that speed.

But then I *removed* the old code path, went into lobby and alt tabbed to read forums. Got an "internal parity error" while alt tabbed 🙂

I'll continue testing though.

is the old code path still working?

-force_old_gather_props

BE microcode is new though. Released last month. AE microcode came out in *February*. And the sad thing is Gigabyte released new bioses for their Z390 boards saying "new microcode to fix a security issue" yet that "new" microcode is AE, which is old (but still newer than A2 which GB Had on the F8 bios)---sad.

9 Replies

Replies have been turned off for this discussion

OrioStorm
EA Staff (Retired)
6 years ago
@Falkentyne thanks for the thorough update. We haven't changed -force_old_gather_props.
OhMyGodNani
6 years ago
Hey hows it going. Hope you can help me out, ive tried reinstalling nvidia drivers (full wipe/custom install without the HD audio driver and then express) and I have nothing overclocked.
ryzen 2700x
asrock x470
16gb ddr4 3000mhz
gtx1080
apex_crash.txt2 KB
Rellik_pt
6 years ago
Still crashing even after the new server update
crash:
{
R5Apex: 0000000000406E3C
EXCEPTION_ACCESS_VIOLATION(read): FFFFFFFFFFFFFFFF
}
cpu: "AMD Ryzen 7 2700X Eight-Core Processor "
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000FFB5A
ntdll: 00000000000A4AB2
ntdll: 000000000008C676
ntdll: 00000000000A119F
ntdll: 000000000006A229
ntdll: 000000000009FE0E
R5Apex: 0000000000406E3C
R5Apex: 00000000003CBF51
R5Apex: 000000000022DF6E
R5Apex: 000000000022E326
R5Apex: 000000000026B52D
R5Apex: 00000000003DA78F
R5Apex: 000000000045D8ED
KERNEL32: 0000000000017BD4
ntdll: 000000000006CE71
}
registers:
{
rax = 65281 // 0x0000FF01
rbx = 0
rcx = 0x00080244CBBBC700
rdx = 0
rsp = 0x000000477BCE7A50
rbp = 0x000000477BCE7B11
rsi = 57
rdi = 0
r8 = 0x000000477BCE7A80
r9 = 0x00007FF64C6EF290
r10 = 0
r11 = 0
r12 = 1950 // 0x0000079E
r13 = 0xFFFFFFFF
r14 = 1
r15 = 0x79000A11
rip = 0x00007FF62A186E3C
xmm0 = [ [-nan, -nan, -nan, -nan], [-1, -1, -1, -1] ]
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: 1561694190
ICrashOften_Sry
6 years ago
not sure if this is the right thread but i have been crashing all the time since the very behinning of the game without a single crash report ever being generated.
origin is enabled in apex, origins diagnostics/ingame protocol option is also enabled, after every crash i search for apex_crash.txt with everything.exe and never found one
how do i fix this?
OrioStorm
EA Staff (Retired)
6 years ago
@OhMyGodNani thanks for the report. I've posted a bug for this. It looks like a bug in our code that we should be able to fix in a future patch.
OhMyGodNani
6 years ago
Hey just wanted to let you know that bringing my ram timing to stock fixed this problem. My ram was overclocked with an xmp profile. I've played a few dozen stable games after that change.
Not sure if that helps the problem for patching it. my system was stable with overclocked ram previously but not a big deal.
OrioStorm
EA Staff (Retired)
6 years ago
@ICrashOften_Sry - a crash that doesn't generate a report is probably a GPU crash. The apex_crash.txt should capture all CPU crashes, but we don't get any useful info on a GPU crash.
I'm not really aware of any good way to track those down. You can try contacting the support for your video card maker and see if they have any tips?
OrioStorm
EA Staff (Retired)
6 years ago
@Rellik_pt you got a crash where the pointer in RCX looks like it had a random bit set and made it invalid.
actual: 0x00080244CBBBC700
correct: 0x00000244CBBBC700
When it referenced the invalid pointer, it crashed. Unfortunately, there isn't much to go on to figure out WHAT set that invalid bit, so I don't think I can fix this without a repro case.
Rellik_pt
6 years ago
i have no ideia what that means, this crash only happens everytime i go fullscreen in the middle of a battle. i normaly play borderless but the game sometimes start being choppy framerate so i change to fullscreen and that stops, but after a while randomly it crashes.