AMD RYZEN Builders Thread

[Aenra]

Are you doing this through bclk OC or by using the 3600 strap?

Just the multiplier
Though to be fair, i did play my part in this, wasn't stingy. RAM i bought was i) in the Giga QVL list, ii) b-die, iii) certified to run dual 4133GHz at 1.35volts; bought on purpose, as it would give the leeway needed to make it run around 3600 in a Ryzen; took 1.41 i think?
Never go low on RAMs with R7s, always higher.

(if you want the SoC and/or all the relevant numbers, next time i visit my da's i could write them down, no biggie; but i can tell you they were high, took a lot)
((was his birthday present, lol, he's an avid AMD fanboy, so.. built him one))

It's just sometimes I think I may of had a better experience is all

I get what you're saying, but i think it's mostly down to two things:

- your confusing the R7s' limitations with those of the motherboard. Even with the latest updates, Ryzens just aren't that.. stable? Easy to fine tune..? And never mind the mobo.
- your (possibly) neglecting that chip per chip, these things will vary, more so than with an older AMD chips or Intels. Could well be you just weren't that lucky with this specific chip; i hate that word, lol

 

[Grep_Linux]

I get what you're saying, but i think it's mostly down to two things:

- your confusing the R7s' limitations with those of the motherboard. Even with the latest updates, Ryzens just aren't that.. stable? Easy to fine tune..? And never mind the mobo.
- your (possibly) neglecting that chip per chip, these things will vary, more so than with an older AMD chips or Intels. Could well be you just weren't that lucky with this specific chip; i hate that word, lol

I think you're getting the wrong message, all I meant was that I've been hearing good things about the xhair now (obviously the whole bricking fiasco was bad but since then), and always had the taichi, like I said I'm happy, I just always wonder what could've been.

 

[VirtualLarry]

PSA: Even with AGESA 1.0.0.6, don't use four RAM sticks.

I've got some Avexir 2400 sticks with blue LEDs, and when I put 4x4GB into an ASRock AB350M Pro4, with UEFI 2.30, they defaulted to 1866, and when I set XMP, I got boot loops, with three beeps, then reboot, repeat.

I flashed 2.50, which has AGESA 1.0.0.6, and expected that I would be able to set XMP, but on either Auto or XMP, still DRAM speed 1866 in UEFI main info screen, and once I got Windows 10 and CPU-Z installed, CPU-Z confirmed DRAM clocks eqivalent to DDR4-1866.

These are my oldest DDR4 sticks, is it possible that they are DS, even though each stick is only 4GB?

 

[Aenra]

wrong message ..
I've been hearing good things about the xhair .. always had the taichi

No wrong message at all; am not here to promote one company or libel another, i got you just fine the first time and gave you the jist of it as i see it. You're more than welcome to think otherwise, anytime. You just got an opinion, would have been the same if you were or were not satisfied with your current mobo

 

[Wall Street]

These are my oldest DDR4 sticks, is it possible that they are DS, even though each stick is only 4GB?

In CPU-Z the SPD tab will tell you if the stick are single rank or dual rank.

 

[DrMrLordX]

Just the multiplier
Though to be fair, i did play my part in this, wasn't stingy. RAM i bought was i) in the Giga QVL list, ii) b-die, iii) certified to run dual 4133GHz at 1.35volts; bought on purpose, as it would give the leeway needed to make it run around 3600 in a Ryzen; took 1.41 i think?
Never go low on RAMs with R7s, always higher.

(if you want the SoC and/or all the relevant numbers, next time i visit my da's i could write them down, no biggie; but i can tell you they were high, took a lot)
((was his birthday present, lol, he's an avid AMD fanboy, so.. built him one))

Sure, write down any voltages and timings/subtimings you feel relevant. Actually over at XS they have a tool that lets you screenshot all that stuff but i don't remember where to get it. I've all but burned out trying to get my DDR4-3733 running @ 3600. It'll boot and pass a lot of benches, but anything AVX and forget about it.

 

[Aenra]

but anything AVX and forget about it

Can you raise your SoC any higher than it currently is?

As to the tool you mention, erm, no idea to be honest, but there is some key you can press while in UEFI, instantly saves a screenshot to any USB currently plugged in? Will check which one does that, never done it before, lol

edit: Yeap, google says it's F12

 

[repoman0]

I'm also using Asrock AB350M Pro4 and have CnQ running with my overclock of my R5 1600. Oddly, it didn't disable it when I set manual mode. I *think* I was running BIOS 2.40 at the time, but currently 2.50.

Edit: have you tried manually reenabling CnQ?

I still can't get reduced idle clocks to work in manual mode on this board, whether or not CnQ is enabled. It seems to totally disable the processor power management section in power settings.

I'm trying out P-state overclocking now. Seems like the CPU won't go into P0 unless the VID is left at stock, otherwise the maximum state is P1. So, I only get 1.1875V to play with, but looks like that gets me about 3.6 GHz, which I am quite happy with. Hoping they fix this functionality in a later BIOS update.

 

[Reinvented]

I still can't get reduced idle clocks to work in manual mode on this board, whether or not CnQ is enabled. It seems to totally disable the processor power management section in power settings.

I'm trying out P-state overclocking now. Seems like the CPU won't go into P0 unless the VID is left at stock, otherwise the maximum state is P1. So, I only get 1.1875V to play with, but looks like that gets me about 3.6 GHz, which I am quite happy with. Hoping they fix this functionality in a later BIOS update.

Values for P State Overclocking -
FID (Clock Speed) 90 - 3600mhz, 91 = 3625, 92 = 3650, 93 = 3675, 94 = 3700, 95 = 3725, 96 = 3750, 97 = 3775, 98 = 3800, 99 = 3825,
9a = 3850, 9b = 3875, 9c = 3900, 9d = 3925, 9e = 3950, 9f = 3975
a0 = 4000, a1 = 4025 (my max sweetspot OC), a2 = 4050, a3 = 4075, a4 = 4100, a5 = 4125, a6 = 4150, a7 = 4175, a8 = 4200 = a9 = 4225, aa = 4250, ab = 4275, ac = 4300, ad = ugh you win the lottery.

Values for DID
8 = 25 mhz increments, 9 =22.2196, a = 20 b = 18.18, c = 16.667, d (final recommendation) = 15.384mhz - 3943mhz cap).

Values for VID Voltage Control = 30 = 1.25v, 2f = 1.256v, 2e, 1.2562v, 2d = 1.268, 2c = 1.275v, 2b = 1.2812v, 2a = 1.287v, 29 = 1.293v, 28 = 1.3v, 27 = 1.3062v, 26 = 1.3125v, 25 = 1.318v, 24 = 1.325v, 23 = 1.3312v, 22 = 1.3375v, 21 = 1.343v, 20 = 1.35v, 1f = 1.356v, 1e = 1.3625v, 1d = 1.368v, 1c = 1.375v, 1b = 1.3812v, 1a = 1.3875v, 19 = 1.3937v, 18 = 1.4v, 17 = 1.406v, 16 = 1.4125v, 15 = 1.418v, 14 = 1.425v, 13 = 1.4321v, 12 = 1.4375v, 11 = 1.443v, 10 = 1.45v, *next set is from f - a, 9 - 9 (1.45 - 1.55v)

These are some of the values for P-State overclocking/downclocking. Hope this helps. I'm trying to tinker with mine as well and figure out if I want it to downclock when idle or not.

https://valid.x86.fr/vph13v (My CPU-Z validation). Might try for a bit less with less volts. Who knows. It's just warm here!

 

[Space Tyrant]

I'm trying out P-state overclocking now. Seems like the CPU won't go into P0 unless the VID is left at stock, otherwise the maximum state is P1. So, I only get 1.1875V to play with, but looks like that gets me about 3.6 GHz, which I am quite happy with. Hoping they fix this functionality in a later BIOS update.

I'm having the exact same problem with pstate overclocking. Lucky for me though, the 1600 default P0 vcore is 1.23750 -- easily enough for 3700MHz. With pstate 2 at .9v & 1550 MHz, this looks to average even cooler than the old 3600 'manual' OC with idle at 1.1375v.

 

[Gideon]

I have to say MSI's timing is impeccable!

I just received all of my Ryzen CPU components bar the CPU itself (which will arrive on saturday) and they just now released official AGESA 1.0.0.6 BIOS for the Tomahawk B350

The rig itself will be:

• CPU: Ryzen 1700X
• Cooling: Noctua NH-U12S SE-AM4
• Mobo: MSI B350 TOMAHAWK
• GPU: Recycled MSI 970 GTX (was hoping to replace it with vega, will see ...)
• Mem: DDR4 Corsair Vengeance LPX 16GB (2x8GB) 3200MHz CL16 1.35V (CMK16GX4M2B3200C16R)
• SSD: SAMSUNG 960 EVO NVMe M.2 500GB
• PSU: EVGA SuperNOVA 650 P2 650W, 80 PLUS Platinum
• Case: Fractal Design Define S

 

[Aenra]

I have to say MSI's timing is impeccable!

How can it be impeccable if they only just launched a 1.0.0.6 update, lol? Every other company has had it out for weeks now

(i get the personal sense of the 'timing' here, O.K., but.. poor wording. Their timing sucks actually, imagine waiting for something every other mobo company has already had out; unless of course i've missed something, in which case my apologies ^^)

 

[Gideon]

Yes, it's true that overall it's quite late. There was even talk that they will skip it and go straight to 1.0.0.7, that got me really worried as I wouldn't be able to run those dimms at anywhere near their designated speeds with 1.0.0.4a (previous BIOS).

I Should have added that it was impeccable for me, not in general, as I can't wait to assemble the rig during the weekend

Anyway, does anyone actually have experience running those dimms (CMK16GX4M2B3200C16R) with ryzen on any motherboard, and what timings/speed did you achieve?

 

[lixlax]

@Gideon, thanks for noting. Updated to the 1.0.0.6 version now and my RAM is now easily running at advertised speed of 2800MHz, was at 2666 before.

The specs as well (upgraded to Ryzen already in march):
CPU: Ryzen 7 1700 (@ 3,7GHz 1,2625V)
Cooler: NZXT Kraken X61
Mobo: MSI B350 Tomahawk
RAM: 2x8GB, 2800MHz, CL14 "Corsair Vengeance LPX"
Graphics: Sapphire Nitro R9 380 4GB @stock
Storage: MX100 256GB and 1TB WD Caviar Black
PSU: Chieftec CTG-550C
Case: Fractal Design Define R5 (black, with window)

 

[Aenra]

does anyone actually have experience running those dimms

None personally, but in the off chance a more general advise is wanted, start with very loose timings, it's really the frequency that matters here (infinity fabric).
May sound extreme to you right now, but i'd seriously start with 20-20-20-39 and 2T, if your mobo allows for that, not sure if all do. Stabilize your freq as high as you can, then assuming you've got any voltage headroom left (up to/below 1.45v), start with the timings.
You will save yourself a lot of time and sweat

 

[Rifter]

So i finally got my Samsung B die ram. Thank god i had cheap ram to use for the wait.... Was a long road, amazon pushed back my order 3 times over 2 months of delays and then finally told me they cant get it in stock,(even though i asked them each time they pushed back delivery and they assured me they are still getting it, TLDR fuck amazon)

Had to finally order it from newegg for $40 more than i had it on order from amazon for.

But IT WORKS AT 3200Mhz CL 14!!!!!

I upgraded my Asus X370 Prime mobo to newest bios 805 and the very first time i tried the ram at its rated speed it worked fine, no tinkering required. I manually set all the timings upped SOC voltage to 1V and ram to 1.35V and it works fine.

Ram latency is now 76-78ns

My ryzen build is almost complete! Now just need to wait and see how AMD does with the new video card and decide between it and a 1080/1080Ti and ill have a final system for the next several years.

 

[Reinvented]

So i finally got my Samsung B die ram. Thank god i had cheap ram to use for the wait.... Was a long road, amazon pushed back my order 3 times over 2 months of delays and then finally told me they cant get it in stock,(even though i asked them each time they pushed back delivery and they assured me they are still getting it, TLDR fuck amazon)

Had to finally order it from newegg for $40 more than i had it on order from amazon for.

But IT WORKS AT 3200Mhz CL 14!!!!!

I upgraded my Asus X370 Prime mobo to newest bios 805 and the very first time i tried the ram at its rated speed it worked fine, no tinkering required. I manually set all the timings upped SOC voltage to 1V and ram to 1.35V and it works fine.

Ram latency is now 76-78ns

My ryzen build is almost complete! Now just need to wait and see how AMD does with the new video card and decide between it and a 1080/1080Ti and ill have a final system for the next several years.

Which memory did you end up getting? I settled for the G.Skill Ripjaws V CL14 DDR4-3200, and it's worked since day 1 at rated speeds using the A-XMP profiles on the MSI B350 Gaming Pro and ASRock X370 Taichi. Vega FE looks good, so hopefully the RX Gaming will be a lot better! Really exciting summer!

 

[Rifter]

Which memory did you end up getting? I settled for the G.Skill Ripjaws V CL14 DDR4-3200, and it's worked since day 1 at rated speeds using the A-XMP profiles on the MSI B350 Gaming Pro and ASRock X370 Taichi. Vega FE looks good, so hopefully the RX Gaming will be a lot better! Really exciting summer!

The Gskill FlareX 2x8GB 3200 CL 14.

I had purchased a Ripjaws V 3000Mhz set to get me up and running originally and will use it now for the girlfreinds computer upgrade this fall. It was Hynix chips and refused to run at 3000Mhz except on the second Bios released for my mobo, 505 version, everything after that broke my memory support and would not run faster than 2133Mhz. So i had been on 505 bios this whole time, upgraded then downgrade each bios release, was sad really that they kept pushing new bios with "better" memory support when for me it was worse and broke my memory support.

So for anyone with my mobo and hynix memory chips i suggest staying on the 505 bios.

 

[Reinvented]

The Gskill FlareX 2x8GB 3200 CL 14.

I had purchased a Ripjaws V 3000Mhz set to get me up and running originally and will use it now for the girlfreinds computer upgrade this fall. It was Hynix chips and refused to run at 3000Mhz except on the second Bios released for my mobo, 505 version, everything after that broke my memory support and would not run faster than 2133Mhz. So i had been on 505 bios this whole time, upgraded then downgrade each bios release, was sad really that they kept pushing new bios with "better" memory support when for me it was worse and broke my memory support.

So for anyone with my mobo and hynix memory chips i suggest staying on the 505 bios.

The hynix chips so far from what I've seen will do no more than 2400 guaranteed using XMP profiles. Regardless of whether or not it breaks memory support, I'd stay updated either way as theres probably some undocumented fixes as well which help other things. (At least in my experience and opinion)
Always remember that just because your overclock was great on one bios, doesn't mean it's the same for the next. Which is why you always re-test until it's stable using latest releases.
Glad the FlareX works really well. I thought about it, but I couldn't justify the price personally.

 

[Avalon]

Finally upgraded and happily running on a Ryzen build now!

Ryzen 5 1600
Gigabyte X370 Gaming K3
2x8GB Gskill Ripjaws 3200
500GB Samsung 960 Evo
MSI RX580 Gaming X+ 8GB

Gaming bliss. No setup issues whatsoever, the motherboard took my memory like a champ and is running the XMP profile for 3200Mhz without a complaint. Still running the stock wraith spire cooler, so no OC'ing yet.

 

[Space Tyrant]

I switched to Pstate overclocking today. I was unable (on the Asrock AB350M Pro4) to (successfully) change pstate voltages, but was able to set P0 to 3725MHz and P1 to 3200 using the stock voltages. On P2 I was unable to even change frequency.

Memory is still at 3333MHz and it's maxing out after an hour of torture testing at 58C on the Wraith Spire. I did get to tickle the CLRCMOS jumpers a *few* times.

 

[repoman0]

I switched to Pstate overclocking today. I was unable (on the Asrock AB350M Pro4) to (successfully) change pstate voltages, but was able to set P0 to 3725MHz and P1 to 3200 using the stock voltages. On P2 I was unable to even change frequency.

Memory is still at 3333MHz and it's maxing out after an hour of torture testing at 58C on the Wraith Spire. I did get to tickle the CLRCMOS jumpers a *few* times.

I really hope an AMD agesa update or something at some point down the line fixes the voltage changing. I had to back down to 3.5GHz at stock 1.18v 3.6 and eventually 3.55 froze up while running both Prime95 and GPU mining for max stress. I would like to get 3.7 or 3.8.

I think it's common to every board that you can't change p-state VID or it won't work, but other boards have offset voltage that can compensate to some extent, as long as you're willing to have a blanket voltage bump over all p-states.

 

[ScottAD]

I switched to Pstate overclocking today. I was unable (on the Asrock AB350M Pro4) to (successfully) change pstate voltages, but was able to set P0 to 3725MHz and P1 to 3200 using the stock voltages. On P2 I was unable to even change frequency.

Memory is still at 3333MHz and it's maxing out after an hour of torture testing at 58C on the Wraith Spire. I did get to tickle the CLRCMOS jumpers a *few* times.

Buildzoid did a great job explaining why p-state OC is pretty much moot.

https://www.youtube.com/watch?v=bzxn1hS7Nq4&t=397s

 

[Space Tyrant]

Buildzoid did a great job explaining why p-state OC is pretty much moot.

https://www.youtube.com/watch?v=bzxn1hS7Nq4&t=397s

Thanks for the link.

My original goal with Pstate OC was more about undervolting than overclocking. As it is, stuck at the stock voltages, it's not bad. I managed to get improved performance with the reasonably low stock voltages. And, my machine has no problem downclocking to P1. I have one program that I sometimes run for hours that mostly pegs a core at 3200, my P1 frequency.

Anyway, I prefer the slightly more fine-grained control over my previous manual 3600 OC, but I'm still hoping the kinks are worked out in the next BIOS update.

 

[Space Tyrant]

I really hope an AMD agesa update or something at some point down the line fixes the voltage changing. I had to back down to 3.5GHz at stock 1.18v 3.6 and eventually 3.55 froze up while running both Prime95 and GPU mining for max stress. I would like to get 3.7 or 3.8.

Is your machine properly downclocking to your P1 frequency?