Ryzen - Return of the Jedi

[os2wiz]

While that is definitely understandable, since you're running your phase change setup, the issue I have with it is I learn better by examples and pictures. My brain is just wired to better figure out how to accomplish something by seeing the end result and working backwards from there with the explanation of why it is that way or works like that. In a sense I guess my brain "decompiles" in order to understand, rather than compiling the answer from the text.

As an example... You've explained to me what quite a few settings do and how they help. The ProcODT being one of them, but for the longest time I wasn't really able to make any use of that because I had no idea where to start, so it wasn't until you offered the baseline of "for 3200 use 43.3Ohm, and for 3333 use 48Ohm" that I was able to make some sense of it all. Same goes for those Drive Strengths. While, granted, you also said you're not entirely sure yourself how they'll function on this platform, your understanding of it as a concept is way more understood due to your experience. You've relayed that to me, but it's a generalization, which while I find helpful, I don't really know where to start with my tinkering heh

While typing that I realized it basically goes back to what I've said earlier (a post from the last couple days), that it's tough for me to get started because on my Titanium it doesn't tell me what Auto is applying. I have no baseline to work from, and that's what the examples from you experienced users are providing me with. That way I'll at least have a data point to base everything on, so I know that I'm not ultimately working against myself if I set one drive strength and things work, then set another to various other points which all fail... Have I actually set the first one wrong (non-ideal) or are the other ones not working because of some other setting that isn't being set as it should due to whatever Auto is applying?

That's also where even other user's auto-settings at higher speeds help me out a bit. Sure, I might not be able to run at their speeds with their timings, but now I have a direction and more importantly a distance. If (arbitrary, unrealistic example) at 3333 my tRDRD is 10 and at 3466 someone's is 14, now I know that it's going to likely take more than just setting mine to 11 in order for there to be a chance.

Lastly, but equally important, the fact that I have no clue what settings carry the greatest impact on stability. Admittedly, I know it sounds like hand holding, but gone are the days of quickly being able to tell if a setting is working or not. This all went way way wwwaaayyyy faster back when we had A64Info with the ability to adjust all the timings IMC's from within Windows :P Set an overclock, if you get into Windows, run a test. Test fails? Adjust a timing, test again. Pass? Try tightening something else, repeat tests. Etc etc. Even ignoring that, before, we'd press the power button and instantly be at the POST screen. Now we have to wait 8 seconds, or 20 should a setting fail multiple times and enter failsafe mode. On mine, the first restart after saving a change might post an F9, but the second attempt passes. So even tweaking via BIOS has became slow and arduous... but painfully so when you don't know what you're doing, like some folk! *raises hand* lol I love doing it, I accept the risks, but not having a clue is a buzzkill

I have some good news to report on 4dimm 32GB memory overclock on my FlareX DDR4 3200 memory on Titanium bios 1.73. With CL14-14-14-48 at 2800mhz with SOC 1.15v Proc 60ohm, dram voltage 1.40 v. at 3.875GHZ at 1.40 v cpu voltage. I have booted successfully and run several benchmarks. I will run stability test later and I plan on saving the oc profile. I will attempt to refine voltages later. Here are attached benchmarks.

I have an AIDA64 benchmark on this memory overclock but it is 235kb and the attachment loader indicates there is a 200kb maximum.