Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MS9 has stopped working.

Featured Replies

Some time ago I upgraded my system as follows:

 

ASUS P8Z68 Deluxe /Gen3 Motherboard

Intel Core i7-2700K CPU

Mushkin PC312800 (2x4GB) Memory

GTX 580 Video Card

Corsair H80 Liquid Cooling

 

I also replaced my Windows XP Pro Operating System with Win 7 Home Premium (Where I think my problem lies).

 

I reinstalled all of my programs, including Flight Simulator 9, and Flight Simulator X.

 

During my installation of both FS9 and FSX, after installing, importing, or copying all of my third party aircraft, I would select them immedately after installation and see that they displayed properly one by one and then move on to the next bird. This was a quick check and I did not make any flights.

 

For some time after my upgrade I have been flying only FSX, particularly the PMDG 737NGX with no problems and having a ball. The system and FSX seems to be performing flawlessly and I am tickled pink.I have no other problems that have shown up yet at all in FSX.

 

I recently decided to migrate back to FS9 for a flight or two. I have discovered that at some point in either setting up a flight, or after beginning the flight that I get an error window telling me, "Microsoft Flight Simulator is shutting down", or in some cases "Microsoft Flight Simulator 9 is shutting down.". The point that I get this is random, anywhere from startup to after a flight has begun. My attempts have usually been with third party aircraft (i.e. Gulfstream V, Dassault Falcon 50). I did just try a flight from the default startup with the MSFSX default Baron to see if I had the same problem with default aircraft. Shortly after takeoff, FS9 shut down with no warning directly to the desktop. (without the error window).

 

Based on other posts for folk that had similar problems after upgrading to Vista or Win 7, I have tried startup of my fs9.exe execution in the Windows XP Service Pack 3 (and 2), and Win 7 compatiblity modes. In these compatability modes, I cannot successfuly select alternate aircraft after starting up FS9. I have started up as administrator.

 

I have also made sure that I have no duplicate airports or AFCAD files.

 

Has anyone else been down this road and possibly found a soulution?

 

Respectfully:

RTH

Did you install the FS9 in the same folder with your OS folder?

Did you install the FS9 in the same folder with your OS folder?

Coltrane has a point it should be under Microsft Games/Flight Simulator 9

  • Author

Thanks for the replies Coltrane and Rich:

 

Negative on the same folder as my OS.

 

I have four dedicated hard drives:

 

"C" is my Operating System.

"E" is FSX

"F" is FS9

"I" is a backup drive.

 

To be Continued:

RTH

 

Did you install the FS9 in the same folder with your OS folder?

  • Author

I am afraid I am in a bit over my head here and don't really know exactly for what I am looking, or how to interpret it after I find it. At the exact time I got my error window and FS9 shuts down, I get the following under "Application" in the "Log Summary"

 

Under "Level" = "Error" (with the red excl mark)

Under "Date and Time" = "7/9/2012 10:33:48 AM"

Under "Source" -= "Application Error"

Under "Event Id" = "1000"

Under "Task Category" = "(100)"

 

When I double click on "Error" , under the "General" Tab I get the following:

 

"Faulting application name fs9.exe, version 9.1.0.40901, time stamp: 0x4135a208

Fai;tomg ,pdi;e ma,e imlmpwm. versopm 0,0,0,0, time stamp: 0x0000000

Exception code: 0xc0000005

Fault offset: 0x0d540f4a

Faulting process id: 0x72c

Faulting applicastion start time: 0x01cd5ddfbcc2barf

Faulting application path: F:\Program Files (x86)\Microsoft Games\Flight Simulator 9\fs9.exe

Faulting module path: unknown

Report Id: 1815ea39-c9d3-11e1-bb78-c860000a7fcd

 

Log Name: Application

Source: Application Error Logged: 7/9/2012 1033:48 AM

Event Id: 1000, Task Cattagory (100)

Level: Error, Keywords: Classic

User: N/A, Computer: Office

OpCode:

More Information: Event Log Online Help"

 

Under the "Details" Tab I get the following"

 

"+ System"

- EventData

 

fs9.exe

9.1.0.40901

4135a208

unknown

0.0.0.0

00000000

c0000005

0d540f4a

72c

01cdfddfbcc2ba4f

F:\Program Files (x86)\Microsoft

Games\Flight Simulator 9\fs9.exe

Unknown

1815ea39-c9d3-11e1-bb78-

c860000a7fcd"

 

To be Continued:

RTH

 

 

 

 

 

 

 

 

Have you checked the Error report? Check and see which is the faulty file.

  • Commercial Member

It doesn't matter if you have FS9 & FSX installed to the root folder of your OS. I have both installed to C:FS9, C:FSX

 

To the OP, download a program called Filemon, I think the Win7 version has a slightly different name. Run filemon and then load FS9, it will tell you what files FS9 is trying to access when the error occurs.

 

Should at least point you in the right direction.

Rob Prest

 

  • Author

Thanks Flex:

 

The program for Win 7 is "Process Monitor - Sysinternals"

 

Now if I can learn how to best implement it.

RTH

 

It doesn't matter if you have FS9 & FSX installed to the root folder of your OS. I have both installed to C:FS9, C:FSX

 

To the OP, download a program called Filemon, I think the Win7 version has a slightly different name. Run filemon and then load FS9, it will tell you what files FS9 is trying to access when the error occurs.

 

Should at least point you in the right direction.

  • Author

Found the problem and a solution (after a fashion, although it leaves a lot to be desired).

 

I removed all addon aircraft with only the MSFS9 default aircraft installed and made a flight with no problems. I then added the Gulfstream V as my only addon third party aircraft and tried a flight. My problem reappeared.

 

By a process of elimiantion with trial and error, I was able to isolate the problem in the panel to the installation of my Reality XP GNS 530 WAAS, GNS GMAGTX, and Dropstack.

 

By deleting these line items from my panel.cfg, all problems went away:

 

"Window13=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE

 

Window15=Reality XP GNS GMAGTX - RXP_CONFIG_TOOL - DO NOT CHANGE

 

Window16=Reality XP DropStack

 

Window13=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE

 

Window15=Reality XP GNS GMAGTX - RXP_CONFIG_TOOL - DO NOT CHANGE

 

Window16=Reality XP DropStack"

Just for good measure I also tried editing the window numbers to 13, 14, and 15 but that makes no difference.

Ironically there is no sign of this problem in FSX, only FS9.

I probably will repost this problem with a reality XP title for exposure and also post it on the RXP Reality forum assuming that is available.

Respectfully:

RTH

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.