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: CRASHING NON STOP

★★★★ Novice

@OrioStorm  So what you are explaining Is that there must be some logical explanation on why Windows Audio Is somewhat connected to Apex Legends.. Very weird. Well It only takes 1 minute to do. I'll make sure to update any other changes. But for now, as weird as it may sound, changing this command and switching it back on seems to have resolved my issue that Ive been struggling with since launch. That or I'm just lucky and using the Windows Audio command as a placebo effect Standard smile . Y'know one of the two.

Message 231 of 435 (292 Views)

Re: CRASHING NON STOP

EA Respawn Team

@Sptz87 this is a crash in a 3rd party DLL. I can't tell what DLL for you, but for a couple other people it seems to have been their graphics driver. It could also be antivirus, in-game overlays, and a host of other things.

Message 232 of 435 (276 Views)

Re: CRASHING NON STOP

★ Apprentice

@OrioStorm So far no CPU Parity Internal errors or crashes since the patch.  Great work!

But is Intel actually going to acknowledge that you found a hardware flaw in their processors? 

Message 233 of 435 (228 Views)

Re: CRASHING NON STOP

★★★★ Novice

Been crashing for a while and been following all of the self helps available, still crashing about 20-30% of the time, if you have any suggestions id appreciate it, attached is my most recent crash report

Message 234 of 435 (210 Views)

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

★★★★ Novice

I know you're a busy guy, any help on the cause or source of this crash would be extremely helpful

 

Thank, 

Vantyrr

 

crash:
{
module@00007FFCEB370000: 0000000000628608
EXCEPTION_ACCESS_VIOLATION(read): 0000000000000808
}
cpu: "AMD Ryzen 5 2600X Six-Core Processor "
ram: 16 // GB
callstack:
{
KERNELBASE: 000000000008669C
ntdll: 00000000000A80CB
ntdll: 000000000008FD36
ntdll: 00000000000A468F
ntdll: 0000000000004BEF
ntdll: 00000000000A33FE
module@00007FFCEB370000: 0000000000628608
module@00007FFCEB370000: 000000000063B8C1
module@00007FFCEB370000: 0000000000636E4E
module@00007FFCEB370000: 0000000000637237
module@00007FFCEB370000: 000000000053A553
module@00007FFCEB370000: 000000000053A5DF
module@00007FFCEB370000: 000000000046F9F1
module@00007FFCEB370000: 00000000003BFCCA
module@00007FFCEB370000: 00000000001C2F3A
module@00007FFCEB370000: 0000000000E2A4B2
module@00007FFCEB370000: 0000000000DA705B
module@00007FFCEB370000: 000000000037A529
module@00007FFCEB370000: 000000000019A8F6
module@00007FFCEB370000: 0000000000451D25
module@00007FFCEB370000: 00000000004EE5B7
module@00007FFCEB370000: 00000000012A066C
KERNEL32: 00000000000181F4
ntdll: 000000000006A251
}
registers:
{
rax = 4
rbx = 2048 // 0x00000800
rcx = 2382 // 0x0000094E
rdx = 14
rsp = 0x00000056F4BED300
rbp = 0x00000056F4BED400
rsi = 0
rdi = 81
r8 = 77
r9 = 0xFFFFFFFF
r10 = 1
r11 = 0x000001FFB1638AB0
r12 = 0x000001FFB1555078
r13 = 81
r14 = 0
r15 = 0x000001FFB1639448
rip = 0x00007FFCEB998608
xmm0 = [ [17.25, 0, 0, 0], [0x418A0000, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [57.142857, 0, 0, 0], [0x42649249, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [57.142857, 0, 0, 0], [0x42649249, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [57.142857, 0, 0, 0], [0x42649249, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [0.5, 0, 0, 0], [0x3F000000, 0x00000000, 0x00000000, 0x00000000] ]
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: 1557879477

Message 235 of 435 (166 Views)

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

EA Respawn Team

@Vvantyr those crashes are not in Apex, but in some 3rd party DLL. Unfortunately, Windows didn't tell us which. I would guess the graphics card driver first, but it could be many other things too, such as antivirus or in-game overlays or video capture or even the OS.

Message 236 of 435 (160 Views)

Re: CRASHING NON STOP

EA Respawn Team

@Falkentyne, thanks for the confirmation!

 

As for Intel acknowledging the hardware flaw... I personally doubt that will ever happen. They weren't that interested in looking into it for us without an easy repro. And you saw how they dismissed your report with "it's their software problem, our CPUs are great" (to paraphrase). My skeptical self thinks they are a large corporation that would see admitting a rare flaw as only harmful to themselves.

 

So, we called them out a bit in our patch notes, but I doubt it will go any further than that. Which I think is a shame, really. They had a repro case to find and fix a flaw in their designs, even though it rarely triggered. Looking into it could make all their future CPUs even more solid.

 

But even if Intel does fix this flaw in firmware, I'm glad we have a proven workaround. I expect that most people don't bother updating their CPU firmware, unless Microsoft forces it on them with an automatic Windows update.

 

I did leave a way for the game to run the old code that would crash Intel chips, but I didn't investigate whether the compiler generated the same assembly. You can get the old C++ code with setting "old_gather_props" to 1 in the console, or by passing "-force_old_gather_props" on the command line. I'll hit up Intel again and see if they care to fix this; if they don't, I'll remove the old behavior in a future patch.

Message 237 of 435 (154 Views)

Re: CRASHING NON STOP

★★ Novice

@OrioStorm So i reinstalled windows and i've now played like 10 games without any crashes, drastic to do it but so worth it! Standard smile

Message 238 of 435 (144 Views)

Re: CRASHING NON STOP

★★★★ Novice

Hi guys.

First time posting. Can anybody help with this:

 

crash:
{
module@00007FF8267D0000: 000000000009C5D3
EXCEPTION_ACCESS_VIOLATION(read): FFFFFFFFFFFFFFFF
}
cpu: "Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 000000000008667C
ntdll: 00000000000A81CB
ntdll: 000000000008FD56
ntdll: 00000000000A477F
ntdll: 0000000000004BEF
ntdll: 00000000000A34EE
module@00007FF8267D0000: 000000000009C5D3
}
registers:
{
rax = 0x00007FF8275229A0
rbx = 0x0000026A5330CC50
rcx = 0x0191104E069064A6
rdx = 0x0000026A679BF970
rsp = 0x000000D29AE7F318
rbp = 131072 // 0x00020000
rsi = 0
rdi = 0x0000026A532C9DA0
r8 = 0x000000D29AE7F328
r9 = 0x00007FF827519628
r10 = 0x00007FF83257F924
r11 = 0x000000D29AE7F330
r12 = 0
r13 = 0
r14 = 0x0000026A532C9AB0
r15 = 0x000000D29AE7F7A0
rip = 0x00007FF82686C5D3
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: 1557879477
00000000004C3136
R5Apex: 00000000004C3527
R5Apex: 00000000004C1D47
R5Apex: 00000000004C3AE2
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 0x8007000E
rbx = 0x0000026A679BF708
rcx = 0x0000026A677D83C0
rdx = 77824 // 0x00013000
rsp = 0x000000D29820C160
rbp = 0x9006A733536E7FC1
rsi = 0x8007000E
rdi = 0x668DECBFDE718CC7
r8 = 256 // 0x00000100
r9 = 0x0000026A677D83C8
r10 = 0x0000026A677D83C8
r11 = 256 // 0x00000100
r12 = 256 // 0x00000100
r13 = 0x0000026A608E38F0
r14 = 0x000000D29820C230
r15 = 0x0000026A608E3958
rip = 0x00007FF826871677
xmm0 = [ [0, 2.4060295e-41, 0, 0], [0, 17170, 0, 0] ]
xmm1 = [ [5.6051939e-45, 2.8025969e-45, 1.4012985e-45, 4.2038954e-45], [4, 2, 1, 3] ]
xmm2 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm3 = [ [-0.5, 0, 0, 0], [0xBF000000, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [3.0517578e-05, 0, 0, 0], [0x38000000, 0x00000000, 0x00000000, 0x00000000] ]
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: 1557879477

Message 239 of 435 (128 Views)

Re: CRASHING NON STOP

EA Respawn Team

@MrGregert, like a few posts before, those crashes are not in Apex, but in some 3rd party DLL. Unfortunately, Windows didn't tell us which. I would guess the graphics card driver first, but it could be many other things too, such as antivirus or in-game overlays or video capture or even the OS.

Message 240 of 435 (124 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