Question Ryzen 5 3600 high voltage ?

rokopro1

Distinguished
Apr 25, 2013
5
0
18,510
Hello guys i recently built this pc
Ryzen 5 3600
Asrock B550M Pro4
2x8 DDR4 3200mhz Ripjaws V
RX 5600 XT
I'm using ryzen balanced power plan.
My bios is on default settings.
While idle cpu drops voltage very low sometimes even under half a volt.
While in game it stays on 1.4.
Temps idle are 34 Celsius and in game never go above 60.
Frequency in game is around 4200 mhz but mostly 4175.
What worries me ive seen online that voltage should usually be 1.4 on idle and go down to 1.2 while under loads like gaming.
So if you can shine some light on this for me that would be great since im very new to ryzens.
Thanks ALOT!
 
Where, exactly, are you seeing that it is reporting 1.4v at idle while only being at 1.2v under load? While 1.4v is within the supposed safe range it would be unusual for it to decrease in voltage under a load compared to while at idle, and I suspect you are looking at the wrong sensor values. What are you using to monitor this and exactly which value, by name, are you referencing?

What is your currently installed motherboard BIOS version?
 
Where, exactly, are you seeing that it is reporting 1.4v at idle while only being at 1.2v under load? While 1.4v is within the supposed safe range it would be unusual for it to decrease in voltage under a load compared to while at idle, and I suspect you are looking at the wrong sensor values. What are you using to monitor this and exactly which value, by name, are you referencing?

What is your currently installed motherboard BIOS version?
Thank you for reply.Program im using is HWmonitor and value which im looking at is CPU VCORE.
BIOS version is P2.30
So you think this is all within normal operation and voltage isnt high?
 
Last edited:
I'd update your BIOS to version 3.2 for starters. That alone might have an impact on the system controlled voltages as there are about four other updates between that one and your current version. No need to do each of them, just update to the latest which is 3.2.

Second thing I'd do is ditch HWmonitor. Here's my standard spiel on that.

Monitoring software

HWmonitor, Open hardware monitor, Realtemp, Speccy, Speedfan, Windows utilities, CPU-Z, NZXT CAM and most of the bundled motherboard utilities are often not the best choice as they are not always accurate. Some are actually grossly inaccurate, especially with certain chipsets or specific sensors that for whatever reason they tend to not like or work well with. I've found HWinfo or CoreTemp to be the MOST accurate with the broadest range of chipsets and sensors. They are also almost religiously kept up to date.

CoreTemp is great for just CPU thermals including core temps or distance to TJmax on older AMD platforms.

HWinfo is great for pretty much EVERYTHING, including CPU thermals, core loads, core temps, package temps, GPU sensors, HDD and SSD sensors, motherboard chipset and VRM sensor, all of it. When starting HWinfo after installation, always check the box next to "sensors only" and de-select the box next to "summary".


Run HWinfo and look at system voltages and other sensor readings.

Monitoring temperatures, core speeds, voltages, clock ratios and other reported sensor data can often help to pick out an issue right off the bat. HWinfo is a good way to get that data and in my experience tends to be more accurate than some of the other utilities available. CPU-Z, GPU-Z and Core Temp all have their uses but HWinfo tends to have it all laid out in a more convenient fashion so you can usually see what one sensor is reporting while looking at another instead of having to flip through various tabs that have specific groupings, plus, it is extremely rare for HWinfo to not report the correct sensor values under the correct sensor listings, or misreport other information. Utilities like HWmonitor, Openhardware monitor and Speccy, tend to COMMONLY misreport sensor data, or not report it at all.

After installation, run the utility and when asked, choose "sensors only". IF you get a message about system stability you can simply ignore it and continue on WITH the option to monitor the sensor OR you can disable the monitoring for THAT sensor and continue on based on the option it gives you at the time. If you choose to continue on, WITH monitoring of that sensor, which is what I normally do, and there IS instability, that's fine. It's not going to hurt anything. Simply restart the HWinfo program (Or reboot if necessary and THEN restart the HWinfo program) and THEN choose to disable that sensor, and continue on with sensors only monitoring.

The other window options have some use but in most cases everything you need will be located in the sensors window. If you're taking screenshots to post for troubleshooting, it will most likely require taking three screenshots and scrolling down the sensors window between screenshots in order to capture them all.

It is most helpful if you can take a series of HWinfo screenshots at idle, after a cold boot to the desktop. Open HWinfo and wait for all of the Windows startup processes to complete. Usually about four or five minutes should be plenty. Take screenshots of all the HWinfo sensors.

Next, run something demanding like Prime95 (With AVX and AVX2 disabled) or Heaven benchmark. Take another set of screenshots while either of those is running so we can see what the hardware is doing while under a load.


*Download HWinfo




For temperature monitoring only, I feel Core Temp is the most accurate and also offers a quick visual reference for core speed, load and CPU voltage:


*Download Core Temp




Ryzen master for Zen or newer AMD CPUs, or Overdrive for older Pre-Ryzen platforms (AM3/AM3+/FM2/FM2+)

For monitoring on AMD Ryzen and Threadripper platforms including Zen or newer architectures, it is recommended that you use Ryzen master if for no other reason than because any updates or changes to monitoring requirements are more likely to be implemented sooner, and properly, than with other monitoring utilities. Core Temp and HWinfo are still good, with this platform, but when changes to CPU micro code or other BIOS modifications occur, or there are driver or power plan changes, it sometimes takes a while before those get implemented by 3rd party utilities, while Ryzen master, being a direct AMD product, generally gets updated immediately. Since it is also specific to the hardware in question, it can be more accurately and specifically developed without any requirement for inclusion of other architectures which won't be compatible in any case. You wouldn't use a hammer to drive a wood screw in (At least I hope not) and this is very much the same, being the right tool for the job at hand.


Also, posting screenshots, when requested, is helpful so WE can see what is going on as well and you can learn how to do that here:

 
I have taken these screenshots after playing bf1 for 1 hour.
Zis7TM8.png
aJ8iXuH.png
 
First off, you realize your memory is running at 2400mhz, not 3200mhz, right? With timings of 17-17-17-39 I can just about promise that is not a Ryzen friendly memory kit, which is probably why it's defaulting to the 2400mhz speed unless you do not have the XMP configuration enabled in the BIOS.

As for the vcore, the likely reason you are seeing this is due to vdroop. Based on everything I've read on Ryzen platforms, 1.4v is within normal spec and so long as you are running at the stock configuration and are not having any issues, it should be fine. There definitely doesn't seem to be any thermal problems, so I would say it's normal for that board and configuration.
 
First off, you realize your memory is running at 2400mhz, not 3200mhz, right? With timings of 17-17-17-39 I can just about promise that is not a Ryzen friendly memory kit, which is probably why it's defaulting to the 2400mhz speed unless you do not have the XMP configuration enabled in the BIOS.

As for the vcore, the likely reason you are seeing this is due to vdroop. Based on everything I've read on Ryzen platforms, 1.4v is within normal spec and so long as you are running at the stock configuration and are not having any issues, it should be fine. There definitely doesn't seem to be any thermal problems, so I would say it's normal for that board and configuration.
Thanks for that info.For some reason i can run my 3200 mhz ram only on 3000 mhz.If i select the 3200 mhz profile it reverts back to 2400 so theres that.Also i undervolted with offset -0,1V and now it maxes at 1.3 so its awesome now.
 
There is nothing worrisome about having that show as a maximum for voltage. Especially in regard to the temperatures.

I do find it odd where you say that the voltage is at 1.4 for idle and then 1.2 for gaming, but in another spot you mention it being 1.4 for gaming? (in regard to the "reading online" concern) The voltage should NOT be dropping for a heavier load. In my own opinion, unless that was a typo, this would be an indication of VRM that cannot deliver the proper amperage. I cannot see that trend in the HWI snippit, so am of the assumption that the voltages were reversed as a "typo"?
 
Voltages CAN drop when under a load, that's the whole point of load line calibration settings, which is to help resolve vdroop, which is, by definition, the core voltage dropping when under heavy sustained loads. Under normal circumstances it shouldn't be a problem, while overclocking it can be, because it happens to a much more significant degree. But it generally doesn't happen with a stock configuration, to the degree seen above. Even so, everything seems within spec regardless of the behavior and so long as there are no recognizable issues occurring, I wouldn't worry about it.
 
  • Like
Reactions: rokopro1
There is nothing worrisome about having that show as a maximum for voltage. Especially in regard to the temperatures.

I do find it odd where you say that the voltage is at 1.4 for idle and then 1.2 for gaming, but in another spot you mention it being 1.4 for gaming? (in regard to the "reading online" concern) The voltage should NOT be dropping for a heavier load. In my own opinion, unless that was a typo, this would be an indication of VRM that cannot deliver the proper amperage. I cannot see that trend in the HWI snippit, so am of the assumption that the voltages were reversed as a "typo"?
i saw that on some forum one guy said that 1.4 on idle is fine and that it should drop down to around 1.2 while under full load, that is what i read so i asked.In my case it was 1.4 under load and on idle it would go down all the way to 0.5V.Now i undervolted offset and it maxes at 1.3 on load so im satisfied now.
 
I went back and RE-read your original post, and sure enough I must have completely mistook what you posted because I could have sworn you said it was 1.4 when idle and dropped down when under a load, which is totally backwards from standard behavior aside from the aforementioned vdroop.

If you are at 1.4v under a moderate to full load and it's dropping down very low on any core that isn't being used, or all of them if it's idle, then that is totally normal behavior for pretty much ANY system so long as the standard power saving features like Cool N Quiet, Intel speed step/shift, etc. are enabled and so long as your advanced power option setting for processor power management is not set to 100/100 for min/max and instead is more like min 0-8% and max 100%. So I'd say you are absolutely in step with standard behavior.