I am going to try to increase the size of my AGP Aperture. I have it set at 128MB now (or it might be 256MB). I'll verify next time I get on my home PC. Someone once said it should be set to approx half of your system RAM - I have a GB of system RAM, so arguably, I can increase AGP to 512MB. I'm wondering if somehow I'm overloading the card and something inside WinXP is just shutting down the application to prevent damage to the card. I have no real basis for supposing this, but its worth a try. Anyone out there with XP knowledge enough to help diagnose the problem?-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

It's not your agp aperture size. It should be a lot lower than 128 because when fly needs more video memory it takes it from system ram, which is much slower than video ram, and your fps drop. It's a balance between your render.ini and your video memory. As for the ctd, is it happening only with PMDG's aircrafts? If so, try flying another aircraft. PMdg aircraft requires a funny installation relative to the fly2 pathches. Read the pMDG forum for instructions. tony

Two things:1 - My aperture size was already 256 MB and couldn't be set higher. So as an experiment, I lowered it to 128 MB and will report back if this helps.2 - It is not ONLY with PMDG aircraft. It seems to happen more often with PMDG aircraft, but then again, I take longer flights with PMDG aircraft. But this has happened with the Pilatus at least once, and I am pretty sure I've had it crash with other aircraft.I just re-installed all my PMDG stuff from scratch following every step of the PMDG forum, but still having crashes since with the 777 and 757. -DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

I used to have crashes on long flights, but his happened only as a result of some bad scenery installations and also memory leaks resulting from a bug in fly2. The last patch fixed it. I hope that you're patching properly.......tony

Yes. As per my signature, I'm at 2.5.240. -DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

Bonjour,I have exactly the same problem as you - and I noticed the following points:- the CTD happens more frenquently with big (and rapid) planes: frequent CTDs with TBM700 and Pilatus12, less frequent with Kodiak, and never happens with FlyHawk or Staggerwing (with long flights in every case). I don't have 777.- CTDs more frequent when flying above hilly landscapes.So I don't have any solution, except using Staggerwing - what I am currently doing, this plane is funny!have a nice day,Jeck

Idea went nowhere. I CTD'd in the Staggerwing today on a flight over the San Francisco Bay. Was on the way from KOAK to HAF and about 3K feet over the bay I pressed the "down" arrow to check a gauge and BLAM - gone.This is getting worse, not better.-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

I'm gonna try flying without T&L for a while. I'll report back in a few days.-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

Hi David,Having the same problem just recently. Have the latest Omega drivers for the Nvidia. I have been making loads of Terrascene (so far about 15 gigs all of the US West Coast). This problem has been getting more frequent the more scenery I put in. I do think you have a point with WindowsXP protecting the video card from overloading. I get the same ctd with CFS3 if the resolotion is too high or 32 bit. Screen goes black and then the desktop is blue and you have to hit refresh to get the desktop background to show again. I'll give a try to the T&L also on flights that give me trouble and let you know. Don't have the 757/777 but the TBM700 and King Air both have ctd'd on me.ZaneFly!II 2.5.240WindowsXP HomeAthlon XP2000Asus GeForce4 Ti4200 128512 DDR 2100CH USB Yoke and Pedals

I lowered my hi-res setting from 6 miles to 4 miles and no problems last night. Will post again if I get another ctd.Zane

Hi David, I last week installed the Nvidia 4.4.0.3 drivers & started having unexplained CTD's but just back to my regular desktop. After some experimentation I went into my video card advanced properties & found the OpenGL Settings, I then unchecked the Enable conformant OpenGL texture clamp behavior & to now at least have not had any more CTD's, mind it is early days yet with this new driver so don't know if this is the answer or not. Hope this helps.Desmond

I am eager to try this. I will run some tests and see if I can eliminate the CTD's. -DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

I just got home and verified that the option you refer to above is already unchecked. Back to the drawing board.-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

I have been running Fly!2 with the standard TRIDX8.dll file instead of the T&L driver, but tonight on final into KSLC, I got the normal CTD. What a disappointment. I thought maybe it was the T&L driver.I was flying the B777.Now back to the drawing board.-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

Dave, you may be able to troubleshoot the problem by examining the XP event viewer. I had a similar problem with XP Pro which I eventually pinned down to the recent installation of an unsigned driver for my preferred AVB FFB USB joystick. I uninstalled that and used an old Sidewinder USB joystick, for which XP had a signed driver, and the problem went away. At least I hope forever. If XP Home has an event viewer that can be accessed via control panel's administrative tools folder (like XP Pro), then you can select the system log in the event viewer and scroll down the cryptic list until you find an entry Save Dump listed in the Source column. Double click that to open the Stop error information. In my case I discovered something called a bugcheck (under the description) that listed a stop error code 0x000000d1 plus some parameters. A little over a month ago I was completely clueless about windows XP and therefore bought Ed Bott's Windows XP book. His book explains many of the error codes, and I found that the stop error may have related to my installing some unsigned drivers. You may have a different error code for your situation.