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

Still getting crashes after the update...

crash:
{
	module@00007FF849D00000: 000000000036878A
	EXCEPTION_ACCESS_VIOLATION(read): 000000000000B880
}
cpu: "AMD Ryzen 5 2600X Six-Core Processor           "
ram: 16 // GB
callstack:
{
	KERNELBASE: 000000000008667C
	ntdll: 00000000000A81CB
	ntdll: 000000000008FD56
	ntdll: 00000000000A477F
	ntdll: 0000000000004BEF
	ntdll: 00000000000A34EE
	module@00007FF849D00000: 000000000036878A
	module@00007FF849D00000: 00000000003697B2
	module@00007FF849D00000: 0000000000CCC5D2
	module@00007FF849D00000: 0000000000389BCF
	module@00007FF849D00000: 0000000000389A76
	module@00007FF849D00000: 00000000003816BD
	module@00007FF849D00000: 0000000000BED65A
	module@00007FF849D00000: 000000000126191C
	KERNEL32: 0000000000017974
	ntdll: 000000000006A271
}
registers:
{
	rax = 0         
	rbx = 0x000001E326609FA0
	rcx = 0         
	rdx = 0x000000DBC70BF260
	rsp = 0x000000DBC70BF1F0
	rbp = 0x000000DBC70BF2F9
	rsi = 0x000001E382D60330
	rdi = 0         
	r8  = 0         
	r9  = 0x000001E40B0941C0
	r10 = 0x000001E375C95640
	r11 = 0         
	r12 = 0         
	r13 = 0         
	r14 = 0x000000DBC70BF360
	r15 = 0         
	rip = 0x00007FF84A06878A
	xmm0  = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
	xmm1  = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
	xmm2  = [ [-0, 2.1861458, 0, 0], [0x80000000, 0x400BE9D0, 0x00000000, 0x00000000] ]
	xmm3  = [ [136, 0, 0, 0], [0x43080000, 0x00000000, 0x00000000, 0x00000000] ]
	xmm4  = [ [1, 0, 0, 0], [0x3F800000, 0x00000000, 0x00000000, 0x00000000] ]
	xmm5  = [ [18, 0, 0, 0], [0x41900000, 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: 1557879477

@Sptz87, that's something besides Apex crashing and taking down Apex with it. Unfortunately, Windows didn't tell us the name of the DLL that crashed, so I can't tell you WHAT is crashing.

@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 🙂 . Y'know one of the two.

@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.

@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? 

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

@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.

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

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

@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.

@OrioStorm, Ok. This is a clean install of Windows. I have disabled all 3rd party software, except for Logitech G Hub. I do not have antivirus-software, only Windows Defender. Should I try a new graphic card driver or what?

Yes, I'd recommend checking for an updated graphics driver.

@OrioStorm 

Thank you.

Tried the command line launch parameter and the errors are back! 🙂

5 minutes of play at 1.270v, LLC6, 5 ghz:

A corrected hardware error has occurred.

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

The details view of this entry contains further information.

(How do you open the console anyway?).

To developers:

About the problem in the lobby "The team is not ready" When a check mark is not set and your team starts without you, do the developers know?

I tried on different systems and on different hardware, with different Internet and different processors, from the whole team I have such a problem. I think on some part of windows, maybe an update package or some kind of video driver module.
Another problem is:
In the settings of the video does not go to make the quality of the models to low, put back to high

It feels like after the end of the match the lobby doesn’t get to the end, if you stand in the lobby for a long time before the match, the problem with checkboxes appears again, you have to leave the team and come back. The solution to the problem, I think will be adding the function "Restart Lobby"

Sorry for writing to you, I don’t know how else to write 🙂

@Falkentyne thanks for proving that the bug happens if we don't change anything!

I'm actually not sure if we ship the console in the retail game or not, or if we ship it disabled and you have to do something to enable it. If it's shipped and enabled, you press the ~ key to open it. If it's not shipped, you can only access it indirectly through the command line or possibly config files.

@OrioStorm what's interesting is that the GAME hasn't actually crashed yet.

It's just triggering CPU Internal Parity Errors and correcting them, but not crashing (yet).

I think the compiler possibly changed something also.

It's acting like the original pre-pre patch, when I was getting parity errors but almost never crashes (rare).

then the patch after that (where you started doing logs) it crashed a lot more often.

But this is just random guessing, left to the realm of programmers.

hey man, with the turning off windows audio and turning it back on, i went 2 days with no crash and that streak is now over. A little more help would be awesome

crash:
{
R5Apex: 00000000002E84F0
EXCEPTION_ILLEGAL_INSTRUCTION: C000001D
}
cpu: "AMD Ryzen 5 2600X Six-Core Processor "
ram: 16 // GB
callstack:
{
KERNELBASE: 000000000008667C
ntdll: 00000000000A81CB
ntdll: 000000000008FD56
ntdll: 00000000000A477F
ntdll: 0000000000004BEF
ntdll: 00000000000A34EE
R5Apex: 00000000002E84F0
R5Apex: 00000000004C374D
R5Apex: 00000000004C3136
R5Apex: 00000000004C3527
R5Apex: 00000000004C1D47
R5Apex: 00000000004C3AE2
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 0x00000187C9DE6900
rbx = 0x0000018700FC96D0
rcx = 0x0000018760F55850
rdx = 0x00000187C9DE6E54
rsp = 0x0000004131E0FA00
rbp = 0x00000187C9DE6D50
rsi = 0x0000018760F55850
rdi = 1
r8 = 104
r9 = 1
r10 = 0
r11 = 0x0000018760F67908
r12 = 1
r13 = 0
r14 = 0x00007FF6712D9CF0
r15 = 0
rip = 0x00007FF64EDE84F0
xmm0 = [ [11563313, 0, 0, 0], [0x4B307131, 0x00000000, 0x00000000, 0x00000000] ]
xmm1 = [ [3614385.3, 0, 0, 0], [0x4A5C9AC5, 0x00000000, 0x00000000, 0x00000000] ]
xmm2 = [ [5734.8745, 0, 0, 0], [0x45B336FF, 0x00000000, 0x00000000, 0x00000000] ]
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 = [ [3.4028235e+38, 0, 0, 0], [0x7F7FFFFF, 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

PLS HELP ME 

crash:
{
ss5lsp: 00000000000016DC
EXCEPTION_ACCESS_VIOLATION(read): 0000000000000000
}
cpu: "Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz"
ram: 16 // GB
callstack:
{
KERNELBASE: 00000000000E9650
ntdll: 00000000000A88CF
ntdll: 0000000000091196
ntdll: 00000000000A4ECD
ntdll: 0000000000026058
ntdll: 00000000000A3DFE
ss5lsp: 00000000000016DC
WS2_32: 000000000000F1A1
R5Apex: 00000000003B0792
R5Apex: 00000000003B11C4
R5Apex: 00000000003B2BDF
R5Apex: 00000000003AFD15
KERNEL32: 0000000000013574
ntdll: 000000000006CB81
}
registers:
{
rax = 0x00007FF808BA16B0
rbx = 0x00000181A316E100
rcx = 3520 // 0x00000DC0
rdx = 0x000000043196A138
rsp = 0x0000000431969FF0
rbp = 0x000000043196A119
rsi = 0
rdi = 0
r8 = 1
r9 = 0x000000043196A124
r10 = 0x00007FF808BA16B0
r11 = 0x00000181B543CA70
r12 = 0
r13 = 623871 // 0x000984FF
r14 = 88
r15 = 0
rip = 0x00007FF808BA16DC
xmm0 = [ [1.0682318e-05, 1.0489932e-08, 1.3542448e-05, 4.1729558e+21], [0x37333835, 0x32343736, 0x3763345F, 0x63623765] ]
xmm1 = [ [4.1729558e+21, 8.4268981e-07, 6.6757474e-07, 3.5873241e-43], [0x63623765, 0x35623534, 0x35333363, 0x00000100] ]
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

Just gonna come back to report I made a few days ago with some DLL taking down Apex with it. Ended up disabling Origin's overlay and the crashing I've experienced randomly during the boot-up video has gone away completely.

@HarlowAhimsa, your crash is in the DLL "ss5lsp". I saw one other user report that same crash, but I can't find it now.

This was called from WS2_32.dll, which is the Windows OS's "Windows Sockets 2" library, which is related to networking. So, this appears to be a crash inside your network adapter's driver. However, a web search for "ss5lsp.dll" doesn't help me discover anything useful.

Anyway, this appears to be a crash in your network adapter driver, so the first thing to do is to make sure that driver is up-to-date.

@Vvantyr your crash is unique. It's the first time I've ever seen a crash report where an AMD CPU tried to execute starting in the middle of an instruction. The call stack shows that the caller didn't tell it to go to that instruction, so I don't know why it would do that. I looked at the code for the function, and I don't see anything suspicious in there.

I'd be interested in seeing any more crash reports you get, to see if there's any sort of pattern.

@OrioStorm, So now I have uninstalled absolutely everything. The only thing remaining is Logitech G Hub and Battlefield V. I did a clean uninstall of the graphics driver and installed to latest version. The game ran good for about 1 hour, then it crashed. It keeps switching between Bluescreen, crash without error and crash with error. I have to mention one thing, and that is when I reinstalled the graphics driver, I got an error message saing that "GameManager32.dll" is not designed to run in Windows or contains an error.

After googling I found a solution to delete the two .dll files in two different folders. After this, the game started without problems. The bluescreen that appeared was this.

And after this it crashed with a text file stating this:

crash:
{
module@00007FFE5CAB0000: 00000000000D5E3A
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@00007FFE5CAB0000: 00000000000D5E3A
module@00007FFE5CAB0000: 00000000000EADD5
module@00007FFE5CAB0000: 00000000000ECE9F
module@00007FFE5CAB0000: 00000000000C932A
module@00007FFE5CAB0000: 00000000000C9E2A
module@00007FFE5CAB0000: 00000000000C90BD
module@00007FFE5CAB0000: 00000000000A5714
module@00007FFE5CAB0000: 000000000006978F
module@00007FFE5CAB0000: 00000000007D0699
module@00007FFE5CAB0000: 00000000007D7DDA
module@00007FFE5CAB0000: 000000000002CFA6
module@00007FFE5CAB0000: 000000000002E33F
module@00007FFE5CAB0000: 00000000007AD02F
module@00007FFE5CAB0000: 00000000007A17B9
module@00007FFE5CAB0000: 00000000009418D4
KERNEL32: 0000000000017974
ntdll: 000000000006A271
}
registers:
{
rax = 0x000001382272F1D8
rbx = 0x0000000E7DFDDB40
rcx = 0x000001382272E538
rdx = 5
rsp = 0x0000000E7DFDD190
rbp = 0
rsi = 0x000001382272DB78
rdi = 0x0000000E7DFDDB40
r8 = 1
r9 = 0
r10 = 0x000001382272F578
r11 = 0x000001382272DCB8
r12 = 0
r13 = 0x0000013822720040
r14 = 1261 // 0x000004ED
r15 = 0x0000013822728E60
rip = 0x00007FFE5CB85E3A
xmm0 = [ [2.0458958e-43, 0, 0, 0], [146, 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

@OrioStorm Hi, I got a new crash today.

Any idea what this is? 
Never seen this code before.

crash:
{
R5Apex: 00000000004C2EFD
EXCEPTION_ILLEGAL_INSTRUCTION: C000001D
}
cpu: "Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz"
ram: 32 // GB
callstack:
{
KERNELBASE: 0000000000006913
ntdll: 00000000000ADA9D
ntdll: 0000000000096476
ntdll: 00000000000AA08D
ntdll: 0000000000019C58
ntdll: 00000000000A910E
R5Apex: 00000000004C2EFD
R5Apex: 00000000004C35A7
R5Apex: 00000000004C1D47
R5Apex: 00000000004C3AE2
KERNEL32: 0000000000012774
ntdll: 0000000000070D61
}
registers:
{
rax = 0x40C6000000000000
rbx = 125
rcx = 0xFFC0000000000000
rdx = 125
rsp = 0x0000009343D1F630
rbp = 0x0140F0D2
rsi = 65535 // 0x0000FFFF
rdi = 0x00007FF7BF2DF100
r8 = 0x40C600007D00007D
r9 = 0
r10 = 0
r11 = 13
r12 = 20
r13 = 0
r14 = 0xFFFF000000000000
r15 = 0x40C0000000000000
rip = 0x00007FF7989A2EFD
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

@Falkentyne that's executing the middle of an instruction. The instructions start at 4C2EF6 and 4C2EFE. The state of the registers is inconsistent with it having recently executed the instructions immediately before here. The most likely causes of jumping to the middle of an instruction are ⚽ a function pointer being corrupt, 🏈 the return address on the stack getting clobbered, or 🏀 a computed jump (sometimes used to implement a switch statement) had an invalid input. But I don't see anything in the registers that would point me to any of these three having happened.

So, I can't really dig in any further. This is the only time I've seen this crash location also. If it starts to be common, we'll invest more effort.

On the bright side, our crash rate appears to be really down now. From my limited sampling, most actual crashes are now in 3rd party DLLs.

@OrioStorm I think it's just from me decreasing my CPU Voltage too low.

Was at 1.270v (Loadline calibration level 6) @ 5 ghz.  Went to 1.265v (5mv lower) and got that crash.

So back to 1.270v I go !

tl;dr; Trying to find my minimum stable voltage where Apex won't generate any errors or crashes post patch.

I already know 1.275v is stable so been doing 1.270v then went to 1.265v just now.

Pre-patch it was 1.315v (Loadline calibration=turbo/level 6)