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

by OrioStorm
Reply

Original Post

Re: CRASHING NON STOP

★★★★ Novice

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

Message 241 of 1,214 (989 Views)

Re: CRASHING NON STOP

Community Manager (retired)

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

Message 242 of 1,214 (984 Views)

Re: CRASHING NON STOP

[ Edited ]
★★★★★ Apprentice

@OrioStorm 

Thank you.

Tried the command line launch parameter and the errors are back! Standard smile

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?).

Message 243 of 1,214 (979 Views)

Windows 10 Latest 1903 update - Bad Module Error

★★ Guide

Windows Event Logger

Log Name:      Application
Source:        Application Error
Date:          5/22/2019 3:13:59 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Owner-PC
Description:
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff69ba43b77
Faulting process id: 0x453c
Faulting application start time: 0x01d510cfada52716
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: 709fee47-4311-4dc7-b9b0-cfa7091b2698
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-05-22T19:13:59.513424600Z" />
    <EventRecordID>973</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Owner-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>bad_module_info</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>00007ff69ba43b77</Data>
    <Data>453c</Data>
    <Data>01d510cfada52716</Data>
    <Data>bad_module_info</Data>
    <Data>unknown</Data>
    <Data>709fee47-4311-4dc7-b9b0-cfa7091b2698</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Apex Crash log

crash:
{
	module@00007FFBAE7A0000: 0000000000331F54
	EXCEPTION_ACCESS_VIOLATION(write): FFFFFFFFFFFFFFDF
}
cpu: "       Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
ram: 16 // GB
callstack:
{
	KERNELBASE: 000000000008667C
	ntdll: 00000000000A81CB
	ntdll: 000000000008FD56
	ntdll: 00000000000A477F
	ntdll: 0000000000004BEF
	ntdll: 00000000000A34EE
	module@00007FFBAE7A0000: 0000000000331F54
	module@00007FFBAE7A0000: 00000000001994D4
	module@00007FFBAE7A0000: 000000000019A947
	module@00007FFBAE7A0000: 0000000000451D25
	module@00007FFBAE7A0000: 00000000004EE5B7
	module@00007FFBAE7A0000: 00000000012A066C
	KERNEL32: 0000000000017974
	ntdll: 000000000006A271
}
registers:
{
	rax = 0         
	rbx = 0         
	rcx = 0x09A16EF8648B0000
	rdx = 0x0000004C3CF7E760
	rsp = 0x0000004C3CF7ED50
	rbp = 0x0000004C3CF7EE01
	rsi = 0x0000018F999C5640
	rdi = 56        
	r8  = 0x0000018EFFBE94A0
	r9  = 84        
	r10 = 0x0000018EFFBE4030
	r11 = 0         
	r12 = 0x0000018F8AF01F20
	r13 = 0x000001906616A030
	r14 = 0         
	r15 = 0x00000190661645A0
	rip = 0x00007FFBAEAD1F54
	xmm0  = [ [1.4012985e-45, 0, 6.417947e-43, 1.9999938], [0x00000001, 0x00000000, 0x000001CA, 0x3FFFFFCC] ]
	xmm1  = [ [0, 0, 0, 0], [0, 0, 0, 0] ]
	xmm2  = [ [1.4012985e-45, 0, 1.4012985e-45, 0], [1, 0, 1, 0] ]
	xmm3  = [ [1.4012985e-45, 0, 0, 1.4012985e-45], [1, 0, 0, 1] ]
	xmm4  = [ [0, 1.4012985e-45, 0, 1.4012985e-45], [0, 1, 0, 1] ]
	xmm5  = [ [0, 0, 1.4012985e-45, 0], [0, 0, 1, 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: 1554860081


I have my cpu overclocked to 4.5 ghz and GPU OCed as well. 

Message 244 of 1,214 (837 Views)

Re: CRASHING NON STOP

[ Edited ]
★★★★ Novice

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 Standard smile

Message 245 of 1,214 (964 Views)

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

★ Novice

crash:
{
msvcrt: 000000000002A556
EXCEPTION_ACCESS_VIOLATION(write): 0000000000000000
}
cpu: "Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz"
ram: 8 // GB
callstack:
{
KERNELBASE: 00000000000EBDC0
ntdll: 00000000000A3167
ntdll: 000000000008B5E6
ntdll: 000000000009F7DD
ntdll: 000000000000D856
ntdll: 000000000009E70E
msvcrt: 000000000002A556
sapi_onecore: 000000000011517F
sapi_onecore: 00000000001151B9
sapi_onecore: 000000000006A0C9
sapi_onecore: 00000000001467DD
sapi_onecore: 000000000000D218
sapi_onecore: 000000000000D1D4
sapi_onecore: 000000000000D2DB
module@00007FFD21560000: 000000000009328D
module@00007FFD21560000: 0000000000093687
module@00007FFD21560000: 0000000000093A08
ntdll: 000000000003B583
ntdll: 0000000000047F85
ntdll: 0000000000047E48
KERNEL32: 000000000001CA7A
R5Apex: 0000000001245764
R5Apex: 0000000001245700
R5Apex: 00000000004B0BE2
R5Apex: 0000000001206836
Activation64: 0000000000011050
Activation64: 0000000000008F82
KERNEL32: 0000000000014034
ntdll: 0000000000073691
}
registers:
{
rax = 0
rbx = 0x000000D677BAE9D0
rcx = 0x9A5A206229600000
rdx = 0
rsp = 0x000000D677BAE960
rbp = 0x0000026FDCCD9870
rsi = -1 // 0xFFFFFFFF
rdi = 0x0000026FDCCBADE0
r8 = 0
r9 = 0x000000D677BADF70
r10 = 0x00007FFD4E78D0B4
r11 = 0x000000D677BAE3A0
r12 = 0x0000026FDCCD9870
r13 = 0
r14 = 0x000000D677BAE9C8
r15 = 0x00007FFD33D5D4C0
rip = 0x00007FFD4E21A556
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

Message 246 of 1,214 (959 Views)

Re: CRASHING NON STOP

Community Manager (retired)

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

Message 247 of 1,214 (958 Views)

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

Community Manager (retired)

@Maca356, thanks for the crash info. That's a known issue where Microsoft's text-to-speech stuff crashes on exit. We have an engineer looking into whether we can do anything to avoid this.

Message 248 of 1,214 (950 Views)

Re: CRASHING NON STOP

★★★★★ Apprentice

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

Message 249 of 1,214 (932 Views)

Still random crashes on exit.

★ Guide

Thought it had cleared up after last patch, but crashing while exiting started happening again today. Crash.txt included.

 

Message 250 of 1,214 (798 Views)