Brand new system, fresh clean and previously stable running install using bojotes tweaks, REX, ORBX at KBFI. WIn7XP 64-bit, Specs in sig Everything loaded normally, got preflight done, pushed out and noticed the tail texture greyed out, same with engine textures.. shortly after when I went to start engines, the screens in the VC froze, shortly after I got a you've run out of resources message. Unhandled exception has occured Restarted, loaded up at BFI with everything already running on the runway, just put the pedal to the medal, and shortly after becoming airborne, exterior textures greyed out again,and climbing thru 9000 I got another CTD. This time with no VC screens freezing, without the run out of resources message. Same Unhandled exception message. Kinda disapointed concidering its a two week old buiild, I7 2600k, GTX550ti, 8GB RAM, default BIOs settings, thats run ORBX, REX, and the MD-11 no problem. Any ideas.

Bit of a shot in the dark but could be a memory leak caused by those textures. Try a re-install, often works for other PMDG aircraft.

I will try that, i have my doubts that will fix much..I installed as admin. Am I really the only person experiencing this? I should point out that after about 5 minutes after I load the NGX. Norton gives me a high usage warning, when I open that it tells me one of my cores is running at 98%. Then the above ensues a couple minutes later. After a third attempt I mixed up the perimeters of my flight. Crash was happening at KBFI, ORBX installed, REX WX running, at night. I was able to do a short takeoff and landing in the daytime at another ORBX covered area this time at CYYC, with no REX. And although I got the Norton warning, it did not crash on me, but had to cut the flight short as it was well past my bed time (1am) for a 4am start at work. I have not experienced any of these popups or CTDs in the two weeks I've had my system running FSX, REX, ORBX/

I'm experiencing problems with VC/2D freeze. Everything still is movable and I can manipulate all controls but nothing works. Switches work but do nothing. Not getting any CTD or warnings but I have the tail greying out as well. Tried a reinstall with no luck. Any ideas?

Do you have FSX service pack 2 and/or Acceleration installed?

Affirm I do, I followed the steps on the PMDG support wiki as I did my install.

Acceleration

Bump (sorry) I feel like Im the only one experiencing this....

YYCVOR - Do you use FSPassengers?

Did you follow all of the suggestions in the introduction?

Brand new system, fresh clean and previously stable running install using bojotes tweaks, REX, ORBX at KBFI. WIn7XP 64-bit, Specs in sig Everything loaded normally, got preflight done, pushed out and noticed the tail texture greyed out, same with engine textures.. shortly after when I went to start engines, the screens in the VC froze, shortly after I got a you've run out of resources message. Unhandled exception has occured Restarted, loaded up at BFI with everything already running on the runway, just put the pedal to the medal, and shortly after becoming airborne, exterior textures greyed out again,and climbing thru 9000 I got another CTD. This time with no VC screens freezing, without the run out of resources message. Same Unhandled exception message. Kinda disapointed concidering its a two week old buiild, I7 2600k, GTX550ti, 8GB RAM, default BIOs settings, thats run ORBX, REX, and the MD-11 no problem. Any ideas.

BIOS is updated?

Did you follow all of the suggestions in the introduction?

BIOS is updated?

Not really, anything I should be aware of other then the FSUIPC auto save? If thats even in there, Im hope im not to be enlightned of something obvious resulting in a faceplam, Like i said, I have been able to fly normally when im not stressing out the sim, not orbx seattle, no rex, daytime. With my specs I find this surprizing. BIOS is updated, default settings set in high performace mode. Highmemfix applied as well.

First off, disable Norton, it is robbing valuable CPU cycles. Test with Norton disabled and see if that is contributing to the problem.Paul Solk

First off, disable Norton, it is robbing valuable CPU cycles. Test with Norton disabled and see if that is contributing to the problem.

Thats a shame, the idea of running my PC unprotected for hours, doesnt do much for me. Had bad experiences with MSE in the past. But alas I will try that when im home in 11 hours, I'll set up the same exact perameters. Sorry if this may have been in the introduction, I got way to excited to jump in and go.

For me not protected is a non-issue as I am not surfing the net or opening e-mails as I am flying, hence my risk is drastically minimized. My home network is protected (ex security engineer here) so the desktop level protection is only relevant when I am doing something that would put the desktop system itself at risk which FS doesn't... :)That is just me though, in 15 years of simming I have never had personal FW or AV on my FS box but then again, my FS box only does FS, it does not even directly connect to the web, only uses Wide-FS to get to other "apps" on the network :)-Paul Solk