Hi Guys, after a bit of advice. At this point in time I am running @ 4.6 GHz stable using an Offset of -0.035. This gives a core voltage of 1.312V. CIE and speedstep are enabled as is HT. I have noticed when using CPU-Z the core speed and core voltage fluctuate a fair bit when FSX is running. At cruise altitude it seems to settle and the VCore and core speed run at 4600 and 1.312 respectively. The FPS are set to unlimited and also do the same, that is fluctuate. Question :Are these two factors connected and would I be better off manually setting the VCore to 1.31V and disabling CIE and speedstep in the BIOS? Thanks in advance Andrew Dixon

That would be because of SpeedStep being ON.

That would be because of SpeedStep being ON.

I realise that but my question remains.

Why not test it yourself Andrew? Personally I like EIST & C1E enabled and offset Vcore, but that's just me.

On my Athlon the C1E is disabled along with Cool N Quiet (SpeedStep) , for your CPU it will be different.

Why not test it yourself Andrew? Personally I like EIST & C1E enabled and offset Vcore, but that's just me.

Hi Dazz, Why do you prefer this arrangement? This is the advice I am after. Thanks Andrew Dixon

Because I like to have those power saving features enabled. Less heat, power draw & degradation

Thanks Dazz, any other personal opinions on this subject? Thanks Andrew

Same as Dario.My PC spends 80% of its time at 1.6Ghz. No need to feed it high volts.

I also would like opinions about this. I've just bought a new 2600K system with an Asus Maximus IV Extreme - Z motherboard and 4x2Gb Mushkin Redline sticks with an Asus Platinum GTX 580 GPU or whatever it's called and a Vertex 3 240Gb SSD cooled by a Noctua DH-14 and powered by a Corsair 1050W modular PSU. Why not. Frankly the BIOS and the instructions and all the software might as well have been written by a shoal of jellyfish for all the sense they make. I've been fiddling around with these things for years but the c**p of the quality control and the jibberish which passes for "English" as well as the impenetrable rubbish presented as a spanking new "Graphical UI BIOS" is now beyond a joke - but don't let me get started on all of that. I've set up many systems in my time but you would not believe the bother I had getting this thing running properly. Anyway, I've managed to work out how to get the thing stable at 4.6GHz on 1.35 vCore with 1600MHz RAM at 6-7-6-24 T2. But this is using the "Manual" settings. Hints - no actual firm guidance or anything like that, of course - but mere tantalising tidbits from Asus and elsewhere, suggest that "offset" might be better. "Offset" is not actually available by default on my MB. I finally stumbled on the clue as to enabling it - not in an instruction manual, or anywhere obvious like that, but on an obscure forum somewhere through Google - namely by changing the phasing to "Optimized". But having done so, and after choosing an offset of -0.07v for a targeted o/c of 4.8GHz, the MB launched a suicide attack on my CPU by ratcheting up the vCore to >1.5v. Luckily I spotted it at once and shut the thing down but now I am completely mystified about what actual settings I need to use in offset mode, to get beyond 4.6GHz. Currently I'm on 4.6GHz with 1.35v and reported temps <56 degrees, Internal PLL Voltage enabled and the fancy frequency thing set to 300, with the Mushkin RAM running nicely at its XMP speed and latency. Shall I just call it a day? Or is it worth trying to go further? Why can't some responsible adult (eg, Asus) tell us what settings to use or at least tell us in plain English what the 1000s of settings in the ridiculous fancy BIOS actually do? I think I'm getting too old for all this nonsense. That's what my wife has been saying for years, though less politely ... Yours in equal measure sceptically, enraged and hen-pecked, Tim PS: forgive the rant: I'm a nice bottle of Pauillac down.

Haha, don't despair TimIs 1.35V the minimum for a stable 4.6GHz? you could still try 1.37 or 1.38V for 4.7GHzAnd is that 1.35 Vcore the one you see in Windows at full load or the one you set it your BIOS?What LLC level are you at now? The idea is to use manual Vcore to find the OC that works for you. Once you have settled for a certain #GHz at it's minimum Vcore, you can (if you want to take advantage of C1E) go find the necessary offset that will provide the same Vcore you had in manual mode. That's basically a trial & error thing. If -0.07 results in 1.5V, you'll need -0.19 or something like that for 1.38V. You can set your offset, reboot and go back to the BIOS and see what Vcore reading you have with the new offset and adjust accordingly. The reading in BIOS won't be exact, but will help you avoid inadvertantly booting into Windows with some ridiculous amount of Vcore only to find out about that once you fire up CPU-Z

Tim There are a couple of approaches to offset mode here that may help http://forum.avsim.n...ples-displayed/

Thanks Dan and Howard: I'll persevere a little this w/e. Tim

An update to my original post, The original question was asked as I had severve FPS fluctuations, as low as single digits after landing, and I wanted to know if there was any correlatation with the change in Core Voltage and Core Speed. Using Offset Mode these two values do change at different times. With a set Vcore and Core speed of course these two values remain constant.Well after testing both ( taking Dazz's advice) the result is there really is no difference between Offset Mode and Manual Vcore where EIST and C1E are disabled.My issue was Nvidia Inspector settings. VSync was being forced. Changed that to application controlled and by magic the FPS and performance commensurant of a 2600K @ 4.6GHz and a GTX580 was present! So back to the Offset Mode setting of -0.040 which gives a Vcore of 1.304/1.312 under load using Prime 95. Andrew Dixon

EIST / SpeedStep controls CPU speed. If it's disabled you'll always have your set clocks (3.4GHz stock + turbo, or whatever you OCed the multiplier to)C1E controls Vcore. If it's disabled, doesn't matter if Vcore is manual or offset, you'll allways have your Vcore constant, but if you use manual Vcore, C1E won't work and your Vcore will remain constant even if C1E is enabled