Beats me!!

You have any demanding sceneries like Aerosoft Manhatten? This is my prime scenario for testing some tuning:Aerosoft Manhatten with 3 major airports nearby, including FSDT JFK and My Traffic or UT, loading up Aerosoft FalconX-F16 at 1500 ft ASL over central park heading south torwards the tip go into Spot plane view so that you are just slightly behind and slightly above the F16 so that we are filling up the view with buildings, traffic as well as some sky. Flying at 300 knts and sharp banking "S" patern to induce maximum stutters. No "Tweaks" what so ever to FSX.cfg other than a few variables to Texture_Multi...=40/60/80 and to really stressing things out by running LOD 9.500000, which when I had removed 3 sticks of memory for Maximum Settings and flew for less than an hour caused a "you have run out of memory...FSX must close" I set LOD back to 8.5x tested and then back to all dims full and 9.5X LOD, testing...testing...testingIt has been my goal to reduce these Stutters and Microstutters with hardware settngs as apposed to the cfg "tweaks" that seem to just pass the problem on only to show up some where else; and and I'm there, there are some things that work and they were not obvious at all, but only after considerable effort to run every combination that these nice boards allow you to accomplish.Sorry if I'm rambling...do you have any scenery or scenario that you can run like this?

You have any demanding sceneries like Aerosoft Manhatten? This is my prime scenario for testing some tuning:Aerosoft Manhatten with 3 major airports nearby, including FSDT JFK and My Traffic or UT, loading up Aerosoft FalconX-F16 at 1500 ft ASL over central park heading south torwards the tip go into Spot plane view so that you are just slightly behind and slightly above the F16 so that we are filling up the view with buildings, traffic as well as some sky. Flying at 300 knts and sharp banking "S" patern to induce maximum stutters. No "Tweaks" what so ever to FSX.cfg other than a few variables to Texture_Multi...=40/60/80 and to really stressing things out by running LOD 9.500000, which when I had removed 3 sticks of memory for Maximum Settings and flew for less than an hour caused a "you have run out of memory...FSX must close" I set LOD back to 8.5x tested and then back to all dims full and 9.5X LOD, testing...testing...testingIt has been my goal to reduce these Stutters and Microstutters with hardware settngs as apposed to the cfg "tweaks" that seem to just pass the problem on only to show up some where else; and and I'm there, there are some things that work and they were not obvious at all, but only after considerable effort to run every combination that these nice boards allow you to accomplish.Sorry if I'm rambling...do you have any scenery or scenario that you can run like this?

You just read my thoughts. I'm using some heavy scenery right now, and wondering how to stop the stuttering. My FPS are generally up to 40, but still, often drop to something like 25, causing a huge stutter.What are your findings?

But you know what I'm actually mad at right now?I have always been satisfied with FS9, my addons, everything working fine, flying etc... but I have always been a visual junkie, no matter what, even Windows-wise.FSX worked terrible, so I didn't even consider installing it.Now that FSX works more or less OK, I am so totally NOT into FS9. After seeing how some sceneries like Mallorca or VFR London look like, even the general scenery, when combined with higher LOD setting, wow.But even basically with this monster-machine, I get good results, but not those results that make you say wow.It's basically less texture quality with high performance vs. very high texture quality with lower performance. And I hate it!Even thought about throwing FS9 away, just for the sake of it - each time I opened it after I used FSX, yuck.

Paul,What is your QPI Link at? I see I can't put it lower than 7.3 when OCed @ 4.2Ghz. And usual settings are 4.8 or 6.4 AFAIK.

Paul,What is your QPI Link at? I see I can't put it lower than 7.3 when OCed @ 4.2Ghz. And usual settings are 4.8 or 6.4 AFAIK.

QPI at a minimum has to be twice as much as your effective Dram frequency.I am the other direction and am running at dangerous uncore and QPI directly equal to each other and results in very high QPI voltages to maintain stability (they flux between 1.4 to as high as 1.8 under max load of many apps running and stress testing) XMP sets QPI v at a static 1.6v , but I am not using that.I have had to reduce to 4.2Ghz as I don