F5F Stay Refreshed Power Users Overclocking Overclocking Ryzen 7 1700x Question

Overclocking Ryzen 7 1700x Question

Overclocking Ryzen 7 1700x Question

Pages (2): Previous 1 2
S
SpookyJay
Member
203
08-30-2018, 07:31 AM
#11
Core voltage can be hard to locate on certain displays, but using HWINFO64 and the SVI2 TFN sensor provides the precise value, which is really helpful.
S
SpookyJay
08-30-2018, 07:31 AM #11

Core voltage can be hard to locate on certain displays, but using HWINFO64 and the SVI2 TFN sensor provides the precise value, which is really helpful.

V
144
08-30-2018, 08:47 AM
#12
HWinfo provides the best data, but the key is to examine the average voltage during normal but extended usage. Higher voltages tend to be brief and don't significantly affect temperatures or cause lasting harm.
V
voetbalboy1998
08-30-2018, 08:47 AM #12

HWinfo provides the best data, but the key is to examine the average voltage during normal but extended usage. Higher voltages tend to be brief and don't significantly affect temperatures or cause lasting harm.

_
_Mishie_
Member
202
08-30-2018, 09:17 AM
#13
That's the method I've been relying on, but I only fully relied on it after performing the DVM measurements at the socket for my board.
However, I needed that confirmation first.
During a stress test where the CPU is heavily loaded, the SVI2 TFN on my 3.95Gig 1700 shows a very reasonable reading.
A VCore reading of 1.472 with a solid line is normal, but an SVI2 reading between 1.36 and 1.38 indicates it's within a safe range for the CPU.
But without any load on the CPU, the SVI2 rises to 1.419–1.425… while the VCore remains in the 300–500mV range!
I had to inspect it at the base of the socket using a DVM, where it consistently reads between 300 and 500mV during idle.
So even if the CPU claims it's getting 1.425, it's actually only receiving a small portion of that at idle—just the VRM controller's output.
The SVI2 TFN isn't a direct voltage measurement; it's an estimated value the CPU assumes.
It appears to be highly inaccurate when the processor is idle, which is what I observed.
I'm not entirely sure why this happens, but that seems to be the pattern I see.
_
_Mishie_
08-30-2018, 09:17 AM #13

That's the method I've been relying on, but I only fully relied on it after performing the DVM measurements at the socket for my board.
However, I needed that confirmation first.
During a stress test where the CPU is heavily loaded, the SVI2 TFN on my 3.95Gig 1700 shows a very reasonable reading.
A VCore reading of 1.472 with a solid line is normal, but an SVI2 reading between 1.36 and 1.38 indicates it's within a safe range for the CPU.
But without any load on the CPU, the SVI2 rises to 1.419–1.425… while the VCore remains in the 300–500mV range!
I had to inspect it at the base of the socket using a DVM, where it consistently reads between 300 and 500mV during idle.
So even if the CPU claims it's getting 1.425, it's actually only receiving a small portion of that at idle—just the VRM controller's output.
The SVI2 TFN isn't a direct voltage measurement; it's an estimated value the CPU assumes.
It appears to be highly inaccurate when the processor is idle, which is what I observed.
I'm not entirely sure why this happens, but that seems to be the pattern I see.

_
_MarshBomb_
Junior Member
22
09-02-2018, 03:58 AM
#14
Are you certain you're viewing Vcore, not VID or another file?
_
_MarshBomb_
09-02-2018, 03:58 AM #14

Are you certain you're viewing Vcore, not VID or another file?

K
kassi123
Member
137
09-02-2018, 05:16 AM
#15
I'm confident it's VCore—it appears as a reading in the HWInfo part for the Nuvoton monitoring chip. It matches DVM readings I obtain at the VRM output (the inductor leads are clearly visible) and consistently across all operating conditions: idle, full load, and varying loads. Comparing fluctuating loads is challenging because of the inherent delay in the HWInfo data.

The VDC is shown in HWInfo under 'CPU [#0]: AMD Ryzen....' and appears separately for each core.
K
kassi123
09-02-2018, 05:16 AM #15

I'm confident it's VCore—it appears as a reading in the HWInfo part for the Nuvoton monitoring chip. It matches DVM readings I obtain at the VRM output (the inductor leads are clearly visible) and consistently across all operating conditions: idle, full load, and varying loads. Comparing fluctuating loads is challenging because of the inherent delay in the HWInfo data.

The VDC is shown in HWInfo under 'CPU [#0]: AMD Ryzen....' and appears separately for each core.

T
ThotsRus
Member
168
09-03-2018, 05:15 PM
#16
I messed up and now it might ruin my chances of getting a 4GHz OC.
T
ThotsRus
09-03-2018, 05:15 PM #16

I messed up and now it might ruin my chances of getting a 4GHz OC.

P
Palmart
Member
58
09-03-2018, 08:26 PM
#17
The temperature is limited to 95C
You will be okay.
P
Palmart
09-03-2018, 08:26 PM #17

The temperature is limited to 95C
You will be okay.

J
JamesHond7
Posting Freak
838
09-11-2018, 07:16 AM
#18
I think the main constraints come from the silicon quality in your 1700x CPU. Plus, your ability to handle higher voltages—perhaps between 1.40 and 1.425 during testing—might be a factor.
J
JamesHond7
09-11-2018, 07:16 AM #18

I think the main constraints come from the silicon quality in your 1700x CPU. Plus, your ability to handle higher voltages—perhaps between 1.40 and 1.425 during testing—might be a factor.

S
Sentio_Cege
Member
246
09-13-2018, 08:53 AM
#19
I managed to reach 4.0ghz at 1.398v, but it occasionally jumps to 1.404. On my H100i the temperatures stay below 60°C, which should be fine for regular use.
S
Sentio_Cege
09-13-2018, 08:53 AM #19

I managed to reach 4.0ghz at 1.398v, but it occasionally jumps to 1.404. On my H100i the temperatures stay below 60°C, which should be fine for regular use.

G
Goljat12
Member
213
09-19-2018, 09:50 PM
#20
Looks good to me.
G
Goljat12
09-19-2018, 09:50 PM #20

Looks good to me.

Pages (2): Previous 1 2