Honestly, I can't say I have experienced that. With the exception for RAM settings that must be done through the tweaker section. Which sucks because the other areas are laid out better than the tweaker secion.
To your points:
No denying that, there are likely still worse ways. I still think you have something else going on keeping things from working the way you expect. But I am with you on just getting things working and moving on at times.
I think that is how a lot of people feel about your method. That said, AMD made Ryzen master for some reason - either because board partners make shitty UEFIs or Ryzen is more finicky than it needs to be.
I think we can kill two birds with one stone here.
The conclusion that I came to - and that was my initial breakthough in cracking my problems - was to only use what we would classically consider to be the BIOS to configure the motherboard, and nothing else. To configure the CPU and RAM I used the
real BIOS, namely the AGESA portion contained in "AMD CBS" and "AMD Overclocking" I switched to Ryzen Master, which is a lot more convenient for configuring the RAM because to do it manually in the "AMD Overclocking" and then changing the RAM timings under "DDR and Infinity Fabric Frequency/Timings" you have to enter the values in hexadecimal.
"Load the XMP profile", I hear you say, "Nothing could be simpler than that", I hear you say.
Yeah, about that, if I load the XMP profile, with a clean BIOS then the first thing I get are the three beeps (I am old-school and although motherboard manufacturers no longer see fit to include a little speaker, I have one installed, because fuck little LEDs or BIOS code displays, just hearing the series of beeps allows me to pinpoint the source of problems a shit-ton easier) that tell me there is a RAM problem.
This is followed by a number of sometimes hangs, sometimes a clean series of reboots, aka "RAM Training" until the system boots into the OS. So it seems to me that the SPD of the RAM is read by the BIOS (which I call "GigaByte Master") and then that attempts to update the real BIOS, namely the AGESA, and there is a negotiation back and forth.
Sometimes it just results in the system shitting itself and giving me the "Cleared CMOS" message and I have to go in and load the XMP profile again - rinse and repeat the procedure outlined in the previous paragraph.
What is certain, at least with the motherboards I have worked with, that setting the XMP profile
IS NOT what configures the RAM, but rather it is the negotiation between setting the XMP profile in the BIOS and then what the RAM timing portion of AGESA agrees with is important.
For instance, if I set XMP and then go through the "RAM Training" I get a value for tRFC of 648 although the XMP profile of my RAM states 312. A number of other timings are worsened.
The thing is though, if I copy out the SPD values displayed by loading the XMP profile, then turn XMP off again, load Windows and put the SPD values into Ryzen Master, it accepts and applies the values with no problems whatsoever.
My way of doing it is admittedly kludgy, but it does have one thing going for it,
IT WORKS!
For any benchmark you care to name, Buildzoid, in a non-exotic cooling scenario (LN2), will not be able to match any score I can achieve given his methodology for overclocking his 3950X (aside from a single core benchmark, which is essentially meaningless and only being clung to by Intel because they have nothing else) and that I can not only beat his scores easily, but beat them with less voltage and lower temperature.
There are a lot of steps I have taken along the way and you reminded me of the time I spent months ago trying to work out what the hell was happening with regard to the RAM problems I was having.
I am not saying this to pat myself on the back, and if anyone can show me a better way of achieving my goals, I will abandon my methodology in a heartbeat. I am not wedded to it. But looking around, there is nothing, a gaping vacuum.
Well, I think a lot of it was mostly a misunderstanding but there are a lot of "experts" here and don't like to except there are alternate ways of doing things.
Back in the mid 1990's I set up a network for one of the biggest porn producers in Germany. After getting it all set up, and writing a database solution for her, because the one she had was a total rip-off, I was invited to a party she was giving.
And no, it was a party just like any other, not what you are thinking.
At the party she introduced me to people as, "My computer expert", and this made me very uncomfortable, and I explained to those people that I was not then nor could I ever be an "Expert", because just when I start to think I know what the hell I am doing, things change and in many cases my current knowledge is more of a hindrance than benefit moving into the future and that "Permanent Scholar" was the highest title I could aspire to.
How much do I know about computers?
Well I'd like you to stretch out your arms as far out from your body as you can, now bring your thumb and your forefinger together so that they are as close to touching as you can. Now look at the distance between your thumb and your forefinger, that is how much I think I know, and the distance of the spread of your arms is how much I feel woefully ignorant about in terms of computer knowledge in comparison. That's not really a great answer from having been a techie for 38 years when someone asks me, "What do you know about computers?", and I have to answer, "Essentially fuck all".
Well, there isn't much that can be done about that. At some point, a user just has to understand what they are dealing with or they will just get what they get from the factory. In that sense, Ryzen is not a bad choice as you get pretty much what you are gonna get from the factory (Let's pretend these last five pages of discussion didn't occur).
That would be all well and good except for the fact that they are leaving a hell of a lot of performance on the table. What worries me more though is that you are left at the mercy of motherboard manufacturers that they have the voltages under control - which they don't in my opinion - and that something you paid good money for will not decline in performance over the short term and be fried over the medium term.
With my original post I went beyond whining and showed how to configure a 3rd Gen Ryzen and be within specs to get a lot more performance for your money than you otherwise would have.
TANSTAAFL applies though, and the kludginess of my solution is a bit of a downside - which AMD could go a long way to remedying if they decided to expand their configuration software with some options. But who am I kidding, it's AMD,
THAT'S never going to happen.
I'll probably do the same with my 3800X setup once I build it. If it works, don't fix it.
It's what I'm doing with my i9-9900K machine and it's doing fine.
If you try to configure your 3rd Gen Ryzen as if it were an Intel CPU then you will be in a World of Pain, with a good chance of frying your CPU.