Vcore vs VR VOUT (Vcore)?

[SmartOne_2000]

What is the difference between these two voltage readings:

1. Vcore (CPU core voltage measured by external sensor)
2. VR Vout (Vcore) defined as "Voltage measured at the output side of the VR. This is the voltage supplied by this VR to the respective component rail (i.e.Vcore, VDIMM, VCCSA, etc"

They are measured by different sensors but their readings are not identical. I need to know the true voltage sent to my 14900K P/E cores to prevent the over voltage Intel Vmin shift bug of no greater than 1.55v.

The VR Vout (Core) has voltages greater then 1.55v (1.565v) but the Vcore does not after stress testing (1.527v).

 

[Martin]

Those voltages are usually measured on opposite sides and the biggest difference is Vdroop.

 

[SmartOne_2000]

Thanks!
So Vcore alone is the actual voltage sent to the cores, regardless of what they request, as indicated in Core VIDs numbers? If not, what is the actual voltage received by the P/E cores?
Also, shouldn't each P/E core have its own Vcore value, as they have individual Core VIDs values?

 

[Martin]

VID is something else - that's the voltage requested by core but usually not what is finally supplied by VR.
VR Vout (Vcore) is voltage supplied by VR measured at the VR side.
Vcore is usually measured inside CPU or on mainboard depending on board/CPU design.

 

[SmartOne_2000]

So, shouldn't each internal P/E core have its own Vcore value, 24 Vcores values in all? I can't seem to see these individual values in the program.

 

[Martin]

No, the entire core (IA) domain is running at one/single voltage. Raptor Lake and earlier CPUs don't support per-core voltage.

 

[SmartOne_2000]

No, the entire core (IA) domain is running at one/single voltage. Raptor Lake and earlier CPUs don't support per-core voltage.

Thanks... so each core can submit its desired Vcore value, as shown in Core VIDs, but then all cores get one single voltage in return? This is really strange!

 

[Martin]

That's how current generations work.. but let's wait a couple of days, there might be some interesting news

 

[SmartOne_2000]

Is it possible to perform some basic math on the voltages or currents? For example, I want to perform VR Vout (Vcore) - Vcore to see how much Vdroop I may have and hence optimize it in bios. Can this be done?

 

[Martin]

Is it possible to perform some basic math on the voltages or currents? For example, I want to perform VR Vout (Vcore) - Vcore to see how much Vdroop I may have and hence optimize it in bios. Can this be done?

Sure, you can create your own sensor:

Thread 'Custom user sensors in HWiNFO'

Jul 31, 2019

HWiNFO since version 6.10 introduces a new feature - ability to display custom user sensors in the sensors window.
This feature allows users with basic programming skills to show any sensor values. This might be useful in case of custom-made devices, or sensor values not implemented in HWiNFO by default (i.e. clock time).
The interface used to provide data to HWiNFO is Windows Registry. Users wishing to publish data into sensors will need to create a few specific keys and values in the registry.
Format of the required registry is following.

Main registry node for custom sensors must...

• Martin
• Replies: 90
• Forum: 3rd Party Extensions, Plug-ins, Gadgets

• 

 

[SmartOne_2000]

Sure, you can create your own sensor:

Thread 'Custom user sensors in HWiNFO'

Jul 31, 2019

HWiNFO since version 6.10 introduces a new feature - ability to display custom user sensors in the sensors window.
This feature allows users with basic programming skills to show any sensor values. This might be useful in case of custom-made devices, or sensor values not implemented in HWiNFO by default (i.e. clock time).
The interface used to provide data to HWiNFO is Windows Registry. Users wishing to publish data into sensors will need to create a few specific keys and values in the registry.
Format of the required registry is following.

Main registry node for custom sensors must...

• Martin
• Replies: 90
• Forum: 3rd Party Extensions, Plug-ins, Gadgets

• 

Wow, ok, Thank you very much!