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

[Doomsayer66]

crash:
{
R5Apex: 00000000002F2E2A
EXCEPTION_ACCESS_VIOLATION(write): 00000000000003AA
}
cpu: "Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz"
ram: 24 // GB
callstack:
{
KERNELBASE: 00000000000EBDD0
ntdll: 00000000000A3167
ntdll: 000000000008B5E6
ntdll: 000000000009F7DD
ntdll: 000000000000D856
ntdll: 000000000009E70E
R5Apex: 00000000002F2E2A
!!!unknown-module!!!: 00000176A2085B2C
}
registers:
{
rax = 244196 // 0x0003B9E4
rbx = 0x0000006326D571C0
rcx = 0
rdx = 1
rsp = 0x000000633116FA40
rbp = 495 // 0x000001EF
rsi = 0x000001783B16A5E0
rdi = 935 // 0x000003A7
r8 = 0
r9 = 122158 // 0x0001DD2E
r10 = 447828 // 0x0006D554
r11 = 447828 // 0x0006D554
r12 = 448215 // 0x0006D6D7
r13 = 448215 // 0x0006D6D7
r14 = 1
r15 = 0x00000176881C0670
rip = 0x00007FF7A3B12E2A
xmm0 = [ [89982912, 0, 0, 0], [0x4CABA0F8, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [4.2848998e+08, 0, 0, 0], [0x4DCC51E8, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5.7398057, 0, 0, 0], [0x40B7AC7D, 0x00000000, 0x00000000, 0x00000000] ]
xmm3 = [ [5.1648442e+08, 0, 0, 0], [0x4DF6476A, 0x00000000, 0x00000000, 0x00000000] ]
xmm4 = [ [1988475.4, 0, 0, 0], [0x49F2BBDB, 0x00000000, 0x00000000, 0x00000000] ]
xmm5 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm6 = [ [1988475.4, 0, 0, 0], [0x49F2BBDB, 0x00000000, 0x00000000, 0x00000000] ]
xmm7 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm8 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm9 = [ [3.4028235e+38, 3.4028235e+38, 3.4028235e+38, 3.4028235e+38], [0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF, 0x7F7FFFFF] ]
xmm10 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
xmm11 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm12 = [ [0.60000002, 0, 0, 0], [0x3F19999A, 0x00000000, 0x00000000, 0x00000000] ]
xmm13 = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
xmm14 = [ [13.8, 0, 0, 0], [0x415CCCCD, 0x00000000, 0x00000000, 0x00000000] ]
xmm15 = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
}
build_id: 1554860081

[JorPorCorTTV]

I made an adjustment to my OC on my PC and played 7 hours without a single crash.

Current Rig:

i7-8700K

MSI GTX 1080

32GB G.Skill RAM

I’ve ran a fixed overclock @ 5GHz since I built the machine. I’ve never had an issue with any other games crashing including Apex Legends, until their most recent two patches. Since I could barely play the game cause I’d crash every other game, I changed my BIOS back to default settings. I set a fixed overclock @ 4.4GHz with EIST and Turbo Boost disabled. I left everything else at stock settings. I have yet to crash and have played roughly 7-8 hours. Clearly something in the newer patches is triggering the crash when the CPU is overclocked pretty high even if it’s a stable overclock. My gaming rig is cooled very well and @ 5GHz it would top out around 65c when under heavy load. Never had issues with anything (software, hardware, games, etc) until Apex Legends and the newest two patches. I run a 240Hz monitor so the drop in overclock has dropped my frame rate by a noticeable amount. In the jump ship I’d average roughly 140-150fps, I now average 95-115fps. Nothing earth shattering, but sucks that the game is having issues with high clocks. I used to run close to 240fps throughout most of the areas in the game, but now I range anywhere from 160-240fps depending on the area. Again I’d rather lose the frame rate then crash every other game. Haven’t taken the time to mess with the overclock and see if I could bump it up more, might just leave it since I have yet to crash. Hope a fix/solution is found so we can all run our higher clocks without crashes. Hope this helps some of you out. If anything changes or a crash happens I will be sure to post an update. 

[McQuak]

Fellas, this is your OVERCLOCK. Revert to factory and your problem will be solved. This has worked for 3 different people who I play with who have had similar issues. I have a 9900k that was clocked at 5.0. Crashed randomly since the release. Reverted back to stock 3.6, played 6 hours with no crash. There's something screwy with overclocking. I am a IT Engineer myself, and I cannot understand how voltage levels by itself can crash a game. It could be, in my opinon that this game prefers lower clock speeds. I've had 3 different software engineers look at my rig for a solution, none suggested it was an overclock issue. 

There is nothing more frustrating than fixing IT issues for a living and having an issue you can't solve on your PC. If there is someone above my expertise that can explain this, I'd love to learn. Thanks!!

[kelbinaaaa]

Removed the overclock on my cpu and haven't crashed since. Its the overclock guys. I have an i3-8350K oc to 4.8 and i reverted it back to base clock.

[_S7ORM-BRINGR]

---

@McQuak wrote:

Fellas, this is your OVERCLOCK. Revert to factory and your problem will be solved. This has worked for 3 different people who I play with who have had similar issues. I have a 9900k that was clocked at 5.0. Crashed randomly since the release. Reverted back to stock 3.6, played 6 hours with no crash. There's something screwy with overclocking. I am a IT Engineer myself, and I cannot understand how voltage levels by itself can crash a game. It could be, in my opinon that this game prefers lower clock speeds. I've had 3 different software engineers look at my rig for a solution, none suggested it was an overclock issue. 

There is nothing more frustrating than fixing IT issues for a living and having an issue you can't solve on your PC. If there is someone above my expertise that can explain this, I'd love to learn. Thanks!!

It's the AVX instructions the game is using, most probably. Just for the record - I play on 5.1Ghz Metro Exodus + BFV and I have never crashed. Apex is the only game that it's handling avx instructions that bad.

2019 will be the year of buggy games - Apex has problems with drivers + cpu avx instructions, battlefield V still has a problem with DXR enabled... hilarious how EA is pushing the teams to launch a game that it's not yet ready and then trying to fix it after the launch.

[Falkentyne]

@_S7ORM-BRINGR The game isn't using AVX instructions.  Ohiostorm (the programmer) said that it uses SSE2 instructions.  AVX instructions don't cause this type of error.  The game is generating "CPU Internal Parity Errors" (WHEA correctable) when overclocked and voltage isn't high enough.  The correctable errors aren't making the game crash.  It's the -uncorrectable- error that crashes the game (or the error that doesn't get caught).

I've been unable to make any other stress test or program generate an "Internal parity error".  It either BSOD's (clock watchdog timeout--meaning an actual core froze, system service exception, iRQ_L not less or equal, etc) at unstable voltage settings, or generates a "CPU Cache L0 error" (high stress programs/prime95/realbench 2.56) when temps get too high if voltage isn't high enough.  Never, ever an "internal parity error" on a core.  Even prime95 with AVX disabled (uses SSE2) doesn't do that.

We also don't know if easyanticheat is affecting or causing it somehow as well.

[Sptz87]

Once again but now it's slightly different. I'm just gonna quit playing altogether until an update comes out as it's impossible to play more than 1 game in a row :/

crash:
{
	module@00007FF9E47B0000: 0000000000CA7F9D
	EXCEPTION_ACCESS_VIOLATION(read): 0000010000000028
}
cpu: "AMD Ryzen 5 2600X Six-Core Processor           "
ram: 16 // GB
callstack:
{
	KERNELBASE: 000000000008667C
	ntdll: 00000000000A810B
	ntdll: 000000000008FD56
	ntdll: 00000000000A46AF
	ntdll: 0000000000004BEF
	ntdll: 00000000000A341E
	module@00007FF9E47B0000: 0000000000CA7F9D
	module@00007FF9E47B0000: 00000000003889FF
	module@00007FF9E47B0000: 00000000003888A6
	module@00007FF9E47B0000: 00000000003804ED
	module@00007FF9E47B0000: 0000000000BEB60A
	module@00007FF9E47B0000: 000000000125F6BC
	KERNEL32: 0000000000017974
	ntdll: 000000000006A271
}
registers:
{
	rax = 0x000001E1CC7D55F0
	rbx = 0x000001E18DC268E0
	rcx = 0x000001E1CC7B4F00
	rdx = 0x0000010000000000
	rsp = 0x0000004305ABFBD0
	rbp = 0x000001E1FCC3AC80
	rsi = 0x000001E1FCC3AC80
	rdi = 61        
	r8  = 1         
	r9  = 0x000001E4142A4901
	r10 = 0         
	r11 = 0x0000004305ABF990
	r12 = 0x000001E2515047F0
	r13 = 0x000001E18DC99BC0
	r14 = 0         
	r15 = 0         
	rip = 0x00007FF9E5457F9D
	xmm0  = [ [-1298981, 6.7402456e-43, 3.6411479e-40, 6.7402456e-43], [0xC99E9128, 0x000001E1, 0x0003F701, 0x000001E1] ]
	xmm1  = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
	xmm2  = [ [-3.0517578e-05, 2.5358734, 0, 0], [0xB8000000, 0x40224BC0, 0x00000000, 0x00000000] ]
	xmm3  = [ [136, 0, 0, 0], [0x43080000, 0x00000000, 0x00000000, 0x00000000] ]
	xmm4  = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
	xmm5  = [ [23, 0, 0, 0], [0x41B80000, 0x00000000, 0x00000000, 0x00000000] ]
	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: 1554860081

[_S7ORM-BRINGR]

---

@Falkentyne wrote:

@_S7ORM-BRINGR The game isn't using AVX instructions.  Ohiostorm (the programmer) said that it uses SSE2 instructions.  AVX instructions don't cause this type of error.  The game is generating "CPU Internal Parity Errors" (WHEA correctable) when overclocked and voltage isn't high enough.  The correctable errors aren't making the game crash.  It's the -uncorrectable- error that crashes the game (or the error that doesn't get caught).

I've been unable to make any other stress test or program generate an "Internal parity error".  It either BSOD's (clock watchdog timeout--meaning an actual core froze, system service exception, iRQ_L not less or equal, etc) at unstable voltage settings, or generates a "CPU Cache L0 error" (high stress programs/prime95/realbench 2.56) when temps get too high if voltage isn't high enough.  Never, ever an "internal parity error" on a core.  Even prime95 with AVX disabled (uses SSE2) doesn't do that.

We also don't know if easyanticheat is affecting or causing it somehow as well.

---

Yes, it is using avx instructions as well as battlefield 5. Don’t know what devs are you quoting, but you can test that by yourself by simply putting an avx offset in the bios.

[Falkentyne]

That doesn't mean that the game is using AVX instructions.
A Gigabyte bios engineer responded to this query.

He said on a brand new windows install (No updates, microsoft patches, C++ updates, etc etc), the CPU was not downclocking via AVX offset randomly unless an AVX application was running (e.g. Prime95, BF5).

Question for you.

Does Overwatch use AVX instructions?

No, it doesn't.

Yet I get an "AVX" downclock in Overwatch randomly, at the same intervals as in Apex Legends, even when I'm sitting around on the *training room* doing absolutely nothing.

Oriostorm explained that AVX instructions can look similar to SSE2 instructions (he also explained that they are related).

Read his posts in this thread and you will see that Apex does NOT use AVX instructions on its own.

Don't mean to be a * but I think a head programmer knows what instructions he's using.

Please read his posts.  I asked him directly.

[MrDakk]

UPDATE: I have not crashed in over three days and now have my i9-9900K at 4.8GHz @1.28 Vcore. This is down from 5Ghz @ 1.35 Vcore where I would crash frequently. I'm also able to run my overclocked 2080 Ti with unlimited frames (200-300 fps).

If you are running at or above 5GHz, I highly suggest down clocking or reverting back to your stock CPU settings.