#$$%#&$^%@(*&$#&^ M$ PROGRAMMING!!!!!!!!OK, there. I said it.Today. Nice organized flight from EGLL to LFMN. There were like 20-25 aircraft waiting at the Heathrow, all nicely queued up in the 3 minutes slot times. Took my beautiful LDS 767-300, with couple of other addons, from Heathrow. Start it up, set it up, waiting at the gate like 10 minutes for a delivery, that much for pushback and start, and just before I want to start taxiing, CTD. Just clean, pure CTD. So I said ok, something happened. I try again. SAME THING! Not in the same moment, but after some time in the sim. No report in the Eventmanager, nothing in Windows. Just pure FS shutdown. Using FSAutoStart, shutting down all possible applications, using my online stuff, and still...CRASH CRASH CRASH!!!Here, again: #$$%#&$^%@(*&$#&^ M$ PROGRAMMING!!!!!!!!Thanks for hearing me out :)

I believe that 95% of the CTD's are directly caused by addons, mainly seem to be AFCAD files, and they don't have to be close to where you are to cause a problem.If you have installed any scenery or AFCAD files recently I would start by looking there.I, and I am going to kick myself for saying this, haven't had a single CTD since the 9.1 upgrade.Godd luck in finding out why you got a CTD.Dan.

Hi Srdjan,First of all you made a mistake, it's not #$$%#&$^%@(*&$#&^ M$ PROGRAMMING!!!!!!!! but #$$%#&$^%@@@@(*&$#&^ M$ PROGRAMMING!!!!!!!!.But that's OK, it's probably because of your nerves and I perfectly understand you, CTDs are real #$$%#&$^%@@@@(*&$#&^ ...Now I suggest, in addition to Dan's advises to do the following: save your scenery.cfg file and create a new one ( copy to Notepad)with the MS default lines only (until area 38 called addon scenery).Then, delete SceneryStatus.DAT from FS main folder and replace the existing copy of scenery.cfg you also have in C:Documents and SettingsYOUR NAMEApplication DataMicrosoftFS9 with the "new" shorter one you just created. Then you will have twice the same file in both places. If you have no more CTD it means that one of your addon sceneries is interfering, you will have to find the culprid.Clean also your addon scenery/scenery folder from double AFCAD files (2 AFCAD for 1 place)Try also to see if CTDs are season or time related, specific to EGLL or not, check that you have NO folder with landclass SCENERIES together with a TEXTURE folder, (direct CTD!) and come back to us, we'll find the reason Good luck and sorry for my bad English, I hope you'll understand me :-) David

Downlaod Scanafd.zip from this web site and see if you have n duplicate Afcads... Its easy , just read the readme about what to do with the duplicates.

I have been getting CTDS all over the UK latley.I bought a brand new Hard Drive Installed FS2004, A complete Vanilla FS2004 Install and Once the Season is set to spring, You get a CTD. so please MS Fix it..And please do not allow this CTD into the next release.ThanksJason

Jason,You make it sound like everyone who owns FS9 has a CTD because of MS programming. If that were true everyone would be here screaming for help. I for one have never had the seasonal CTD that many people such as you had. I have had several CTD's though but they were caused by me. Most of them were caused by bad installation of video card drivers and a simply uninstall/reinstall of the drivers fixed the problem every time. I have had crashes due to duplicate AFCAD's too or bad installations (by me) of aircraft or scenery. CTD's will continue even with new releases of Flight Simulator IMHO. There have been many discussions in this forum and others regarding CTD's, their causes and fixes. I believe a lot of these problems would be fixed if people would conduct a search of the forums and read some of the possible solutions such as deleting the FS9.cfg and restarting the sim and letting the config rebuild itself. I remember having excellent graphics and frame rates once but the sim kept crashing. I uninstalled FS9 and reinstalled (w/o addons) and still had excellent graphics and frame rates but the CTD's continued. I determined then it was not FS9 but it had to be a piece of hardware causing the problem. I uninstalled my video card drivers and reinstalled them and the crashes stopped. Now whenever I have a crash the first thing I do is reinstall the video card drivers. Hope this helps others who may be suffering unexplained crashes.Ciao,Jim

I re-installed WinXP and FS9 for this reason two weeks ago done this several times since the release of FS9 already).And now I swore myself to take extreme care what I'm gonna install and what not.CTDs are extremely hard to track (last time it was FSFreeware USA Roads which of course doesn't trigger CTDs when installed onto a fresh FS9 installation).It's a mixture of textures, AFCADs and BGLs of all kind (I once moved UT's traffic.bgl to its own folder - crash!) which can cause a CTD by themselves ore only when combined in some special configurations.I gae up hope to ever get rid of CTDs: last time I re-installed FS9, I had a CTD after installing a payware scenery. Being sure that was the problematic part, I de-activated it in scenery.cfg and installed the next add-on scenery. No CTD, then installed the next - bang, there was a new CTD. Deactivated all installed sceneries, the CTD was gone. Re-activated the first installed one, and wonder over wonder, no CTD!You see why I'm giving up. Had CTDs one time until I REMOVED the corresponding lines in scenery.cfg (de-activation didn't help, that's why I thought there's some hidden, inompatible character in the TEXT file which causes the parser in FS9 crash by simply reading scenery.cfg!).This time, I hope I can make it better (limit the installation of add-ons, and be extremely cautious with freeware).Hope the next FS version will at least contain some information why a CTD has ocurred...Andreas

>Jason,>You make it sound like everyone who owns FS9 has a CTD because>of MS programming. If that were true everyone would be here>screaming for help. I for one have never had the seasonal CTD>that many people such as you had. I have had several CTD's>though but they were caused by me. Most of them were caused>by bad installation of video card drivers and a simply>uninstall/reinstall of the drivers fixed the problem every>time. I have had crashes due to duplicate AFCAD's too or bad>installations (by me) of aircraft or scenery. CTD's will>continue even with new releases of Flight Simulator IMHO. >There have been many discussions in this forum and others>regarding CTD's, their causes and fixes. I believe a lot of>these problems would be fixed if people would conduct a search>of the forums and read some of the possible solutions such as>deleting the FS9.cfg and restarting the sim and letting the>config rebuild itself. I remember having excellent graphics>and frame rates once but the sim kept crashing. I uninstalled>FS9 and reinstalled (w/o addons) and still had excellent>graphics and frame rates but the CTD's continued. I determined>then it was not FS9 but it had to be a piece of hardware>causing the problem. I uninstalled my video card drivers and>reinstalled them and the crashes stopped. Now whenever I have>a crash the first thing I do is reinstall the video card>drivers. Hope this helps others who may be suffering>unexplained crashes.>>Ciao,>Jim So why do I not get CTD's Anywhere Else then? Oh I Know My badly configured system Dosent like the UK, or maybe the Nvidia Disp.dll cant draw the UK's land shape....Please my friend id be the last to knock MS, but FS2004 has been a nightmare as far as satbility goes.Jason

Word Not Allowed, I fly out of Heathrow a lot and have no CTD's there. Really don't seem to have them anywhere (except when I screw up). This goes for the PMDG aircraft and the lovely LDS767.Must be some application you have.

:)

Not for me. It's been rock solid stability-wise right from day one. No problems flying in the UK in springtime here either...

>> And now I swore myself to take extreme care what I'm gonna install and what not.Andreas is absolutely correct!All of us have unique FS setups and there is no magic bullet to get rid of CTD's. The best we can do is try to isolate the issue and fix it.For example, I had a CTD at EHAM, but only at certain times of the day and night. At all other times the sim worked fine. I moved to KSEA and tested all different hours and no CTD. So it couldn't be hardware and it had to be something associated with EHAM. I removed all of my EHAM add-on scenery plus EHAM AFCAD and still had the CTD. So I removed all of my AI traffic textures for airlines at EHAM and guess what? No CTD at any time of the day or night. It was a matter of isolating which texture BMPs were causing the crash. There were two files causing the problem. Luckily, those airline repaints existed for other AI models, so I installed different model textures and no more CTD.I relate this story because it's possible to root out the cause of the CTD, though it's not an easy task and one must have some patience. If you're willing to add on to FS, or change your hardware after FS is installed, then be prepared to fix possible CTDs.If FS has a CTD right after a clean install with no add-ons, then then that is a legitimate reason to complain to Microsoft. But to come to the forum and complain about CTDs when the sim has been modified umpteen times after it's original install is just immature and silly. Take some responsibility for one's choices and fix the CTDs or, at the least, stop using add-ons!Listen to the wise words of Andreas: "limit the installation of add-ons, and be extremely cautious with freeware." You'll save yourself both wasted time and trouble.

Thank you all for all your help!I think I isolated these CTDs now to a duplicated EGLL AFCAD2 file. After removing it, things *seem* to be ok.I hope it keeps working OK.And something else... I was not so frustrated about the CTD, but I was frustrated that I missed such a nice organized flight, where I would definitely have MUCH joy in flying it. But no... CTD had to destroy it...OH WELL... next time hopefully...

People have been recently discussing not enough voltage for their "Corsair" brand memory, and having to go into the Bios to adjust it. If you a plagued by CTD's, it could be hardware.

So, it wasn't #$$%#&$^%@(*&$#&^ M$ PROGRAMMING!!!!!!!! after all?????