Add highmemfix=true to your fsx.cfg :)

Not a valid command - it's =1, not =true.Greg,This isn't a common issue at all - I'd suspect something going on with the video card or driver. I have no idea what could possibly cause that issue relating to the actual aircraft model or code.

Ive had it happen on a few occasions, and its been either SM3.0 or highmenfix that fixed it, cant remember which.

Thats the -950er version... Very fuel efficent! Didnt you knew PMDG released it with SP1C?

Will it autoland?

Just to check, FSX is installed properly.....Fsx install (run as administrator on everything you install) > open close > reboot (probably not necessary) > SP1> open close > reboot (probably not necessary) > SP2 > open close > reboot (probably not necessary)....pmdg....etcI use PC#2 for checking out demos/betas and sometimes come across this in FSX, this system is definitely not up to date as it has no internet access. Try windows update as there may be direct X , MS Visual C++ or MS.NET Framework updates available. Probably irrelevant but worth a shot!!Vanilla 580 drivers should be able to handle the bird - try the latest drivers though.

Ok enough with the funny comments now. This looks like a shader problem. Try to install Bojote's Shader 3.0 mod.

OK I'm back in business !!....not sure which of the following issues was the culprit1. complete uninstall PMDG2. deleted leftover files3. removed EZCA and all associated files ( I remembered having issues while running the FSX Config Utility )4. deleted Recycle bin5. ran Reg cleaner6. INSTALLED SHADER MOD3 ( thanks Arjen )7. installed PMDG 800/9008. checked in FSX ( all looking good )9. installed sp1C10. installed 600/70011. check FSx ( still all good )12. uninstall / reinstall FS2Crew13. downloaded and reinstalled EZ Dok V 1.1514. checked FSX ...ALL VARIANTS ARE OK !thanks for all the help guys !cheersgreg

It was the shader mod, you may have installed it wrong previously and the files were left there.

One other thing to consider if this ever happens again. Same thing happened to me one time when I had a corrupted install of FS Dreamteam KLAX. I know it was FSDT cause it happened right after I installed the Demo. The solution was uninstall FSDT KLAX Demo and the Stand Alone addon on manager. Then reinstall the very latest FSDT Stand Alone Addon Manager. That fixed it. Later on I purchased the full version of KLAX and never had any further issues after that. The only other time I had that kind of issue was related to uninstalling Shader 3.0 and fixing that issue was much more complicated.