Hi Gang any body else getting the CTD's.Im about Fed up with it now. Ill not except that its a peice of Freeware/ add-on scenery or what ever. My hardware is fine / my drivers are all up to date. I think Ive had enough of this now. Ive never in my life of gaming had a game that has so many crashes. Ive spent

HiI've been getting major CTD's for a while now. I have the usual fixes installed- not sure what it is. Personally, I think it's an AI-related issue. (probably too much!)Looking forward to FS10 already! (Don't suppose it'll make all that much difference anyway!)Yours, in sympathy!

Have you tried the seasonal CTD fixes explained in the thread below?http://forums.avsim.net/dcboard.php?az=sho...d=315&mode=fullKurt M

No problems with CTD's here...

"Ill not except that its a peice of Freeware/ add-on scenery or what ever. My hardware is fine / my drivers are all up to date."My average run time of FS2004 is twelve hours or more, although I usually only have one day a week to really tax it--the rest of my sessions are an hour here or there when I can grab time. I haven't had a CTD since Lord knows when--probably last had one when before I applied the seasonal CTD fix... I have several aircraft add-ons, but the only scenery add-ons are my own landclass creations along with some of my users landclass creations.My system is ancient--my O/S is ancient--yet this sim is as stable as any MSFS sim before it on my rig. As I just mentioned, I was able to reproduce the seasonal CTD's--fixed that with Joachim's fix and textures. But--and this is a big one--I rarely fly with autogen and almost never fly with AI, simply because my rig is too slow to support AI.So that has to make me wonder, assuming the above quote is true and you've ruled out all your freeware, add-ons and hardware--turn off AI and see how long a session you can run. If you get a CTD, then turn off autogen. There has to be something which accounts for why many of us can run hour after hour, while others can't. If FS2004 can break, my system should be able to break it. OTH, I make my living keeping systems--especially the older ones--pristine and breathing long past their prime. I can't believe it takes that level of expertise to get the sim to be stable--others here are pilots, lawyers, etc...and they have stable sims as well.Before you rule out hardware, here's a bit of advice. I've run many memory tests with different types of software, gaming, productivity, and other... FS2004 soaks up more memory than any software I've run into. If you have one chip that is marginal, or placed too close to a heat source--you can easily get a CTD. I had fits with FS2002 when out of the blue CTD's started happening to me. I tried all the RAM testing tools at my disposal, and all the RAM checked out fine. But I could think of nothing else--so I replaced the chip in the last bank, as it was the oldest. CTD's were gone.Hope something helps from this post... It's frustrating as heck, because I've been there with the problem mentioned above...And I should mention one more item--best way to rule out any aircraft add-ons is to just fly with one of the default aircraft. Also, remember that any module dropped in the modules folder that isn't FS2004's own could cause issues. You'd be surprised what ends up there that people never check when trying to rule out add-ons... These are the default FS2004 module dll's:ABLSCPT DLL 90,112 06-12-03 8:36p ABLSCPT.DLLACONTAIN DLL 90,112 06-12-03 8:36p ACONTAIN.DLLAI_PLAYR DLL 118,784 06-12-03 8:36p AI_PLAYR.DLLATC DLL 311,296 06-12-03 8:36p ATC.DLLCONTROLS DLL 167,936 06-12-03 8:36p CONTROLS.DLLDEMO DLL 73,728 06-12-03 8:36p DEMO.DLLDYNAMIC DLL 16,384 06-12-03 8:36p DYNAMIC.DLLFACILI~1 DLL 212,992 06-12-03 8:36p FACILITIES.DLLFE DLL 102,400 06-12-03 8:36p FE.DLLFLIGHT DLL 135,168 06-12-03 8:36p FLIGHT.DLLFSUI DLL 937,984 06-12-03 8:36p FSUI.DLLG2D DLL 950,272 06-12-03 8:36p G2D.DLLG3D DLL 487,424 06-12-03 8:36p G3D.DLLGLOBAL DLL 8,704 06-12-03 8:36p GLOBAL.DLLGPS DLL 110,592 06-12-03 8:36p gps.DLLGPS_EX~1 DLL 6,144 06-12-03 8:36p gps_export.DLLINSTRU~1 DLL 13,824 06-12-03 8:36p INSTRUCTOR.DLLMAIN DLL 192,512 06-12-03 8:36p MAIN.DLLMPCHAT DLL 9,216 06-12-03 8:36p mpchat.DLLMULTIP~1 DLL 114,688 06-12-03 8:36p MULTIPLAYER.DLLPANELS DLL 409,600 06-12-03 8:36p PANELS.DLLREALITY DLL 7,168 06-12-03 8:36p REALITY.DLLSIM1 DLL 602,112 06-12-03 8:36p SIM1.dllSIMSCH~1 DLL 14,848 06-12-03 8:36p SimScheduler.DLLSOUND DLL 73,728 06-12-03 8:36p SOUND.DLLSYMMAP DLL 159,744 06-12-03 8:36p SYMMAP.DLLTERRAIN DLL 393,216 06-12-03 8:36p TERRAIN.DLLTRAFFIC DLL 39,936 06-12-03 8:36p Traffic.DLLUTIL DLL 131,072 06-12-03 8:36p UTIL.DLLVISUALFX DLL 208,896 06-12-03 8:36p VISUALFX.DLLWEATHER DLL 229,376 06-12-03 8:36p Weather.DLLWINDOW DLL 73,728 06-12-03 8:36p WINDOW.DLL

I had them when flying around KGEG, until I did the fix. Go to the terrain.cfg, and change all the MaskClassMap=3 and MaskClassMap=1 to MaskClassMap=0.That worked for me.

Hi all,I too have experienced several CTD despite having installed the CTD patch. I sometimes have the ATC.DLL error when the ATC is directing me to descent. Someone in this forum have suggested that this might be related to AFCAD (indeed, that happen to an airport that have been AFCAD-edited).Can someone confirm this?japangg

I have applied the seasonal CTD fix with good success. However, I have also discovered that faulty AFCAD files can also be a cause of CTDs as well as having duplicate AFCADs for the same airport. Check these additional things out before you give up.Lee

>I have applied the seasonal CTD fix with good success.>However, I have also discovered that faulty AFCAD files can>also be a cause of CTDs as well as having duplicate AFCADs for>the same airport. Check these additional things out before you>give up.>>LeeFaulty AFCADs have given me tons of problems. One of the first things I check if I get repeated CTD.

Dear Lee and fred,Thank you for the reply. I am curious to know what kind of AFCAD error that causes this. Before I isntall any AFCAD-edited airports, I always check to see whether that airport has error (from AFCAD Find error menu - don't know the exact name as I'm at the office now).regards,japangg

Hi AllI wrote up my experience in the "CTD Fix Confusion" thread. In my case I have confirmed that my CTD was caused by a specific add-on scenery package. I can repeat the CTD at will and remove it just by removing the scenery add-on. That scenery uses the VOD/APT2.6 scenery textures also.

You say that your drivers are "all up to date", which makes me think that could be the problem. I don't know what this "seasonal" CTD thing is, as I've never experienced it. However, I have had many lock-ups after I've installed "up to date" drivers. I cannot run any driver set from the 50.XX series and up with my FX 5200 Ultra card. I'm running the 45.XX series of drivers, and the sim just keeps on going and going and going-just like the Energizer bunny!Newer or Up-To-Date does not always equal "Better".Darrell

Not sure if this qualifies as a CTD but it sure is frustrating. Twice within the past week I would be flying and then the FS screen goes black. Only the menu is visible. After some time it then shuts down and asks to send an error report which I did in both cases. The first time had an error in the weather module but I forgot to check the second one. I was so ###### after 2 hours flying for this to happen that I just sent the report. I been using FS9 from the start through other seasons so cant understand why it would start now. The only recent addition was UT.System is p4 1.9/1GB Ram/Win XP ATI 9600XT.Also if I try the patch I assume the change is to be made at every occurrence of the maskclass line.thanksBill

For AFCAD errors, I do what you do, run the fault finder and try and correct any faults until the AFCAD file shows no faults found. If there's still a CTD at that airport, then something is wrong with that particular scenery. I also find that when you install a new scenery, you have to check and see if you might have also installed an AFCAD for the default scenery for the same airport. This can cause conflicts. Just use one or the other.Lee

exactly the same problem here!I have an ati radeon mobility 9600 128Mb;the screen goes black after a view chage (from vc to 2dpanel, or resizing window, or from fullscreen to windowed). It loads for awhile and then crash with error report.I have noticed the cause:(while the screen is still black) open the menu and select display and then activate rendertotexture if it was off or deactivate it if ON.basically it 'refresh' the panel back without crashing.SO it's definitely something to do with it.Unfortunately I can't find a solution as keeping render to texture on/orr (either ways) doesn't fix it.I'm using the ati catalist 4.2 and not managed to fix it.I have the feeling some catalist version prefear rendertotexture on while other off.Also had a crash to desktop without errors (fs2004 disappeared at once!!!!!) which concer me most as I doesn't tell me the cause...luckily it only happened once so it could be an one off cause.what catalist drivers are you using?RLuca