p2.0 bios broken taichi x370

TooQik wrote: Optik wrote: Install p1.60 and u don't have problems. P2.0 Smt disable don't work Voltage reading don't work correctly 2 settings 4 voltage settings the Mainboard calculate both an say 2,7v not 1,35v. Pls fix it Asrock. I don't gain anything by going back to 1.60. The only "problem" I currently have is I can't get my RAM to run at speeds higher than 2400. This is the same for both the 1.60 and 2.00 BIOSes so I'm better off sticking with 2.00 until the next AGESA update in May. Patience is a virtue, although these days it's more and more a lost virtue. Too many people are part of the NOW Generation.

Edited by Optik - 25 Apr 2017 at 9:09am

TooQik wrote: Yes, I wasn't worried by the high voltage as I figured I'd either be smelling something burning or the PC would have shut down by now if it was actually the case. Here's another screenshot of a voltage HWiNFO reports incorrectly for my PC: That's one hell of a 12 volt power supply.

I had that +12v (over 22V) reading too with that version of HWiNFO64 with my Ryzen system. I guess you did not see the +12V reading in my HWiNFO64 screenshot in my previous post on page 1 of this thread. That's with the v5.51-3141 Beta version, which fixes that bug. I like to use the Beta versions since they have the latest features, and rarely have any issues.

You can also see sensor readings that are meaningless, like the 7° C Auxiliary reading that never changes.

That +12V display error is a great example of how the outputs of the sensor/monitoring chip must be processed to provide the correct value. All boards don't use the same monitoring chips, and good programs like HWiNFO are coded to determine which monitoring chip and board is being used. From there the appropriate processing is applied to the monitoring chip's output.

Yes, that's a lot of work and support, which is why some programs, even famous ones like CPU-Z, have bugs in them occasionally. I've casually worked with the programmer of HWiNFO to fix a bug in it occasionally, when new boards I have are released. You can read in the HWiNFO News section (basically release notes) how enhancements are added for various boards in different versions.

This is scary stuff really, we depend on these programs and assume they are always correct. Their programmers do a great job, but no one is always perfect, and since there a few standards about how this all works, it's not easy getting everything right all the time.

Yes, the hardware manufacture ought to know how there own product works... they better.

You've brought up another situation that the third party programmer must deal with, as the HWiNFO programmer has mentioned in his forum. He has asked mobo manufactures for information about their sensor/monitoring designs, and is refused. He must figure it out himself, by using his experience and when possible the documentation for the monitoring chip from its manufacture. That still does not give them every detail, such as which sensor inputs or outputs are not being used for example. That's where owners of various boards can help them get things right.

HWiNFO64 always has at least a few sensor readings that are meaningless, but that depends on the board manufacture, type of system (AMD or Intel), chipset, the board itself (high end or entry level), etc. Plus how can they have one of every mother board made by every manufacture to work with? Recently ASRock began using a new monitoring chip on a few of their boards, and most of the existing monitoring programs could display only a few readings correctly, until the programs were updated (if they ever were updated.)

what is good
is real people with real setups posting what they can do and their settings
it helps educate us all

p.s. i like your ram choice (it does very very well on intel systems hopefully it will eventually show same promise on the am4)

Hwinfo64 5.51-3141 (beta) work fine for me, previous version and latest CPU-Z (1.79) showed a doubled voltage. The only thing I noticed is that it does not always show a drop in frequency in idle time (to ~1500mhz, always p0 - 3700), voltage drops.