Forum Discussion

Re: Apex Legends Crashing

@OrioStorm  Okay, new development... I submitted my crash report and then went to play again, and when I opened the game I got 2 error messages. #2 popped up after I clicked ok on the first. 

But my game won't open now. I'm going to try a repair and see what happenes, maybe a restart. 

10 Replies

  • OrioStorm's avatar
    OrioStorm
    Icon for EA Staff (Retired) rankEA Staff (Retired)
    7 years ago

    Those errors look like the OS was temporarily preventing you from using your nVidia display driver. If you rebooted after repairing the game, the reboot may have been what fixed it? I'm not sure, I've never seen that before.

  • @OrioStorm Wonderful, lol. Glad I could show you something new! hahahahaa, That's just my luck with PCs. I'm thinking I'm going to reinstall Apex but to my SSD and see if that makes a difference.
  • Orbnotacus's avatar
    Orbnotacus
    7 years ago

    Since moving my game to my SSD via Origins "move" function, I crash less, but it seems all my crashes are straight to desktop with no report. :/

  • Orbnotacus's avatar
    Orbnotacus
    7 years ago

    @OrioStorm  So I got another super strange error just now. Idk if there's a way for me to give you more info, if so just tell me what and how and I'll be more than happy to oblige. 

  • Orbnotacus's avatar
    Orbnotacus
    7 years ago

    2 errors from the event viewer from the moment of my last crash report, as well as my DxDiag file.

    Log Name: Application
    Source: Application Error
    Date: 6/16/2019 10:59:16 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-R8E5326
    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: 0x00000000
    Fault offset: 0x0000000000000000
    Faulting process id: 0x37e0
    Faulting application start time: 0x01d524ae39ce8c9a
    Faulting application path: bad_module_info
    Faulting module path: unknown
    Report Id: 7c3ae7ae-0336-49ac-8803-b6f6ee53d56f
    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-06-17T02:59:16.899087800Z" />
    <EventRecordID>5408</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-R8E5326</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>00000000</Data>
    <Data>0000000000000000</Data>
    <Data>37e0</Data>
    <Data>01d524ae39ce8c9a</Data>
    <Data>bad_module_info</Data>
    <Data>unknown</Data>
    <Data>7c3ae7ae-0336-49ac-8803-b6f6ee53d56f</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    </EventData>
    </Event>

    NEXT ERROR

    Log Name: System
    Source: Microsoft-Windows-DistributedCOM
    Date: 6/16/2019 10:59:24 PM
    Event ID: 10016
    Task Category: None
    Level: Error
    Keywords: Classic
    User: DESKTOP-R8E5326\PC
    Computer: DESKTOP-R8E5326
    Description:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {D63B10C5-BB46-4990-A94F-E40B9D520160}
    and APPID
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
    to the user DESKTOP-R8E5326\PC SID (S-1-5-21-3534119408-349143720-254664468-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10016</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2019-06-17T02:59:24.714166600Z" />
    <EventRecordID>4131</EventRecordID>
    <Correlation />
    <Execution ProcessID="296" ThreadID="6740" />
    <Channel>System</Channel>
    <Computer>DESKTOP-R8E5326</Computer>
    <Security UserID="S-1-5-21-3534119408-349143720-254664468-1001" />
    </System>
    <EventData>
    <Data Name="param1">application-specific</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>
    <Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>
    <Data Name="param6">DESKTOP-R8E5326</Data>
    <Data Name="param7">PC</Data>
    <Data Name="param8">S-1-5-21-3534119408-349143720-254664468-1001</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
    </EventData>
    </Event>