Forum Discussion

3 Replies

Replies have been turned off for this discussion
  • Hubrisx2's avatar
    Hubrisx2
    7 years ago

    I can upload the Dxdiag.txt for sure,and i was only able to find this, unsure if it will help. But here you go!

    Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
    Source: Microsoft-Windows-Kernel-EventTracing
    Date: 2/18/2019 10:05:48 PM
    Event ID: 2
    Task Category: Session
    Level: Error
    Keywords: Session
    User: DESKTOP-KPNUKVT\ricks
    Computer: DESKTOP-KPNUKVT
    Description:
    Session "dfa2c640-651d-488d-a479-2fd7a7ca6e29" failed to start with the following error: 0xC0000022
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
    <EventID>2</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>12</Opcode>
    <Keywords>0x8000000000000010</Keywords>
    <TimeCreated SystemTime="2019-02-18T21:05:48.805178200Z" />
    <EventRecordID>99</EventRecordID>
    <Correlation />
    <Execution ProcessID="1188" ThreadID="5036" />
    <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
    <Computer>DESKTOP-KPNUKVT</Computer>
    <Security UserID="S-1-5-21-1743875097-2972059101-958828858-1002" />
    </System>
    <EventData>
    <Data Name="SessionName">dfa2c640-651d-488d-a479-2fd7a7ca6e29</Data>
    <Data Name="FileName">
    </Data>
    <Data Name="ErrorCode">3221225506</Data>
    <Data Name="LoggingMode">4194560</Data>
    </EventData>
    </Event>

    Log Name: Application
    Source: Application Error
    Date: 2/18/2019 7:34:13 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-KPNUKVT
    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: 0x12f0
    Faulting application start time: 0x01d4c7b58b3371df
    Faulting application path: bad_module_info
    Faulting module path: unknown
    Report Id: f60dc087-49b2-4d1b-bd41-8ae15e494c6d
    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-02-18T18:34:13.898194900Z" />
    <EventRecordID>19129</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-KPNUKVT</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>12f0</Data>
    <Data>01d4c7b58b3371df</Data>
    <Data>bad_module_info</Data>
    <Data>unknown</Data>
    <Data>f60dc087-49b2-4d1b-bd41-8ae15e494c6d</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    </EventData>
    </Event>

    Log Name: System
    Source: Microsoft-Windows-DistributedCOM
    Date: 2/18/2019 10:15:42 PM
    Event ID: 10016
    Task Category: None
    Level: Error
    Keywords: Classic
    User: DESKTOP-KPNUKVT\ricks
    Computer: DESKTOP-KPNUKVT
    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-KPNUKVT\ricks SID (S-1-5-21-1743875097-2972059101-958828858-1002) 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-02-18T21:15:42.188000400Z" />
    <EventRecordID>13897</EventRecordID>
    <Correlation />
    <Execution ProcessID="340" ThreadID="5516" />
    <Channel>System</Channel>
    <Computer>DESKTOP-KPNUKVT</Computer>
    <Security UserID="S-1-5-21-1743875097-2972059101-958828858-1002" />
    </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-KPNUKVT</Data>
    <Data Name="param7">ricks</Data>
    <Data Name="param8">S-1-5-21-1743875097-2972059101-958828858-1002</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
    </EventData>
    </Event>

  • Awesome, just a note for next time that the times have to be within a few seconds of each other to be relevent to a single crash unless they are at the times for each time you crashed.

    Event ID and there meanings:

    1. Memory issue

    2.The Bad_module_info is a common issue so its a known bug that is being looked at since its been our for a while.

    3. This is safe you can ignore this

    Looking at your DXDiag your system is falling behind on updates, updating your system may reduce some issues.

    (like the memory issue you have in your event log)

    If you wanna get up to date on that, start by updating windows and no more updates are availible when you check for them.

    You can get your GPU driver here: https://www.geforce.co.uk/drivers/results/141954

    As for the Core drivers of your PC, follow my guide here under Core windows maintenence:

    https://answers.ea.com/t5/Technical-Issues/In-Depth-Trouble-shooting-Guide/m-p/7472105#M165

    This should get you up to date so that issues are less likely to pop up in future. (as long as you keep updating :P)

  • Hubrisx2's avatar
    Hubrisx2
    7 years ago

    Indeed, However I have not experienced these "crashes" untill today. and I have been playing from launch

    However i shall update my system.

About Apex Legends Bug Reports - Archive

23,008 PostsLatest Activity: 5 years ago