F5F Stay Refreshed Power Users Overclocking Verify VCore or VID during overclocking

Verify VCore or VID during overclocking

Verify VCore or VID during overclocking

A
Amegahoney
Posting Freak
789
02-12-2016, 04:51 AM
#1
Hi, I'm trying to overclock my 6700k CPU for the first time. When stress testing, I want to know what to check regarding the VCore or VID. Since the VID goes much higher than what I set in my BIOS (about 0.1v above), like when I set core voltage to 1.32 and got VID up to 1.36v and even 1.402v. Also, what's a safe voltage for continuous use? Should I use an LLC converter because I often struggle to get from 4.4 to 4.5 and need to apply high voltage unless I switch to LLC on high.
A
Amegahoney
02-12-2016, 04:51 AM #1

Hi, I'm trying to overclock my 6700k CPU for the first time. When stress testing, I want to know what to check regarding the VCore or VID. Since the VID goes much higher than what I set in my BIOS (about 0.1v above), like when I set core voltage to 1.32 and got VID up to 1.36v and even 1.402v. Also, what's a safe voltage for continuous use? Should I use an LLC converter because I often struggle to get from 4.4 to 4.5 and need to apply high voltage unless I switch to LLC on high.

M
mineuout482
Posting Freak
812
02-12-2016, 06:11 AM
#2
I recommend a maximum of 1.4V, with LLC configured as "medium" or "high," avoiding "ultra high" or "extreme." Excessive LLC can lead to voltage spikes beyond your target, while insufficient settings may trigger Vdroop, causing the voltage to drop under load—both detrimental for overclocking. Regarding voltage fluctuations, are you operating in manual, offset, or adaptive mode? If manual and it seems correct, then the increase is likely due to your LLC adjustment.

HWMonitor isn't ideal for tracking core voltage accurately; it tends to misreport values. A better option would be AIDA64 for more consistent monitoring. Ensure that your voltage choices and LLC configuration don't push the CPU above 1.4V continuously during operation.
M
mineuout482
02-12-2016, 06:11 AM #2

I recommend a maximum of 1.4V, with LLC configured as "medium" or "high," avoiding "ultra high" or "extreme." Excessive LLC can lead to voltage spikes beyond your target, while insufficient settings may trigger Vdroop, causing the voltage to drop under load—both detrimental for overclocking. Regarding voltage fluctuations, are you operating in manual, offset, or adaptive mode? If manual and it seems correct, then the increase is likely due to your LLC adjustment.

HWMonitor isn't ideal for tracking core voltage accurately; it tends to misreport values. A better option would be AIDA64 for more consistent monitoring. Ensure that your voltage choices and LLC configuration don't push the CPU above 1.4V continuously during operation.

R
Ryanl785
Junior Member
6
02-14-2016, 12:24 AM
#3
Vcore represents the voltage your CPU receives, while VID refers to the signal sent to the motherboard that determines the higher value.
R
Ryanl785
02-14-2016, 12:24 AM #3

Vcore represents the voltage your CPU receives, while VID refers to the signal sent to the motherboard that determines the higher value.

G
GreenLantern15
Junior Member
4
02-14-2016, 02:30 AM
#4
I recommend a maximum of 1.4V, with the LLC setting at "medium" or "high," avoiding "ultra high" or "extreme." Excessive LLC will lead to higher voltage than intended, while too little can cause Vdroop, which is dangerous for overclocking. Regarding the voltage fluctuations, are you operating in manual, offset, or adaptive mode? If manual and it seems correct, then the increase is due to your LLC configuration.
G
GreenLantern15
02-14-2016, 02:30 AM #4

I recommend a maximum of 1.4V, with the LLC setting at "medium" or "high," avoiding "ultra high" or "extreme." Excessive LLC will lead to higher voltage than intended, while too little can cause Vdroop, which is dangerous for overclocking. Regarding the voltage fluctuations, are you operating in manual, offset, or adaptive mode? If manual and it seems correct, then the increase is due to your LLC configuration.

N
nathy2402
Member
75
02-19-2016, 08:32 PM
#5
On my setup, HWMonitorPro incorrectly identifies Vccin as Vcore, which causes it to display a value of 1.88.
N
nathy2402
02-19-2016, 08:32 PM #5

On my setup, HWMonitorPro incorrectly identifies Vccin as Vcore, which causes it to display a value of 1.88.