Yup, UT as well, but this is a loading (performance) issue with many addons installed which I honestly now believe exagerate some existing underlying issue. I've been through every thread, both XP and x64 OS's, multiple CPU's and video cards. 1GB and then 2GB of Corsair XMS ram, memtest'd & Heavyload'd for days. Again, I've come to the conlusion that this is some sort of compounding problem. If I fly from KLAX to my KCHS with a default arrival airport, I don't get the CTD on final, even after an additional hour of enroute flightime. Hence, I'm hoping that that this NavAid hicup, exagerated by many addons and the 744, is fixed by matching the airport name and Navdata file.I'm now enroute from KLAX to KATL, leveled off at 380 (just west of Phoenix) after renaming the airports in the wpNavApt.txt file as mentioned above.After all the friggin troubleshooting I've been through in the past few weeks, I really wish PMDG (Robert) would confess their (PMDG) findings to date on the "final approach CTD" issue. It may not be fair to whoever they suspect to be causing these CTD's, but it really isn't fair to their loyal customers who are about to walk-away from this entire mess permanently.I'll brief my KATL landing outcome in a few more hours.AL | KCHS - Charleston, AFB | Home of the 437AW (53 C-17's)

>After all the friggin troubleshooting I've been through in the>past few weeks, I really wish PMDG (Robert) would confess>their (PMDG) findings to date on the "final approach CTD">issue. It may not be fair to whoever they suspect to be>causing these CTD's, but it really isn't fair to their loyal>customers who are about to walk-away from this entire mess>permanently.We honestly do not know - I'm absolutely not kidding here. None of us on the development or beta team have ever seen this error and all we've been able to discern with any degree of certainty is that it seems to be predicated on scenery and a hardware issue (memory related usually) somewhere. This is system specific - people (such as Paul, who started this thread) have seen the error occur not just with our 747 but also with the LDS 767, the PSS 777 and other high end addons. That right there tells us this is not related to the programming of our aircraft. If it was we'd be able to reproduce it here. I have personally run the EXACT same configuration as Paul as far as installed addons and he sees the error and I don't. That's not a bug, that's a system specific failure related to a combination of factors that we have absolutely no control over. I really wish there was a way to get this solved for you guys, but we can't fix what we're not causing.

Gents-To back up Ryan a bit more:The reason why we will not come out and say, "XYZ product is a problem" unless we can clearly and certainly establish this as fact is quite simple: With the tens of thousands of free/commercial products out there- it might be a really unique set of circumstances that causes a particular problem.if we were to insinuate that any one particular product was the problem child- and we were wrong- it would simply be unacceptable.PMDG is not a group of hobbiests- we aren't a group of code hacks- we are a professionally organized and operated company- and we take our role as leaders in the development community very seriously.If we ever find a competitor/freeware product that causes a clearly reproducable problem- we will take that issue to that developer quietly and try to help them resolve it FIRST. In this instance- we have seen some folks able to reproduce OOM/CTD problems with a specific mix of addons and circumstances- but we have never once been able to cause that scenario to be reproduced across a wide swath of tests. This leads us to believe that nearly all of these OOM/CTD problems are local to the users individual machine/addons.I assure you that if/when we find a reproducable pattern to it- we'll help stamp it out. Until then we are just guessing- and when you are guessing you have to be careful about apportioning blame!In the end- we do not think it is a problem caused by any PMDG product- but we think that many high-end addons are capable of triggering the problem from wherever it originates. We'll keep looking, I promise.

Thanks Ryan & Robert,I appreciate you guys taking the time to comment on the subject again. I was lead to believe from previous posts that you had a better idea as to what/who might be causing these CTD's than us users/pilots/flaming-darts, LOL... I never meant to sound like I was blaming PMDG or the 747(F). As I stated above, I agree that it is definitly a "compounding" problem with high-end addons. This is just like playing with fire; my Atlanta problem is evident if I have the PMDG 747, UT, & SF KATL v2 up and running. If I take away anyone of the three, the CTD on final does not occur. For the record, I build UNIX server systems for a living with a prior career in electronics and this is one of the damndest things I've ever troubleshot, but I will prevailNow passing east of Texarkana VOR and the FMC tells me to expect an answer in about an hour.Is there a "praying" emoticon for this board, LOL?AL | KCHS - Charleston, AFB | Home of the 437AW (53 C-17's)

Hey guys,Just to back up the PMDG team a little bit here.Ryan, Rob, Vangelis, Lefteris have done everything possible to try and isolate these issues. They respond to my annoying e-mails and PM's, never ever complain or bat an eye when it comes to offering advice and genuinely want to see this issue solved as mush as we do.I agree with Robert that it is not a problem caused by the PMDG products. Many users getting an OOM an a specific route can replicate it with mutiple add-on a/c. That alone rules out a PMDG exclusive problem. Trust me, if the team knew anything they would be screaming it to us, not hiding it from us...I have also seen this issue on multiple hardware configurations, ATI and Nvidia systems and I have not seen any silver bullet to resolve the issue. While I have not been able to isolate any one product, A LOT of us have been able to resolve it by uninstalling UT. I was able to get UT installed again with just LandClass, CoastLines and Enhanced Roads to work but it took a lot of trial and error.I am running a very unique FS setup as well with an Nvidia 7900GTX and an Nvidia 7800 GTX in the same system running non-SLI powering 3 monitors. Along with a lot of other issues my OOM's seemed to go away with the 84.25 v2 drivers by www.tweaksrus.comIf you are really interested, here is what I did to get back to a stable FS and get everything working. I have gone through this process numerous times and it seems to have worked repeatedly. This just describes FS related info, not info on rebuilding your swap file which in MANY cases can become corrupt. Search MS for their KB.Prior to all of this, I created a system restore point, created a copy of my ENTIRE FS directory as well as a copy of my documents and settingslocal settingsapp dataFS9 directory (You can NEVER be too safe)1. Go into UT setup and restore all FS defaults. Load FS 2. Uninstall UT entirely3. Let me know if you have GE as well, this requires additional steps3a. I also have a vanilla FSSceneryWorldTexture directory I restore at this time and the Load FS4. Download DriverCleaner3 and CCleaner Crap Cleaner5. A good registry cleaner is usefual as well, personally I purchased Registry Mechanic 6. Uninstall Video drivers via control panel7. Reboot into Safe Mode8. While in Safe Mode run Driver Cleaner A. Run the driver cleaner for your video card B. Under Options run the .Cab cleaner9. Run Ccleaner A. Click on Analyze/Run Cleaner B. Click on issues/ Scan for issues/ Fix issues (do this as many times as necessary until it says no issues found)10. Run registry cleaner11. Reboot 12. Cancel out of XP hardware installation and install DIFFERENT drivers than you are currently using. For me the 84.25 V2 are great13. Fly a few flights without UT and see if the error goes away.14. If not, UT is not your issue, if the error is gone, report back here and we can proceed...Also, check the UT forums, there are a lot of Out of Memory posts, one very active right now and people get it with numerous a/c. Good luck,-PaulBTW, I usually start my please don't let FS crash on me prayers about 3 hours from arrival... If you hop on your right leg while spinning counter clockwise scratching your nose with one finger in your ear there is a 1.1111345% less chance that FS will crash. I told you, A LOT of trial and error LOL!!! Good luck, more than happy to try and help if I can.

Can we define "UT" please . . .I have Ultimate Traffic, but i believe there is also Ultimate Terrain . . . which one are we talking about . . .

Ultimate Terrain. Sorry about that, forgot about the other UT...-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0

Thanks Paul for the tips, but honestly, I've used those utilities and similar steps for quite a while now. Since I upgraded to an AMD 4000+ with a Evga 7900GT, the problem seems more pronounced even though this is my third FS9 installation in less than a month on both WinXPx64 and WinXP the problem persists, only when all three are installed and FS9 settings pretty much maxed. It just seems to be a shame that with this rig, I can run all these add-ons and not make the avg FPS fluctuate off 25 FPS. It just irritates me that these just don't wan't to play nice together now that I've got the hardware to make it run like it should...BTW, it crashed again on a 10nm final from KATL 27L ($^#@W!3). The sunset this evening was beautiful with this video card, even took a few screenshots that I was going to post had my landing been successful.Time for a Jack & Coke, a stogie, and waller in contemplation as to what to try next.Good night...AL | KCHS - Charleston, AFB | Home of the 437AW (53 C-17's)

Hey everyone. I have not reinstalled my 737 or 747 yet in my new rig. The sim has been working perfectly. My other rig crashed all the time. I was getting ready to enjoy my 737 and 747, but now after reading this post, I'm afraid to install either plane again. Does this mean that odds are after installing the 737 and 747, I could start having problems as well? I do have the DF727, FLT1 MD80 & ATR, and Maj Dash8Q300. These are the only complex AC installed, and I have had nothing but perfection in the CTD department. I didn't know if it's ok to mention others. But this way other users would know where I'm at with aircraft. The only complex AC left are the 737 and 747. Are any of the planes I mentioned above, causing other users problems with the two PMDG aircraft? Thanks for your help. I hope I'm reading into this way too much? I'm just freaked out now, that's all.

What other add-ons, scenery etc... It seems to be a combination thing, not just a PMDG thing...-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0

Hey Paul, Thanks for your reply. I have FlyTampa KSEA , Boston V2, and FlightSCenery Rhode Island. I may get Midway by FlyTampa soon. Also I have UT USA, FE2004, GE2006. That's it for those type of add-ons. I guess I just have to go for it. The idea is to get enjoyment from it, and I am feeling cautious after what I went through on my other system for a very long time. I feel like a person with a brand new sports car that won't drive it because I feel like I'll have a fender bender. If any problems develop after installing the two planes, I will check back here first. I don't think it is just a PMDG thing either, but wanted to make sure. Thanks again Paul.

I would definitely say go for it. IF and that is a big IF you have issues, you can come back here and there are quite a few that would be more than happy to try and help. But lets put it like this, even me who had all these issues never had an issue with default FS and PMDG... That says a lot...-Paul

Thanks Paul, I couldn't go without my PMDG heavies anyway. My simulation and pilot studies would not be complete without them. I will let you know how it goes. Again, thank you.