z370 Taichi/8700k OC voltages too high |
Post Reply | Page <123> |
Author | ||
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
|
First, VID is NOT the actual VCore. They are two different things. Core Temp labels the reading as the VID. VID is the easiest thing to read from an Intel CPU, since it comes from an internal register whose ID/location is known and easily read. VID is the voltage requested by the processor from Intel's built in VID table, for the core speed, CPU load, etc. Note there is a VID for every core, but whichever core requests the highest VID voltage, that is what will be provided to the processor. VID voltage is usually if not always more than the actual VCore required by the cores in a CPU. Intel over compensates the VID voltage values to insure the processor will always operate. The actual VCore voltage being used by the board is normally always lower than the actual VCore voltage being provided to the CPU. If your board has CPU VRM voltage sensor outputs, only shown by a few programs (HWiNFO64 will show CPU VRM output voltage if the board provides it), you'll see that voltage is below that of the VID, and very close to the actual VCore. Reading the actual VCore provided to a CPU takes specific programming for EVERY make of board, and possibly different between different models of the same make of board. That's why you see just the VID being displayed by some programs, it's easy to do. Facts about monitoring programs: Is the VID or "VCore" reading a continuous, analog meter type of reading? No, it is a sample reading done at specific programmed intervals, such as once every two, three, or five seconds. Each monitoring program has its own VID/VCore sample interval programmed into it. HWiNFO64's sample interval can be set by the user, the default is 2,000ms/2 seconds. When running multiple monitoring programs at the same time, do they have their sample intervals synchronized? How could they be synchronized, when they can have different intervals between samples? Next, if two monitoring programs try to read a sample at the same time, for some reason that results in one or both programs receiving bad data. That is just a reality of the sensor chips used in mother boards to provide readings like VCore. So monitoring programs that are programmed correctly use a read instruction that waits its turn to get the data. So we are assured that the sample read by each program is not read at exactly the same time. Adding these three things together, results in the differences between readings of multiple monitoring programs. Include a VID reading instead of the true VCore, we have another difference. Now consider the CPU itself. Is it using the same VCore constantly? It may or may not. If any of the CPU performance and/or power saving options are enabled (Turbo, Power Saving Mode, SpeedStep, C1E, C States, etc), and the Windows Power Plan is not set to High Performance, the VCore will change constantly, except when under a constant load. In this scenario, the VCore will change thousands of times a second. Multiple monitoring programs each reading this dynamic VCore at different times will result in different readings. This does not take into consideration the CPU Cache Ratio, Long and Short Term Power and Current option settings, etc, which all affect the VCore. How do we get a static (or as close as possible), non-changing VCore? Only by using Fixed Voltage as the VCore mode, none of the CPU power saving features enabled, Turbo not active by an all core OC at or beyond the max rated Turbo frequency, LLC set to the highest level, and the Long and Short Term current and power setting set high enough, etc. With the Windows Power Plan set to High Performance, of course, and a high quality PSU whose +12V rail will not droop much under high loads. Which is correct? They all probably are, for the reasons I just explained. When each program read the VID or VCore, that's what it was when it took its sample, each at a slightly different time in human terms, but in CPU terms, very far apart. Core Temp read the VID, the other two the actual VCore, each in turn. We'd like to believe that a VCore reading is simple just like the speedometer reading in our cars. But it is for more complicated than that. By the time we see it on the program's display, it has changed many, many times, unless we have it locked down statically. |
||
delatroy
Newbie Joined: 15 Nov 2017 Status: Offline Points: 2 |
Post Options
Thanks(0)
|
|
Many thanks for your detailed reply - very informative. I'm getting the hang of it more and I'm going by CPUz and A-Tuning for the load numbers.
Provisionally I'm at 50 at 1.275v bios / 1.280v CPUz load LLC1 51 1.380v bios / 1.396v CPUz load LLC1 Is there any way on the Taichi to measure VRM temperatures? |
||
amd7674
Newbie Joined: 23 Nov 2017 Location: Canada Status: Offline Points: 11 |
Post Options
Thanks(0)
|
|
Dikonou
Newbie Joined: 24 Jan 2018 Status: Offline Points: 14 |
Post Options
Thanks(0)
|
|
Have a similar issue here.....
HWinfo64 shows vcore 1.344 max and core VID 1.439 but on CPU-Z while stress testing with cinebench15 on CPU test vcore never went above 1.216! no OC.... but i run with Cstates off and the core multiplier enabled... 4.7Ghz Which one should i take for correct?
Edited by Dikonou - 17 Feb 2018 at 4:10am |
||
TAMW
Newbie Joined: 07 Nov 2016 Location: Norway Status: Offline Points: 56 |
Post Options
Thanks(0)
|
|
SkyCorrigan
Newbie Joined: 10 Mar 2018 Location: Chicago Status: Offline Points: 2 |
Post Options
Thanks(0)
|
|
SkyCorrigan
Newbie Joined: 10 Mar 2018 Location: Chicago Status: Offline Points: 2 |
Post Options
Thanks(0)
|
|
Anth_iv
Newbie Joined: 10 Aug 2018 Status: Offline Points: 33 |
Post Options
Thanks(0)
|
|
Should I start thinking it?™s my motherboard and not my CPU causing me to not hit 5ghz?
8700k delidded Taichi of course H115i pro Tridentz 3000/15 I try 1.37 V in bios and 50 multiplier. Running x264 for about 10 seconds max and get BSOD. Temps during that short time are about 74C I should be able to do better than this. :(. |
||
chinmoypborah
Newbie Joined: 28 Oct 2018 Location: India Status: Offline Points: 1 |
Post Options
Thanks(0)
|
|
Thanks?
Edited by Xaltar - 04 Dec 2018 at 11:45pm |
||
chinmoypborah
|
||
Globespy
Newbie Joined: 28 Sep 2018 Status: Offline Points: 65 |
Post Options
Thanks(0)
|
|
Why do you post this trash here Edited by Xaltar - 04 Dec 2018 at 11:46pm |
||
Post Reply | Page <123> |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |