F5F Stay Refreshed Hardware Desktop The high-end Ryzen 3600 uses a 1.8V power supply voltage.

The high-end Ryzen 3600 uses a 1.8V power supply voltage.

The high-end Ryzen 3600 uses a 1.8V power supply voltage.

T
tonnmode
Member
50
07-11-2019, 07:05 PM
#1
Hello. I set up a new setup using an Asus X570-P, a Ryzen 3600 and a DeepCool Gammaxx GTE v2. I kept my UEFI on its standard configuration and during stress tests the voltage usually reached between 1.35v and 1.39v, which seems quite high, particularly given the stock level of 1.10v. Could this be due to the turbo boost settings? Might my motherboard have an overclocking option enabled by default? Is this voltage actually typical for the CPU to operate at? Most of my knowledge on this topic comes from older guides like Lynnfield, Sandy Bridge and Ivy Bridge Intel releases.
T
tonnmode
07-11-2019, 07:05 PM #1

Hello. I set up a new setup using an Asus X570-P, a Ryzen 3600 and a DeepCool Gammaxx GTE v2. I kept my UEFI on its standard configuration and during stress tests the voltage usually reached between 1.35v and 1.39v, which seems quite high, particularly given the stock level of 1.10v. Could this be due to the turbo boost settings? Might my motherboard have an overclocking option enabled by default? Is this voltage actually typical for the CPU to operate at? Most of my knowledge on this topic comes from older guides like Lynnfield, Sandy Bridge and Ivy Bridge Intel releases.

N
nuclernoah101
Member
120
07-13-2019, 05:46 PM
#2
I focused on stress testing various systems. The software I'm using for monitoring is [insert software name]. Did you mention the VID value—was it intended to be a specific setting?
N
nuclernoah101
07-13-2019, 05:46 PM #2

I focused on stress testing various systems. The software I'm using for monitoring is [insert software name]. Did you mention the VID value—was it intended to be a specific setting?

M
Mario_Logan
Member
65
07-13-2019, 07:14 PM
#3
Running AIDA64 with CPU, FPU, cache and memory stress tests active. 2. I'm verifying AIDA64 results and Ryzen Master data. Also noticed in my UEFI the CPU voltage is near 1.35v. 3. In AIDA64 I see "CPU Core" voltage, while in UEFI it's labeled "CPU Voltage"; I'm not sure what VID stands for.
M
Mario_Logan
07-13-2019, 07:14 PM #3

Running AIDA64 with CPU, FPU, cache and memory stress tests active. 2. I'm verifying AIDA64 results and Ryzen Master data. Also noticed in my UEFI the CPU voltage is near 1.35v. 3. In AIDA64 I see "CPU Core" voltage, while in UEFI it's labeled "CPU Voltage"; I'm not sure what VID stands for.

D
DDBanister
Member
60
07-19-2019, 04:28 PM
#4
Typically, the auto voltage is structured based on how PBO functions. If you're concerned, you can choose a fixed voltage, but you'll avoid entering C states and idle voltages. In my opinion, it's better to keep it on auto.
D
DDBanister
07-19-2019, 04:28 PM #4

Typically, the auto voltage is structured based on how PBO functions. If you're concerned, you can choose a fixed voltage, but you'll avoid entering C states and idle voltages. In my opinion, it's better to keep it on auto.

U
Ultima_cj0628
Junior Member
9
07-20-2019, 02:54 AM
#5
It can reach up to 1.47V during minimal activity, which may increase readings when idle. VID is the frequency the CPU requests from the board based on workload, but it doesn’t consider voltage droop. Under heavy load, voltage will drop noticeably below VID. Hwinfo64 in sensor mode displays VID and core voltage (SVI2, on-chip sensing). You might reduce the voltage slightly using negative offsets, but always test each run—excessive adjustments can hurt performance even if frequency stays the same.
U
Ultima_cj0628
07-20-2019, 02:54 AM #5

It can reach up to 1.47V during minimal activity, which may increase readings when idle. VID is the frequency the CPU requests from the board based on workload, but it doesn’t consider voltage droop. Under heavy load, voltage will drop noticeably below VID. Hwinfo64 in sensor mode displays VID and core voltage (SVI2, on-chip sensing). You might reduce the voltage slightly using negative offsets, but always test each run—excessive adjustments can hurt performance even if frequency stays the same.