Manual setting of vcore won't stick?

[TheVrolok]

Now that I backed down a BIOS revision I'm OC'ing much better, however, I can't seem to lower my vcore. I had it set to 1.2625, CPU-Z read it at 1.328. I went back and set it to 1.2 and CPU-Z still reads it at 1.328. The Asus Windows programs both claim that the BIOS setting is indeed 1.2v but that the vcore is currently at 1.33v. I don't understand why I can manual set my vcore, but it'll have no effect? Maybe I'm missing a setting that's automatically kicking it back up if it's detected to be too low?

 

[NoelS]

Vrolok,

If you have an Intel CPU, it could be the Intel SpeedStep setting, which adjusts VCore under load. When the computer is idle, it keeps voltages low to conserve energy, when under load it will loosen up on the voltages.

So I would suggest disabling Speedstep and also C1E Support which also enables/disables the "Enhanced Halt State." I found that by disabling both of these settings in the BIOS under CPU Settings (or similar), my VCore always stayed at nominal (high) voltages.

Noel

 

[BonzaiDuck]

There may be several types of perceptions here, although NoelS knows what he's talkin' about.

Some BIOS versions (I have personal experience with ASUS), were notorious such that the "Set" voltage would not change the VCore after some level, as in "above 1.44V" or "above 1.5V."

Worse -- the BIOS version "set" value and the monitored value would vary.

Worse than that -- neither "set" nor "monitored" would equate or approximate the reading taken with a multitester.

But here's something I'VE experienced: a scenario where you set the CPU multiplier to 8, get a stable over-clock, and then, for some mysterious reason the next time you boot the system, it starts posting with a multiplier of 9. I think that, TOO, is a BIOS problem of some sort.