Georgios

Sajin

Georgios

Sajin
I think you have to manually type in 1250 after setting cpu vore control to manual.

Here

Change current vcore from auto to manual and input 1250. 

Yes, I know, the problem is, it won't let me.
 

Are you running the latest bios version 1.22? If yes, have you tried older bios versions to see if you experience the same issue with them?

You can download older bios versions here... https://www.evga.com/support/download/

No problem.

Georgios

Sajin
You can download older bios versions here... https://www.evga.com/support/download/

That's 1.22.

You can also download the newest version on that page.

Yes, I did suggest installing an older version. You can try them all if you'd like.

Make sure you uncheck "show latest driver" before clicking submit.

...And this is pby a key point to a vet, but the clock is bouncing from 3.6 to 1.6GHz  on XTU when I set the peak clock setting at 4.6 prior to running a benchmark that inevitably crashes...

Sorry for the long delay in response (I appreciate any discussion I can stir on these issues and this hardware), had to tear my system down and work something else for a bit.  I'm only now getting back to it....
Running windows 10 Pro on my Z77 FTW 3570K.
VDroop is supposed to be the LLC setting in this system tho, doesn't that make it inherently less stable at high voltages/OCs ?
(is that why this board didn't break any records?)
Can you clarify "C States" ? (pegging core frequencies?)
...Considering shelling out $300 for a Maximus V Extreme (IN 2019 ! F ! ...sorry for the EVGA sacrilege)
According to CPUZ S/B able to hit 7GHz with this generation (with LN2 but...) lame to be stuck at 4.5 GHz at 60F...

sdcgsb

VDroop is supposed to be the LLC setting in this system tho, doesn't that make it inherently less stable at high voltages/OCs ?

(is that why this board didn't break any records?)

I don't really know about records but in overclocking vDroop can be useful when used in conjunction with c-states and other variable voltage scenarios to adjust voltage for more headroom should the processor need it. If you're setting a constant overclock and disabling c-states you shouldn't need it in my experience with this board. It'll cause you more problems than it's worth.

sdcgsb

Can you clarify "C States" ? (pegging core frequencies?)

Sure. C-states are idle power saving states. It's basically for energy saving when not under load or during certain load conditions. You can read more about them here: https://software.intel.co...-and-package-c-states. If I remember correctly (I'm not at home at the moment so sorry I can't give specifics) it should be in the Overclocking-> CPU Configuration menu somewhere and it should be labeled c-states.

sdcgsb

BTW, was thinking maybe XTU was a/the factor (especially since the bs update/changes)

Still a glass ceiling at 4.5GHz on heritage E-LEET and manually in Bios.

...XTU was nice tho.

 I wouldn't really use any Intel software to do the overclocking just based on personal preference. I'm not too familiar with XTU though. I've always just done overclocking straight from the bios rather than doing it from the OS. I would imagine that trying to use more than one thing to control the overclock might cause some problems, but like I mentioned I only overclock through the BIOS so I guess I can't really comment on it.

When I first setup the machine in 2013 I spent all of my free time for the better part of a week learning overclocking on this board and it was a lot of fun. The machine has been my only gaming rig ever since then. I've been running with c-states and vdroop turned off and setting a constant voltage for the overclock I wanted and it's been running fine for 5+ years like that at 4.2ghz with a corsair H100. Nothing to brag about for sure but the system has been very good to me.