entropic remnants

Preliminary:
 
You will need a BIOS for your motherboard that uses the AGESA 1.0.0.6 microcode.  For your board that may be a public beta or a production BIOS.  For me on the ASUS Crosshair VI Hero it was all beta's after the 9943/9945 twins.  Current public beta is 1403 and that's what I'm running.
 
Step 1:
 
I don't know any other Ryzen motherboard, but in my case I have to use what's called a "manual" overclocking profile.  None of the automatic ones work for me.  I suspect you will need at least a B350 or maybe even only X370 board to have access to these.
 
Then, you need to select what is commonly referred to as a "strap" or "strapping" -- basically you may have a drop down list of memory speeds, or have to type in your desired memory speed.  This ONLY sets the clock speed when you do this though and you will be responsible for getting the parameters right and that's what this tutorial is all about.
 
Step 2:
 
You need to find your XMP parameters I listed above.  You can use a variety of programs to do this.  Unfortunately it appears that CPU-Z does not give you the full set you can see in my previous post.  The free version of Thaiphoon Burner, or the free AIDA 64, and many other programs for checking hardware can give you that set of parameters.  Many BIOS have an area that will show you the SPD data on your memory sticks including the Intel XMP profile. They may seem slightly different (like omitting the "t" that is often used) but you will figure it out.  
 
Print them out and hang on to them as depending on your BIOS you may or may not have access to them.
 
Step 3:
 
Find where in your BIOS the section is that allows you to tweak the memory timings.  That's where you will enter these numbers. 
 
Step 4:
 
Enter the timings from your memory's normal specifications, and the XMP data in the appropriate places.  AMD adds some suffixes to the parameter names but you'll figure them out.  Attached is how they look in the Ryzen Timing Checker from "The Stilt", sans suffixes.  Take a look and get used to seeing them and where the ones you need are.  Yes, they're like ancient Greek -- but they can be utilized so have a look so they aren't totally foreign.
 
More to come...
 

Well, sorry I've not followed up.  I actually have a bit more information to share as well as how to get your memory voltage down if you are having to set it over 1.4 volts to get your overclock to work.  I've been busy with some other things in life but I will return to this and again sorry for the delay.

Oh, Tom, you brought me back from a nice dream where I did not read forums and get mad at trolls and fan-boi types, lol.  I have been off the forums for awhile now and only came back to some with the release of Ryzen.. and then I've avoided them again.  So full disclosure: cranky old man who doesn't suffer fools gladly, even myself, lol.
 
Okay, off the soap box now.
 
First off, something about Corsair: they market the same product with different chips in order to hit demand.  Corsair sells more memory than anyone else.  Part of knowing what to do is knowing what you have and that can be an issue.  One thing you will notice is that Corsair kits often have a "version number" attached and that's an indication of what's used.  You don't see this so much on other products that tend to have only one hardware type per SKU.
 
Dominator Platinum have apparently used both Samsung and Hynix chips, but the ones I'm familiar with use Samsung D-die, E-die or B-die chips.  The E-die versions are dual-rank (due to lower density) and harder to get "up to speed".  I'm using CMD16GX4M2B3200C16 version 4.24 which are Samsung, dual-rank, E-die.  Version 4.31 of my kit are supposed to be B-die.  
 
I have been able to get these E-die variants up to speed since beta BIOS 9943/9945 and the succeeding beta BIOS which are based on AGESA 1.0.0.6.  I'm currently running beta 1403 with stable 3200 mhz memory on a low-spec 1700 non-X which will only go to 3800 mhz reliably.  It does involve manually setting many of the sub-timings exposed with the 1.0.0.6 AGESA.
 
What I will do is update a post I did on the ASUS forums about this with my latest information and put it on this forum.  But you can see my original post on how to do this over here: 
 
https://rog.asus.com/forum/showthread.php?93472-Get-Corsair-Dominator-CMD16GX4M2B3200C16-Up-to-Speed
 
You do NOT need Thaiphoon Burner as you can see the subtimings you need from the Intel XMP profile right in the Crosshair VI BIOS.
 
I'm not at sure why AMD doesn't read the XMP data on the sticks and fill in the appropriate sub-timings for you.  These current BIOS just are NOT that smart yet.  Even when you do this some "tweaking" is involved to get other timings optimized.
 
Here are my current results attached both in terms of performance, and the actual timings I have.  I'll make a new post here on what I did when I have the time, but the information I've given you can get you down the road.  Again, if you don't want to use the AGESA 1.0.0.6 beta BIOS to get there, you'll have to wait until ASUS s-l-o-w-l-y rolls out new production BIOS for the Crosshair VI.
 
 
 
 

Some further notes:
 
I have to set voltage to 1.4 or higher on the RAM to do this.
SOC is 1.15.
ProcODT is now at 68.6
Set retries to 5 in the AMD CBS UMC options.
I use Auto for GearDown and Command Rate these days.
BankGroupSwap also on Auto.
 
If you have the B-die variant, you can likely not have to do any of this (see jjohnthedon1's post).  This is the great confusion on this memory: some people will tell you to just set D.O.C.P. and it works for them, and others it never works.  I'm in the latter with my E-die and D.O.C.P. to me means "Doesn't Operate Computer Properly"...
 
So a Corsair stick is not a Corsair stick -- by that I mean that only ones of the same version can be compared within the same SKU.
 

Oh, Tom, you brought me back from a nice dream where I did not read forums and get mad at trolls and fan-boi types, lol.  I have been off the forums for awhile now and only came back to some with the release of Ryzen.. and then I've avoided them again.  So full disclosure: cranky old man who doesn't suffer fools gladly, even myself, lol.
 
Okay, off the soap box now.
 
First off, something about Corsair: they market the same product with different chips in order to hit demand.  Corsair sells more memory than anyone else.  Part of knowing what to do is knowing what you have and that can be an issue.  One thing you will notice is that Corsair kits often have a "version number" attached and that's an indication of what's used.  You don't see this so much on other products that tend to have only one hardware type per SKU.
 
Dominator Platinum have apparently used both Samsung and Hynix chips, but the ones I'm familiar with use Samsung D-die, E-die or B-die chips.  The E-die versions are dual-rank (due to lower density) and harder to get "up to speed".  I'm using CMD16GX4M2B3200C16 version 4.24 which are Samsung, dual-rank, E-die.  Version 4.31 of my kit are supposed to be B-die.  
 
I have been able to get these E-die variants up to speed since beta BIOS 9943/9945 and the succeeding beta BIOS which are based on AGESA 1.0.0.6.  I'm currently running beta 1403 with stable 3200 mhz memory on a low-spec 1700 non-X which will only go to 3800 mhz reliably.  It does involve manually setting many of the sub-timings exposed with the 1.0.0.6 AGESA.
 
What I will do is update a post I did on the ASUS forums about this with my latest information and put it on this forum.  But you can see my original post on how to do this over here: 
 
https://rog.asus.com/forum/showthread.php?93472-Get-Corsair-Dominator-CMD16GX4M2B3200C16-Up-to-Speed
 
You do NOT need Thaiphoon Burner as you can see the subtimings you need from the Intel XMP profile right in the Crosshair VI BIOS.
 
I'm not at sure why AMD doesn't read the XMP data on the sticks and fill in the appropriate sub-timings for you.  These current BIOS just are NOT that smart yet.  Even when you do this some "tweaking" is involved to get other timings optimized.
 
Here are my current results attached both in terms of performance, and the actual timings I have.  I'll make a new post here on what I did when I have the time, but the information I've given you can get you down the road.  Again, if you don't want to use the AGESA 1.0.0.6 beta BIOS to get there, you'll have to wait until ASUS s-l-o-w-l-y rolls out new production BIOS for the Crosshair VI.
 
 
 
 

Understood.  When I do the full post on this hopefully it will result in a "step-by-step" you can try to see if you can get there.
 
By the way, this is one of the problems I have with ASUS and AMD: from their marketing, this is all easy and you are buying the highest quality system and it looks plug-and-play -- but man that's not reality right now.
 
I get mad at trolls who shame the newbies, and the manufacturers who neither apologize nor fix their shite in a timely manner.  Like I said: I'm old and crotchety.

I apologize then, but you should have read some of the posts -- already suggested.
 
No, Ryzen's memory issues are FAR from sorted, lol.
 
Intel is SOOOOOO far ahead of AMD in DDR4.  It's actually at times shocking.  And this from someone who actually likes the AMD platform, lol.

Somewhat true: but not for certain DDR4 chips (as opposed to DIMM makers).  The same chips which would run at "rated overclock" (an interesting term in and of itself) on Intel won't on AMD without large amounts of hand tweaking.  I have to tweak about 10 parameters that SHOULD either come from the XMP profile (read automatically by the BIOS, FFS), or get set less conservatively during training.  This is true even on 1.0.0.6.  In fact, you can't even get some sticks up to speed prior to that and it's still not a production BIOS for my mobo.
 
That's the situation.  You're right it's better, but it's NOT fixed by any stretch of the imagination.

Well, you are pulling us out of the woodwork, one Ryzen user at a time, lol.  I joined to say thanks and that this is one of the cleanest, easiest to understand single posts on this subject.  The information is often available by an OP who doesn't communicate quite as well as you do, or it's spread through a discussion that you kind of have to dig out.
 
My only constructive criticism would be that in the step where you do the math for the offset your result is incorrect.  The result as you showed the calculation should be 0.23125.  But I think the error comes from using 1.118... instead of 1.18... for the core base voltage.  Your result is correct when using the larger number so it's just a boggled number in the post.  I'd like a dollar for every time I've done something similar, lol.
 
Again, thanks!
 

Hi everyone i'm just throwing this up as hopefully a short and easy to understand guide to p state overclocking on the crosshair vi hero motherboard (AM4/Ryzen). First of all don't be turned away if you don't have the crosshair! Most of this guide features the AMD common bios which should be common across motherboards (it is just up to your board manufacturer which options to make available in their BIOS).
 
Why should you want to do this? Well as you may has noticed if you have overclocked your powerful new ryzen cpu that it no longer downvolts/downclocks when idle . This is because this is a fixed all core overclock. Which while good for performance, it is bad for: the cpu's lifespan, excess heat generation when idle and your electricty bill. A power state or "p state" overclock however will not only enable you to overclock above stock speeds but also step back down when idle (similar to Intel's speedstepping).
 
Crosshair specific info:
- This should be working on any BIOS revision later than and including 1002 (which at the time of writing is 1002, 0079, 0081, 0082 and 0083)
- Update 0081 and later should be working with custom BCLK values (though i personally haven't tested this yet), 1002 must use default BCLK.
 
As above i'm using the crosshair vi hero motherboard and BIOS revision 0082 but this should be fairly similar across manufacturers:
 
Step 1: Always best to start with a clean slate so head into the bios and hit "load optimised defaults"
 
 
Step 2: Head to the extreme tweaker screen and check everything is back to default and most importantly that the cpu core ratio is on "auto"
 
 
Step 3: Head to the advanced tab and open the AMD common bios specification or "AMD CBS" for me
 
 
Step 4: Next open "Zen Common Options"
 
 
Step 5: Head down to "Custom Core Pstates" As you can see I left all above options on auto but you might want to force enable "Global C-State Control"
 
 
Step 6: Accept the terms (this is no more dangerous than a fixed all core overclock so don't worry)
 
 
Step 7:  Pstate0 will be set to auto by default, change this to custom
 
 
Step 8: Setting Pstate0 to custom reveals 5 boxes, 3 of which can be changed by the user and the top 2 greyed out boxes show the results. It gets a little complicated here because we are using hexadecimals. we are going to try a 3.9GHz overclock in this guide. Change Pstate0 FID to "9C", do not touch DID or VID, DID is the divisor there is no need to change this and VID is the voltage. We could change VID but at the moment anything different from the default VID breaks it and it will boost 100% of the time. (3A on my 1700 - if this is different for you please use YOUR default value NOT mine)
 
I will add a table to calculate your FID values soon TM   File is now attached: Ryzen Hex Values.xlsx
 
Note: Voltage is in micro volts so that is 1.187500V and not 1187500V (Take a note of this number btw it will help later for the offset)
 
LEAVE ALL OTHER P STATES ON "Auto"
 
 
Step 9: Head back to the extreme tweaker tab because we now need to set the voltage offset. Change the CPU Core Voltage to "Offset mode" and positive "+" Now from your manual OC which you have probably dont prior to this you will know what voltage you need to be stable at 3.9GHz, for me this is 1.3375V but its always good to be a little generous when using offset instead of manual so i'm going to allow 1.35V maximum. To calculate your offset voltage take the desired value and subtract the voltage value that you noted down in the previous step. 1.35V - 1.1875V = 0.16250V
 
Note: My RAM speed and RAM voltage have defaulted to 2133 and auto, leave these as they are and redo your RAM overclock once you are happy with what we are focusing on here.
 
 
Step 10 (Optional): Enter "Extreme Tweaker\External Digi+ Power Control" and give the CPU voltage and SOC voltage some load line calibration to reduce V droop, personally I like level 2. Although this step is entirely optional!
 
Step 11: Boot! Yeah we aren't done yet sorry  Change your Power plan to "high performance" (May also work for AMD Ryzen Balanced plan - untested) or "Ryzen Balanced" (now confirmed to be working) and edit the plan -> change advanced power settings -> expand "Processor Power Management" -> expand "Minimum Processor State" -> set this at 20%
 
Change Log:
 
20/04/17 - Release
20/04/17 - Added Hex Value Calculator
17/05/17 - Minor Text Changes & Confirmation of Ryzen Balanced Plan
 

it works!!!
 
i created this account just to say: thank you!
 
i tried two different methods:
1. changing the VID in P0 => did not clock over 2,7GHz (default on my 1700 in P1)
2. changing the FID & VID in P0 and P1 => did not clock down lower than P0
 
AMD Ryzen Balanced plan does not work => it doesn't clock up to P0
 

Thank you I hope it helped  I will see if it needs updating once we get the latest microcode from AMD in the next BIOS. We should be able to adjust VID then. Also yes you are indeed correct well spotted hawkeye  fixed it  

Ha ha! Well thanks for taking it well.  There are folks that no matter how nicely you point out an error they get all weird, lol.
 
It worked STUNNINGLY well.  I'm just doing 3.8 ghz at 1.35 volts on a Ryzen 1700 and the difference in power input to my box measured with a "Kill-A-Watt" meter is from over 120 watts at idle to about 80 watts at idle.  Nice power savings when the computer is just sitting there.
 
I'd used a guide previously but it only got my clock changing.  Somehow I never picked up how to use the offset voltage mode properly for this and how to calculate it.  Like I said, your document just gelled everything for me.  Very happy with the results.  Using the Ryzen Balance plan with the minimum set to 20% and my benchmarks are returning the same numbers as when I had a static overclock.
 
I linked this over on the ASUS forum so hopefully you'll help a few more lost souls.

Yeah I have noticed no performance drop, though must admit I haven't measured power at the wall so that was interesting. Edited OP as 2 people have now confirmed Ryzen Balance Plan is now working.
 
Thanks for spreading it, I check the ASUS ROG forum for the latest BIOS but I don't post there.

Just an update to the Ryzen Balanced Plan -- I stopped using it but it only affected ONE game and it's a game with many issues: No Man's Sky
 
For some reason under the Ryzen plan, the sound would occasionally cut off then come back and sometimes lock the game up entirely though the computer overall was still responsive.  I was worried that it was the p-state overclock but apparently not since reverting to the Windows High Performance plan solved the issue.  
 
I set the minimum processor state to 20% on the Windows plan just like the Ryzen plan and I really can't tell any difference between the two.  Power during idle still drops down to around 80 watts going slight plus or minus that as background stuff runs and idles.
 
Still, that's the only issue I've had so far and I'm thinking it's likely related more to how the game marshals resources than the plan itself.