Thanks Ed I'll give it a try...

I checked around this morning to see if I could find a published AFCAD for this airport, but no luck. I checked the airport through AFCAD but its not showing any kind of error. Have you ever added any type of scenery to this area? Are you certain this is the airport that is causing the problem? I'm going to load up my sim and see what else I can come up with. Keep us posted in case you do indeed find that this is the problem with directly related to the CTD. Do you have Ultimate Traffic or My Traffic or any other Military type AI program installed? Hopefully we are narrowing it down. John Haley

Thanks John, I think this is specific to my system as I didn't have this problem before. The only major add-on I installed and uninstalled recently when I started noticing this was Ultimate Terrain USA. I never had this problem until after I uninstalled UT USA. I'm not saying that's the reason but these weird CTD

I also had CTD's after uninstalling UT:USA. It's possible that the uninstall process doesn't completely clean up after itself. Unfortunately, I had to do a reinstall to clear it up. :-( Good luck!

It might be time to take this issue over to Flight1's forum if that's indeed the case. I have way too much installed/invested to try and rebuild my whole FS9 installation... :-hang

I never had this problem until after I uninstalled UT USASomeone with this software should check to see which default texture files might be modified by the install.Then check to see which modified files might have been removed by the uninstall and the default texture files not reloaded.The only two causes I've seen of a persistent CTD in one area are bad texture files and bad AFCAD files.The default air field data - there is not such thing as a default AFCAD - Lee's program just reads the default data - is in the APnnnnn.bgl files for the scenery area. Each of these files can include up to 150-200 airports. You do not want to delete or mess with them. But creating an AFCAD file will make FS not read data in a default file.There are four or five default airports in Europe with bad data which will cause a CTD. Each of these has a helo pad with a start location with exactly the same name as a runway start location.Normally an AFCAD CTD is caused by an airport about 70-90 miles ahead of your flight path, with 40 degrees of your course. That's about when the program reads the airfield data and moves it from disk to the paging file.Bad textures can be in the main texture folder, and add-on scenery folder, the SceneryWorldTexture folder or on AI aircraft. I've seen an AI aircraft loading 95 nm out cause a CTD.But since you can pin this down to one program uninstall, I'll bet it's a texture which was removed and has not been reloaded.A good alternate would be to just take the install CD and copy the texuture files from the CD to your texture folder and sceneryworldtexture folder.If you've used something like AEU or some modified cloud textures, you'd not want to overwrite them, but any missing textures should copy in quickly.

Thanks Reggie... I'm finding it amazing missing textures can affect FS9's stability...

I narrowed this problem down to the modules folder. It's late and I'm off to bed. Tomorrow I'll try and figure out which module is the true culprit... :-smile12

I found the two dll's that are causing the problem. Lago's two 'ViMaCore2004.DLL' files. These dll's are the main controllers for add-ons like FDE and Georender. I wonder why these files are now causing a problem throughout FS and if reinstalling programs like FSE will resolve this.What's troubling is the error message above states that these files are trying to contact a remote server. Lago has no business sending info off my machine to a remote server for any purpose unless I know before hand.

I wonder id that is actually the culprit but instead errors in the scenery elements that have been interfaced to it by authors of add-ons using it.

Reinstalling FSE seems to have solved the problem. I'm still testing though. FSE was the main add-on that placed this .dll in the modules folder. I figured reinstalling FSE should correct whatever's wrong on the registries side. So far I'm right but we'll see...