Not yet, I like to run a few days gaming and some prime 95 here and there as well as general use just to see if I get any blue screens at what I'm at, will move it up in a day or two though
i5 2500k vcore
- Thread starter king2104
- Start date
Not yet, I like to run a few days gaming and some prime 95 here and there as well as general use just to see if I get any blue screens at what I'm at, will move it up in a day or two though
hi,
quick update i think i may have grabbed it. what i done is raise the lcc level to 3 and put the multiplyer on 4.5ghz with a vcore of 1.365 while running ibt my vcore slightly decreases to about 1.320 in cpu-z bear in mind testing on high at 4.5ghz, and with no testing my vcore is 1.380 but all in all good always wanted 4.5ghz but is there any suggestion to maybe how i can lower my vcore in cpu-z with lcc rasing it up abit.
thank you everyone for the massive support much ebbter then tomshardware took nearly 1 day to get one reaply.
quick update i think i may have grabbed it. what i done is raise the lcc level to 3 and put the multiplyer on 4.5ghz with a vcore of 1.365 while running ibt my vcore slightly decreases to about 1.320 in cpu-z bear in mind testing on high at 4.5ghz, and with no testing my vcore is 1.380 but all in all good always wanted 4.5ghz but is there any suggestion to maybe how i can lower my vcore in cpu-z with lcc rasing it up abit.
thank you everyone for the massive support much ebbter then tomshardware took nearly 1 day to get one reaply.
Permabanned
- Joined
- 15 Sep 2010
- Posts
- 2,691
hi,
quick update i think i may have grabbed it. what i done is raise the lcc level to 3 and put the multiplyer on 4.5ghz with a vcore of 1.365 while running ibt my vcore slightly decreases to about 1.320 in cpu-z bear in mind testing on high at 4.5ghz, and with no testing my vcore is 1.380 but all in all good always wanted 4.5ghz but is there any suggestion to maybe how i can lower my vcore in cpu-z with lcc rasing it up abit.
thank you everyone for the massive support much ebbter then tomshardware took nearly 1 day to get one reaply.
That is a good vcore for your 4.5ghz oc, i would leave it at that, you could try lowering it but there really isn't any point if you are stable at your current settings, just enjoy your new oc. Have fun.
Permabanned
- Joined
- 15 Sep 2010
- Posts
- 2,691
So you're 4.5ghz is failing prime at 1.368v? And you have your vcore a little higher than this in the manul setting? If this is the case then try the next stage up with LLC to see if match the voltage in your manul setting then rerun prime, if it still fails then increase your vcore a lttle more, you will eventually find the sweet spot for 4.5ghz. Excuse my spellings, i have a hangover from my brandy nite
Permabanned
- Joined
- 15 Sep 2010
- Posts
- 2,691
Sorry just reread your posts and see you have set the vcore to 1.365, so you may need to incresse it, just do it a little at a time.
Nope, vdrop is the difference between what you set in BIOS and what you get at idle. Vdroop is a specific design feature of Intel chips that reduces the voltage with increasing CPU load to prevent transient voltage spikes damaging the CPU when it goes from load to idle. The aim being that any spike doesn't exceed the normal idle voltage.Is`nt Vdrop and Vdroop the same thing!!!
Permabanned
- Joined
- 15 Sep 2010
- Posts
- 2,691
Just check to see which way you're going with the LLC as boards vary, for example some boards are at their highest setting at level 1.
.05 is not a big increase in volts so just do it at that, not sure if you can increase it in smaller amounts, maybe someone with knowledge on gigabyte boards could comment here?
.05 is not a big increase in volts so just do it at that, not sure if you can increase it in smaller amounts, maybe someone with knowledge on gigabyte boards could comment here?
Note that on Gigabyte boards LLC levels less than 5 will mean lower load voltages than you manually set, 5 will be around the same and only 6+ will give it more than you set. Just to avoid any further confusion, the only vcore hat matters is the one taken when the CPU is under load, note those with something like OCCT or another program that can stress and monitor. People go like oh my 2500k 4.5 is stable at 1.28 in bios cool, when really they, for example, put the LLC at level 8 and are actually feeding 1.38 to in under load.
I suggest you forget about LLC, if you put 'normal' as the vcore in bios and use DVID to offset the stock voltage it gives you until you're stable, power saving features will work with the overclock and because the CPU will idle at like 1.04 you can easily justify even 1.4 (if needed) for the 4.5 overclock under load which I bet the vast majority will do. Leave the default multiplier at stock and put all turbo ones to 4.5. My 2500k (not a very good clocker) was stable with an offset of +0.050 which ends up at around 1.34 vcore under load. (though the exact numbers will likely vary in your case)
Also note that sometimes with Gigabyte boards softwere (including cpuz and hwmonitor) will get confused and show QPI/Vtt voltage instead of vcore.
I suggest you forget about LLC, if you put 'normal' as the vcore in bios and use DVID to offset the stock voltage it gives you until you're stable, power saving features will work with the overclock and because the CPU will idle at like 1.04 you can easily justify even 1.4 (if needed) for the 4.5 overclock under load which I bet the vast majority will do. Leave the default multiplier at stock and put all turbo ones to 4.5. My 2500k (not a very good clocker) was stable with an offset of +0.050 which ends up at around 1.34 vcore under load. (though the exact numbers will likely vary in your case)
Also note that sometimes with Gigabyte boards softwere (including cpuz and hwmonitor) will get confused and show QPI/Vtt voltage instead of vcore.
Last edited: