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

@OrioStorm I just got the weirdest error ever.

Check this one out (an "execute" error).

It said something like the CPU memory controller didn't want to execute one address while the CPU wanted (or didnt want) to execute another.

@Falkentyne, that's another bug that tended to happen in the same function. The crash referenced these two memory addresses:

0x00007FF79DD561B3 -- this is the memory address of the next instruction to execute

0x00007FF78CD061B3 -- this is the memory address that it claimed it did not have permission to execute

You'll notice that those numbers are very similar, except some of the lower 32 bits that are set in the top number are clear in the bottom number. For example, look at the first place the two numbers differ. 9D in hex is 1001_1101 in binary. 8C in hex is 1000_1100 in binary. The least significant bit goes from 1 to 0 in each of those digits. Later, 5 becomes 0, which goes from 0101 to 0000 in binary. (You can put your Windows Calculator into Programmer mode and let it do the conversions between decimal / hex / binary for you if you want to see for yourself.)

So, this is another example of a CPU not behaving properly. The instruction that the CPU wants to execute is the instruction at RIP, by definition. (RIP = Instruction Pointer Register. In 16-bit days it was just IP, then in 32-bit days it became EIP for Extended Instruction Pointer, and in 64-bit days it's RIP.) But it crashed saying it didn't have permission to execute an instruction NOT at RIP, which is a memory location it shouldn't have wanted to execute in the first place.

The patch that includes the work around for the Intel CPU crashes went live at 10 AM Pacific time today. It is version 1.1.3.

I'd be very interested in learning whether this fixes the crashes for everybody, even without lowering CPU speed.

had a crash on every game played since the release of the patch, first was a freeze with no crash report, second the program closed itself after a match, third generated a crash report, 2 other reports enclosed taken from today, have re-installed countless times, re-installed windows as well as other work arounds. hopefully get fixed soon.

@Ruon-21, the first two crashes are from the previous patch.

The first crash is in our loading code; it is populating memory, but the OS says it doesn't have permission to write to that memory. I don't know why it would crash this one time and work every other time; I'll have to see if there are any further clues in the crash info.

The second crash from the prior patch is inside the Windows OS called from inside DX11 called from when Apex was freeing a texture that it no longer needed in memory. Unfortunately, I can't really figure out anything more from this crash since it happened so deep inside 3rd party code.

The last one is from 1.1.3, but it is in an unknown DLL. Basically, we asked Windows what the DLL name was, and it said "I don't know". I can tell that this is not a thread that Apex creates, because there are no entries in "R5apex" at the bottom between "KERNEL32" and "module@...". The "KERNEL32" line is when the OS creates the thread that crashed, and the "module@..." line is the entry point in whatever 3rd party DLL it was that crashed for you. Unfortunately, if Windows can't tell us the name of the DLL that crashed, we can't tell you how to avoid the crash.

@OrioStorm 

Thank you for the feedback.

That crash I mentioned the other day that you commented on happened at 5.1 ghz @ 1.360v bios setting (loadline calibration =Turbo, so load voltage was probably about 1.340v).

I did another run after that crash at the same voltage that day (same windows session) and got an "CPU Internal Parity Error" (WHEA Correctable).

Not 100% sure this is the exact timestamp of that error, but this happened *after* the crash I had posted.  

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 10

The details view of this entry contains further information.

so whatever Intel bug that was being generated was changing bits somewhere, and if it was "corrected", the game would continue playing and a WHEA would be logged.  If it wasn't corrected, then you get one of those two 2F2DA breakpoints or something like as you mentioned.

With the new patch out:

I *REDUCED* the cpu core voltage at 5.1 ghz from 1.360v to 1.335v.
Been playing 1 hour 40 minutes.

ZERO crashes so far.

ZERO WHEA "Internal Parity Errors" generated.

So far it's been an improvement but I've seen "long sessions" in the past without WHEA parity correctable errors, then suddenly the game crashed when I got my hopes up.

But this is an improvement.  I'll keep playing and keep testing the results.  But preliminary answer is: "Good so far!"

Is Intel acknowledging this bug in their firmware?  I know how stubborn Intel can be...

I know how to get new microcode ahead of time (before it's put into bioses), that's easy: Just download VMWare microcode updater and the microcodes as discussed here:

https://www.win-raid.com/t3355f47-Intel-AMD-amp-VIA-CPU-Microcode-Repositories-Discussion.html

and then the DAT to bin converter over here:

https://onedrive.live.com/?authkey=!AE_9xt1wnaLT5lk&id=11F4002E1134F403!617750&cid=11F4002E1134F403

Then you can download the microcode patcher itself (that has a current DAT file conversion already) from here:

https://mega.nz/#!gZBzBIib!wNZwqhegXl1FME7h5HLhsfAT55Xk_EyTN6QNBo7l6Qo

For new microcodes that are not in "Microcode.dat", you can convert the bin files from the archives to a new DAT file, then patch it with the mega microcode vmrware updater, after you rename your new dat file to "microcode.dat" and copy it into the cpucodeupdater folder manually. 

Anyway tl;dr: it's a definite improvement *so far*.  I'll keep playing all day until I find how stable it is.  

@OrioStormthanks for the super fast reply man, kudos! ill post any more crash reports I get, have since repaired the game and not had a crash since, but its so unpredictable I'm sure more will occur

A crash... Again.....

@POF_Wyjakx, the CPU reported an illegal instruction at an address that has a legal instruction. This is in code that runs every single frame, where the instructions aren't changing. This shouldn't be possible if everything is working right, so the most likely causes are hardware issues, such as overclocking or memory that's slowly dying.

Are you overclocking your CPU by chance?

This is the error I get. Nothing fixes it. I have tried everything and it had gone away and now it came back again!!!