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

@OrioStorm 

I want to thank you GREATLY for the time that you've spent here.  It's VERY rare these days for programmers and developers to engage with gamers like you are doing, and this is very appreciated.  Back during the glory days of Usenet (before the flight sim and space sim genres crashed), this was a lot more common.  3dfx devs posting in the 3dfx groups, flight sim pilots and programmers posting, and all of this before the Ultima IX Fiasco too...

In my case, all crashes are purely due to overclocking.  And yes, I found out that if I ever get a random CTD (no error or log) or exception breakpoint (log), if I keep playing, eventually I will get a "Internal Parity Error" on any one of the 16 threads (8 physical cores), although it can sometimes take hours to happen.   Once I increase vcore to a point or lower clockspeed to where these "Internal parity errors" NEVER happen, the game never crashes, ever.

Is it possible that the "Anticheat" is putting extra load on the CPU?  Because I've never seen a game which will cause errors like this if there is is any sort of instability anywhere, not even Battlefield 5.  Apex Legends is indeed the gold standard for testing CPU stability.

That being said, the people who are crashing at *STOCK* speeds concerns me greatly, as that should NOT be happening.  Intel validates their chips to run up to 100C at the max single core turbo boost frequency and the max 4, 6 or 8 core turbo boost for that SKU.  They should never crash, even with a power virus like Prime95 small FFT FMA3.

I want to ask EVERYONE here who is crashing at STOCK SPEEDS (NOT OVERCLOCKED):

1) Are you using windows version 1809 or newer?

2) is your CPU a 7700K or newer?

3) Are you using SPECTRE AND MELTDOWN mitigations enabled?

4) Is your Bios updated and your CPU microcode current?

If the answer to all four is YES, can you please do the following?

Please go here, download this:

https://www.grc.com/inspectre.htm

then disable all protections.

Then run the game at your stock CPU settings and see if you crash anymore.

Please report back.  This is important.

There were reports of early mitigation protections causing internal parity errors on several intel SKU's *even at idle*, and It may be possible you guys are running into a microcode bug which is making the game crash

The easiest way to determine if Intel's meltdown protections are making the game crash are to simply disable them.

This has NO effect if you are using a windows version which is not protection aware (like 1709 or older).

tl;dr: microcode bugs can cause strange problems.  Intel has *PULLED* early microcodes for Spectre protection in the past because in SOME CASES they were actually *DESTROYING* CPU's--yes--DESTROYING them.  (Prema, who is a bios modder over on notebookreview's forums, encountered this when testing early protection microcode--that's why some of you may remember those "rolled back" intel microcode/bios patches and windows updates...