F5F Stay Refreshed Power Users Overclocking VCORE at 1.71V on an i5 4690k is normal and shouldn't cause issues.

VCORE at 1.71V on an i5 4690k is normal and shouldn't cause issues.

VCORE at 1.71V on an i5 4690k is normal and shouldn't cause issues.

Pages (2): 1 2 Next
C
coyote888
Posting Freak
838
06-25-2016, 08:25 PM
#1
I've been using my i5 4690k for nearly a year and recently began exploring overclocking to enhance its performance. From the discussions I've read, OCCT is the recommended software, so I installed it and started testing. I noticed that VCORE should ideally stay below 1.3V, but when launching the program it displays 1.71V before I even adjust any settings. Can I still attempt to overclock? Is there anything wrong with my system? Any guidance would be greatly appreciated.
C
coyote888
06-25-2016, 08:25 PM #1

I've been using my i5 4690k for nearly a year and recently began exploring overclocking to enhance its performance. From the discussions I've read, OCCT is the recommended software, so I installed it and started testing. I noticed that VCORE should ideally stay below 1.3V, but when launching the program it displays 1.71V before I even adjust any settings. Can I still attempt to overclock? Is there anything wrong with my system? Any guidance would be greatly appreciated.

R
Retrebution
Junior Member
29
06-26-2016, 03:56 AM
#2
Maybe the 1.7V Vcore from OCCT is what some others might call Vccin.
But now that Vcore (or VID, slight different meaning, but in this context can be the same) is 1.2V, we can be sure that it is in a safe value.
Now, there's nothing left to worry.
I asked you to compress a file because Haswell will jump to lower voltages when idle (unless every power saving feature and C state is disabled), and will only yse the real Vcore when under load, so it doesn't really make sense to check voltages when idling.
But now, problem solved. You can go back to overclocking, if that was your original objective. Here are some guidelines that you could use as reference later:
I strongly recommend carefully reading this guide...
R
Retrebution
06-26-2016, 03:56 AM #2

Maybe the 1.7V Vcore from OCCT is what some others might call Vccin.
But now that Vcore (or VID, slight different meaning, but in this context can be the same) is 1.2V, we can be sure that it is in a safe value.
Now, there's nothing left to worry.
I asked you to compress a file because Haswell will jump to lower voltages when idle (unless every power saving feature and C state is disabled), and will only yse the real Vcore when under load, so it doesn't really make sense to check voltages when idling.
But now, problem solved. You can go back to overclocking, if that was your original objective. Here are some guidelines that you could use as reference later:
I strongly recommend carefully reading this guide...

P
PvPking1999
Member
50
06-26-2016, 05:04 AM
#3
I think the program might be giving incorrect data or using another term. I recommend checking CPU-Z and HWMonitor for confirmation. Once verified, adjust the BIOS settings to Manual mode with a voltage of 1.2V (maintaining original clock speeds) and recheck the readings with all three tools. Avoid stress tests until the Vcore is confirmed stable.
P
PvPking1999
06-26-2016, 05:04 AM #3

I think the program might be giving incorrect data or using another term. I recommend checking CPU-Z and HWMonitor for confirmation. Once verified, adjust the BIOS settings to Manual mode with a voltage of 1.2V (maintaining original clock speeds) and recheck the readings with all three tools. Avoid stress tests until the Vcore is confirmed stable.

D
DankLlamas
Member
108
06-28-2016, 02:28 AM
#4
The program might be displaying incorrect values or using a different naming system. Verify with CPU-Z and HWMonitor. Adjust BIOS settings to Manual mode, set the voltage to 1.2V (with stock clock speeds), and recheck readings with all three tools. The HWMonitor reports 1.712V, while CPU-Z shows Core Voltage between 0.75V and 0.85V. BIOS lists VCORE at 1.007V, but it doesn’t allow manual voltage adjustment. Consider enabling 'extreme over voltage' if needed.
D
DankLlamas
06-28-2016, 02:28 AM #4

The program might be displaying incorrect values or using a different naming system. Verify with CPU-Z and HWMonitor. Adjust BIOS settings to Manual mode, set the voltage to 1.2V (with stock clock speeds), and recheck readings with all three tools. The HWMonitor reports 1.712V, while CPU-Z shows Core Voltage between 0.75V and 0.85V. BIOS lists VCORE at 1.007V, but it doesn’t allow manual voltage adjustment. Consider enabling 'extreme over voltage' if needed.

M
mj18wals
Senior Member
256
06-29-2016, 03:03 PM
#5
What kind of motherboard are you using? Examine it for power-saving options, automatic overclocking, gaming settings, and ensure all are turned off. Perform a light CPU-heavy task such as compressing a large file with 7zip or winrar, or use tools like Speedfan and cpuz. You might also test RealTemp or Aida64 (as a trial). Regarding the configuration, attempt to enable it to verify manual Vcore adjustments. If unavailable, re-enable it before leaving BIOS.
M
mj18wals
06-29-2016, 03:03 PM #5

What kind of motherboard are you using? Examine it for power-saving options, automatic overclocking, gaming settings, and ensure all are turned off. Perform a light CPU-heavy task such as compressing a large file with 7zip or winrar, or use tools like Speedfan and cpuz. You might also test RealTemp or Aida64 (as a trial). Regarding the configuration, attempt to enable it to verify manual Vcore adjustments. If unavailable, re-enable it before leaving BIOS.

K
KR4TOS
Member
193
06-29-2016, 07:41 PM
#6
Check the motherboard closely for power-saving options, automatic overclocks, gaming settings, and disable them all. Perform a light CPU-heavy task while monitoring Speedfan and CPU-Z, such as compressing a large file with 7zip or WinRAR. You might also try RealTemp or Aida64 (as a trial). Regarding the settings, attempt to enable them to verify manual Vcore adjustments. If not possible, revert before exiting BIOS.
K
KR4TOS
06-29-2016, 07:41 PM #6

Check the motherboard closely for power-saving options, automatic overclocks, gaming settings, and disable them all. Perform a light CPU-heavy task while monitoring Speedfan and CPU-Z, such as compressing a large file with 7zip or WinRAR. You might also try RealTemp or Aida64 (as a trial). Regarding the settings, attempt to enable them to verify manual Vcore adjustments. If not possible, revert before exiting BIOS.

M
marwinspaans
Junior Member
4
06-30-2016, 04:30 AM
#7
The VCORE represents the overall voltage of your entire CPU. It's the voltage provided by your motherboard to the voltage regulator built into all Haswell CPUs, managing power distribution to components like the memory controller, cache, CPU cores, and PCIE controller. The actual core voltage is the VID, which matches the voltage applied directly to the CPU cores.
M
marwinspaans
06-30-2016, 04:30 AM #7

The VCORE represents the overall voltage of your entire CPU. It's the voltage provided by your motherboard to the voltage regulator built into all Haswell CPUs, managing power distribution to components like the memory controller, cache, CPU cores, and PCIE controller. The actual core voltage is the VID, which matches the voltage applied directly to the CPU cores.

T
The_Redstreak
Member
56
06-30-2016, 08:56 AM
#8
Maybe the 1.7V Vcore from OCCT is what some others might call Vccin.
But now that Vcore (or VID, slight different meaning, but in this context can be the same) is 1.2V, we can be sure that it is in a safe value.
Now, there's nothing left to worry.
I asked you to compress a file because Haswell will jump to lower voltages when idle (unless every power saving feature and C state is disabled), and will only yse the real Vcore when under load, so it doesn't really make sense to check voltages when idling.
But now, problem solved. You can go back to overclocking, if that was your original objective. Here are some guidelines that you could use as reference later:
I strongly recommend carefully reading this guide:
http://www.overclock.net/t/1411077/haswe...statistics
As safe voltages for a stable overclock to set once and use everyday, Tom's community usually recommends 1.3V CPU Vcore as a maximum, although that depends also on your temperatures.
Try to keep your chip below 80ºC. What is your cooler?
As an average,
which may or may not apply to your particular cpu
, you can expect aroubd 4.5GHz with 1.25-1.30V CPU Vcore. This is only a guideline.
I just gave you a lot of information in only 1 post, sorry. It's not meant for you to take it all in at onxe, but to use as reference as you advance with each step.
T
The_Redstreak
06-30-2016, 08:56 AM #8

Maybe the 1.7V Vcore from OCCT is what some others might call Vccin.
But now that Vcore (or VID, slight different meaning, but in this context can be the same) is 1.2V, we can be sure that it is in a safe value.
Now, there's nothing left to worry.
I asked you to compress a file because Haswell will jump to lower voltages when idle (unless every power saving feature and C state is disabled), and will only yse the real Vcore when under load, so it doesn't really make sense to check voltages when idling.
But now, problem solved. You can go back to overclocking, if that was your original objective. Here are some guidelines that you could use as reference later:
I strongly recommend carefully reading this guide:
http://www.overclock.net/t/1411077/haswe...statistics
As safe voltages for a stable overclock to set once and use everyday, Tom's community usually recommends 1.3V CPU Vcore as a maximum, although that depends also on your temperatures.
Try to keep your chip below 80ºC. What is your cooler?
As an average,
which may or may not apply to your particular cpu
, you can expect aroubd 4.5GHz with 1.25-1.30V CPU Vcore. This is only a guideline.
I just gave you a lot of information in only 1 post, sorry. It's not meant for you to take it all in at onxe, but to use as reference as you advance with each step.

P
PugBoss
Member
92
07-05-2016, 10:37 AM
#9
This occurred when I switched to a different motherboard. One reported the VCCIN, which is the voltage provided to the CPU, while the Vcore was lower at 1.1-1.2 during operation. My regular motherboard consistently shows Vcore around 1.1-1.2.
P
PugBoss
07-05-2016, 10:37 AM #9

This occurred when I switched to a different motherboard. One reported the VCCIN, which is the voltage provided to the CPU, while the Vcore was lower at 1.1-1.2 during operation. My regular motherboard consistently shows Vcore around 1.1-1.2.

I
IkBenHetBram
Senior Member
735
07-07-2016, 04:06 AM
#10
anbello262 :
Maybe the 1.7V Vcore from OCCT is what some others might call Vccin.
But now that Vcore (or VID, slight different meaning, but in this context can be the same) is 1.2V, we can be sure that it is in a safe value.
Now, there's nothing left to worry.
I asked you to compress a file because Haswell will jump to lower voltages when idle (unless every power saving feature and C state is disabled), and will only yse the real Vcore when under load, so it doesn't really make sense to check voltages when idling.
But now, problem solved. You can go back to overclocking, if that was your original objective. Here are some guidelines that you could use as reference later:
I strongly recommend carefully reading this guide:
http://www.overclock.net/t/1411077/haswe...statistics
As safe voltages for a stable overclock to set once and use everyday, Tom's community usually recommends 1.3V CPU Vcore as a maximum, although that depends also on your temperatures.
Try to keep your chip below 80ºC. What is your cooler?
As an average,
which may or may not apply to your particular cpu
, you can expect aroubd 4.5GHz with 1.25-1.30V CPU Vcore. This is only a guideline.
I just gave you a lot of information in only 1 post, sorry. It's not meant for you to take it all in at onxe, but to use as reference as you advance with each step.
Thanks for your help. I will read that guide carefully. I have the intel e97378 which I'm pretty sure is just the stock cooler. I'm hoping to still be able to overclock by a moderate amount but I'll keep a close eye on the temperature.
I
IkBenHetBram
07-07-2016, 04:06 AM #10

anbello262 :
Maybe the 1.7V Vcore from OCCT is what some others might call Vccin.
But now that Vcore (or VID, slight different meaning, but in this context can be the same) is 1.2V, we can be sure that it is in a safe value.
Now, there's nothing left to worry.
I asked you to compress a file because Haswell will jump to lower voltages when idle (unless every power saving feature and C state is disabled), and will only yse the real Vcore when under load, so it doesn't really make sense to check voltages when idling.
But now, problem solved. You can go back to overclocking, if that was your original objective. Here are some guidelines that you could use as reference later:
I strongly recommend carefully reading this guide:
http://www.overclock.net/t/1411077/haswe...statistics
As safe voltages for a stable overclock to set once and use everyday, Tom's community usually recommends 1.3V CPU Vcore as a maximum, although that depends also on your temperatures.
Try to keep your chip below 80ºC. What is your cooler?
As an average,
which may or may not apply to your particular cpu
, you can expect aroubd 4.5GHz with 1.25-1.30V CPU Vcore. This is only a guideline.
I just gave you a lot of information in only 1 post, sorry. It's not meant for you to take it all in at onxe, but to use as reference as you advance with each step.
Thanks for your help. I will read that guide carefully. I have the intel e97378 which I'm pretty sure is just the stock cooler. I'm hoping to still be able to overclock by a moderate amount but I'll keep a close eye on the temperature.

Pages (2): 1 2 Next