2500k mobo and software vcore

[grandpatzer]

I recently installed a Intel 2500k and Sapphire Pure P67.

Now if I put in BIOS vcore to 1.45v then start HWINFO32 for logging and start Intel Burn Test then the MAX vcore according to HWINFO32 is 1.356v.

If I put BIOS vcore to 1.55v(!!) then the MAX vcore in HWINFO32 is 1.376v.

If I put in BIOS vcore to 1.45v and 4.5Ghz then the Intel Burn Test give me BSOD, but then the HWINFO32 vcore is 1.356v.

The 2500k I bought used and it's previous owner has been running it at 1.45v and 4.9Ghz.

 

[Kenmitch]

Never used the MB before. Maybe you need to enable or up the load line calibration look for something similar in bios and see what it's currently set to.

 

[Yuriman]

What you're experiencing is vdroop, this is normal.

I posted this a few weeks back for another member trying to overclock here:

I recommend you try the Intel Extreme Tuning Utility for your first overclock. You don't need to reboot when changing multipliers/voltages, and it works a LOT better than the software included by motherboard manufacturers.

First you need to go into bios and change vcore to offset mode, but don't change the voltage (I set mine to +.005v because +0v wasn't available). In power saving features, disable C3/C6 and Package C states, but make sure you leave C1E enabled. Basically everything else can be left at default.

Once in windows, load up the Intel utility and max out the Turbo Boost Power Max and Core Current Limit, like so:

This basically turns off TDP limitations (your chip is rated at 77w TDP but you want to be able to draw more power than that when overclocked).

To overclock, drag the multiplier sliders up and hit apply. Do not play with the reference clock, only multipliers. You'll probably want to go up 1x at a time and run Prime95 or IBT to test for errors. When you reach a threshold where you're no longer stable, you can either increase the voltage, or drop your multiplier back down.

The max safe voltage for day-to-day usage is arguably about 1.3v, which on my board is about +132mv. I can get up to around 4.6ghz on my chip without going over 1.3v but your mileage may vary.

^ Those voltages are for Ivy Bridge, but the rest of it applies to you. In the past software overclocking wasn't as good as overclocking from bios but this is no longer the case.

 

[grandpatzer]

What you're experiencing is vdroop, this is normal.

I posted this a few weeks back for another member trying to overclock here:

^ Those voltages are for Ivy Bridge, but the rest of it applies to you. In the past software overclocking wasn't as good as overclocking from bios but this is no longer the case.

Seriously is Software overclocking just as safe as BIOS overclockin?
If that's true it's really awesome

I'll have to look further into sofware OC.

Edit---> I'm pretty sure my BIOS only has AUTO mode, incase no OFFSET mode is AUTO ok?

 

[Yuriman]

I think so. As long as you're not using "fixed" voltage.

 

[grandpatzer]

I think so. As long as you're not using "fixed" voltage.

For now I'll OC using BIOS, I'm not confident using a software for this stuff.

in BIOS CLL was enabled, I'm assuming enabled is 100%?

To make sure CLL is active I changed enabled to 75%
So now CLL is at 75%

I put speed to 3.4ghz and vcore to 1.3v still seems like I have too low vcore...

 

[Yuriman]

The only issue with fixed voltage is that you won't be able to adjust voltage in the utility. Load line calibration (LLC) is fine to use but my preference is with it off. It's not a big deal what you set it to.

 

[grandpatzer]

The only issue with fixed voltage is that you won't be able to adjust voltage in the utility. Load line calibration (LLC) is fine to use but my preference is with it off. It's not a big deal what you set it to.

So I put vcore to AUTO in BIOS then I can change vcore in Intel Extreme Enthuasiast?

 

[Yuriman]

So I put vcore to AUTO in BIOS then I can change vcore in Intel Extreme Enthuasiast?

I think that's the case, yeah. Let me know if it's not.

To me, it's super convenient that I don't have to reboot when I want to make a slight tweak to an OC.

 

[grandpatzer]

I think that's the case, yeah. Let me know if it's not.

To me, it's super convenient that I don't have to reboot when I want to make a slight tweak to an OC.

Well I tried the Intel software but basicaly on my PC I need to restart and then the Intel software modifies the BIOS so I could just aswell use the BIOS instead of Intel software they do the same thing.

This is what I have achieved so far:

my Mobo has LLC: Disabled, 25%, 50%, 75%, Enabled.
I'm assuming Enabled is 100%(?)

Also I read the wrong reading that was VID and not Vcore.

there is vcore in HWINFO and it's simply called Vcore, however this motherboard that I today install seems to always have too low readings
When putting Vcore to AUTO it reads MIN 0.600v, MAX 0.848v and now in IDLE Current: 0.632v

So far I have had BIOS DEFAULT and just increasing multiplier to 42x and IBT (Intel Burn Test) crashes after just 2 runs.

41x is 100% stable at this stressing: 2hour small FFT Prime95 + 20runs IBT 2048mb (High) stable with in BIOS everything at DEFAULT besides the multiplier.

I did try following: LLC:75%, Vcore 1.45v, 44x, Interna PLL overvoltage enabled. Everything else is DEFAULT I think the default PLL is 1.80v.
First time running IBT it passes, 2nd time I try IBT 2048MB it crashes after just 2 runs, warning me that PC not stable.

 

[Yuriman]

Interesting, it may be that the Intel software only allows windows adjustments on Z-series chipsets (or at least not with a P67). I've been looking for a compatibility chart for it.

LLC attempts to compensate for vdroop. For instance, if you set your vcore to 1.3v and then load your CPU, voltage will droop (let's say down to 1.25v). LLC adds voltage when the CPU is loaded to bring it back up to the value you want. Setting LLC higher will compensate more, sometimes even higher than your requested voltage.

Intel designed their chipsets and CPUs with vdroop in mind so there's debate as to whether or not it's a good idea to use LLC, but the end result is that the higher the LLC you select, the lower the vcore you need to set in bios to get the voltage you want. You can get your desired voltage either way. You just need to check what your actual load voltage is in windows and then adjust up or down.

____

When you set your vcore to 1.45v and then load your chip in IBT, what does your actual voltage drop to? You might yet need more volts, but 1.45v is quite high for 4400mhz.

It sounds like you're doing everything right... you could try dropping your RAM speed to see if that improves stability.

 

[grandpatzer]

Interesting, it may be that the Intel software only allows windows adjustments on Z-series chipsets (or at least not with a P67). I've been looking for a compatibility chart for it.

LLC attempts to compensate for vdroop. For instance, if you set your vcore to 1.3v and then load your CPU, voltage will droop (let's say down to 1.25v). LLC adds voltage when the CPU is loaded to bring it back up to the value you want. Setting LLC higher will compensate more, sometimes even higher than your requested voltage.

Intel designed their chipsets and CPUs with vdroop in mind so there's debate as to whether or not it's a good idea to use LLC, but the end result is that the higher the LLC you select, the lower the vcore you need to set in bios to get the voltage you want. You can get your desired voltage either way. You just need to check what your actual load voltage is in windows and then adjust up or down.

____

When you set your vcore to 1.45v and then load your chip in IBT, what does your actual voltage drop to? You might yet need more volts, but 1.45v is quite high for 4400mhz.

It sounds like you're doing everything right... you could try dropping your RAM speed to see if that improves stability.

Well I have realised that I have been reading VID voltage and not the real voltage.

Interesting enough both CPU-Z and HWINFO show vcore: MAX: 0.848v this is what was shown when stressing it 100% all 4 cores, IDLE it is 0.632v, and MIN is 0.600v.

So I think that either my mobo BIOS or a sensor on mobo is defective.
Seems like it is measuring vcore but something like 0.40 to 0.60v too little on vcore.

I have Mugen push pull and MAX core is 74c and CPU is 76c so atleast I'm not at damaging vcore yet.

 

[Yuriman]

Without an accurate reading I'd suggest caution with increasing your vcore too much. Over 1.35v seems high for day-to-day use on Sandy Bridge, though others may feel differently.

You could "calibrate" your readings by measuring what your vcore reads at stock and then compare it with the actual stock vcore others get on their 2500k's. I don't have one so I can't help ya there.

 

[FalseChristian]

I have my i5 2500K at 4.5GHz using AUTO voltage which sets it at 1.275v. Try AUTO instead.

 

[grandpatzer]

I have my i5 2500K at 4.5GHz using AUTO voltage which sets it at 1.275v. Try AUTO instead.

AUTO only gets me up to 4.1Ghz stable.

I bought this CPU used and the previous owner run it at 1.45v and 4.9Ghz.

My hope would be to have at most 1.4v(depends on my temps) and 4.3-4.7Ghz.