Hello:

 

For some reason, when I start a flight at certain airports, (3 I have determined so far) my FSX locks up.

 

What I do is I go into "free Flight" set up my flight as I always so; everything loads and then when the load bar reaches 100% Complete, everything just locks up. As I said, this only happens at 3 airports that I have determined so far, and only when I start a flight from the airport. In other words, I have no problem flying around or landing at the airport, it only when I load a flight.

 

Also, none of these airports have any add on scenery.

 

Could the airport .bgl's be corrupt?

 

If so, how do I replace them?

 

Others have told me I need to run a "repair". But to do that, I need to uninstall the SP's which has been a problem.

 

Let me know.

 

Thanks,

 

Dave

You should download and install App Crash View - http://www.nirsoft.net/utils/app_crash_view.html and let us know what caused your crash(es).

 

We also need to know system specs. Are you overclocked? Windows 7 64 bit?

 

Deleting your fsx.cfg and restarting FSX and letting the config rebuild is just as effective as a repair in most cases. A lot of people rename the fsx.cfg to something like fsx.orig instead of deleting it so that if the problem is not resolved, they can go back to the original fsx.cfg. If you have an SP installed or Acceleration, many problems have been fixed by uninstalling SP2 (or Acceleration) then running FSX and seeing if this fixes the problem. If not then you should do a complete repair and reinstall the SP's. We need to see what caused the crash first as it could be something simple.

 

What are the names of the airport sceneries? That would be important. What aircraft are you trying to load? Is it the same when you have your crashes?

 

Best regards,

Jim

lehbird,

 

I have had hangups like what you are describing when I switch to a monitor with a different resolution than the one connected on the previous startup of FSX. It doesn't crash, but it just hangs at 100%. It can be fixed easily by going into settings from the FSX startup page, before you load a flight. However I don't think it is airport specific for me.

 

Mike

You should download and install App Crash View - http://www.nirsoft.n...crash_view.html and let us know what caused your crash(es).

 

We also need to know system specs. Are you overclocked? Windows 7 64 bit?

 

Deleting your fsx.cfg and restarting FSX and letting the config rebuild is just as effective as a repair in most cases. A lot of people rename the fsx.cfg to something like fsx.orig instead of deleting it so that if the problem is not resolved, they can go back to the original fsx.cfg. If you have an SP installed or Acceleration, many problems have been fixed by uninstalling SP2 (or Acceleration) then running FSX and seeing if this fixes the problem. If not then you should do a complete repair and reinstall the SP's. We need to see what caused the crash first as it could be something simple.

 

What are the names of the airport sceneries? That would be important. What aircraft are you trying to load? Is it the same when you have your crashes?

 

Best regards,

Jim

 

Jim:

 

Thanks for the response. To be clear, FSX does not CTD it just hangs up at "Loading 100% Complete". So will "Crash View" work?

 

I run Windows XP, no overclocking, 4MB RAM

 

It crashes at KATL, KCVG, (and a 3rd that escapes my memory). None of which have any add on sceneries. I also have 0% ground, air, and road traffic.

 

It occurs with ANY aircraft at these airports.

 

"Crashes" are always the same; Loads to 100% and freezes.

 

Thanks,

 

Dave

Jim,

 

Thanks for the link to App Crash View (and a number of other similar useful programs). It has already helped me to possibly track down the source of a recent otherwise inexplicable crash.

 

Mike

I run Windows XP, no overclocking, 4MB RAM

 

Unfortunately AppCrashView will not work with XP systems. The only solution to find what caused your error would be for you to look in your Event Viewer which records every Application crash, including hangs. Without this information, it would be impossible to find out what caused your crash. Just a statement that it hung at 100% complete loading does not indicate what could have caused the hang. In a crash report or hang report, you will see in the event viewer a reason for the crash or a faulting module (for instance Faulting Module: PMDG.dll). That tells you and us that it must have been caused by a PMDG module. You would then be asked to uninstall PMDG and reinstall it.

 

Some crashes can be fixed by simply deleting your fsx.cfg, restarting FSX and seeing if that fixes the problem. If it does, then you probably had a bad tweak installed. Some crashes can be easily fixed by uninstalling Acceleration, running FSX and seeing if this fixes the problem.

 

I know of no cases of FSX crashing at Covington or Atlanta defaults. KATL payware has had CTD's but you say you have no addons.

 

I suspect your FSX.cfg as the problem but you should take a look in your Event Viewer and see if you can identify a faulting module. Here's how to use the Event Viewer for XP - http://support.microsoft.com/kb/308427 (easier for them to explain that I giving you more detailed info). You want to look in the Application Log for FSX and it will show you all FSX events. If nothing there, then go to the System Log.

 

Hope this helps!

 

Best regards,

Jim

 

Jim,

 

Thanks for the link to App Crash View (and a number of other similar useful programs). It has already helped me to possibly track down the source of a recent otherwise inexplicable crash.

 

Mike

 

Glad it was useful Mike. BlueScreenView is another good one for BSOD's. The best thing about it is they are free!

 

Best regards,

Jim

It occurs with ANY aircraft at these airports.

 

"Crashes" are always the same; Loads to 100% and freezes.

 

Thanks,

 

Dave

 

Dave, I don't mean to annoy you, but this is exactly what happens when I attach an external monitor to my laptop, and the hardware setting in FSX is not correct for the different resolution of my external monitor.

 

Mike

Dave, I don't mean to annoy you, but this is exactly what happens when I attach an external monitor to my laptop, and the hardware setting in FSX is not correct for the different resolution of my external monitor.

 

Mike

 

Mike:

 

You're not annoyiny me :-) It's just that as you pointed out, your situation occured at the start up for EVERY airport, not just a few. So I am geussing my situation is different.

 

Thanks!!

 

Thanks Jim; I will give your suggestions a try.

Well I just removed my FSX.cfg file to get a new one written (as I have done many times before) but I get a dialog box which says: " Flight Simulator can not be run because it could not write FSX.CFG"

 

Thoughts....

Well I just removed my FSX.cfg file to get a new one written (as I have done many times before) but I get a dialog box which says: " Flight Simulator can not be run because it could not write FSX.CFG"

 

Thoughts....

 

Did you once have the FSX demo installed? Here's a possible fix - http://answers.micro...59-06ba9eb116b8

 

Best regards,

Jim

Well I got it to re-write. still crashes @ 100%. Will have to try the event viewer.

Dave,

 

I just thought of something else. I used to have problems of weird directional readings in FS2002 when, if I remember correctly, an FS9 AFCAD was installed for an FS2002 airport. This would show up very far away from the airport that contained the troublesome AFCAD. So I am wondering, since your issue is airport specific, if perhaps you have some AFCAD or something similar installed from a previous version of FS? Just a thought.

 

Mike

Dave,

 

I just thought of something else. I used to have problems of weird directional readings in FS2002 when, if I remember correctly, an FS9 AFCAD was installed for an FS2002 airport. This would show up very far away from the airport that contained the troublesome AFCAD. So I am wondering, since your issue is airport specific, if perhaps you have some AFCAD or something similar installed from a previous version of FS? Just a thought.

 

Mike

 

Mike:

 

I agree completely with what you are saying. It has been my belief all along they are corrupt afcad files causing the problem. What I am not clear on is how to determine the offending files, and if I were to remove them, how and with what do i replace?

 

Thanks,

 

Dave

Dave,

 

The original AFCAD program should still recognize all airport files, including add-on ones, even though it can damage airport files created by newer software if you use it to save an airport. I can't find it at the moment, but I also came across this:

http://library.avsim.net/zipdiver.php?DLID=45600

I am not familiar with it but it might do what you want.

 

I will look further this evening at home.

 

Mike

 

Mike

Dave,

 

My advice yesterday was wrong. The AFCAD program only works with FS9. The utility I mentioned also appears to work only with FS9. ADE, the successor to AFCAD, does not appear to find all airport data, only stock airports. I am a bit stumped -- my advice is to suggest that you search Addon Scenery and all its subfolders, as well as FSX/Scenery and all its subfolders, for the codes for the airports that give you trouble. If that doesn't work, just search all of FSX. For Atlanta I would suggest using "ATL" without the K as that is more likely to find something.

 

Another thought: FSNavigator for FS9 usually shows the source files for its data, so you might try downloading FSTramp for FSX, by the same author. http://www.fstramp.com/ After it has constructed the database, open the map display and see if the source files display when you hover the cursor over various elements of your airport. FSTramp is not free, but it comes with 20 free startups.

 

Maybe Jim has a better idea.

 

Mike