Odd issues since overclocking I5 3570k

I found my 4.2GHz sweet spot. The difference isn't much you are right, glad I got it working anyway though. I am actually at 4.5 now, with speedstep it stops it being at 1.28V constantly, dropping to 0.96v 80% of the time can't be bad for the life of my CPU.

Just checked how much it cost's to run my PC for a month, with speedstep I could save up to £1. Amazing! :rolleyes: My pc actually only draws 95-120W from the mains when using chrome etc. Pretty good.
 
Last edited:
Hey all,

Thanks for the replies, I will look at them properly tomorrow when I am not tired.

I have changed the voltage to "auto" at the moment which is (according to gigabyte easytune) 1.212 V underload (using IBT).

I do have a question regarding this value though... The voltage is being recorded differently in all the monitoring programs I am using (easytune, core temp, cpu z).

What do you guys use to monitor voltages? I am unsure which value to believe.
 
I'd suggest that the different monitoring programs are polling for and receiving the voltage data at different times and at different intervals, because the voltage continuously fluctuates it would be down to coincidence for you to get the exact same voltage reported by different tools. It's also possible that one tool reports the exact voltage snapshot whilst another reports an average over a short timespan.

I tend to use CpuZ for voltage monitoring whilst stress testing.
 
Last edited:
Thanks for the reply, currently using prime95, running CPU z and HWinfo32.

CPU z reporting 1.200v and HWinfo32 reporting 1.256 (minimum reported as 1.256 and max recorded as 1.261).

They are quite different so not sure which to believe!

I would assuming since HWinfo32 reports min, max, and current that it would show 1.2 even if it does take averages etc.

I believe my voltage in bios is currently set to standard, which if i remember correctly is 1.178 volts, and so both readings would be wrong. :S

edit: Just realised cpu-z is reporting core voltage and HWinfo32 is reporting the VID of each core. I believe these values represent different things?
 
Last edited:
Yes VID is read from the CPU's table and is what the CPU expects to receive at any given speed, the core voltage is what the CPU is actually being given. I'm not sure why your CPU is being given -0.056v less than it's potentially asking for but if it's stable .........

/Edit - Apparently it's not unusual for the reported core voltage readings to be up to 20% off so that could explain it.
 
Last edited:
haz_pro said:
Thanks for the reply, currently using prime95, running CPU z and HWinfo32.

CPU z reporting 1.200v and HWinfo32 reporting 1.256 (minimum reported as 1.256 and max recorded as 1.261).

They are quite different so not sure which to believe!

I would assuming since HWinfo32 reports min, max, and current that it would show 1.2 even if it does take averages etc.

I believe my voltage in bios is currently set to standard, which if i remember correctly is 1.178 volts, and so both readings would be wrong. :S

edit: Just realised cpu-z is reporting core voltage and HWinfo32 is reporting the VID of each core. I believe these values represent different things?
Click to expand...

These results are pretty much Identical to mine for 4.3GHz (i.e> 1.200v under Prime load, using a manual vcore of 1.232v and a medium LLC, Temps around the 60's
Spread Spectrum (disabled) C1E (Enabled) other states (disabled) 1.256v was at 44, but I found this a little too jittery, startup wasent as instant, the welcome screen buggered about for about 2o secs before desktop loaded, using 43 and its Hit Power, and desktop in 22 secs from cold start :cool:
 
You must log in or register to reply here.
Back
Top Bottom