johnnyb Posted January 13, 2018 Share Posted January 13, 2018 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) Link to comment Share on other sites More sharing options...
il88pp Posted January 13, 2018 Share Posted January 13, 2018 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/showthread.php?270280-A-note-to-those-creating-threads-regarding-FSX-crashes [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
johnnyb Posted January 13, 2018 Author Share Posted January 13, 2018 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. Link to comment Share on other sites More sharing options...
KKilo2 Posted January 14, 2018 Share Posted January 14, 2018 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. Link to comment Share on other sites More sharing options...
stinger2k2 Posted January 14, 2018 Share Posted January 14, 2018 In the fsx general settings make sure that you untick the "pause on task switch" Cheers Stinger Sent from my SM-G935F using Tapatalk Link to comment Share on other sites More sharing options...
johnnyb Posted January 17, 2018 Author Share Posted January 17, 2018 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: 10016 0 2 0 0 0x8080000000000000 3845 System FS-PC application-specific Local Activation {D63B10C5-BB46-4990-A94F-E40B9D520160} {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} FS-PC John S-1-5-21-1114903088-3943235688-1464229143-1000 LocalHost (Using LRPC) Unavailable Unavailable 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: 916 4 1 0x80000000000000 5273 Application FS-PC DllHost 7464,G,0 EseDiskFlushConsistency ESENT 0x800000 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: 10016 0 2 0 0 0x8080000000000000 3845 System FS-PC application-specific Local Activation {D63B10C5-BB46-4990-A94F-E40B9D520160} {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} FS-PC John S-1-5-21-1114903088-3943235688-1464229143-1000 LocalHost (Using LRPC) Unavailable Unavailable The first one was under Custom and the second two were under Windows. Thanks in advance for the help. JohnnyB Link to comment Share on other sites More sharing options...
JSkorna Posted January 17, 2018 Share Posted January 17, 2018 None of those is the cause of your FSX crash. http://www.air-source.us/images/sigs/000219_195_jimskorna.png Link to comment Share on other sites More sharing options...
il88pp Posted January 17, 2018 Share Posted January 17, 2018 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/2015/09/28/windows-10-event-10016-fix-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid-d63b10c5-bb46-4990-a94f-e40b9d520160-and-a/ https://answers.microsoft.com/en-us/windows/forum/windows_8-performance/event-id-10016-the-application-specific-permission/9ff8796f-c352-4da2-9322-5fdf8a11c81e This may also help. It's about the same issue. https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install-insiderplat_pc/local-activation-permission-for-the-com-server/392a6350-2dbb-49a9-b0aa-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.:cool: 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) [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
johnnyb Posted January 18, 2018 Author Share Posted January 18, 2018 Thanks. I'll give it a try as soon as I get a chance. I'll also let you know how it went. JohnnyB Link to comment Share on other sites More sharing options...
mrzippy Posted January 18, 2018 Share Posted January 18, 2018 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 Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
johnnyb Posted January 19, 2018 Author Share Posted January 19, 2018 Success! Made two flights, one over 300 NM and one 180 NM no crashes. Did a repair on the registry and permissions. Thanks loads. JohnnyB Link to comment Share on other sites More sharing options...
il88pp Posted January 19, 2018 Share Posted January 19, 2018 Glad to gear that!! Like the others I wasn't sure it had anything to do with fsx crashing, but it seemed serious enough that it needed fixing. Glad it helped run fsx too.:D Happy Flights! [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
stinger2k2 Posted January 19, 2018 Share Posted January 19, 2018 Glad to hear that you are sorted. There's nothing more frustrating than FSX ctd's. Ok, maybe the other half shouting at you from the next room to get on with some chores when you are on short finals [emoji4] Cheers Stinger Sent from my SM-G935F using Tapatalk Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.