Hi Luca, I would like to help you, if you can send me a flight plan, and I will redo the same flight and see.I have just fly Zurich to Innsbruck with the current season set winter, no weather and I got no CTD, (users nick rogue1 have ctd in this flight) this is why I have done this flight.I am Using the default cessna in this flight above, ALL official PAI Aircraft installed, All PAI official AFCAD from them installed, and 650MB mesh installed.All fs2004 to full expect mesh to 85%, no shadows at all, no dynamic scenery, 2x antialasing, 4x anasotropy, 1024x768 32 bits, full screen, render to texture enabled, no weather.ThanksChris Willis[link:fsw.simflight.com/FSWMenuFsSim.html]Clouds And Addons For MsFs

Hi Chris.First of all, and then to my (our) problem, thank you for your wonderful work. I've been using your clouds since Fs2002, and am enthusiastic about them.I'm going to cut and paste a post I wrote in one of the many topics about CTD's. What I'm describing is exactly what happened when I fired up the sim purpously to save the flight situation I was going to send you.This is to show you how baffling this matter is getting for me.Then, if you don't mind, I'm hitting the sack and will get to you later. Please bear with me and take a few minutes to read on. I will come back to the forums whithin the next 10 hrs. Thanks again for your help, and happy new year.---------------------------------------------------------------------The combination of factors causing CTD's it's going to be a hard one to track down.This is what happened to me, if it can be of any help:I got my first endless sequence of CTD's taking off from Zurich in December (real date/real weather, FPL to LIMF). I was using Jon Murchison's BAe 146-200 with a freeware panel found at Avsim (rjpnl2.zip).By changing plane to the default 737, I was able to fly a few minutes longer, but the CTD happened anyway.I was then able to use the BAe 146-200 ONLY WITH BLACKED-OUT PANEL (i.e. removing all gauges lines in panel.cfg). Although, I didn't fly long enough in that situation to see if the CTD would occurr again (flying with NO instruments gets boring pretty soon!).So here I go, and a couple of days later I decide to take off from LIMF (Torino, Italy), my hometown airport. I'm using Jon Murchison's BAe 146-200 once again.Once again, right before rotation or a few thousand feet off the ground...CTD.In all of these occasions, I had a flight plan loaded which was including LSZH (Zurich) as a departure or arrival airport.In all of these occasions I tried every possible combination in terms of landclass, afcad files, terrain mesh, weather, AI, you name it. A situation with ALL default files (ALL add-ons removed, ALL left overs cleaned out, scenery.dat files recreated, default fs9.cfg) would STILL give me CTD's.CHRIS, HERE IS WHERE I LOAD THE SIM TO SAVE A FLIGHT SITUATION:So yesterday (Dec. 30th) I go back to LIMF, and take off from RWY36 with the default Lear, Fair weather theme and NO FPL loaded.And there I go; RWY HDG to FL5000, turn right HDG 090, climb to FL20000...No CTD so far. I'm getting excited, so I start flying freely over the alps. Gee, I say to myself, this is what I've been missing!Air outside is cold and crisp,glaciar planes open up below me,glittering under the sharp winter sun-light.My engines purr,and so do I,in my warm and cozy cockpit.A distant flickeringdraws my eyes to look up:on the other end of a long contrail,a big metal bird is cruising,high and fast.OK, I THINK, THIS IS IT!So I go back to LIMF, RWY36. This time I'm on the default 737, destination NOWHERE. Everything goes smooth as before, so halfway through my extacy I decide to open an IFR FPL to, guess where, Zurich!Right after Zurich center has tracked me and assigned me to ILS RWY16, I start my descent to FL 19000 as per instructions.All of a sudden the dream is over. CTD.Ok, this is beginning to wreck my nerves.At this point I decide to dare, and create a flight starting from Zurich, default Lear, Fair Weather theme.I once again try ALL possible combinations software-wise (ALL add-ons removed, ALL left overs cleaned out, scenery.dat files recreated, default fs9.cfg).Now this is what happens:flight simulator ALWAYS kicks me back to the desktop 56% through flight loading. EVERYTIME.I don't even get to see the runway, this time.I could nail all this down to Zurich, if other people wouldn't be getting CTD's in completely different areas and situations.OK CHRIS, HOPE THIS MAKES SENSE.GET BACK TO YOU LATER.Luca

Dazzlercee.This may do no good but still worth checking....Look at your CPU/system temps and also PSU voltages- not just via the hardware BIOS monitor. Install and run something such as Motherboard monitor - this can give you a continuous readout and also save to a text file so you check the moments before a CTD .A couple of years ago I had similar problems with FS2k2 when I first built this PC and installed the sim.Eventually came down to a slightly unhappy PSU coupled with slightly high CPU temps under heavy load.A new PSU and some extra cooling cured all.Good luckDave

I would suggest that you get hold of memtest86 and run it overnight. I had CTD problems which I eventually traced to RAM. HTH--qnh

If it was ram or overheating or bad voltages etc etc... surely this would affect all other software as well such as LOMAC, Comanche 4, IL2, Flanker 2.51.As I have said previously, FS is the only software I am experiencing problems with. I will however try your suggestions.Thanks.Daz

Just downloaded Memtest86 but unfortunately it won't run on my system. Must be something to do with the new AMD64 memory architecture.

I'm sorry to repeat myself, but I'm afraid that if we insist with this "update your drivers and check you BIOS" business, we are not going anywhere with this CTD.As far as I'm concerned there have been no changes in my system since I've had fs9 installed (5 months), and all of a sudden, in December, I started having CTD's.Getting your system in shape sure is the first thing to do, but I would be assuming that people experiencing this sudden show stopping bug have already taken care of that.I think the road to hit, as it's happening in another similar topic, is to track down changes whithin the sim itself, as well as a series of factors that these damn CTD's seem to have in common, mainly time of the year.All of a sudden we find ourselves doing funny things, like running memory tests overnight (I ran memtest myself!), when there is clearly a software flaw.But then again, I might be wrong.Whatever you think its best.Hope this makes sense to you.Luca

I'm running an AMD64 3200+ based system with ATI 9800 video and Catalyst 3.10 drivers and have no problems. I did have the same problem and corrected it by replacing flawed Microsoft textures. I'm going to take the liberty of pasting in an answer I found in the PMDG Newsgroup as to the reasons for the CTD and the solution. Good Luck!DickHi all,just as a heads up, Jobia has released a new version of his global patch that fixes the CTDs during late fall and early spring. The likely hypothesis for the crashes is that the CTDs are triggered by incomplete or incorrect look-up tables for texture blending at airfields. The patch works by deactivating the new feature in FS9 that blends the underlying landclass textures with the airport background (grassy) polygon. In other words, the airport grounds will look more like the FS2002 versions again, with singular textures. Currently, all the documentation is in German only, so here's a quick guide for installation:1. Download crashto.zip at http://jobia.bei.t-online.de/crashdes.htm and unzip into temporary folder, with "Use folder names" enabled.2. make a backup copy of your FS9terrain.cfg file3. copy the .bmp files from the PatchTexture folder into your FS9Texture folder4. copy one of the two replacement terrain.cfg files into your root FS9 folder. The version in the "terrain_cfg mit ..." folder retains the default blending of landclass textures along the utility lines, the version in "terrain_cfg ohne ..." replaces the blending with simple textures. Both versions fix the seasonal CTD crashes, the additional changes to the utility corridors are just a pet peeve of Jobia and have no influence on the crashes (in Europe, most utility corridors don't have clearings cut, unless they run through forested areas). The patch is easily reversible by deleting the new terrain.cfg and replacing it with the original. You don't have to delete the .bmp files that came with this patch because they get called only by the altered terrain.cfg.Cheers, HolgerP.S.: For the technically inclined, Grahame has kindly (and freely) translated some of Jobia's information, copied from this post http://portal.fsgenesis.net/index.php?name...viewtopic&t=374 :"In my opinion,the main reason why this is happening is due to the new Landclass funtion MaskClassMap2 in the terrain.cfg, and the way the airport ground polygons are displayed. The files in themselves work OK, but MS has changed the parameters of some of the associated data that influence the way these files work."They saved programming time by building in a sort of "chameleon" effect into the data, so that the airport grass is displayed over the surrounding landclass scenery, in that the texture display switches automatically to a partner landclass file. This has the advantage that MS doesn't have to worry about the ground texture polygons at airports.The advantage for MS is that the airport and surrounding scenery blend together more easily."It was well thought out, but unfortunately, it only works with default landclass scenery."However, with addon landclass, the original landclass textures are displayed at the airports, due to the fact that the partner landclass file doesn't work with the addon landclass data, and so you have effects like cornfields between the runways etc."One of the specific problems at Sion (and possibly why it causes a CTD) is caused by the fact that the borderline for the texture change to display the seasons runs right through the middle of the airport,and due to the new BGL coding in FS9, it's not possible to use landclass data for the airport ground polygons, then you get unpleasant effects like autogen trees etc all over the airport. So,you have to use textures instead, to get round the problem with the "masking effect" that MS uses to make the programming easier."The only disadvantage from using textures instead of landclass data is the fact that polygons only use one texture, independant from the size, whereas landclass has seven different polygon sizes available. But with grass at the airports it doesn't pose a big problem, as grass always looks about the same everywhere."

Maybe it is a daft idea but have you tried older ATI drivers. I went back to 3.9's from 3.10 'cos the multimonitor support did not seem to work properly. Maybe it will cure other problems. Worth experimenting.Regards

>If it was ram or overheating or bad voltages etc etc...>surely this would affect all other software as well such as>LOMAC, Comanche 4, IL2, Flanker 2.51.>>As I have said previously, FS is the only software I am>experiencing problems with. I will however try your>suggestions.>>Thanks.>>DazFS was the only software that I was experiencing problems with too! Word, Excel IE etc. all ran fine, even FS2K2 ran fine, FS2K4 did a spiralling (:-))CTD usually within 30 minutes to a hour. It took multiple passes of memtest before a failure was recorded. --qnh

>I'm sorry to repeat myself, but I'm afraid that if we insist>with this "update your drivers and check you BIOS" business,>we are not going anywhere with this CTD.>As far as I'm concerned there have been no changes in my>system since I've had fs9 installed (5 months), and all of a>sudden, in December, I started having CTD's.>Getting your system in shape sure is the first thing to do,>but I would be assuming that people experiencing this sudden>show stopping bug have already taken care of that.>I think the road to hit, as it's happening in another similar>topic, is to track down changes whithin the sim itself, as>well as a series of factors that these damn CTD's seem to have>in common, mainly time of the year.>All of a sudden we find ourselves doing funny things, like>running memory tests overnight (I ran memtest myself!), when>there is clearly a software flaw.>But then again, I might be wrong.>Whatever you think its best.>Hope this makes sense to you.>>LucaLuca,Whilst I understand your anger and frustration, if it were a software problem then it would be experienced by everyone and not just a few. The personal computer has evolved rather rapidly over the past 20 odd years. Such evolution results in incomaptibilities and other problems that only come to light when a certain set of circumstances exist. I would suggest in your case that you reformat and start again (if possible). If you are using Windows XP then use the system restore function to checkpoint your system as you add software and/or drivers. If you have had a working system as you state in your message then that also indicates that the software does work. I would also strongly suggest the use of anti-virus and anti-spyware software. You would be surprised some of the things that virus's and spyware change without your knowledge.HTH--qnh

I am joining in with a 'me too' post. I used to fly my plane perfect, and then all of the sudden in Dec(mid Dec) I get CTD. After dealing with it for a few days, I go for the 'big one' and reinstall. No joy. Still had the CTD problems. My GPU fan was being flaky, so I thought what the heck and went out and bought a new fan for my 4600. Installed it, no joy. RE-installed it(I thought I messed up the first time, but I didn't), no joy still. It doesn't matter the plane, or the flightplan, or the locale, it happens.The *only* thing that clears my problem up with 100% success(so far, cross my fingers) is blowing a fan into my case. Seems to indicate my system is overheating, but that doesn't make sense to me. I play Metal of Honor: Breakthrough and I don't get CTD. That game puts my system through the same high paced CPU and GPU calculations, making the same amount of heat, often times for the same amount of time as my FS would, and it doesn't CTD. So I state it again, I don't know why the fan is helping me. Maybe I just happen to be lucky.I think the ball is in Microsoft's court. I don't know if my CTD is software related(as I feel most of the CTD on this forum are), but I think FS9 has a serious problem that needs to be addressed.

About this memtest application. My PC was up and running all day yesterday, running apps, online games and various flight sims. Not one restart or crash to desktop until I ran FS2004 last night.Someone mentioned that only after numerous runs did memtest find an error. Well how come this so called possible memory problem *only* affects FS. Nothing else has problems all day then 10 minutes after booting FS last night....wham...bam...hello desktop.If their is a problem with memory then in my opinion it is created by FS. I don't know how or why, I'm just sure that FS is the cause. It may only be with certain chipsets, memory speeds etc but there is definately something about FS that is incompatible with certain combinations of hardware (and maybe only at certain times of the year).Daz

>About this memtest application. >>My PC was up and running all day yesterday, running apps,>online games and various flight sims. Not one restart or>crash to desktop until I ran FS2004 last night.>>Someone mentioned that only after numerous runs did memtest>find an error. Well how come this so called possible memory>problem *only* affects FS. Nothing else has problems all day>then 10 minutes after booting FS last>night....wham...bam...hello desktop.>>If their is a problem with memory then in my opinion it is>created by FS. I don't know how or why, I'm just sure that FS>is the cause. It may only be with certain chipsets, memory>speeds etc but there is definately something about FS that is>incompatible with certain combinations of hardware (and maybe>only at certain times of the year).>>DazIt is quite possible that the problem with memory is detected by FS, I doubt that it is created by FS. My suggestion would be to take the machine back to a basic state. 1 stick of RAM, no overclocking, defaults in the BIOS. Reformat and install XP and SP1. Install latest chipset drivers, install Microsoft recommended video driver. Install FS9 and try a flight with the default aircraft only - don't install any addons, no FSUIPC, no clouds, no nothing - just the defaults. If you can fly for two hours with this setup then add extra hardware - i.e. RAM an so on, one piece at a time - test for at least two hours after adding each piece. Once all your hardware is back in then move on to the software, again, one a time and test after each install. Remember to keep a log of what you are doing - use System Restore to checkpoint the system before adding software.It sounds painfully slow and it is but welcome to the world of problem diagnosis - if all the "quick fixes" have failed then this is all that is left.HTH--qnhP.S. You may need a soundcard installed for the first flight - if you do then make sure it is either on board or in the PCI slot that is the furthest away from the AGP slot.

I just encoutered the CTD related to landclass clashes within FS9. After finding this thread I applied the Jobia fix and it worked. I had saved a flight that crashed everytime and the flight continued on without a hitch after the fix. If I have to "suffer" some texture imperfections on aprons and such, so be it. I really appreciate the research done by Jobia and by those here at the forums to find a fix for this awful problem!!!!!!..........PS...hope it works for everyone invovled!!Randy Jura, KPDX