Help us improve Answers HQ! Take Survey No, Thanks

Crash after update Season 1

by Gioxor1
Reply

Original Post

Re: Crash after update Season 1

EA Respawn Team

These are all the Intel crash (see post 1984) that is worked around by lowering clock speed. Unfortunately, I still don't know when a patch with a software workaround will go live:

@spackmanbr @pigfaceguy @GudLuckTurret @BartukTheGreat @solrflar @zzilis

Message 2051 of 2,183 (316 Views)

Re: Crash after update Season 1

EA Respawn Team

These are crashing in something besides Apex, but it's bringing Apex down with it. See post 1985 for more information:

@BuzzNose12 @karntuso @StTonyG @PotatoePEECEE @TheRipMasta 

Message 2052 of 2,183 (305 Views)

Re: Apex Legends Crash Report.

EA Respawn Team

@kkusson, I just looked into this. I can't figure it out either. This is not related to any crash I've seen before. But, I'll tell you what I figured out.

 

You are crashing trying to execute an instruction at 34E40A. That's in the middle of an instruction starting at 34E409, so it shouldn't do that. The CPU should only execute the start of an instruction.

 

This is at the end of a recursive function (you can see the same address on the stack 7 times). The instruction at 34E409 is supposed to jump to a leaf handler for 0-7 items. Based on the register rax in the dump, I can see that you had 3 items, so it should jump to the 3-item handler.

 

The easiest way to execute the wrong instruction is for code to clobber the return address on the stack. However, I can tell that all the return addresses still on the stack are valid. In particular, the next return address is valid, so I can see what function that called. That should be the current function, and the crashing address is in there, even though it's in the middle of an instruction. Then, for return address corruption, the current function would have had to call another function that corrupted its return address. But the current function was actually reached by a recursive call, meaning the function called itself. In fact, the only function it calls is itself, and I see no way this code could corrupt a return address on the stack.

 

If you have more copies of apex_crash.txt from other crashes, that could be useful. Otherwise, I unfortunately don't see anything else I can do.

Message 2053 of 2,183 (303 Views)

Re: EXCEPTION_ACCESS_VIOLATION(write): 00007FF76F74F004

EA Respawn Team

@TucoIlBrutto, thanks for this report. This is a unique crash. I've added a bug for it to be addressed by the appropriate engineer.

Message 2054 of 2,183 (301 Views)

Re: Crash after update Season 1

★★★★ Novice

Thank you for confirming this.  I should have mentioned that I removed my overclock recently, so that is likely what has made my game more stable.  I sure would like to get that overclock back though...

Message 2055 of 2,183 (300 Views)

Re: Apex Legends Crash Report.

★★ Newbie

Thank you OrioStorm ! I do not have any other Crash files. That's the only one and seems like the crash. txt files are overwriting on previous crash txt file.

 

Thank you !

 

 

Message 2056 of 2,183 (274 Views)

Re: Crash after update Season 1

[ Edited ]
★★★ Novice

@OrioStorm

So basically, what you're telling me is there's no fix as of yet?

 

I feel like I wasted my $40 and should probably take a break from the game at this time..

 

I sure hope there's an upcoming patch for these issues as I do enjoy the game a great deal.

Message 2057 of 2,183 (248 Views)

Re: Crash after update Season 1

★★ Newbie
Message 2058 of 2,183 (226 Views)

Re: Crash after update Season 1

★★ Novice

I crash approximately every 2-4 games.

Message 2059 of 2,183 (173 Views)

Re: Crash after update Season 1

★★★ Newbie

Seems to fix the issue! Thank you.

Message 2060 of 2,183 (214 Views)
Twitter Stream