Print Page | Close Window

vCores please [1700x/TaiChi]

Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=6185
Printed Date: 25 Jun 2024 at 11:35pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com


Topic: vCores please [1700x/TaiChi]
Posted By: VUMeter
Subject: vCores please [1700x/TaiChi]
Date Posted: 25 Sep 2017 at 10:37am
" rel="nofollow - Still in the 'side off / testing' phase.
I installed the latest Ryzen drivers 17.30, with the "Ryzen Balanced Power Plan" for Windows 10.

Whilst I haven't started getting all of the content software installed, the system doesn't feel sluggish - why would it 32GB RAM and 8x cores at 3.4GHz?

Anyway, I put the 'tweaked' plan on and HWinfo, Ryzen Master and anything that I could see all indicated maxed out cores.
Sure, OK, a screw up in the reporting perhaps.  It's not really going that quick, the temps aren't climbing, the fans are going nuts.
But importantly the voltages looked like they bouncing u to 1.45v on vCore.  

Under the regular stock balanced plan, vCore is reported in the 0.87v region - this is idle, browsers open, monitoring tools, nothing taxing.

Playing with the Power Saver plan, things look even nicer in terms of vCore bouncing to 0.84 but dropping to ~0.7.

Just what is going on here?

If anyone has a guide to keeping things stock and dropping voltages, I'd like to hunt for longevity and low temps as much as possible here.  I guess it's mostly follow the OC guides, omitting the chip-thrashing.


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">



Replies:
Posted By: parsec
Date Posted: 25 Sep 2017 at 12:54pm
Originally posted by VUMeter VUMeter wrote:

" rel="nofollow - Still in the 'side off / testing' phase.
I installed the latest Ryzen drivers 17.30, with the "Ryzen Balanced Power Plan" for Windows 10.

Whilst I haven't started getting all of the content software installed, the system doesn't feel sluggish - why would it 32GB RAM and 8x cores at 3.4GHz?

Anyway, I put the 'tweaked' plan on and HWinfo, Ryzen Master and anything that I could see all indicated maxed out cores.
Sure, OK, a screw up in the reporting perhaps.  It's not really going that quick, the temps aren't climbing, the fans are going nuts.
But importantly the voltages looked like they bouncing u to 1.45v on vCore.  

Under the regular stock balanced plan, vCore is reported in the 0.87v region - this is idle, browsers open, monitoring tools, nothing taxing.

Playing with the Power Saver plan, things look even nicer in terms of vCore bouncing to 0.84 but dropping to ~0.7.

Just what is going on here?

If anyone has a guide to keeping things stock and dropping voltages, I'd like to hunt for longevity and low temps as much as possible here.  I guess it's mostly follow the OC guides, omitting the chip-thrashing.


You're using the default UEFI/BIOS VCore settings, right? They are always set very high by design, on purpose.

Why? Simple, the VCore must be high enough to guarantee that any and all processors used with the board will complete POST, allow the user to get into the UEFI/BIOS interface, and run Windows without failing. Even if that VCore is much more than will really be needed by most if not all processors.

Again, why? Imagine a UEFI/BIOS whose default VCore was set too low for a processor to POST, and get into the UEFI interface. Meaning no way to adjust the VCore to a higher value. How could you work around that if the default VCore was to low to allow a processor to POST and run the UEFI? You can't, and the board would be worthless, unusable. To avoid that situation completely, the default VCore is set to a value high enough that it will never happen. It's a compromise biased towards guaranteed operation, rather than a refined operation.

Yes, the default VCore when one or more cores Turbo up to their maximum speed is ~1.45V, I see the same thing my different ASRock X370 board and a 1700X. At idle and with different Power Plan Processor State settings, the VCore is much lower. My VCore with C6 enabled will go down to 0.384V. My OC to 3.9GHz is stable with a VCore that slightly exceeds 1.350V occasionally. I have the VCore set to 1.350V for that speed.

Reduce your VCore by setting OC Mode to Manual. Don't change the base processor speed, and you won't be over clocking. Set your Vcore in a now revealed VCore option to ~1.3V for a start. You can also change the VCore mode now, using Offset Mode for example. Also the LLC option will be available. As long as the don't change the base processor/core speed, you'll stay with the stock clock.

Your board's UEFI layout will be different than mine, so other X370 Taichi users can provide more exact details, but you should be able to figure it out if you have any experience with configuring the VCore in a UEFI/BIOS.

The different Power Plans have different Minimum Processor State settings, that only allow the processor to reduce its clock speed by different amounts, or not at all. That is in the Advanced settings of a Power Plan.



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: datonyb
Date Posted: 26 Sep 2017 at 1:50am
why when you can have both Smile

at 'locked' 3.9 my vcore still drops to less than half a volt

at idle my temps are 23 degrees

amd and ryzen with some asrock jam filling

HAVING YOUR CAKE AND EATING IT !


-------------
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold


Posted By: VUMeter
Date Posted: 03 Oct 2017 at 7:13pm
Thanks for the info.  Sorry for perhaps being dense here.

Here is a screen grab of HWinfo readout.
Which vCore are we supposed to be looking at?  OpenHardwareMonitor, which I know cannot access the CPU Tdie, can only provide the vCore data at the bottom, off of the motherboard(?)

UEFI is all set to AUTO everything.

These results are just idling with Win10 x64 Creators power plan set to" PowerSaver" - "AMD Ryzen Balanced" gives me the willies seeing all the stats flat out.  I know what they say, but the temps do actually increase on that setting.

The reason for the 1.475v is because I had run Prime95 on 2 threads.  That caused the 3.9GHz on those two threads and thus the added voltage.  When all cores are maxed (16 threads) in Prime95 the vCores all sit at 1.2v or just a hair under.


Additionally, I set the UEFI vCore to 1.2v LL3 and SoC to 1.0v LL1 and everything was fine until I did a 2 thread test on Prime95, then the screen went black, but I couldn't get back to UEFI without holding the case power button.  I've a feeling I have found that my CPU won't run on that low voltage when boosting 2 threads.  Should that be surprising, probably not.
Annoyingly when I did set the vCore manually in EUFI it did not drop back down when the CPU wasn't being used, but rather stayed at that same voltage all of the time.

Again, I apologise that I am probably making you folks roll eyes here.  I'm having a tough time finding a concise and easy to follow guide on overclocking that I can apply to simply under volting.  It seems I can find different settings but there isn't so much explanation behind them or what to expect - eg. the vCore becoming static.
Admittedly, I did this on the old C2D system and the vCore as static, except for droop on load, hence LLC or whatever ASUS called it then.

Thanks as always.




-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: parsec
Date Posted: 03 Oct 2017 at 9:01pm
" rel="nofollow - So what VCore mode did you use when the VCore did not drop? Fixed or Offset? Sounds like Fixed, or using the Ryzen power plan. Both the VCore and power plan determine the VCore in Windows.

A VCore of 1.2V is too low for stress testing, as you know. If you're using you C2D CPU as a reference, don't, your Ryzen CPU is different. I suggested 1.35V for the VCore, but you didn't apparently didn't like that value. I suggested it because I have a 1700X.

As you have seen, the power plan used affects the VCore in Windows. The Ryzen so called Balanced plan sets the Minimum processor state to 90%, and will keep the VCore high at idle.

The reason the VCore is 1.475V is because the "UEFI is set to AUTO everything", as you said, while stress testing.

Use the "Vcore" reading in HWiNFO64 at the very bottom of your picture. The max is 1.424V, and the minimum is 0.432V. That is clearly with VCore on Auto, right?

It seems you tried a manual VCore of 1.2V, which failed running Prime95. Then you want back to Auto, resulting in over 1.4V.

Set the VCore to 1.35V, using Offset mode. Set the Offset voltage below Offset Mode to one step above Auto, by pressing the + key. Then run the stress test and see what you get. You may be able to reduce the VCore from 1.35V without an OC.



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: VUMeter
Date Posted: 03 Oct 2017 at 9:30pm
Originally posted by parsec parsec wrote:

" rel="nofollow - So what VCore mode did you use when the VCore did not drop? Fixed or Offset? Sounds like Fixed, or using the Ryzen power plan. Both the VCore and power plan determine the VCore in Windows.

A VCore of 1.2V is too low for stress testing, as you know. If you're using you C2D CPU as a reference, don't, your Ryzen CPU is different. I suggested 1.35V for the VCore, but you didn't apparently didn't like that value. I suggested it because I have a 1700X.

As you have seen, the power plan used affects the VCore in Windows. The Ryzen so called Balanced plan sets the Minimum processor state to 90%, and will keep the VCore high at idle.

The reason the VCore is 1.475V is because the "UEFI is set to AUTO everything", as you said, while stress testing.

Use the "Vcore" reading in HWiNFO64 at the very bottom of your picture. The max is 1.424V, and the minimum is 0.432V. That is clearly with VCore on Auto, right?

It seems you tried a manual VCore of 1.2V, which failed running Prime95. Then you want back to Auto, resulting in over 1.4V.

Set the VCore to 1.35V, using Offset mode. Set the Offset voltage below Offset Mode to one step above Auto, by pressing the + key. Then run the stress test and see what you get. You may be able to reduce the VCore from 1.35V without an OC.


Muchas Gracias!

Yup, I used fixed mode in UEFI.  I didn't quite understand how offset would work.  I'll go read a bit more about that and then poke around in that again.

I picked 1.2v based on what HWinfo was showing with all cores working.  I didn't really think about the high-boosted low-thread count work.  As such it totally failed at that point.
I wasn't using the C2D as a reference, no for a minute, entirely different silicon!

AMD Ryzen Balanced power plan = 90% min CPU state, and a high vCore.  Well that totally explains why it was a bit warmer than regular Balanced or Power Saver options!

vCore from the motherboard sensor, that's the one at the bottom of the image, and the one that shows in OpenHardwareMonitor, SpeedFan, CPU-Z and most other software.  HWInfo just gives a more comprehensive set of data as it taps into the CPU too.  But we look at the motherboard sensor for this, cool, that clears things up some.

Yes, vCore was on Auto in UEFI, it does a lot of jumping around.  Normally sits around 0.848v when doing something trivial like web browsing, but is constantly moving below this.

So far so good, your detective skills are very sharp.  You knew what I had done here from the data I have provided.

OK, so UEFI vCore to 1.35v using offset mode, not fixed (I think this might be a value I have found AMD recommend for long term use).
I'll follow your suggestions and report back.

I'll leave SoC on auto for now, as it's frankly not gone above 1.0v


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: VUMeter
Date Posted: 03 Oct 2017 at 9:55pm
Ah, now this looked more like I was expecting.
vCore (Motherboard) 0.384v - 1.456v
Idle vCore sits around 0.544 more often now.

The NH-U14s did it's job in keeping the Tdie below 60°C (~75-80% fan speed).

vCore was around the 1.2v again, slightly over, with all cores.
The high vCore is when taxing the two threads only.

The first + option after Auto on the Offset mode is 0.00625
This seems a strange number being that 1.35+0.00625 is 1.35625 not 1.456, so I wonder how I attempt math on that.

So now, I just reduce the main 1.35v to the next lowest, and so on, until things become unstable, then bump them back up a little.

Thanks, this does make some sense to me.


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: VUMeter
Date Posted: 04 Oct 2017 at 12:52am
After some fiddling around and numerous reboots (using the ASRock to UEFI tool), I've gotten somewhere.

I had to reset the power plans to default which has removed the Ryzen one.  All of the cores clocks were pegged in HWinfo and I just couldn't seem to find a way to make them not be.  OK, I appreciate this maybe a cosmetic issue, but it was also not really reflecting vCore movement.
Open cmd.exe as admin and type: powercfg.exe -restoredefaultschemes
That'll reset all of the power plans to defaults, including the drive sleeping and such.  "AMD Ryzen Balanced" will be gone.

I have left everything at auto again, NOT setting CPU to 3400 and Core to 1.35000.
I have just change the voltage mode to offset and hit - key 4 times.  It's now -0.02500.
The vCore doesn't go above 1.408v with LLC3, and sits mostly at 1.392v.  It's a matter of tweaking and this will come down more.
When hitting at 16 threads with Prime95 it's still at vCore 1.2v

Loweset measured vCore is 0.352v

So, thanks Parsec.  I'll poke about some more, I think I know what I am doing now.


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: datonyb
Date Posted: 04 Oct 2017 at 1:48am
or just use the same old sh1t i have used since bios 1.6

and kindly enough somehow asrock have assisted in bios 3.1 and now without even asking for it
i get vcore drop to sub 0.500volts when idle

and im fixed at 1.3 volts and 3.9ghz Smile
my bios setup take me mere minutes to do and never creeps above 1.3 volts

the taichi board has been a real smooth ride for me since start of april when i built it


-------------
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold


Posted By: VUMeter
Date Posted: 04 Oct 2017 at 4:22am
@datonyb,
So you are saying you have vCore in EUFI set to "Fixed", but it's dropping the voltage lower when not doing anything?  That's definitely not my experience with using the fixed setting - parsec seems to agree that fixed means just that, static, unchanging no matter what the load.  Obviously under heavy stress it could 'droop' which is where more aggressive LLC (lower numbers) comes in.

I notice your post here:
http://forum.asrock.com/forum_posts.asp?TID=6175&KW=&PID=36821&title=x370-taichi-oc-tips-for-begginer#36821
Originally posted by datonyb datonyb wrote:

ok so heres the full settings im running now 
in p states first and second section
9c
8
28
this is 3.9ghz and 1.3 volts
for some reason third box is set to
 7c
10
6c this translates apprently to 1550 mhz and .875 volts (i know i didnt set this)  Disapprove

i then on oc tweaker leave everything to auto apart from
cpu volts =overclock mode
cpu core = fixed
cpu volts = auto
llc level 2

soc = fixed
soc volts 1.100
llc = level 2

in advanced tab
cool and quiet off
c6 off
global c state is on auto

this is working like a dream for me on bios v3.1
max volts never above 1.3v
and auto downvolts down to silly low figures without issue on idle

But you are using P-state options, which is why I think the 1.3v is coming in.  The rest is all based off of that.
Without fiddling with that stuff yet, I think by default vCore is going to be higher when 2 threads are stressed.  I am playing with offset negative in hopes of reducing the rather high short-term vCore when single threaded tasks occur.

I've also got to work on seeing if that buried Fan control hysteresis will actually work.  So far it did nothing.  It's the one in the Advanced tab > AMD CBS > (?)


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: datonyb
Date Posted: 04 Oct 2017 at 4:56am
yes the vcore dropping itself ONLY started from bios 3.1 onwards (or maybe version3)
all bios before that the vcore stayed firmly at 1.3 volts

as ive said i cannot explain why, i am quite strict and practised at setting up my overclock
(i still follow techcity's you tube guide which was based on bios version 1.6)

all i can say is

it works well for me Smile

the down-volting wasnt required as has been proven enough even stuck at 1.3 volt the cpu's current drops off when on idle as does the temps so i never bothered with worrying about downvolting (i still get 23 degrees idle)
and yes i use ryzen power plan

im U.K. based as well
south london your welcome to pm me for a phone call if you want


-------------
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold


Posted By: VUMeter
Date Posted: 04 Oct 2017 at 6:02pm
Cor blimey, cheers cobber! ;)
OK, so it might be worth me just going to v3.10 if not for the potential for it to down volt itself, but to get the fan control options as well.

You raise an interesting point.  Volts aren't necessarily heat.  There is another component in the Ivy-Watts equation, current.  Current the actual amount of flow of electrons, rather than the steepness of the gradient and thus their speed.  Low current  = low heat with same volts.  Though low volts and low current mean lower temps (potentially) longer life etc.

Mine is sitting around 23°C Tdie on idle and 25.5°C T-socket on idle.  NH-U14s A14 is on 20% duty ~350rpm, Fractal GP-14s on medium setting (7v).

I'll take a gander at techcity and see what notes I can take.

Thanks for the offer to chat.  I may take you up on that if I get real stuck.  It'll be a message sent from the RPi crying "Help" when something won't turn on :D


Aside from these tweaks, every morning I put this machine on I have a great big smile on my face as it boots quicker than I can put a T-shirt on, and is taking everything I can throw at it, and quietly!


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: datonyb
Date Posted: 05 Oct 2017 at 1:41am
" rel="nofollow - bryans you tube taichi overclocking guide

second half is the p states bit

https://www.youtube.com/watch?v=52Tw-wcT7o4


-------------
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold


Posted By: VUMeter
Date Posted: 07 Dec 2017 at 7:42pm
...back to this again.

I thought I'd have another little play around.
Dropped Fixed Voltage to 1.325 (minus 4).

CPU MHz still drop to ~2.2GHz and boost up to XFR speed to ~3.9GHz, so all is working there.

I think I still need a little clarification on just what numbers I should be monitoring:

Individual Core VID I think might be a bit bogus - well 1.55v is shocking if not!
We know that the frequency isn't strictly true either, as when using "Ryzen Balanced" powerplan, the frequency is pegged at max always.

The bottom screen grab shows two lots of info that might be at least believable.
However, who's numbers are correct?  I know the 'Tdie' is a real sensor on the chip, and the 'CPU' temp (lower) is the Tsocket sensor in the motherboard.
But regarding voltages?  I set it to 1.325 LL2, so they are both quite close.





My temps are still nicely low, and I don't see 1.4v+ any longer, so that's good.  I haven't yet ventured into P-states, but could do so.

Maybe I should check out UEFI 3.1 and see if the vCore drops off more when idle, as this is pretty static, even though the low temp shows that it's clearly not burning the chip up.


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: datonyb
Date Posted: 07 Dec 2017 at 7:49pm
since writing the above
i have been playing myself
mainly getting my ram sorted

i now overclock a little different

i dont set p states anymore
i just liteally set freq, and volts on the oc tweaker page (top section)
and leave the lower voltage set to auto (further down page)
i do however set the llc to l2 down the page
0.384 - 0.688 on idle  while still at 3.9 ghz

im still on bios 3.1 (and will be for a while )


-------------
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold


Posted By: VUMeter
Date Posted: 08 Dec 2017 at 3:42am
Interesting you say that you adjust the uppermost voltage, and not the lower.
I found that if I edit the voltage lower down the page it makes a difference, whilst the upper does not.

Maybe I need to jump to p3.10.

I am still very impressed at just what this system is capable of.  It's mildly annoying that the router and modem take longer to start than this PC gets to the Windows desktop, I never expected that to be the case.


Note: These are not actual screen shots of what I have edited.
In the top image I have it set to Auto.
In the bottom image I have it set to Fixed mode, 1.325v Level 2 for both LLC options.

It looks like there is still some playing around here to get the most out of it.  AS far as I am concerned, I am totally happy with the stock performance and have no need to disable that.  But why have extra volts running through it when they aren't needed?


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: VUMeter
Date Posted: 14 Dec 2017 at 7:34am
" rel="nofollow - Ich glaube das ich habe etwas gefunden!  Yeah, well my German probably makes as much sense as my questions and typed out thoughts....but I think I have found something, and it seems relatively offiicial no doubt:

https://www.reddit.com/r/Amd/comments/6dawyw/overclock_ryzen_1800x_vs_relying_on_turbo/di1h591/

This is from AMD_Robert an AMD Technical Marketing rep:

"Temporary blips into the range of 1.4V and 1.5V are completely normal, part of the design, and totally harmless. The dynamic vcore we use is always relative to the number of utilized cores, the load on those cores, the current being drawn from the CPU socket, and the current temperature. If temps are high, load is high, core loading is high, then the CPU will not run up the voltage. If they're low, any one of these values offset or "cancel out" a few milliseconds at 1.4V+.
If you watch HWiNFO's average vcore for a few hours, you'll see that the average vcore for Ryzen over time is about 1.1 or 1.25V. So if you're running all day long at 1.35V, you're putting more volts through the chip than it would if left alone.
Your mileage may vary, but all day at 1.35V is not safer than transient bursts up to 1.4 or 1.5V."

From what I read here:
- The CPU vCore will spike to even 1.5v when XFR turbo boosting.
- Running on dynamic vCore with these transient bursts is safer than a higher vCore (1.35v) permanently.

However, I still see that these "transient bursts" are not so transient when running stress tests like Prime95 on 1 or 2 cores.  Maybe the 1.495v might be a spike, but it's still not coming down from 1.395v - which is basically 1.4v in my book.

When all threads are being stressed vCore drops down to just under 1.2v with the default "Auto" settings.

Fixing 1.3v on the vCore in EUFI stops the chip from pulling anything else than 1.3v.  XFR still worked perfectly on my chip at least.

So, what I am aiming for is limiting vCore to 1.3v max draw, as it has zero need to go above that.  I may be able to adjust this in the P-state settings, which is my next point of call.  However the XFR boost frequency is hidden as a ghost P-state and governed by the on chip system management.

For us that don't want to overclock but instead want to achieve a best possible optimised efficiency / longevity setup are we stuck between a hard place and a rock that has just been chucked down?  I shall investigate more.


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: VUMeter
Date Posted: 14 Dec 2017 at 8:01am
" rel="nofollow - Ah!
Well, of course the vCore will be high under default "auto" settings because of the 0.01% of chips that need it.   That's normal.  I'd doubt AMD would let their chip get hammered too hard by design - it's be planned obsolescence gone too far, unless they wanted their company to become obsolete!

Right, political waffle and speculation aside; the SMU!
Apparently, and I have no way to test, the power management on the actual chip requests # volts but may actually use something else.  Does the SMU get damaged by pulling too many volts, what is it's safe limit?  The indication is that the SMU provides safe voltage (1.365v?) internally where needed.

Now, when one ants to overclock, the SMU is gonna pull and keep pulling more power in and distribute it on a less than personally optimised graph.  Why is it not optimised?  Because it's meant for normal operations, not overclocking.  So, when overclocking it's back to the old manual affair of setting up your own voltages.

Still I think I will play with P-states to achieve an optimal low idle voltage and not too high load voltage.  It'd be nice to set up 2-core and all core volts but we'll see.


-------------
X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz.
https://valid.x86.fr/ikadaa" rel="nofollow">


Posted By: zlobster
Date Posted: 14 Dec 2017 at 7:47pm
Manually fixing a static voltage always leads to 2 possibilities (at least in my case):
1) I end up with unnecessarily large value, leading to excess heat waste and CPU 'wear'
2) I end with a tad too low voltages and under heavy stress the system becomes unstable

Something odd here. Other than Gigabyte's bad BIOS that was frying Ryzens, no other manufacturer seems to be having this Vcore behavior. None I was able to find, at least.

Here is the course I plotted for now - first, try to ask The Stilt about the voltages; second - try a DOS UEFI flash, AFTER Win 10 FCU and 'Adrenalin' matures a bit.


-------------
1700X ZP-B1 (stock); X370 Taichi (UEFI 3.10); 16GB F4-3200C14-8GFX XMP; 256GB 960 EVO; RX 580 NITRO+ 8GB



Print Page | Close Window

Forum Software by Web Wiz Forums® version 12.04 - http://www.webwizforums.com
Copyright ©2001-2021 Web Wiz Ltd. - https://www.webwiz.net