DylanC

Pretty sure it's not the fix. I was one of the first few people to report it as a fix when the 777 came out. It may be a contributing factor, but not the end all be all fix. The only fix I found to actually work is to reduce your overclock. I brought my speed down to 4.05 GHZ from 4.2 GHZ and that seemed to be sweet spot for my CPU. I say that because even the NGX at one point was freezing. The NGX never ever froze before and I surmised the increased OC didn't agree with FSX, the 777 or the NGX. I had recently increased my OC when I upgraded to water cooling; my CPU prior to that upgrade ran stably OC'd to 4.02GHZ for the last 2 years. Now I'm in the business of building and fixing computers on the side and I can say without a doubt, FSX has always proven to be the best benchmark of a stable CPU. There is no forgiveness for errors. If the audio fix doesn't work, I guarantee dropping the OC will work. You won't notice the difference performance wise going from 4.2 to 4, but it will make FSX a whole hell of a lot more stable.

Awesome! Thanks Ryan. I actually hoped you would respond directly to my question.

I notice some people talking about how great the turbulence effects are in ASN. I thought PMDG frowned upon having any turbulence effects turned "on" since it degraded the aircraft's flight dynamics.

No never did. Once I did the complete OS and FSX wipe and reinstall, I never installed IS's VHHH again. AIG's freeware version is pretty good anyway, so really was no need to install the IS version. I'm certain though that I've come across others with the same issue, so if you do a few searches there may be a fix.

You should take this to the CTD forum. Most certainly isn't a PMDG issue. The fact that the .dll file appears in the error just really means that driver was accessed at the time of the crash. BEX errors can be attributed to so many things including memory issues, driver or software conflicts, overheating...the list goes on and on. If you're running on an OC'd rig or you just recently installed new drivers or software, that's your starting point to figure out what went wrong.

The freezes I experience are anywhere from 6 to 7 minutes long and FSX eventually resumes. As time goes on the freezes come closer and closer together. Each time the simulator resumes with around 2 - 3000 lbs of fuel is consumed. I thought I cured it some time ago after I updated my realtek drivers, but they reappeared. Definitely not a PMDG issue as Ryan has pointed out when this issue first popped up when the 777 was released. In fact the freezing issues began back when Windows 7 came about. There's an old thread about it somewhere on Avsim, I believe in the CTD sub-forum. Doesn't seem to be much of a solution presented, but it gives you a starting point to at least start troubleshooting.

I'm curious. Everyone that receives these freezes, do you notice once the sim starts again the amount of fuel has reduced by about 2 or 3000 lbs? Or is it just me.

Learn something new everyday. Great tip!

There can be so many causes for this error. Are you certain you "googled" for an answer? There are so many topics on this. This is one of many I found. http://www.google.com/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&cad=rja&ved=0CCsQFjAA&url=http%3A%2F%2Fforum.avsim.net%2Ftopic%2F385571-stackhash-ctd-possible-fix%2F&ei=P16CUr6eG7jUsASclYDgAQ&usg=AFQjCNHSCPxIWQMhmsaLE4aa_pSw8wuf9A&bvm=bv.56343320,d.cWc

PFPX REX (Textures only, no clouds) AS2012 (Weather and clouds) SHADE UT2

In the beginning even after a clean install of windows, FSX and the 777, I would constantly get the freezes. It would last for 6 minutes exactly and then the sim would start working again. I saw a couple of posts from people who said after they updated their HD audio drivers (I have realtek), the freezes/pauses disappeared. I tried this and it worked flawlessly for me.

Best way for us to help you is for you to upload a screenshot of your Inspector settings. I have a feeling where it says "Antialiasing: Behavior Flags" you probably do not have it set to "None". It must be set to none for it to work in FSX.

Is FSX actually causing a CTD or is it just freezing and you're manually shutting it down thinking that FSX crashed?

I had the same issue with Imagine Sims VHHH. Every time I approached the airport, roughly 20 - 30 NM out, boom CTD. It's definitely not the 777 causing it. I was due for a full reinstall and reformat anyway which is how I cured the issue. The CTD could have been caused by the scenery or the issue that's explained in the pinned "777 current issues and fixes" thread regarding the runways file. I've decided not to reinstall the airport and went with AIGs freeware version instead. No CTD again, but after all the maintenance I performed, I wasn't expecting any further issues.

This sir made me laugh out loud!

How long did you wait before you pressed the windows key? The long pauses/freezes are known by PMDG and are investigating. It's happening to many of us including me, but my experience with it is if you wait for about 6 minutes the flight will resume as normal. If and when it does revert back to normal flight, you should quickly disable auto time compression and the freezes will not return as long as you are flying at the 1x (normal) rate.

By any chance are you using payware scenery for VHHH?

Parked at KSFO after a flight from VHHH yesterday.

I feel your pain. Just finished reinstalling windows and FSX as well. I would suggest uninstalling the NGX and 777, then verify FSX is running normally. Maybe the CFG file is corrupt, try deleting it and having FSX rebuild it to a clean version.

+1 LOL!

LOL, yeah that's the one. One of my favorite videos.

Haha, Isn't there a video floating around of two pilots hanging out of the cockpit of a 757 at the runway hold line washing their windows. I think it was JET2. It's actually pretty normal to see this at the airport. Pilots tend not to trust ground crews to clean it for them.

It was the same way with the NGX. This too shall pass. Great words to live by.

I think we need some more info from you before we can help. I check out your computer specs, but doesn't specify if it's overclocked. You should also download this nifty little program I use when I build my systems and OC them. http://www.nirsoft.net/utils/blue_screen_view.html If you go to some of the overclocking websites (regardless if you overclocked or not) they will often have a list of what these BSOD codes mean.

The thing about Windows 7 is that it is way ahead of it's time when you consider a program like FSX. You need to ensure every single Windows 7 update is applied before installing FSX. Uninstall FSX as Diego recommends and you need to follow this guide to the letter. http://www.simforums.com/forums/the-fsx-computer-system-the-bible-by-nickn_topic46211.html It will help immensely. Good luck!