CTD's Program Freezing and other Errors

[usb777]

Maybe this will help those like me who being a slow learner nothing gets by me kind of guy. For those old timers who have helped us in the past will probably laugh at this one. So to start and not take up a lot of time this hopefully will address a lot of those dreaded ctd's, program freezes, ntdll.dll errors, ai_player.dll, even a g3d.dll as long as many other possible errors you can see when opening up the events log after an FSX crash. What I believe I have found that has given me a lot of these errors in the past and though I cannot rule out all the possibilities the good people here have given us many valid explanations, but for years I have changed aircraft in mid-flight, relocated to different airports mid-flight and after landing by using the menu bar short cut to select another airport and or aircraft. I believe I have found that instead of using the program that way especially when moving to a new airport to actually use the ESC key and ending the flight then choosing the next airport and or aircraft. Now as I use Kosta's tweaks with the exception of running my water all the way high (love the cloud reflections in the water), boats at 100% (love my aircraft carriers) some road traffic and the frame rate unlimited, Active Sky always one can see I push my build to the limit and have often had all the errors I mentioned and a few others but since I have gotten into the habit of ending the currant flight and actually resetting the program this way I have not experienced any. I also noticed before I changed my bad habit the FSX clock lost time as I moved around the world and that might have had something to do with the errors. Now I may not be totally correct so please feel free to add to this post. Sorry for the lengthy explanation, hope this helps a little. One last note, turning down the water of course has a big impact on everything as well.

[Rupert]

Mike,

 

I've also found that too many inflight changes leaves so much detail in memory and all sorts of errors can occur. Often when I've been simming for some while I look for a logical place to "land," say to refuel. After that stop I have much better luck for the rest of the trip if I close the flight and also close FSX down. This clears even more off the clipboard & I can reboot the program and continue on from that point.

 

Think stopping at a rest area and getting out to stretch your legs. ;)

[saburrows]

After many years of using FSX and being at times totally fustrated to nearly giving up, I can finally now state, after hundreds of hours of googling and trialing, to now have a stable FSX using PMDG and AEROSOFT aircraft, with some payware airports such as ORBX, via a TH2GO home cockpit flying many 1-14 hour flights without any further issues! So to put it in print for anyone else experiencing VAS or FREEZING problems, try these 3 main fixes that have helped my fsx to be totally enjoyable to use.

 

1. Use KOSTAs tips to set up your fsx. And be careful on increasing fsx options such as traffic or water resolution (start low then option up one each flight to experiment on its frame rate impact). Even reducing cloud draw distance from 100 to 70 helps!

2. For VAS leakage problem tick the DirectX10 preview option in fsx. Also uninstall and then reinstall Active Sky Next if you are using that for weather (esp after pmdg update).

3. For freezing halfway into a flight (when VAS is still ok).... reduce your screen resolution (for example, from 1680x1050 to 1280x800).

 

My 5 monitor (3 on TH2GO) system is a win7 64bit using saitek panels, FSUIPC (full ver), FSPASSENGERS, FSINN, SPAD.NEXT and LINDA.

 

Hope these tricks help, and if it does, your welcome!