Folks..I have several times attempted to originate a flight and/or fly into the area of the United Arab Emirates: OMAA or OMDB and get that infamous "Fatal error has occurred Microsoft Flight Simulator X is restarting"

 

Thinking I had a corrupted freeware scenery (normally i never do) I removed it to the default scenery and still..got the "fatal error message".

 

I've only had this particular area mess up on me...

 

Any tips or has anyone experienced similar issue?

 

I have the UIAutomationCore.dll..installed correctly..(this was based on suggestions to my problem, however, "NO WORKEE")

 

Any input...welcome..

 

Respectfully,

Chris

 

First thing I do when I have unresolved "fatal errors", is disable all 3rd party scenery and/or rebuild FSX.cfg. I almost always find this to be the resolution.Save your current .cfg copy first though.

Actually, the first thing to do is to check your Events Viewer to see what faulting module is happening that is

 

causing your "Fatal Error".   See this link  http://www.avsim.com/topic/482537-fsx-application-crash/#entry3363438

 

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,
Probable addon problem.  See below!


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
 

I will give it a try...thank you both...for your tips..

 

Chris

Below is what I discovered in (Bold/Italics) Now next question...what to do with sim1.dll?? (grinning a bit)

 

Log Name:      Application

Source:        Application Error

Date:          1/26/2016 2:08:16 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Starrhouse

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: sim1.dll, version: 10.0.61472.0, time stamp: 0x475e180d

Exception code: 0xc0000005

Fault offset: 0x0006df64

Faulting process id: 0xefc

Faulting application start time: 0x01d15873ec9b2df4

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll

Report Id: 88f05607-c468-11e5-bffa-2016d8f9994c

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="2016-01-26T20:08:16.000000000Z" />

    <EventRecordID>411357</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Starrhouse</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61472.0</Data>

    <Data>475e17d3</Data>

    <Data>sim1.dll</Data>

    <Data>10.0.61472.0</Data>

    <Data>475e180d</Data>

    <Data>c0000005</Data>

    <Data>0006df64</Data>

    <Data>efc</Data>

    <Data>01d15873ec9b2df4</Data>

    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>

    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll</Data>

    <Data>88f05607-c468-11e5-bffa-2016d8f9994c</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Let me try a few things I found..thru Google..search...I'll do a pc scan...etc...maybe I can fix it...

 

thanks for helping..(cross your fingers)

Lots of different answers for that faulting module.  Your best bet is to either Google "FSX sim1.dll crash" or

 

check out the AVSIM CTD Forum.

I'll check it out...

 

Many thanks!

According to the AVSIM CTD Guide (see link in my signature), the probable cause for a sim1.dll crash:

 

Sim1.dll CTD – This crash is caused by a corrupted or incompatible aircraft texture, most likely the latter.  Look at recent aircraft installations, especially from previous versions of flight simulator.  Right click on FSX.exe in your main FSX folder and select ‘Properties’.  Once open, click on the compatibility tab and check “Run as Administrator”.

 

Best regards,

Thanks Jim for the input..on the Sim1.dll CTD...so far the FSX.exe "properties" is checked to "Run as Administrator" and to run thru..the  aircraft recent installations.would be gruesome...lol..;however,

if i get the "nerve" to  start from scratch to uninstall / reinstall...everything just for OMAA and OMDB then i will return a reply that all is running fine at these two locations. I will keep efforts up..to get my 

FSX running good..and hopefully get a "fix" on these two culprits...in the UAE! :-)

The aircraft could be from repaints, AI aircraft, or static aircraft (i.e., they are installed with scenery).  I would look at any addons (aircraft or scenery) you installed after this crash started.  You have FSX SP2 installed too.  Make sure you do not have any aircraft that was made for Acceleration (which is the same as SP2 except Acceleration was coded so that SP2 users could not use the addon aircraft that came with Acceleration).  Personally, I would move all of your non-default aircraft to a temporary folder, run FSX and make sure the problem has gone away (if not, it is an aircraft in an AFCAD or scenery), then move 3-4 of the aircraft back at a time until the problem comes back.

 

Best regards,

I will give it a go!  (cross your fingers)...I wonder if that FAIB AI Aircraft product..could be the culprit...i'll reply a bit later to see what has happened..stay tuned..

 

Many thanks ....Jim.

 

Respectfully,

Chris

Jim...YOU THE MAN! 

 

I went and cleaned out and placed in a workspace so to speak: my add-on, ai aircraft..and trash i didn't remember putting in SimObjects (grinning a bit)  and only had defaults...I can happily report..OMAA and OMDB scenery worked just fine!

 

NOW that i cleaned up Simobjects...i gotta go to work...I'm glad i went ahead and took your instruction--- now i can return the aircrafts I fly and AI traffic that i really use!

 

I put a donation in the coffers..not a whole lot..but am appreciative..for all the help..and knowledge...AVSIM contributors provide..

 

As I work in the aircraft I'll test the OMAA and OMDB and report the culprit..it's hiding in swarm of aircrafts..and I mean swarm!!

 

Respectfully,

Chris

Just a quick update, re-entered the aircraft into FSX that I usually fly...and reserved all of my others to perhaps a later time...

 

I tested the scenery OMAA and OMDB and was able to originate a flight without the "fatal error-pop up" 

 

thanks to all who responded..and I tweaked my fsx.cfg..also..to aide in optimizing..the performance of FSX.

 

Until another issue..(if any) :-)

many thanks

Chris