Ryzen - Return of the Jedi

[Formula350]

Well heres a tip..

Xmp is intel specific and "unsupported" by AMD officially.

Jedec is industry standard and supported by all and 2666 is the highest officially supported speed by amd.

Drop to 2666 @ auto on all but primary timings....look at the subs 2666 strap sets...start from there as a guide line.

As far as the bclk question previous guy asked...

There was a rookie "rumble" comp at hwbot. One part of it was highest ref clock...money prizes etc...if i narrowed it down to which board and exact settings to use...it might have well been me doing the result.
<snip>

While I did indeed know that about the XMP being Intel's profile, and thus only added to AMD systems through boardmaker's kindness, I hadn't considered using 2666 as a reference point. So I may indeed just have to do that Thanks.

As for the influencing competitions... That's the part about it all that I said I do understand people's reasoning behind withholding info/tips on. At the same time it's what I find frustrating because we went from being a niche group of people willing to share everything and turned into a cutthroat segmented/factioned submarket that's fueled by competitions with real money prizes. On the one hand, it's great that overclocking has gotten to where it has, where we have such an interest that there are competitions, because like most advancements in life there is a trickle-down to consumers like me. On the other hand... all of these nice shiny features now are generally left unexplained or with really vague descriptions. (Unfortunately that really hasn't changed much, as in the past those 'help' tips on settings were generally hard-to-understand or poorly translated Engrish anyways).

Like I remember with my Llano APU system, which the OC guide I read might have even been by you Chew lol, but there was lots of help you could find with those. Might've been because it was an APU and not as much of interest to extreme overclockers, but it was details like changing the SATA from AHCI to IDE to help attain higher BCLKs that I feel might not be a shared nugget of info with Ryzen. Granted, I have no idea if that would even help, given the years that have passed, as AMD could've came up with something to help prevent the need for that. Alas, I can't even test that since A) the Titanium lacks BCLK beyond 103MHz, B) the Titanium lacks the option to change to IDE mode. (It's in there, deep in a submenu, but there are SO damn many different SATA menus, all with similar options. So I don't know if changing one and leaving the rest on Auto would even result in the change being applied...)

New progress on 2 dimm overclocking. 3466mhz achieved at 3.875 GHZ . I am uploading validations. I have screen shots of the bios but they a re too large a file to upload the image. I just added AIDA64 memory report only.

Bios settings core voltage 1.3625 LLC profie 1 actual 1.408 v. , SOC voltage 1.152 actual CLDO_VDDP .99 v , dram voltage 1.44 v actual
memory timings 2T CR CL 16-16-16-16 42 tRC 72 BGS disabled ProcODT 63.3 OHMS. BIOS 1.73 beta MSI Titanium

Nice, dude!
"LLC profile 1" is CPU LLC I presume?

Also, for your BIOS screenshots (using F12), if you open them up with Image Viewer, then use Snipping Tool and click the dropdown on NEW to set to Rectangular Snip, if you select the whole BIOS view and save as a JPG, it'll only be 130KB However, I always save as PNG which they're ~330KB and upload just fine (as evidence by my previous posts).


As for my own tweaking, I tried out the SubTimings from these 3200 "Moderate" tightened timings, but primary at 14-14-14-35 1T and they caused SPI @ 32M to fail after the first pass. heh

(Settings: No CPU OC or voltages, CPU NB @ 1.05V (1.056V), DRAM @ 1.360V (1.376V) ODT 48Ohm (likely forgot to Auto it after coming off 3333), LLCs all Auto except "CPU NB Power Duty Control" which was set to "Current Balance")

Went back and changed JUST SubTimings to these in the below screenshot, leaving all the above settings the same, and now it passes SPi32M; however, does fail AIDA's RAM StressTest after only 25seconds (though, see headscratch after the pic) lol On the plus side, the Cache stress, where I usually have the problems, went on for >11mins before I stopped it. Also had absolutely no problems playing Minecraft all yesterday or the day before, which laugh all you want, but at the tighter timings above, it crashed fairly often :P (I own a server so I am playing MC a lot for that reason, mostly spent 'babysitting' the teenagers that play.)

(hah I just noticed that it converts the PNGs I upload; it's 102KB instead of the 322KB uploaded file)


*scratches head* And yet, I played around with K17TK, upped only the P0 FID to 36.5x and re-ran tests, came back and am running the RAM stress again, but this time it's ... 7m30s so far w/o a problem. Perhaps my chip/system just doesn't like CPB and setting the multi (which with this tool, SEEMS to disable CPB for me) disables some of the auto clock/voltage management, stabilizing things? I dunno... Now it's up to 9m45sec. I mean it's either that, or previously running the Cache test for 11mins had gotten things sufficiently heatsoaked, somehow causing the IMC to hiccup. Because I ran the RAM stress immediately after the Cache the first time, only difference being the fact the system was running totally default for PStates, etc. Either way. Cool in my book Stopping it at 12mins so I can go get the settings out of the BIOS.


Lastly, I typed this yesterday but didn't get around to submitting it, so as for the last post, I haven't had a chance to dive into that. However, I did run P0 up to 3.8GHz (default voltage, under load is usually 1.275V) and everything was solid as heck. Better than I've been, at least; ran Minecraft for a solid 10hrs w/o a single crash.

EDIT: Updated with image and LLC setting. This board is silly though... I actually had AXMP set on these Tridents, which beings nothing changes except primary timings, I had everything else set manually anyhow. Nevertheless, I disable AXMP, set 2133, left all my subtimings on accident and restarted... D2 code >_> *shrug* Silliness. Anyways, time to try the "JEDEC Trick" heh