At first I too, thought it wasn't my OC, because it "appeared" stable for about 1.5 weeksBut I've turned mine back to stock and no G3D errors, no CTD's (normally G3D.dll related), and no BSOD.Can't wait to turn it back up to 4.5 GHz though - I really miss the fps with my Mustang VC, 8.5 lod, and very dense autogen lol

I am on a lowly Q9650 at 3.76Ghz and have wonderful smooth performance, wonderful IQ, and often fly w/ BLOOM on now when not in the most complex situations. Why the need to take these new iX processors and aim for such as high O/C? Can't imagine what would stress your machine at 1.37Ghz or even less, using my own as the comparison. As I understand it, the newer processors are moving stuff at 1.5 to 2x what I am able to process, and mine is good enough allow me to postpone an upgrade for almost . . . ever! I guess it's just a case of never being satisfied or something. I'm thankful I have no need to upgrade currently.Noel

Shame you had to give up your overclock in favor of stability. I've been running an overclocked system for the last five years on two different sets of hardware with no stability issues whatsoever. Many folks tend to push things to far though with arbitrary number goals in their head (must get to 4.2!). I overclock mine to the point of matching my memory's rated capabilities and everything runs great.

Shame you had to give up your overclock in favor of stability. I've been running an overclocked system for the last five years on two different sets of hardware with no stability issues whatsoever. Many folks tend to push things to far though with arbitrary number goals in their head (must get to 4.2!). I overclock mine to the point of matching my memory's rated capabilities and everything runs great.

----------------------------------------------------------------------------------------------------------------Actually, I didn't 'give up' my overclock. What I did was go from 4.03 GHz, back to 3.74 GHz. That translated to only a loss of 3 FPS on average. Not even noticeable on smoothness or simulation play. What I got back was enormous though. FSX is stable from start to finish. That is priceless to say the least! :))) The i7-975 Extreme CPU actually is a 3.33 GHz part. with cores factory set to a multiplier of 25. I now have them all set to 28 across the board. My 1066 MHz memory is set to 1333.0 MHz. In all, only a shave off of 300 MHz did wonders!Mitch

i7-930 o/c 4.1GhzASUS P6TD Deluxe mobo6 gigs DDR3 ramEVGA GTX 470640 Gig HD at 7200 rpm150 Gig HD at 10,000 rpmcreative Xfi soundblaster cardFSX w/sp2Win 7 64bit home premiumwow, I had my first complete flight in a LOOOONG TIME!! I flew the Carenado B58 from KRBG to KAST 1.3hrs and everything went fine. I had a few stutters but nothing significant. Maybe I found it, my next flight I've decided to o/c my graphics card and try it again and see if I can find the sweet spot, maybe o/c my graphics card I can get rid of those hickups here and there.

i7-930 o/c 4.1GhzASUS P6TD Deluxe mobo6 gigs DDR3 ramEVGA GTX 470640 Gig HD at 7200 rpm150 Gig HD at 10,000 rpmcreative Xfi soundblaster cardFSX w/sp2Win 7 64bit home premiumwow, I had my first complete flight in a LOOOONG TIME!! I flew the Carenado B58 from KRBG to KAST 1.3hrs and everything went fine. I had a few stutters but nothing significant. Maybe I found it, my next flight I've decided to o/c my graphics card and try it again and see if I can find the sweet spot, maybe o/c my graphics card I can get rid of those hickups here and there.

---------------------------------------------------------------------------------------------YOU GO GUY!!!! Ain't it sweet?!? After discovering this cure, I had no sleep throughout the night...merely flying/smiling, flying/smiling...and OH...did I mention SMILING?!?!?!?You and I are in the groove now, Brian. Congrats.Mitch

It's funny, isn't it? I recently had much the same experience with FSX. It almost seems like lately we discover that FSX really isn't that faulty as we thought. It's mostly the addons we install or actions we perform on our computer that cut FSX's throat... Had the same experience when with WoAI I had installed. Ever since dumping it and installing MTX again, I havn't had a problem with FSX freezing after going out of windows such as the map.

Ok...I would like to offer an apology to 'FSX' as if it were a person...."so...before the entire FSX community on AVSIM, please except my apology...and I will look forward to opening my FSX bound wallet once more while enjoying that STABLE flight simulation environment, that you now are!"--------------------------------------------------------------------------------------------------------------------------Man, was I tired...last night..'except' should have been 'accept''Tuscon' should have been typed 'Tucson'.oh geez.....

Yeah, goes back to what I was saying. Can't push the overclock too far in pursuit of numbers. Glad you found the right balance.

I have totally nailed the CTD's/BSOD/ANIMATION FREEZE issue with some user's systems, including my own.I am now back to running my CPU at 4.0 GHz and have the SYTEM MEMORY back to stock as recommended by the manufacturer.If you, by ramping up your CPU, also have to ramp up your MEMORY MHz....then that is where you are having the above issues with FSX. The crashes and freezes are MEMORY related and not CPU related. Because I have an EXTREME CPU, I can merely ramp up the clock speed of each core and not have to ramp up the system speed (which also affects your memory speed...), but can leave MEMORY at stock MHz. I am running totally stable now, with all CPU O/C performance restored. I do complete flights and have no further instability/CTD's/BSOD/animation freezes.So folks...if you have either O/C'd your system memory, and/or your graphics card memory...ten-to-one that is where you are having issues. Either you have to take your CPU (if not an unlocked multiplier part) back to system stock, so you can run your system memory at manufacturer's MHz settings, or you will keep running the P.I.T.A. of FSX instability. It is any O/C of MEMORY (system or graphics cards) that causes FSX to act with the above issues...and not running your CPU at around 4.0 GHz. If you have an unlocked CPU, you are breezing....Mitch

That's why it's recommended to overclock in stages: first test the system with no overclock, then overclock the CPU, finally overclock your RAM if you want to. Isolating things is the keyMemory OC doesn't really provide much of a performance boost anyway, but if you do you may also need to bump your Vtt/Vimc/Vccio to get it stable

I always underclock the RAM with all my CPU OCs, RAM OCing generally just causes instability or burns out the RAM in a very short period of time and does next to nothing for performance. We haven't been bandwidth-bound on the desktop in many years...

I agree that RAM OC is useless and will may cause CTDs and lockups. I learned the hard way too. :Big Grin: