Whenever I run fs9, whether from desktop or direct from fs9.exe, fs will crash around 15 seconds after the splash screen appears. I have searched this problem on google and this forum, but everyone appears to have installed something new on their system. My fs9 was running normally just 20 minutes before the crashes started, and no changes to my computer.The only lead I can give you is that the remote procedure call (RPC) keeps terminating after a few hours, all internet sources point to a worm in my computer, but my AV providers checked, and nothing found in my computer. However, RPC failing does not affect any programs, including fs9, I've learnt to live with this possible error for a few weeks now. But now I cannot run fs9, I'm actually raging. FSX works fine.

Whenever I run fs9, whether from desktop or direct from fs9.exe, fs will crash around 15 seconds after the splash screen appears. I have searched this problem on google and this forum, but everyone appears to have installed something new on their system. My fs9 was running normally just 20 minutes before the crashes started, and no changes to my computer.The only lead I can give you is that the remote procedure call (RPC) keeps terminating after a few hours, all internet sources point to a worm in my computer, but my AV providers checked, and nothing found in my computer. However, RPC failing does not affect any programs, including fs9, I've learnt to live with this possible error for a few weeks now. But now I cannot run fs9, I'm actually raging. FSX works fine.

This is often discussed.It is usually either a corrupt or wrongly configured fs9.cfg file, or a startup situation for an aircraft now removed from the setup.First thing to do is to back up the fs9.cfg file and delete the original. FS will build a new default file although you may then want to re-customise your settings.From memory (somebody else may confirm) you just delete the errant startup file for the latter situation but again take a back-up copy first.John

You can also use Process Monitor to see what files FS9 accessed just before the CTD. Search Google.

This is often discussed.It is usually either a corrupt or wrongly configured fs9.cfg file, or a startup situation for an aircraft now removed from the setup.First thing to do is to back up the fs9.cfg file and delete the original. FS will build a new default file although you may then want to re-customise your settings.From memory (somebody else may confirm) you just delete the errant startup file for the latter situation but again take a back-up copy first.John

I already tried renaming fs9.cfg, it still crashes, although it creates another empty fs9.cfg

Now fs9 gets past the splash screen, but immediately crashes again when it gets to the main screen.I used process monitor. No help there. Everything is successful

Did you try running FS9 without addons?

Did you give the Flight 1 Registry Repair Tool a try?

That isn't the purpose of this gadget, I'm afraid. It is for add-ons that read the registry.This article may help:http://support.microsoft.com/kb/837195John

That isn't the purpose of this gadget, I'm afraid. It is for add-ons that read the registry.This article may help:http://support.microsoft.com/kb/837195John

Thanks for the clarification. :)

Did you try running FS9 without addons?

Yes, same thing happens. I think it might be another program having conflicts with fs9.exe, and closing it.

That isn't the purpose of this gadget, I'm afraid. It is for add-ons that read the registry.This article may help:http://support.microsoft.com/kb/837195John

I'm afraid none of the methods work.

Yes, same thing happens. I think it might be another program having conflicts with fs9.exe, and closing it.

It could be your anti-virus updated unbeknownst to you which in turn is causing fs9 to crash. Did you try running fs9 with your anti-virus temporarily off?