Page 1 of 2 1 2 LastLast
Results 1 to 10 of 13

Thread: FSX Crash

  1. #1

    Default FSX Crash

    Hi fellow flight simmers. It's been a while and I hope everyone out there are doing well.
    Here is my problem and I hope someone can help.
    I cannot complete a flight in FSX. The sim will crash to desktop without any notifications. This
    occurs mostly on approach to the destination airport, but not always. Sometimes it's in mid flight and sometimes
    on climb out. The screen freezes and all you have is the engine sound, then the desktop. I have already tried the repair procedure
    but the crash still happens. I am running an i7 on Windows 10. Just prior to the crash the hard drive get very busy. Any suggestions?
    Thanks in advance.

    John B Loney Jr (johnnyb)

  2. Default

    Post the crash report. See this post on where to find that. It's a sticky at the top of the forum.
    https://www.flightsim.com/vbfs/showt...ng-FSX-crashes

  3. #3

    Default

    Thanks for the tip. I saw nothing about FSX in the event logs. I will take another flight and if it crashes again I will immediate;y go to the event log to see what the last error recorded is. Have a great day Top Gun.

  4. Default

    Look for and read the AVSIM crash to desk top guide, it has a lot of useful info that can often (not always) fix CTD problems.

  5. #5

    Default

    In the fsx general settings make sure that you untick the "pause on task switch"


    Cheers Stinger

    Sent from my SM-G935F using Tapatalk

  6. #6

    Default

    Hello all, I finally got to fly FSX again and upon the crash I found several error notices. They are as follows: Log Name: System
    Source: Microsoft-Windows-DistributedCOM
    Date: 1/17/2018 2:14:55 PM
    Event ID: 10016
    Task Category: None
    Level: Error
    Keywords: Classic
    User: FS-PC\John
    Computer: FS-PC
    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 FS-PC\John SID (S-1-5-21-1114903088-3943235688-1464229143-1000) 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="2018-01-17T19:14:55.108418700Z" />
    <EventRecordID>3845</EventRecordID>
    <Correlation />
    <Execution ProcessID="1076" ThreadID="3188" />
    <Channel>System</Channel>
    <Computer>FS-PC</Computer>
    <Security UserID="S-1-5-21-1114903088-3943235688-1464229143-1000" />
    </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">FS-PC</Data>
    <Data Name="param7">John</Data>
    <Data Name="param8">S-1-5-21-1114903088-3943235688-1464229143-1000</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
    </EventData>
    </Event>

    Log Name: Application
    Source: ESENT
    Date: 1/17/2018 2:10:48 PM
    Event ID: 916
    Task Category: General
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: FS-PC
    Description:
    DllHost (7464,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">916</EventID>
    <Level>4</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-01-17T19:10:48.210016300Z" />
    <EventRecordID>5273</EventRecordID>
    <Channel>Application</Channel>
    <Computer>FS-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>DllHost</Data>
    <Data>7464,G,0</Data>
    <Data>
    </Data>
    <Data>EseDiskFlushConsistency</Data>
    <Data>ESENT</Data>
    <Data>0x800000</Data>
    </EventData>
    </Event>

    and: Log Name: System
    Source: Microsoft-Windows-DistributedCOM
    Date: 1/17/2018 2:14:55 PM
    Event ID: 10016
    Task Category: None
    Level: Error
    Keywords: Classic
    User: FS-PC\John
    Computer: FS-PC
    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 FS-PC\John SID (S-1-5-21-1114903088-3943235688-1464229143-1000) 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="2018-01-17T19:14:55.108418700Z" />
    <EventRecordID>3845</EventRecordID>
    <Correlation />
    <Execution ProcessID="1076" ThreadID="3188" />
    <Channel>System</Channel>
    <Computer>FS-PC</Computer>
    <Security UserID="S-1-5-21-1114903088-3943235688-1464229143-1000" />
    </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">FS-PC</Data>
    <Data Name="param7">John</Data>
    <Data Name="param8">S-1-5-21-1114903088-3943235688-1464229143-1000</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
    </EventData>
    </Event>

    The first one was under Custom and the second two were under Windows.

    Thanks in advance for the help.

    JohnnyB

  7. #7
    Join Date
    Jan 1999
    Location
    Warren, Michigan, USA
    Posts
    12,132

    Default

    None of those is the cause of your FSX crash.

  8. Default

    I Googled:
    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}

    That gave a lot of results!
    Here's three of them.
    The fix involves changing permissions on two registry keys. (Make a backup of the registry before you do !!! )
    And then also changing permissions on "RuntimeBroker".

    https://shauncassells.wordpress.com/...d520160-and-a/

    https://answers.microsoft.com/en-us/...2-5fdf8a11c81e

    This may also help. It's about the same issue.
    https://answers.microsoft.com/en-us/...a-f27289ea4afb
    In the text is explained again what to do, but very briefly.
    Instead of a long explanantion he placed in the text links to files (.reg) that should edit and correct the registry files for you.
    And also then explained the other step to do:
    2-Open up dcomcnfg.exe and navigate to RuntimeBroker, click Permissions.
    3-Edit the security settings and add yourself and Administrators as have authorization.

    The explanation is brief, maybe the first two links I gave explain better. But the .reg files he links may be helpful.

    Be careful though. As he says too: Use the files at your own risk. And make sure you have a backup of your registry before you start.
    With a backup of the registry you can undo any changes these .reg files do.

    Better way is to just navigate to the registry keys yourself, and change their permissions manually.
    That way you know what you did, so you know how to undo it if needed later.
    Still, make a registry backup before you start!!

    il88pp.

    PS: I searched for a fix for the third error you posted. I have a feeling the first one might be fixed after that too, it's also about DCOM. Not so sure about error two. (yet)
    Last edited by il88pp; 01-17-2018 at 05:53 PM.

  9. #9

    Default

    Thanks. I'll give it a try as soon as I get a chance. I'll also let you know how it went.

    JohnnyB

  10. #10
    Join Date
    Jan 2012
    Location
    San Francisco, California
    Posts
    14,903

    Default

    Quote Originally Posted by JSkorna View Post
    None of those is the cause of your FSX crash.
    +1 You need to find out what "Faulting Module" is causing your FSX to crash.

    Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events.
    One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area.

    Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting.


    BELOW IS A SAMPLE OF WHAT YOU MIGHT SEE!

    General Tab:
    Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
    Faulting module name: This is what we need to Know!
    Exception code: 0xc0000005
    Fault offset: 0x0000ee3a
    Faulting process id: 0x748
    Faulting application start time: 0x01ce0253dc4b69d4
    Faulting application path: R:\FSX\fsx.exe
    Faulting module path: R:\FSX\window.dll
    Report Id: 9caf77b4-6e50-11e2-8570-3085a99825d1

    If there is not one listed:
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000,
    you will need to do as previously noted


    No Faulting Module? ->
    Remove all of the add-ons, and test the sim. If it works OK, then reinstall them one at a time and test.
    Be sure to test each thoroughly before moving on to the next
    Mr Zippy Sent from my keyboard using "Whackamole", NudgeAKey + 2 Fingers

    Emachines T3418 AMD 3400+ processor 2GHZ/256KB L2 Cashe 2Gig Ram 160Gig HDD NVidia GEForce 6100 GPU Running WinXP Home Can't believe it still works! Running FSX Standard with SP1 and SP2

Page 1 of 2 1 2 LastLast

Similar Threads

  1. Partial Crash or Total Crash
    By heyford in forum FS2004
    Replies: 1
    Last Post: 01-30-2009, 07:42 AM
  2. Crash, Crash, Crash
    By medicus2404 in forum DreamFleet 727 Support Forum
    Replies: 4
    Last Post: 07-21-2005, 04:38 AM
  3. Crash on load flight AND crash to desktop?
    By BickBz in forum FS2004
    Replies: 11
    Last Post: 01-12-2004, 03:59 PM
  4. Look my pictures, the crash is .... crazy! (Crash of 737)
    By lobo in forum MSFS Screen Shot Forum
    Replies: 1
    Last Post: 03-22-2002, 01:45 PM
  5. A crash or not a crash, that is the question.
    By eagle013 in forum FS2002
    Replies: 15
    Last Post: 01-21-2002, 10:38 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •