CRASHING NON STOP

[Vvantyr]

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

[HarlowAhimsa]

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

[Gumpyyy]

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.

[macchky]

ramdomly crashing

My spec:

Ryzen 1700

Asus Strix Vega 56

Mem 24GB

[OrioStorm]

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

[OrioStorm]

@macchky @Gumpyyy, your crashes are in third party DLLs, and Windows wasn't able to tell us their names. So unfortunately, I can only give you general advice. We don't have a way to rule out any specific DLL, but I'd say this is most likely a crash in your graphics driver, since that's one of the few DLLs that's known to create its own threads. But it could also be a lot of other things.

[OrioStorm]

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

[MrGregert]

@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

[Falkentyne]

@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

[OrioStorm]

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