Hello again!I am almost getting desperate, because I have ransacked my FS9 installationto find out why it crashes to desktop over and over again.I use MRAI's Traffic View Board (an excellent gadget) and I have contactedAarnt Helge about this, but he only gets annoyed for bothering him.The Traffic View Board used to work perfecly before and I never got any crashes, but now it almost always crashes to desktop, and, I haven't a clue why.I checked virtually everything about my FS9, installation, files, modules, etc.and everything seems OK.I also contacted Pete Dowson about FSUIPC, but never got a reply.Could it be to do with FSUIPS, or Microsoft's FS9.1 upgrade?I tried FSUIPC 3.40 and 3.83, and they crashed.It seems like a basic fault in my FS9 system, which I fail to discover.......Any further help much appreciated........Thanks a million.Hans HermanssonSweden

Sorry to hear you have these problems.I know you haved checked your hardware.....But...I had just the same issues and the hardware checked out just fine. so in frustration, just before I was about to reformat in desperation I tried removing the memory modules, one at a time. It fixed it.Another problem I've had was when my Russian wife's friend had installed eDonkey to get some Russian music. I only found this out when I was getting crashes to desk top for no reasons with FS9.When I removed edoneky I couldn't and had to use system restore to get the system back but even then could not revmove some edonkey files. But it did fix the crashes to desk top.AFCAD files doubling up can also cause this problem. Make sure you have no AFCAD's with the same name or that apply to the same airport. There is a file to fix these issues called scanafd.exe or similar name.Another thing to check is the power supply. PSU's can go faultly at any time and cause this kind of issue. Best is to have a 450W power supply and at least 350W. Anything less could be asking for problems.Overheating is another possible cause. Overheating normally results in a frozen locked screen. Some fans in the case pushing and pulling the air through the case may help this issue.I can't think of anything else ohter than the obvious like correct chip sets installed for the MB, up to date BIOS, viedo drivers etc.Hope you manage to get up and running.Peter

Hello!I don't think my hardware is the problem; my PC is new since January of this year, and I have run checks for HDD, memory, etc. with no problems.It has to be something to do with FS9, somewhere, that I just fail to discover..........I have reformatted another drive, where I will, carefully try to reinstall it. I don't hope for too much, though.......Thanks for your tips.Hans/Sweden

Hans I feel for you. Had similar problems (or 'issues' as they're now known) myself. Getting rid of duplicate AFCADS helped a lot.But lately a really pernicious Gremlin has taken residence in my machine and causes a crash if I switch around between cockpit views in the Flight1 C172, and only if I'm flying between London and the south coast. These things are sent to try us...Best of luckIan

I've had a similar problem before and found the FS9.cfg to be the problem.Open it and save as something like FS9.bak. Then delete FS9.cfg and let FS build a new one when it starts........worth a try.http://www.dreamfleet2000.com/gfx/images/F...BANNER_PAUL.jpg

Hello!And thanks for the tip about the FS9 cfg.file.I'll try that,too........Hans/Sweden

I'm commiserating with you. In the last two days, I've yet to complete a flight without either a CTD, or a total, spontaneous reboot.This morning, following a tip in this thread, I let FS regenerate the FS9.cfg file. I also removed most of my scenery, a bunch of which was installed recently. Other than the default, I only have FSGenesis and Ultimate Terrain mesh and scenery for Alaska.That seemed to help. At least I was able to complete a one hour flight to the point of touchdown (all other recent flights CTD'd or rebooted without 20-30 minutes of flying), only to have the screen go blank after touch down when I tried to shift view to the VC. At that point, I had sound, but nothing else, and could not ALT-TAB to anything else. Had no choice but to reboot. And no time to troubleshoot further; it was time to go to work.Next to consider: I've recently been modifying panels, so I'm going to be removing those panel mods on a "last in/first out" basis and see how it goes.FS9 is such a complex beast, especially when we start modifying it, supplementing it with addons, etc., that troubleshooting problems like this can be extremely frustrating!Basil

I hope you guys get your FS9 sorted soon.I started getting CTDs yesterday and after 3 of them I realised it might be the aircraft itself. And sure enough it was. A British Airways iFDG A318 was the culprit and the CTDs vanished when I switched to another jet (a different A318). I too was getting a CTD each time I swtiched to an external view or tried to call the GPS window etc. I deleted the offending A318 and then re-downloaded it. Now it works just fine which means something was amiss in the orginal download. So yea...you might want to test out the planes youre in when you get CTDs...Good luck :)

>Hello again!>>I am almost getting desperate, because I have ransacked my FS9>installation>to find out why it crashes to desktop over and over again.>I use MRAI's Traffic View Board (an excellent gadget) and I>have contacted>Aarnt Helge about this, but he only gets annoyed for bothering>him.>>The Traffic View Board used to work perfecly before and I>never got any crashes, but now it almost always crashes to>desktop, and, I haven't a clue why.>>I checked virtually everything about my FS9, installation,>files, modules, etc.>and everything seems OK.>>I also contacted Pete Dowson about FSUIPC, but never got a>reply.>>Could it be to do with FSUIPS, or Microsoft's FS9.1 upgrade?>I tried FSUIPC 3.40 and 3.83, and they crashed.>>It seems like a basic fault in my FS9 system, which I fail to>discover.......>>Any further help much appreciated........>>Thanks a million.>>Hans Hermansson>Sweden I am gonna go out on a limb here, but it's worth a shot. I used to use FSAutostart, and I used to get crashes all the time. When I stopped using it, no more crashes. Now, before I start a flame war here, I am not saying that the program will cause CTDs, but a novice user like myself probably created an improperly configured windows which can definately cause computer problems. Of course, if you don't use FSAUtoStart, this is all mute.Peter

I've also been experiencing crashes lately. FS never crashed on me until about a couple days ago and ever since then, it's been constantly doing it. It crashes at various times. When it crashes, the screen disappears and turns black and the sound is gone...but I can still see the FS tool bars on top. Then, a few moments later, MS message shows up and I reboot. One time, there was no sound while playing.I don't know exactly what I might've done in terms of modifying FS but it's been a while ever since I installed anything new. I suspected the sound file but I've never touched it recently and I know all my aircrafts' sound files are good to go.Then, I was thinking virus but I constantly update and scan for virus. I also update windows as well. Anti-virus never interrupted flying before either. Any help would be greatly appreciated! Thanks.

Gentlemen & Ladies,The INTEL and ATHLON high performance processors run atextremly high temeperatures when confronted with a programsuch as FS9.This is July.Remove the side casing and install a "home" fan to coolthe system down. A temperature of +/- 70F (20C) shouldhelp.A first step prior to other checks.This is certainly the case in Los Angeles (I live near the beach)and I don't use air conditioning. Despite the wind, interiortemperatures can rise dramatically.If the above doesn't work proceed as mentioned in other posts.Regards, JAHamilton - Los Angeles.

OK This may..may help..any addons lately?? legal or illegal:) the .dll may be causing the problem. Check your latest install.check the .dll and delete it ....if not..restore it!process of elimim=nation??My 2 cents..had it happen before! :)M&M

Are you saying you only have problems with the Traffic View Board? I use it all the time and never have had a CTD or any other problem with it. It's GREAT! Regards, Bob.

This has happened to me too many times..lol...don't get me going!Three things that worked for me in the past were 1.) Recognizing and removing a redundant AFCAD file, as mentioned above 2.) Removing a recently downloaded or added third party panel, and 3.) Reinstalling my (I keep them current) video drivers - CAUTION! ask for help in the forums if you haven't done this (3.) before. Have you clicked the DETAILS tab in the error message to see if you can learn where the problem originated? Often, despite the coded complexity of the message, it will tell you exactly where the fault lies, for example the PANELS.dll or FACILITIES.dll which in my experience with CTD's (EXTENSIVE!), usually at start up with an "out of memory" message, typically points to a roque or incompatible add-on panel or aircraft.http://www.alaska.faa.gov/fai/Clipart/SmlAcft.gifAlex ChristoffN562ZBaltimore, MD

The FS9 CFG file has caused numerous problems for alot of users. Rebuilding a new one can correct your problem 90% of the time. Also are you using any new add-ons? The reason I ask is some of them use the GDIpluss.dll file and this can cause problems as well. I think if you have WinXP, that file is already there. Good luck and keep us posted. The more info you can give us about any changes you have made to FS9 when this problem arose, the more we can help. Best regards, Jeff