Ft.Lauderdale scenery crashes

[davio40]

I recently noticed that my scenery for FLL crashes about 1 minute after start-up.  Not sure why.  I've reduced the sliders for texture and scenery and it still crashes.  I've checked to see where it sits in the Scenery Library and it is above other scenery for Miami (Mega Scenery).  Not sure why this is happening.  Any ideas?

[virtuali]

I recently noticed that my scenery for FLL crashes about 1 minute after start-up. 

Your FSX crashes at KFLL, that doesn't mean your "KFLL scenery" is crashing. Whenever you are parked on an airport, there's A LOT of other scenery loaded too, not just the airport so, you can't say for sure what really crashed.

You might check the Windows Event Viewer, under the Tools in the Control Panel. Looking the Application log, you should find the FSX error report, which might give some hints about what FSX module crashed, and depending which one was, we might have a better idea what's causing it.

[davio40]

I saw this error message:

Log Name:      Application
Source:        Application Error
Date:          15/02/2014 21:02:35
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Smee-PC
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: 0xab8
Faulting application start time: 0x01cf2a54a5c03665
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: 7dc0784a-9684-11e3-86e4-485b39aeb9df
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="2014-02-15T21:02:35.000000000Z" />
    <EventRecordID>53416</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Smee-PC</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>ab8</Data>
    <Data>01cf2a54a5c03665</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>7dc0784a-9684-11e3-86e4-485b39aeb9df</Data>
  </EventData>
</Event>

Any ideas?

[virtuali]

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

The sim1.dll crash can be anything but, in general, is something related to your airplane, because that module handles all the airplane variables. Does it happen with a specific airplane ? Try a default airplane, for example.

[davio40]

Tried with the default 737 and the same thing happened.  I do have Mega Scenery for Miami...could this be impacting something (it's a pretty dense scenery).  Not sure what else to do other than uninstall and reinstall?

[virtuali]

I do have Mega Scenery for Miami...could this be impacting something (it's a pretty dense scenery). 

What is causing this is something that is trying to WRITE into FSX simulation variables so, if it's not an airplane, it's any other kind of utility like weather programs, etc.

The message is fairly clear: it's s 0xc0000005 code, which is one of the most common error codes around, the "access violation". Something is trying to write into something into an area protected by the OS.

I'm 100% sure it's NOT the scenery or any of our software, because the ONE and ONLY interaction with SIM1.DLL we have, is to READ the airplane name, to identify the model (for example, to operate docking systems).

But it's only a read operation, we don't try to write into it, which mean we can't possibly cause an access violation with that operation.

Not sure what else to do other than uninstall and reinstall?

Reinstall what ? Surely not KFLL, since the problem is not caused by the airport, you wouldn't accomplish anything by reinstalling it. A problem in the scenery like a corrupted file on your system (that CAN be fixed by reinstalling the scenery), will generate a crash in G3D.DLL, not SIM1.DLL, which is something more related to the simulation itself, not the graphic objects.