I'm having constant 'Crash To Desktop' at or just before I reach my cruising altitude. This is happening no matter what aircraft or location I fly out of. I have no multiple Afcad2 files anywhere so I'm at a loss as to what's causing this. Has anyone seen this message in event viewer concerning FS9 before???"The description for Event ID ( 1000 ) in Source ( Microsoft Flight Simulator 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: fs9.exe, 9.1.0.40901, unknown, 0.0.0.0, 00000000."This has really become a serious problem for me...Thanks to anyone that can help... :-hmmm

Dillon, what else are you running besides FS9.1, FSMeteo, Active Sky anything like that? Multiple monitors?Ed GreenKCLThttp://www.panelshop.com/DEV.jpg

While not directly related, although I do not fly online, everytime I start FS9.1 my firewall app tells me FS9 is trying to use the Internet. Since I'm not plugged in I tell it to let it go.Perhaps you have turned off some windows service that it requires. The failure description you posted notes a problem with a remote computer access. Do you have on-line weather download enabled? Are you using any networking facilities? Instructor's station disabled?It is possible that whatever service is being requested has a time-out field that expires just about the time you reach cruise.Run a test with no add-on apps activated and using only the clear weather theme with a default aircraft and go from there. Also check that the .dlls in your modules folder with the version displayed on properties (right click on file name) are in fact for MS supplied ones version 9.1.xxxx. Any non-FS modules must be 9.1 compatible such as FSUIPC must be 3.45 or later (3.48 is current).

Hey Ed, I'm not using anything out the ordinary. I was on the same page as you thinking it could be external programs causing this problem so I ran FS2k4 without programs such as ASV, FDC, and AI Smooth running in the background. I took off from Dekalb-Peachtree in Atlanta headed for KLGA under a full IFR flight plan (FS9 default flight plan that is) and soon as I almost got to my cruising altitude of 25,000ft (in ES's Citation II), FS9 crashed to desktop. I'm always using the ATL-KLGA route for testing now as the CTD happens like clock work every time. It's the strangest thing.I changed the name of the default FS9 directory and reinstalled FS to see if whatever missing DLL could be replaced. That still didn't solve the problem. I've since renamed the FS9 directories to reflect my active install with all my add-ons (the other install is my test bed). I'm at a lose right now because I've made sure there were no DLL's missing from my original installs directory. Maybe there's a problem with the Flight Plan itself so now I'm off to create a new one and see if that solves the problem... :-hmmm

Ronzie I think you could be on to something. There may be a service turned off, I'll check. I've tried your suggestion about not activating any active weather. The only thing I didn't try was using a default plan such as the Learjet. I'll give your suggestions a try..."Do you have on-line weather download enabled?"I would think so... :-hmmm "Are you using any networking facilities?"Not sure what you mean here or how to check it... :-hmmm "Instructor's station disabled?"I totally have no idea on this one... :-zhelp Thanks... :-wave

DillonAssuming you're using Windows XP, why don't you try System Restore using a restore point logged before these CTD's started.Then, if FS behaves normally, start adding back whatever programs you've installed after that restore point or system changes you've made until you nail the culprit.Hope this helps.Toni.

Check the AFCAD's around the area where you reach cruise. My guess is one is incomplete. CTD's are not just about duplicate AFCAD's, they are also about incomplete ones as well. Some time ago I had a crash on climb from Ottawa to Halifax in the same area. When I jotted down the airports in the area and checked, one that I was climbing over was incomplete. Verified it through the AFCAD fault finder. I fixed it myself, saved it and voila, no CTD. Just a suggestion. John Haley

The funny thing Toni is I went into Event Viewer and discovered these FS9 errors have been going on for some time (at least since March 2005). My restore points don't go back that far... For some strange reason I didn't notice it or something else was triggering the errors (I guess it would be virtually impossible for me to miss a CTD). So at this point since CTD'a are so frequent now (we'll like clock work) I need to find out what's causing this... The last thing I feel one should ever do is reinstall the sim. At this point it would take me at least two to three weeks to build the sim back up to where it is today (add-ons, etc.)... This is the sad difference of FS and many other titles out there (the huge add-on library we all have)...

"AFCAD fault finder"Where can I get this utility??? I have no add-on airports over South Carolina... :-hmmm

No sweat, the fault finder is not a separate program, it is built right into the AFCAD program itself. It's listed under the "tools" heading. Do you have AFCAD installed? Check airports in the area where you are experiencing your CTD's. You can do this by starting the sim and slewing to the area you are having problems. Then fly around and see if you CTD. Make sure you jot down the airports in that vicinity. Then check those airports through AFCAD and the fault finder. This is not about add-on airports, this is about AFCADS that may/may not be installed in the area you are flying. Even default AFCADS can be replaced and or altered without your total knowledge. Good luck, I can only say that my CTD's have been few and far between. When I have checked, its always been an AFCAD problem. John Haley

How do you fix it if you find it???

Where are the default FS2k4 Afcads located???

Dillon,I had the same problem (or at least very similar)... For starters, move ALL of your AFCAD2 files to a temporary folder somewhere away from .../Addon Scenery/Scenery and see if you still get CTDs. If you do, well, then at least you will be sure that your AFCAD files are ok and can move them back. If no CTD, then one of them is to blame. Then, like John wrote, check one after another with the Fault Finder within the AFCAD2 program.Another idea... is it possible that one or more texture files are missing? I believe that x:/FS9/Scenery/World/texture is the correct path - I am at work right now and my memory isn't what it used to be. :) Anyway, it's the folder with lots of files that have lots of numbers in their names, like: 035b2sp5.bmp and so on. Regards,Jure

Well John it looks like your right. My problem seems to stem around Flyen-N-S Ranch in Georga (GA09). AFCAD2 is reporting no problems with this airport but soon as I get close to it or choose it in the menu to fly out of, FS9 crashes. This is the weirdest thing more so because it's puzzeling how this happened... :-hmmm Again does any know where the default Afcads are stored in FS9???

Dillon, try starting AFCAD2 and then loading that particular airport. Use the analize function of AFCAD2 to see if you can identify the problem with the airport. Chances are, if that's the problem, you will be able to fix it using AFCAD2.Ed GreenKCLThttp://www.panelshop.com/DEV.jpg