During my last few flights, the first in the B744 and rest in the MD11 suffered a CTD. These were the first times I ran these two aircraft in FSX but everytime, it crashes during approach. First I was on Final to KSUX. It was the default airport and default scenery (minus FSGlobal) and running ASE, Ultimate Traffic2, and Radar Contact. The second time, I was approaching KJFK southbound. I was at my closest to the airport before i would turn around and line up. This one I thought might be the fact that I was running ManhattanX and FSDreamTeam KJFK. My computer was slowing up a bit. But then today, I was on final into EGLL and everything was running very smoothly despite London VFR and Aerosoft's Heathrow2008. The second I was cleared to land, everything locked up for about 45 seconds, then the screen went black for a bit, then CTD.Apart from the New York area running slowly, KSUX and EGLL ran incredebly well up until the crash. I thought it could be RC or maybe even FS2Crew but the only commonality was that I was within 5nm horizontally of each airport in the MD11 (and the B744 on one occasion but I don't think i need to post the same thing in two different forums). At KSUX, I was fully configured and landing checklist complete but not cleared to land. At KJFK, I was still at 8000' and on vectors. At EGLL, I was cleared to land but still at flaps 28 w/gear down.Anyone hear of something similar or have idea's on what to try?

Set Data Execution Prevention DEP to protect the OS only; use the HIGHMEMFIX as suggested by ******* in the pinned thread on graphics corruption, and move your sliders to the right slightly.All these are just guesses, not knowing your OS and I am just a parrot on anything technical :)

I have the HIGHMEMFIX set. I've had it already done prior to all flights. I'm not sure how to set the DEP though. Could you provide instructions on that? Finally some of the sliders are already to the right a bit but like I said, flying into KSUX and Heathrow, FSX ran very smoothly.Anyway, I have Win7x64 with 4GB ram and an Intel i5 2.27GHz processor.

Use F1 help to find the instructions. Tip: I found it through Computer properties.

I checked the DEP it was already set to protect only "essential Windows Programs". I tried another flight today and during descent (about ~15000ft and 50nm out of FSDT's KLAS), I had the computer completely froze. I didn't get a CTD this time; just a frozen screen in FS only. I could use the task manager to access ASE, RealTime, etc.So far I have worked out that CTD's (or screen freeze) only happen in this aircraft during approach or well into the descent.

I'm out of ideas Ryan, maybe turning off add-on sceneries (not uninstall, just turn off using scenery library manager) and see if there is one that reproduces the problem. A while back I recall reading about a similiar problem at end of flight that turned out to be OOM problem, solved with 64b OS. Not sure what you got going on here.

I checked the DEP it was already set to protect only "essential Windows Programs". I tried another flight today and during descent (about ~15000ft and 50nm out of FSDT's KLAS), I had the computer completely froze. I didn't get a CTD this time; just a frozen screen in FS only. I could use the task manager to access ASE, RealTime, etc.So far I have worked out that CTD's (or screen freeze) only happen in this aircraft during approach or well into the descent.

Ryan,You can check the event logs(Right click computer -> manage) and open the windows application log. It should tell you more specifically what caused the crash.Stefan Ticusan