Hello All,Read the above and these are the results.First flight, with AFCAD added, stock Lear got from KWER to Harrisburg Pa and then lock up and reboot.Second Flight with AFCAD again removed, but using CS 727-200, from KWER got to Pittsburg.No Joy at all.Going to try another flight, stock lear, no afcad, no scenery again east to west . . . if it dies then, I will be convinced that there is a inherient flaw in FS as the seasonal bug should not apply.I can imagine the rest of you and what you have gone through . . .Film at eleven,Clay

Keep at it Clay! Your close to what I was experiencing. Let us know what you come up with. My feeling is you'll make it in the default Lear...MickeyKLAS

Oh well, no crash today.Like I said, that was the first time MSFS2004 had crashed on me (yesterday).

Whew, this is getting to be like old home week!This flight:KEWR TO KDAY, (Thats Newark to Dayton Ohio,) With the recent failures I decided to put everything back, scenery, afcads, (see list above which I turned off), everything! Started this flight with Standard Lear, using everything that I had for acc's for FS9.BEFORE I STARTED, WENT TO DXDIAG AND TURNED OFF SOUND HDWE ACCLER. ALSO WENT INTO MY NVIDIA OMEGA CONTROL PANEL AND TURNED OFF FAST WRITE. IT SEEMS i CANNOT TURN THIS OFF PERM, BUT MUST DO IT EVERY TIME.FLAWLESS FLIGHT, WAS ON AND OFF LINE DURING FLIGHT . . . USED DIFFERENT VIEWS, USED FSNAV, (WENT THROUGH PITTSBURG ON WAY TO DAYTON) AND NO LOCK UPS OF BLACK SCREEN OF DEATH!!!!Holy CPU Batman! I did notice that ATC talking to me was very garbled, so will try same flight tomorrow, with it set to basic. Also, flew flight in heavy snow storm/cold front. Only thing I noticed was that on approaching Dayton, frame rates dropped below 20 and hovered about 14-15 which is acceptable, but never have seen them that low with this rig.Ok, boys and girls, seeing that I am well beyound my allowable cockpit time for this 24 hour period, I'm done for the evening. But I will try to repeat this flight again tomorrow with sound acc set to basic and see what happens. Forgetting the seasonal hickup that everyone knows about, this perhaps, could be something . . . maybe.Nite to all and will have another update tomorrow around noon.Clay

Yes Greg, you're right... I was aiming my previous post at you. Sorry for the name mixup. I decided to do a bit of testing last night using the flight parameters you mentioned above. I took off from KSFO rwy 10R, pointed it at a heading of 350 until abeam Candlestick Park and then set autopilot in the default 172 for hdg 005 at 3500'. I was able to get about 12 flights in last night, using the dates of Nov. 17th and 20th, December 21,22 and 23 and January 5. All flights were daytime and all were allowed to run through the box you mentioned as the "crash zone" and then on. In fact, I went to the gym at one point with a flight running, and when I got back the plane was sitting atop a mountain near Susanville! The results: not one crash. In fact, my frame rates were even pretty good considering the high-detail scenery and the fact that I'm running Ultimate Traffic at 100% for both GA and Airlines. So it just gets curiouser and curiouser... the only thing this really proves is that on my particular system, for whatever reason, this particular area doesn't cause CTDs. But at least that rules out a fatal across-the-board flaw in MS programming in this build of FS9. Since I'm on a roll I'd like to continue trying to help others figure this out. If you're interested, we can pursue it further. You didn't say what video cards the computers you were using had, so maybe that's a factor. I'm running an ATI All-In-Wonder 9700 Pro card.thanks,

Hi Bill,"So it just gets curiouser and curiouser... "Amen to that!! During the weekend the subject of there being a problem with my FS9 discs came up. We had enough variety of systems that we felt confident that the problem wasn't hardware related. The crashes we experienced in the "box" as outlined in my post above were predictable almost to the minute no matter which system!To that end... I checked the FS9.cfg on each of the four systems and noticed that the Terrain_Default_Radius and Terrain_Extended_Radius were both set to 0.0 during all 4 installs. After returning home and checking my original FS9.cfg from the first install in late July (which ran wonderfully until mid December) the TDR at install was 2.5 and the TER was 4.5.In my latest e-mail to MS yesterday I requested replacement discs. I've not heard back from them yet, but hopefully they'll send a set out to me. Would be nice as a tool to eliminate the bad disc possibility.Concerning your question about video cards... we had 2 9800 Pros (one was running 3.9 CATs the other 2.5.04 Omegas). My 9700 Pro was running the 2.5.04's. The fourth rig had a GF4 4600 on WHQL 53.03 Dets.Cheers,

Hello All,Well, I will make this short and sweet. Same as above . . . no problems what so ever, this time going from kewr to kcvg. nO LOCKSUPS, no black screen of death, flight was perfect.Reinstalled all scenery, afcads and all acc programs. Used Arianes 737-800 with FS Nav and their panel. No problems.Now if this makes any sense, it sure is loosing me. The only thing I can think of would be taking DX sound acceleration to basic and turning off 'Fast Write' in my display settings.Other than that, everything is the same as when I had massive CTD's.Will keep trying,Clay

Glad you found something that worked for you. If you want, try re-enabling your hardware with the terrain.cfg mod I posted in another message. I'd be interested to know the results.

I've been suffering constant crashes the past month. Changing either sound acceleration or AGP fast writes did not improve anything. I don't have much time for flight simming these days, but last evening I did complete a 20-minute night flight without a crash. This was in an area (northern Utah) where I never made it past about 2 minutes without a crash during the daytime. Next is to try the calendar trick (avoid winter textures) and a couple of the fs9.cfg fixes posted here.BTW, I have no add-ons of any kind.

Good news... I finally had a CTD! ;-). I was using the flight you posted in your thread which Chris Willis had recommended (ENAN on October 25th, Day) and for once WAS able to get the sim to crash. Using your terrain.cfg modification fixed it for me. Fair warning to everyone, though... make a backup of your terrain.cfg before doing this! It's easy to find and replace all the instances of TerrainMask = 1, but once you've set it to "0", you'll find that there are a number of other entries in the cfg file that already had it at "0", so it won't be so easy to change it back if there turns out to be another fix down the road. Thanks for the idea, though. It did fix this particular problem for me.

>Good news... I finally had a CTD! ;-).Well, no CtDs here, and I'm on holidays with nothing better to do than try out everybody's scenarios. The only time I experienced a CtD was about two months ago after I bought a new mainboard (ASUS A7N8X Deluxe). The CtD occured at a time when I was learning about what memory timing and CPU to memory latency settings were stable (or not) and at the I had set them a little too agressively. Since then, not a single CtD, blue screen, re-boot, freeze or anything in FS2004. It's been 100% stable under every scenario I've tested, including all the CtD scenarios listed in these forums.I'm not saying you are all full of it, just that I'm not (yet) convinced there is an issue with Microsoft's code.

Give it a rest, Jon.We're all happy that you ALLEGEDLY don't have CTD's. (As you have stated in more than one post)I'll leave it with your quote, slightly adjusted:"I'm not saying that Jon is full of it, just that I'm not (yet) convinced there is not an issue with Jon's system."Saying we are not full of it is the same as I wrote above then huh?Maybe now, you can appreciate where some of us are coming from.I also get a CTD with Chris's Scenario. But Like I said. MS don't give a rip about us. Regards,Joehttp://aboutpolitics.net/images/bannerav.gif.About Politics.net - FORUMShttp://pub162.ezboard.com/baboutpolitics.Contribute to the Richard Harvey Scholarship Fund.http://www.avsim.com/pages/scholarship.shtml

Interestingly, that's the exact same motherboard I've got. We should compare notes about timings and the like.

Well Joe, I've tried to be diplomatic about it, but posts like yours, accusing me of being a liar really get my goat.So no more beating around the bush trying to help people. The problem is not Microsoft, it's yours. You all just need to learn how to build and run stable computers. End of story.

>Interestingly, that's the exact same motherboard I've got. We>should compare notes about timings and the like.>No. No more helping people run here. Three years, close to 1000 posts, and I get called a lair.You can all just take a hike off a high cliff as far as I'm concenred.Tom, please arrange to close my account.Regards and good bye.Jon "the liar"