cpu vcore is extremely low (~0.621)

[cwalker457]

I recently built a computer after saving up for about 6 months and I thought I would dive into overclocking.

 

My CPU is the Ryzen 7 1700 

Mobo is Asus Rog Strix x370-f gaming

 

When I went to overclock, I set a D.O.C.P that set my APU at 102.2 and my RAM at 1.35v and the ram at 2933 mhz.

 

I then set my cpu multiplier at 36 and my voltage at 1.2250 which I ran on prime 95 for about 3 hrs, no errors so far.

 

However, when I look at HW Monitor and CPU-Z my vcore is a mere ~0.6v at max load, my VID is around me set 1.225v, and the VDD (Node 0) says that my max was 3.15 volts!

 

I have no clue what is happening and how my voltage is either really high, or really low. I have updated all my drivers and the BIOS but still, no avail. 

Additionally, in the bios, it never seems to show the voltage that I actually set (1.225) it always shows a little more.

 

Any help would be greatly appreciated because I do not want to destroy my computer and I want to get the most longevity as possible. Thanks!

 

Here are some screenshots:

 

HWMonitor P1 and P2:

https://gyazo.com/216b4b851a09833dee06f530834a712a

https://gyazo.com/c9f812d543f70442da2e182dda236454

 

CPU-Z:

https://gyazo.com/c9f812d543f70442da2e182dda236454

 

Ryzen Master:

https://gyazo.com/795daf2cb2dd8dcc91ea7ee2561cabe3

[TrigrH]

Can I see CPU-Z please.

[Nah Xirok]

Its just a bug with CPU-Z and some motherboards.  It reads the voltage as half of what it is.  I have a 1700+ and Crosshair VI extreme and it always reads it as half of what I set it to. I've found Ryzen Master to be the most reliable & accurate for Ryzen vcore.  If it was less than 1 volt you'd have severe throttling or it just plain wouldn't boot.  If you were getting 3v or more, you'd either live on pluto or you'd be putting out a fire.  So I wouldn't take hwmonitor or CPU-Z too seriously although you might want to make sure you have the latest version of both. But Ryzen Master (on the C tab at the bottom) should give you the right numbers.

That said, its never going to read 'exactly' what you set.  Differences in quality of VRMs, quality of the CPU, and whether load line calibration is used or not can all affect what number you actually see.