ACTIVE FTX NA PNW FSX shutdown at certain airports

[bumprock]

I have been experiencing shutdown of FSX with the message: "Microsoft Flight Simulator has stopped working ... a problem caused the program..." with no error code. As far as I can tell it is only occurring in the PNW scenery and only near specific airports. It will occur immediately as you near the airport as a destination, or if you attempt to spawn at that airport. Currently the one I am having difficulty with is CYYD (Smithers).

 

I am flying a hoplist and it has occurred on a couple of previous hops. The workaround has been to apply FTX Global and disable North America. 

 

I am using Windows 8.1

Intel i5-3330 CPU @ 3.00 GHz

64 bit operating system

 

 Thank you.

[Stewart Hobson]

No offense, please, but at 3.00 GHz, I suspect your processor simply "gave up" and forced FSX to shut down.  With the work demanded by the full region PNW and airports in that region, I suspect it was too taxing for the processor.  PNW is notorious for punishing cpus of less than 4.0 Ghz processor speed.  Other folks may jump in here with their observations as well.

 

Stew

[Holger Sandmann]

Hi there,

 

CYYD is in PFJ rather than PNW and in a remote area that really shouldn't cause any performance issues. Have you checked whether you may have other add-on files active for the airports in question? Those can cause compatibility problems. Run a Windows search of your entire FSX folder tree -- including any external scenery locations you may have -- for .bgl files that include the airport's ICAO as part of their names, e.g., the search term "*CYYD*.bgl".

 

Also, I assume you have the current Orbx libraries installed?

 

Cheers, Holger

[bumprock]

Hi Holger,

 

Yes, the current libraries are installed. I checked for the *CYYD*.bgl files and found only the three which appear to be legit. When the failure occurs during loading a free flight from CYYD the message appears during the terrain loading process on the progress bar. 

 

Interestingly one of the other airports where this is now occurring (and one where I have spent a great amount of time in and around) is CYBD, Bella Coola. In this case, the scenery loads but then I get the Shut down message after about 30 seconds. 

 

I have also recreated the fsx.cfg with no luck.

 

I am wondering if this may be a result of using FSX Booster.

 

Thank you,

Sherman

[Doug Sawatzky]

It sounds like a crash to desktop (CTD) and I doubt it would be the FSX Booster as I use the XtremeFSXPC also from FSPS....but could it be the UIAutomationcore.dll issue?

 

    http://www.flightsim.com/vbfs/showthread.php?272452-FSX-crashes-on-Windows-8-1-New-user-needs-help

[bumprock]

Here is the event log: 

 

Log Name:      Application

Source:        Windows Error Reporting

Date:          8/23/2015 9:10:32 PM

Event ID:      1001

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      STWDesktop

Description:

Fault bucket 555068015, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: fsx.exe

P2: 10.0.61637.0

P3: 46fadb14

P4: g2d.dll

P5: 10.0.61637.0

P6: 46fadb58

P7: c0000005

P8: 000843ac

P9: 

P10: 

 

Attached files:

C:\Users\Sherman\AppData\Local\Temp\WER2163.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_e8dc6966775f8fd0e88f317045578d8bc658533_68a774f9_15ff590d

 

Analysis symbol: 

Rechecking for solution: 0

Report Id: e1856463-49fc-11e5-bf5f-a41f7274f99b

Report Status: 0

Hashed bucket: 1db65598c8e02897d9daf6820d9b1188

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Windows Error Reporting" />

    <EventID Qualifiers="0">1001</EventID>

    <Level>4</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-08-24T01:10:32.000000000Z" />

    <EventRecordID>102039</EventRecordID>

    <Channel>Application</Channel>

    <Computer>STWDesktop</Computer>

    <Security />

  </System>

  <EventData>

    <Data>555068015</Data>

    <Data>1</Data>

    <Data>APPCRASH</Data>

    <Data>Not available</Data>

    <Data>0</Data>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>g2d.dll</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb58</Data>

    <Data>c0000005</Data>

    <Data>000843ac</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Data>

C:\Users\Sherman\AppData\Local\Temp\WER2163.tmp.WERInternalMetadata.xml</Data>

    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_e8dc6966775f8fd0e88f317045578d8bc658533_68a774f9_15ff590d</Data>

    <Data>

    </Data>

    <Data>0</Data>

    <Data>e1856463-49fc-11e5-bf5f-a41f7274f99b</Data>

    <Data>0</Data>

    <Data>1db65598c8e02897d9daf6820d9b1188</Data>

  </EventData>

</Event>

[Doug Sawatzky]

Sherman

 

Have you added the UIAutomationcore.dll to your main FSX folder?

[bumprock]

It was not there before. 

I added it to the FSX root directory

loaded FSX and unfortunately the same failure.

[bumprock]

After a couple of weeks of frustration, a clean reinstall of FSX, and partial reinstalls of the relevant FTX scenery, the shutdowns near specific airports continued. I then did a complete uninstall and reinstall of FTX and no more shutdowns. While I am no closer to knowing the specific cause, at least it is working. Thank you to Holger and Doogles for your help.

 

Sherman