Adventures in 2700X Overclocking

DuronBurgerMan I take it they can't handle 3000 @ 14-15-15-35? Even with a small DRAM voltage bump to like 1.37V (not sure what you currently have it set to)?

I'm no RAM aficionado but if you post that RyzenTimingsChecker shot, I may be able to point out some things I've read about for you to change, if they aren't already.

Here you go. And no, voltage bump didn't help. It helped to get 3000 CL16 stable (1.36v instead of 1.35), but was no help going lower on the latency at that clock speed, or in getting any additional clockspeed over 3000.
 

Attachments

  • timing.jpg
    timing.jpg
    466.4 KB · Views: 0
For reference:

Average OC on air 4125MHz
Average OC on watter 4291MHz

HWBOT averages with 233 samples.
 
For reference:

Average OC on air 4125MHz
Average OC on watter 4291MHz

HWBOT averages with 233 samples.

How many of those air OCs are on the stock cooler, though?

Second value sounds about right. I'm using a pretty high end air cooler - equals some of the lesser AIO coolers. And I pulled 4.3 out of it. This turned out to be in the top 1% of all benches on userbenchmark though, so I may have a better sample.

http://www.userbenchmark.com/UserRun/8424911
 
For reference:

Average OC on air 4125MHz
Average OC on watter 4291MHz

HWBOT averages with 233 samples.
I would be more interested in the top two core max OCs using PB2 for increasing IPC (instructions per core) and not all the cores. For single threaded calculations that is what matters. When you are doing all cores then you are limited to the slowest core overall. So for the slowest core, average is around 4.3ghz on water - what about the top two cores? 4.5ghz? 4.6ghz+?
 
I dont think it works that way. It will not increase xfr2 speeds.
With BCLK OCing it does. AMD got rid of the OC mode restriction on BCLK changes or allowed some wiggle room there. Not sure if one can take it up to 130hz and not be in OC mode.
 
Yikes... That's a whole lotta volts... Sounds like either Duron knows more about what he's doing that they do, or he ended up with a golden chip when comparing to their results >_> Especially considering they aren't using any air coolers.

DuronBurgerMan, Original Post: "Okay so for the lulz I bought a 2700X and dropped it into my Asus Prime X370 Pro board today. <snip>. Note, I am running a Noctua U12 air cooler, so I imagine folks on water will do better."

DuronBurgerMan, Second Post: "Second attempt: 42x multiplier, Vcore @ 1.365. 4.2GHz total.

Booted to Windows. Appears fully stable at this vcore. Ran Cinebench successfully (score: 1883). Will conduct burn test later to verify stability."


Seems like their SOP is: Buy Ryzen. Insert in motherboard. Boot with voltage at 1.425V. Find max stable overclock at said voltage. Re-test in next motherboard until no boards left. Done. CONSIDER IT BINNED!
No bother of finding if it'd handle a lower voltage? :(

I just approach it from the other end. Incrementally increase voltage at a given speed until stable. If more voltage headroom still exists, try next highest multiplier. Keep going until I hit a wall, which with this CPU was 4.3.

Since Silicon Lottery has to bin a LOT of chips, I'm sure, this is probably inefficient for them. So they just set max voltage right away and check for a couple pre-defined speeds, and call it a day.

Edit: it still could be a golden sample, but I've seen enough other 4.3+ overclocks on the 2700X to think it's not THAT rare. Guru3d got 4.4 out of theirs (on water). Anand got 4.35. Both were unstable for me at any reasonable voltage. Though I'd be curious what other [H]ard folks are getting.
 
Last edited:
I just approach it from the other end. Incrementally increase voltage at a given speed until stable. If more voltage headroom still exists, try next highest multiplier. Keep going until I hit a wall, which with this CPU was 4.3.

Since Silicon Lottery has to bin a LOT of chips, I'm sure, this is probably inefficient for them. So they just set max voltage right away and check for a couple pre-defined speeds, and call it a day.

Edit: it still could be a golden sample, but I've seen enough other 4.3+ overclocks on the 2700X to think it's not THAT rare. Guru3d got 4.4 out of theirs (on water). Anand got 4.35. Both were unstable for me at any reasonable voltage. Though I'd be curious what other [H]ard folks are getting.
I just see it as if they are going to provide this service to begin with, then they ought to be putting in that effort. Pretty much any yahoo can chuck a Ryzen into a board and get what they are lol What they've done hasn't really binned anything. Showing that it can do a speed at a reasonable voltage, well now you're starting to determine something! :)

I dunno, I just feel like it's a bit of a ripoff to buy a Ryzen from them. And who knows, this could just be due to them having experience with Intel, meaning they'll hone their process in time *shrug*
 
After messing with overclocking which I have done for nearly 20 years on everything I have ever owned.. this is the first time I feel no need to OC.. even for fun it seems pointless. I wonder when Precision Boost overdrive is going to become an option.. it might be the little extra boost we all want without having to tweak for it.
 
After messing with overclocking which I have done for nearly 20 years on everything I have ever owned.. this is the first time I feel no need to OC.. even for fun it seems pointless. I wonder when Precision Boost overdrive is going to become an option.. it might be the little extra boost we all want without having to tweak for it.
I don't know if it's my age that has imparted this upon me, or if it's wisdom, or... what... lol However, personally, CPU overclocking has not been as fun as it had been back with the S939 A64 and X2's. So I kinda welcome that PB2 can do it all and save me from having to bother. I find, these days, that DRAM is more enjoyable to tinker with, and at least with Ryzen it's a rewarding endeavor with it having a real impact on the performance.

The gains in clock were really not much more than what we're seeing now, 300-500MHz (on the high end Ryzens), so it's not that in which I feel anything is lacking.
No, it seems like there was just more accomplishment in it back then. You needed a chip that could handle the overclock, which then was pure FSB due to locked multipliers, though the chipsets weren't really picky back then so could handle substantial increases in clock. Then you needed to massage out a higher HyerTransport speed, as that actually was actually of benefit in those days. THEN you needed to squeeeeeze out higher memory clocks. When all of that was dialed in... finally you had DRAM timings!

Funnily enough, I still have my old sig from back then. (Dragon came from a screenshot I took in pre-expansion WoW, took awhile to PShop it heh)
dragonsig.jpg

I ran that system right up until 2009 when we moved, where my 8+yr old Corsair 430W PSU (that had seen basically 8yrs of continual nearly 24/7 service) packed it in and took out the board AND chip :( Sad day...


Fun Fact: The Infinity Fabric is pretty much just a renamed built upon the original HyperTransport interconnect, so part of the A64 lives on in the beast that is Ryzen. [Wasn't originally an accurate statement, so it's been worded properly now ;)]

I think if we had the ability to change the IF's divisor, and give it the ability to run at various other speeds, up to the 1:1 with DRAM that Eng samples ran with... that it'd restore some of that olden fun that A64 had. As much as I'd like to say that I wish MSI's Titanium had FSB OC options, these days the FSB (on AMD's systems) are way too integrated and open to causing other problems. So unless AMD takes another page from Intel's book and makes everything unlinked, so that we don't have to worry about our nVME SSDs corrupting at >105FSB heh
 
Last edited:
So unless AMD takes another page from Intel's book and makes everything unlinked,

DIdn't higher-end Ryzen boards have separate DRAM clock generators so as to allow additional memory clock flexibility without affecting the rest of the system?
 
DIdn't higher-end Ryzen boards have separate DRAM clock generators so as to allow additional memory clock flexibility without affecting the rest of the system?
I'm not certain. That'd be the first time I've heard of that beyond something similar sounding that ASRock did on... Taichi and/or Fatal1ty Ryzen boards. I just recall some feature being talked up that was intended to make like better in that regard. Whether or not all that is, is a stand-alone BClk gen (as giga mentioned) or something actually more in ASRock's case, I have no clue... Alas, my Titanium lacks an independent clock gen completely, so I can't raise or lower. (Now, I did find in the BIOS a functional option that does allow BClk on the Titanium, but it is limited to 103MHz, and I speculate that all this does is tap into Ryzen's internal clock-gen and is really nothing more than what mobo makers use in order to fine-tune their board to running as close to 100MHz for BClk. 103MHz wasn't stable in my initial testing, and 102MHz was mostly-stable. The increase in performance was too negligible to bother, in the end.)

If you ARE talking about BClk, which did help people attain higher memory clocks by using lower memory speeds (and thus some internal timings), then yes that did help.
However, that is exactly what I mentioned as causing nVME SSD corruption, at least for The Stilt, when he tried going over 105MHz, since it increased the clock on the PCIe bus due to everything being linked together.

I'm not sure if motherboard makers have he ability to designate a clock-gen for each thing or not anymore, with us having moved to SoC designs. These days you see very few crystals on motherboards heh And not just because they've changed in appearance to also coming in tiny flat SMD components, they just seem to run off a more unified source. Sorta shame-on-AMD with this, considering the impact that overclocking BClk can have on subsystems, which their Llano on FM1 exhibited with the SATA controller. If you wanted to achieve higher speeds you had to disable AHCI and run the controller in IDE Mode. The fix now is to drop the PCIe protocol down a version. Gen 3 I think flakes out at 107MHz, and running with a max of Gen 2 affords you a higher frequency window, albeit at a drop in bandwidth... So the tradeoff from higher memory speed doesn't currently seem to merit the drop in PCIe bandwidth or stability, considering most of us are starting to adopt nVME drives!
 
I just see it as if they are going to provide this service to begin with, then they ought to be putting in that effort. Pretty much any yahoo can chuck a Ryzen into a board and get what they are lol What they've done hasn't really binned anything. Showing that it can do a speed at a reasonable voltage, well now you're starting to determine something! :)

I dunno, I just feel like it's a bit of a ripoff to buy a Ryzen from them. And who knows, this could just be due to them having experience with Intel, meaning they'll hone their process in time *shrug*

Fair point. I don't buy anything from them for this reason. Don't feel like paying a premium for that. I just roll the dice and see how it goes. But their service could be useful for some, I suppose.
 
If you look at Der8auer's voltage/clockspeed graph in the video below (around 1:20 in), note that he had almost exactly the same results I did on the scaling curve. 1.425 vcore bought him 4300MHz. But even going up to 1.5 did not result in any additional gains. My results were 1.406 got it *mostly* stable (passed Cinebench & Blender) - but not stable in prime or the burn test. 1.420 was required for prime & burn test. At this vcore, temps were a bit scary for long term use with this Noctua cooler. So 4.3 remains the ceiling at reasonable voltage (supposing you think 1.42 is reasonable), unless your sample is really good, in which case you may be able to get 4.35 or 4.4 like Anand and Guru3d, respectively.

The Stilt observed that some of the individual cores will individually boost up to 4350 at a low vcore of ~1.37 - these are the 'good' cores. The shitty cores require as much as 1.47 (+ 100mV) to boost that high individually. So if you get lucky and your shitty cores are, perhaps, a little better, you may snag the 4.35 or 4.4. Otherwise, 4.3 is the ceiling. Some of the shittier CPUs seem limited to ~4.25. And I wouldn't go higher than 4.2 on the stock cooler or basic air cooling. It's good, yes - way better than most stock coolers - but not THAT good.

Either way, overclocking this chip doesn't seem worth it.

 
Is there enough of a difference in the process to make Ryzen2 vs Ryzen that in 6 months we need to review overclocking again to see if there is an improvement after AMD gets some experience making Ryzen2 CPUs?
 
Fun Fact: The Infinity Fabric is pretty much just a renamed HyperTransport, so part of the A64 lives on in the beast that is Ryzen.

not really :p
The Infinity Fabric consists of two separate communication planes - Infinity Scalable Data Fabric (SDF) and the Infinity Scalable Control Fabric (SCF). The SDF is the primary means by which data flows around the system between endpoints (e.g. NUMA nodes, PHYs). The SDF might have dozens of connecting points hooking together things such as PCIe PHYs, memory controllers, USB hub, and the various computing and execution units. The SDF is a superset of what was previously HyperTransport. The SCF is a complementary plane that handles the transmission of the many miscellaneous system control signals - this includes things such as thermal and power management, tests, security, and 3rd party IP. With those two planes, AMD can efficiently scale up many of the basic computing blocks.
 
Is there enough of a difference in the process to make Ryzen2 vs Ryzen that in 6 months we need to review overclocking again to see if there is an improvement after AMD gets some experience making Ryzen2 CPUs?
I'm not sure I fully understand what you are asking?

For starters, when you say "Ryzen2" are you talking about the 2000-series chips such as the 2700X? Or are you talking about what is, on the AMD roadmaps, called Ryzen 2?

This is an important distinction since the 2000-series chips are based on "Zen+" (thus, Ryzen+), and on an architectural level really is just some minor improvements overall (to improve latency, updates the core boost functionality, allows for higher memory clocks, etc).


The second clarification I'd need is: when you say "process", I presume you mean the manufacturing process (node) at which the chips are made on?
If so, then it's been a year since Ryzen came out, not 6 months, and it was made on the Global Foundries 14nm node (LPP, or Low-Power Plus, licensed from Samsung, and is the 'higher performance' sibling to LPE). Ryzen+ is made on a 12nm node, so lower power, less heat, potentially higher clocks --at least, provided that the ~4.1GHz wall we saw with Ryzen wasn't an architecture limit-- and so that naturally needs to be all tested again. BUT in addition to that small process shrink, Ryzen+ is now manufactured by..... ok nevermind! I just double checked and apparently wherever I originally read what I was about to say, was incorrect. So in case anyone else thought this: Ryzen+ is not made on TSMC's 12nm, it's still on GloFo's, their 12nm LP (Leading Process) which is again a process licensed from Samsung. And according to some digging, 14nm and 12nm are qualifiably "Half Nodes" since they aren't one of the official node sizes (16nm and 10nm being the closest).

And while there's arguably not a huge difference between the 14nm process and 12nm process, it still does merit overclocking tests (to spare further rambling, the nodes aren't technically processed entirely at this size, there are aspects that are, but other aspects that are sized more in line with those of the 16nm node). I mean there's always been room to increase clocks, which is sort of the entire point of overclocking. There are limitations of a design or node, but then there are what the CPUs get binned as being capable of... which is just an average of what their samples have been capable of achieving and thus can be sold as "stable at this frequency". Beyond that is where Boost comes in, as it's not a guaranteed speed, at least for any specific period of time.


Last clarification part for me: in regards to "AMD gets some experience making Ryzen2", are you asking about CPU Steppings? I don't believe we saw any with the original Ryzen. The closest thing we saw was the difference in manufacturing location between some of the 1700 (diffused in China I believe) and 1700X/1800X (diffused in Malaysia I believe), where the 1700 was being found to not quite able to achieve the same memory speeds as the X variants. This could all come down to the plant having sourced their chemicals from a different supplier. But that goes to show as well that if 12nm required different chemicals than 14nm, it is another reason for taking a look at overclocking. I seem to recall that being a case with the AthlonXP... but that's a long time ago, so details are sketchy haha Either way, new steppings still generally require retesting. The Athlon64 X2's saw improvements in this way, granted it was marginal, but it all adds up :)


All in all I have admittedly no doubt read too deep into your question, so hopefully something from my rambling answers your question :shame:


not really :p
I dunno man... Superset/Subset/Successor, it all, to me, means "heavily based on" for whatever it is the superset/subset/successor to. Considering the fact that the Wiki page for Infinity Fabric redirects to the HyperTransport page says a lot in my opinion. HyperTransport was, among other things, a high speed CPU-to-CPU interconnect. The Athlon X2 can be looked at as two CPU's (cores) on a chip, and thus the HT ferries data between them and the IMC (also on chip). Ryzen can be seen as two 4c CPUs on a chip, and the Infinity Fabric ferries data between them and the memory.

Granted, the HT in its original function and how it executed things was eventually replaced by the PCIe bus, but it was still called HT the entire time as far as I am aware. Which as far as I know, the Infinity Fabric has been said to be heavily interfaced with the PCIe bus as well.

It definitely seems like a matter of semantics, but for all intents and purposes, they seem more similar than dissimilar and so saying that it is "pretty much" --which implies for the most part, but not entirely-- a renamed HT isn't accurate to you? It's like the saying "If it walks like a duck and talks like a duck, it must be a duck" in my eyes lol

Not trying to say I'm right, just... more trying to explain how I reached this. If consensus is that no, it isn't, I'll happily edit my post! :D
 
I'm not sure I fully understand what you are asking?

For starters, when you say "Ryzen2" are you talking about the 2000-series chips such as the 2700X? Or are you talking about what is, on the AMD roadmaps, called Ryzen 2?

This is an important distinction since the 2000-series chips are based on "Zen+" (thus, Ryzen+), and on an architectural level really is just some minor improvements overall (to improve latency, updates the core boost functionality, allows for higher memory clocks, etc).


The second clarification I'd need is: when you say "process", I presume you mean the manufacturing process (node) at which the chips are made on?
If so, then it's been a year since Ryzen came out, not 6 months, and it was made on the Global Foundries 14nm node (LPP, or Low-Power Plus, licensed from Samsung, and is the 'higher performance' sibling to LPE). Ryzen+ is made on a 12nm node, so lower power, less heat, potentially higher clocks --at least, provided that the ~4.1GHz wall we saw with Ryzen wasn't an architecture limit-- and so that naturally needs to be all tested again. BUT in addition to that small process shrink, Ryzen+ is now manufactured by..... ok nevermind! I just double checked and apparently wherever I originally read what I was about to say, was incorrect. So in case anyone else thought this: Ryzen+ is not made on TSMC's 12nm, it's still on GloFo's, their 12nm LP (Leading Process) which is again a process licensed from Samsung. And according to some digging, 14nm and 12nm are qualifiably "Half Nodes" since they aren't one of the official node sizes (16nm and 10nm being the closest).

And while there's arguably not a huge difference between the 14nm process and 12nm process, it still does merit overclocking tests (to spare further rambling, the nodes aren't technically processed entirely at this size, there are aspects that are, but other aspects that are sized more in line with those of the 16nm node). I mean there's always been room to increase clocks, which is sort of the entire point of overclocking. There are limitations of a design or node, but then there are what the CPUs get binned as being capable of... which is just an average of what their samples have been capable of achieving and thus can be sold as "stable at this frequency". Beyond that is where Boost comes in, as it's not a guaranteed speed, at least for any specific period of time.


Last clarification part for me: in regards to "AMD gets some experience making Ryzen2", are you asking about CPU Steppings? I don't believe we saw any with the original Ryzen. The closest thing we saw was the difference in manufacturing location between some of the 1700 (diffused in China I believe) and 1700X/1800X (diffused in Malaysia I believe), where the 1700 was being found to not quite able to achieve the same memory speeds as the X variants. This could all come down to the plant having sourced their chemicals from a different supplier. But that goes to show as well that if 12nm required different chemicals than 14nm, it is another reason for taking a look at overclocking. I seem to recall that being a case with the AthlonXP... but that's a long time ago, so details are sketchy haha Either way, new steppings still generally require retesting. The Athlon64 X2's saw improvements in this way, granted it was marginal, but it all adds up :)


All in all I have admittedly no doubt read too deep into your question, so hopefully something from my rambling answers your question :shame:



I dunno man... Superset/Subset/Successor, it all, to me, means "heavily based on" for whatever it is the superset/subset/successor to. Considering the fact that the Wiki page for Infinity Fabric redirects to the HyperTransport page says a lot in my opinion. HyperTransport was, among other things, a high speed CPU-to-CPU interconnect. The Athlon X2 can be looked at as two CPU's (cores) on a chip, and thus the HT ferries data between them and the IMC (also on chip). Ryzen can be seen as two 4c CPUs on a chip, and the Infinity Fabric ferries data between them and the memory.

Granted, the HT in its original function and how it executed things was eventually replaced by the PCIe bus, but it was still called HT the entire time as far as I am aware. Which as far as I know, the Infinity Fabric has been said to be heavily interfaced with the PCIe bus as well.

It definitely seems like a matter of semantics, but for all intents and purposes, they seem more similar than dissimilar and so saying that it is "pretty much" --which implies for the most part, but not entirely-- a renamed HT isn't accurate to you? It's like the saying "If it walks like a duck and talks like a duck, it must be a duck" in my eyes lol

Not trying to say I'm right, just... more trying to explain how I reached this. If consensus is that no, it isn't, I'll happily edit my post! :D



Superset means it contains the thing it is a superset of meaning, HT is only a part of, one of the parts of, what makes up IF.

IT's like saying PCI-E is just PCI renamed. :D
 
I'm not sure I fully understand what you are asking?

For starters, when you say "Ryzen2" are you talking about the 2000-series chips such as the 2700X? Or are you talking about what is, on the AMD roadmaps, called Ryzen 2?

This is an important distinction since the 2000-series chips are based on "Zen+" (thus, Ryzen+), and on an architectural level really is just some minor improvements overall (to improve latency, updates the core boost functionality, allows for higher memory clocks, etc).


The second clarification I'd need is: when you say "process", I presume you mean the manufacturing process (node) at which the chips are made on?
If so, then it's been a year since Ryzen came out, not 6 months, and it was made on the Global Foundries 14nm node (LPP, or Low-Power Plus, licensed from Samsung, and is the 'higher performance' sibling to LPE). Ryzen+ is made on a 12nm node, so lower power, less heat, potentially higher clocks --at least, provided that the ~4.1GHz wall we saw with Ryzen wasn't an architecture limit-- and so that naturally needs to be all tested again. BUT in addition to that small process shrink, Ryzen+ is now manufactured by..... ok nevermind! I just double checked and apparently wherever I originally read what I was about to say, was incorrect. So in case anyone else thought this: Ryzen+ is not made on TSMC's 12nm, it's still on GloFo's, their 12nm LP (Leading Process) which is again a process licensed from Samsung. And according to some digging, 14nm and 12nm are qualifiably "Half Nodes" since they aren't one of the official node sizes (16nm and 10nm being the closest).

And while there's arguably not a huge difference between the 14nm process and 12nm process, it still does merit overclocking tests (to spare further rambling, the nodes aren't technically processed entirely at this size, there are aspects that are, but other aspects that are sized more in line with those of the 16nm node). I mean there's always been room to increase clocks, which is sort of the entire point of overclocking. There are limitations of a design or node, but then there are what the CPUs get binned as being capable of... which is just an average of what their samples have been capable of achieving and thus can be sold as "stable at this frequency". Beyond that is where Boost comes in, as it's not a guaranteed speed, at least for any specific period of time.


Last clarification part for me: in regards to "AMD gets some experience making Ryzen2", are you asking about CPU Steppings? I don't believe we saw any with the original Ryzen. The closest thing we saw was the difference in manufacturing location between some of the 1700 (diffused in China I believe) and 1700X/1800X (diffused in Malaysia I believe), where the 1700 was being found to not quite able to achieve the same memory speeds as the X variants. This could all come down to the plant having sourced their chemicals from a different supplier. But that goes to show as well that if 12nm required different chemicals than 14nm, it is another reason for taking a look at overclocking. I seem to recall that being a case with the AthlonXP... but that's a long time ago, so details are sketchy haha Either way, new steppings still generally require retesting. The Athlon64 X2's saw improvements in this way, granted it was marginal, but it all adds up :)


All in all I have admittedly no doubt read too deep into your question, so hopefully something from my rambling answers your question :shame:



I dunno man... Superset/Subset/Successor, it all, to me, means "heavily based on" for whatever it is the superset/subset/successor to. Considering the fact that the Wiki page for Infinity Fabric redirects to the HyperTransport page says a lot in my opinion. HyperTransport was, among other things, a high speed CPU-to-CPU interconnect. The Athlon X2 can be looked at as two CPU's (cores) on a chip, and thus the HT ferries data between them and the IMC (also on chip). Ryzen can be seen as two 4c CPUs on a chip, and the Infinity Fabric ferries data between them and the memory.

Granted, the HT in its original function and how it executed things was eventually replaced by the PCIe bus, but it was still called HT the entire time as far as I am aware. Which as far as I know, the Infinity Fabric has been said to be heavily interfaced with the PCIe bus as well.

It definitely seems like a matter of semantics, but for all intents and purposes, they seem more similar than dissimilar and so saying that it is "pretty much" --which implies for the most part, but not entirely-- a renamed HT isn't accurate to you? It's like the saying "If it walks like a duck and talks like a duck, it must be a duck" in my eyes lol

Not trying to say I'm right, just... more trying to explain how I reached this. If consensus is that no, it isn't, I'll happily edit my post! :D


I was wondering if the 12nm Ryzen2 (based on Zen+) is a sufficiently different process that after half a year to improve yields and fine-tuning of manufacturing that there could be enough improvement to see if overclocking would improve. If Ryzen2 is based only on a small tweaked version of the 14nm process used to make Ryzen then there may be little to no improvement as they have been pounding them out for a year now. I'm curious because if there is unlikely to be any more overclocking room on the Ryzen2 then a 2800X SKU is unlikely as it is clear AMD built and shipped the 2700X already at optimal performance.

I'm kind of torn about it because I need to replace my ESXi server (dual X5650's, unsupported in ESXi 6.7) - I wanted to wait for a Zen2-based Threadripper (not Zen+), but I need to keep up with ESXi as it is used by the company I work for and I don't want to fall behind in case a higher position opens up. I am deeply concerned that ESXi 7 will kill support for everything Haswell and lower, which is why I haven't been seriously thinking about a used server as the law of diminishing returns starts to come into play. I can wait until the 2nd gen Threadripper hits the market, just hoping that AMD's new design doesn't have to make too many compromises to stick 16 cores/32 threads on a single CPU.
 
I was wondering if the 12nm Ryzen2 (based on Zen+) is a sufficiently different process that after half a year to improve yields and fine-tuning of manufacturing that there could be enough improvement to see if overclocking would improve. If Ryzen2 is based only on a small tweaked version of the 14nm process used to make Ryzen then there may be little to no improvement as they have been pounding them out for a year now. I'm curious because if there is unlikely to be any more overclocking room on the Ryzen2 then a 2800X SKU is unlikely as it is clear AMD built and shipped the 2700X already at optimal performance.

I'm starting to think there IS room. Not so much from the process - I think AMD and GloFo extracted as much from this process as is possible *directly*. But given how some of the cores boost to 4350 at much lower vcore than other cores on the 2700X, I suspect there is room for a higher model after sufficient binning. Maybe a HEAVILY binned 4.0 base/4.45-4.5 boost 2800X with just a hair more performance. One with an OC wall of 4.4 all core instead of 4.3. Of course, we may see that on the Threadripper platform anyway, since those are usually top binned dies.

Such a processor wouldn't be much faster than the 2700X, all things considered, but may be possible to bin if Intel gets out an 8 core Coffee Lake S chip early enough to cause trouble for AMD. Otherwise, though, I'd bet AMD wouldn't go to the trouble and would just wait for Zen 2.
 
Superset means it contains the thing it is a superset of meaning, HT is only a part of, one of the parts of, what makes up IF.

IT's like saying PCI-E is just PCI renamed. :D
Aaaalright lol Fair enough ;)
Instead of "is just a renamed HT", would "is an evolution of HT" be acceptable? :p
 
What are you benching these overclocks against?

Nothing? I'm just doing fucking with it for the lulz. I don't even run it OC'd day-to-day, because there's not much point.

I guess I just miss overclocking and tinkering and shit. I spoke about that in one of the other threads earlier.
 
DuronBurgerMan I take it they can't handle 3000 @ 14-15-15-35? Even with a small DRAM voltage bump to like 1.37V (not sure what you currently have it set to)?

I'm no RAM aficionado but if you post that RyzenTimingsChecker shot, I may be able to point out some things I've read about for you to change, if they aren't already.

Mind giving me some pointers?
 

Attachments

  • My Timings.JPG
    My Timings.JPG
    68 KB · Views: 0
Mind giving me some pointers?
I wish I knew more about squeezing out performance on RAM to be honest :p Some important factors though would be to let us know what model kit you have and then if they're Single or Dual Rank sticks (CPU-Z tells you in the memory tab).

I have a feeling that they're Hynix ICs though, based on those timings (if you are really interested in finding out for certain you can do so with Typhoon Burner, I posted how to in the old Ryzen memory speeds thread if you need assistance finding it). So I'm not specifically sure how much luck you'd have with my suggestions in terms of how well they'll carry over from my Samsung B IC sticks.

That being said, are those timings currently with everything set to Auto, or did you manually input them? (I only ask because they're, curiously, identical to Duron's lol).
If not, that'd be my first request, is a screenshot with auto-timings. That's our baseline, and lets us know where we're starting from. Otherwise I don't know how far you've tweaked them already and one tick more might equal instability :)

As far as overclocking the RAM... If you haven't tried faster speeds with Auto-Timings, that's my initial suggestion. Bump the SoC voltage and DRAM Voltage a little (see AMD guide linked below for safe limits) and try 3000 or the next speed higher. For 3000 you can probably just try it with those timings you're at currently, but higher speed, definitely try with Auto-timings. But when it comes to changing tthe termination values, I'm not the person to ask :(

But to at least offer something to start with...
First you'll want to have a memory benchmark so you can determine if you've increased performance. So either with the RAM configured as it is in that screenshot or with auto-timings, get a few passes on that to get a baseline. I used AIDA64's CacheMem test (it's in the Tools drop down menu), since it gives the Read, Write and Latency results for RAM, L1, L2 and L3 caches. So it knocks them all out rather quickly AND lets you easily save a screenshot of it.

I'd then try Disabling the GearDownMode, give it a quick stability test (either MemTest or AIDA64's System Stability Test set only to "Stress Cache" and "Stress System Memory", which I found identifies stability fair well). Then run the benchmark to see if it helped, and how much. If it didn't really help at all, then might be better to leave it on to ensure stability.
Next I'd see if you can try to lower the tRRDS and tRRDL. You could try 4 and 6. Re-test.
I'd try then to drop the tFAW, maybe 28 (mine's at 25). Re-test.
Seeing if you can knock that tWR down as well will help a decent bit. Just whittle it away slowly, but could try 20 to start with. (mine's at 11). R-t!
As I recall the tRDRDSCL and tWRWRSCL don't impact stability much, but can help a tiny bit with latency, an can be dropped fairly low. Mine are at 2 and 2, so maybe try 4 and 4 with yours.
If you can get the tRFC down then it helps with latency mostly (I think, maybe it was bandwidth). I don't know if there's a method to calculating the number though :( If you want to try mine, have at it: 312 (or 195ns)
GENERALLY LEAVE tWCL ALONE. Is finicky and can impact stability. Typical rule of thumb is 1:1 with tCL
tRTP, tRDWR and tWRRD can result in decent gains, but you may only be able to lower tRTP a tiny bit without impacting stability. Could try 10 or 9. (mine's at 9)

Beyond that, you can definitely always try the primary timings. However, until they allow for odd numbered tCL's again, it might not yield much stability since you'd have to drop back to tCL 14 for it to work. However, you can definitely give 16-16-16-36 a shot, or even 14-16-16-36. Those may require increasing the DRAM voltage in order to get working. I mean realistically the subtimings could even benefit from a little bump. I'm not sure what you're running at currently, if it's like most of the GSkill kits, for 3000 it might just be 1.3V, but either way just start with adding a little bit... so like +0.02V (1.32V in this example). But I bought a CL15 kit so for me to get CL14 working is more likely in my eyes, than you having to go to the next even number down which is also 14.


Something always to keep in mind, though, is that a lot of those timings have a 'mate'. They're grouped pretty well in RyzenTimingChecker and so you can see that rather easily. Not always do they require the name initial letters though, like tRDWR and tWRRD are kinda mates, but tRTP plays a roll with them too. So you'll want to pay attention to the amount of distance between their numbers and then try to keep a similar gap in your adjustments. Those three it's a situation of (bottom to top) WRite to ReaD, ReaD to WRite, and Read To Precharge. So if you drop the tRTP down too low, it'll start wanting to do it's task before tRDWR has had a chance to finish.
This was a handy guide from AMD as it explains some of that, as well as a lot of other aspects:
https://community.amd.com/community/gaming/blog/2017/05/25/community-update-4-lets-talk-dram
This, albeit rather old, may help fill in some gaps as the terms still apply (note: not all of these will be available to you, and some may even have different letter combinations in your BIOS, even between RyzenTimingChecker and your BIOS!)
http://www.overclock.net/forum/18051-memory/381699-ram-timings-explained.html

Hopefully that'll help some. And yes, as it may sound, it is all time consuming, since you have to restart, adjust, boot, test, restart, adjust, boot, test... over and over ;) Daunting... but rewarding!
 
Last edited:
^^ Great tips for dialing in timings. It is indeed time consuming, especially on my board which refuses to post with bad timings (requiring a cmos clear every time). These are the timings I've ended up with on my kit (F4-3200C15D-16GTZ, cas15 single rank b-die). I can't seem to push higher than 3200, but I'm seeing a nice bump in performance with these tightened primary and subtimings versus the stock XMP profile. I started with settings from the Ryzen dram calculator and tweaked until I got things stable.

WnS7VPE.png
 
Here you go. And no, voltage bump didn't help. It helped to get 3000 CL16 stable (1.36v instead of 1.35), but was no help going lower on the latency at that clock speed, or in getting any additional clockspeed over 3000.
I'm not sure how I missed this originally, but I only noticed it last night while making the above reply, sorry about that! :(

I presume you tried disabling the GearDownMode as well? Though it no doubt is needed for that much RAM.

Also, how high did you try on the RAM Voltage? And what's your SoC (CPU_SOC or CPU_NB) voltages that you had tried?

Beyond that, a few of those sub-timing suggestions I made to Rauelius would apply to you, though as I"m sure most of what you have in the screenshot are already dialed in by you, I'd personally probably only be attempting to lower: tRC, tFAW, tWR and tRTP. Mine are: 54, 25, 11, and 9, respectively.

^^ Great tips for dialing in timings. It is indeed time consuming, especially on my board which refuses to post with bad timings (requiring a cmos clear every time). These are the timings I've ended up with on my kit (F4-3200C15D-16GTZ, cas15 single rank b-die). I can't seem to push higher than 3200, but I'm seeing a nice bump in performance with these tightened primary and subtimings versus the stock XMP profile. I started with settings from the Ryzen dram calculator and tweaked until I got things stable.

View attachment 72232
Given we seem to have the exact same kit, here are my 200% MemTest stable timings for comparison (1.36V just to keep them >1.35V), as I have a few subtimings that are tighter if you want to give them a go (and I could probably drop my tRTP and tRDWR a tick or two each as well):
3200-14-14-14-Stable.png
 
Given we seem to have the exact same kit, here are my 200% MemTest stable timings for comparison (1.36V just to keep them >1.35V), as I have a few subtimings that are tighter if you want to give them a go (and I could probably drop my tRTP and tRDWR a tick or two each as well):
View attachment 72246

Good stuff! I'll try lowering some of the subtimings (there's still quite a bit of room to move down - the ryzen dram calc extreme presets are even lower). Did you have any luck getting yours to 3466? I couldn't get mine stable no matter how much I pushed the voltage up or slackened the timings. Not sure if I'm running into IMC limitations or the memory itself.
 
Good stuff! I'll try lowering some of the subtimings (there's still quite a bit of room to move down - the ryzen dram calc extreme presets are even lower). Did you have any luck getting yours to 3466? I couldn't get mine stable no matter how much I pushed the voltage up or slackened the timings. Not sure if I'm running into IMC limitations or the memory itself.
Well you have a Ryzen+, I don't, so I can't really partake in the benefits of higher RAM speeds :( Which I'm pretty sure is a limitation of either my old BIOS (my setup has ran so beautifully I've not been bothered to update since last June!) with older AGESA, or my IMC. I bought this kit specifically because reviews on Intel platforms had been able to overclock them QUITE easily, and to very high speeds. Nevertheless, my adventures stop at 3333. I've gotten 3466 to POST only twice. First time was the absolute first time I tried the speed, and the second time was after a metric crapload of futzing about. That's why I stuck to dropping my timings instead heh

That being said, I did have some, albeit unstable, success with 13-13-13-34, which my notes show I used 1.39V on DRAM and 0.710V on DRAM VREF.

I'm sure my setup could achieve more, I just lack the know-how, and those that DO know how lack the willingness to share their secrets. Really sucks that overclocking has become a cut-throat competition with considerable winnings to be obtained through it, to make people be so tight lipped about these things :( I poked and prodded Chew* for a few months, reading his thread over at XtremeSystems, but after July of last year (annual month long vacation) I never went back to catch up, and there'd be pages and pages to catch up on by now :(

The little bit of help he was willing to share is what I'm in turn sharing with everyone else (to spare them from having to read through that thread, too heh), but I unfortunately lack real knowledge to be of further help to most people. The Termination strengths are no doubt an untapped path for a lot of us, but it's hard to find any info on what to try at what speeds and if you should go up, or down, or even what the Default is :\

At least it was that way as of mid-last year. There could be some guides up now, as I kinda stopped looking around and tweaking :p Given the new AGESA and BIOS for my Titanium, with a further wealth of features added, I may give it a shot again. Still sorta reluctant on account of being in a stable spot right now lol

If you have an MSI board, though, I can easily crank you out a modded BIOS :) Chew never tried my modded ASUS one, so I don't know if it'd work. They are rather locked-down to prevent flashing of modded BIOSes, and the only plausible trick relies on the person flashing the BIOS they want modded, dumping it using AMI's flashing utility, and modding that (which if I do it, requires uploading it for me to download). Apparently that keeps whatever unique code for that system only in the BIOS and will let you re-flash it. As for ASRock or Gigabyte boards, I have no clue. My last Gigabyte board was an FM1 system and they signed their BIOSes, so I couldn't flash my modded ones to it :( I know that's pretty common on their modern Intel variants, so I'd assume just the same on AMD's.

EDIT: Just noticed in your screenshot, you have the ASUS Strix B350 heh I'd be willing to poke around the BIOS, if you want. So long as you understand the usual disclaimer applies of "I can't be held responsible for any issues you have". I've been running my own modded BIOSes since like the 3rd week of Ryzen being released, so I know they save just fine!
 
Overclocking is a cutthroat competition? Lolwut?

To me, it's just getting more performance for free because bored.
 
Overclocking is a cutthroat competition? Lolwut?

To me, it's just getting more performance for free because bored.

Exactly... not many of us use or need the extra power but like any hobby it a numbers game.. almost like drag racing... only the number goal is to go smaller
 
I'm not sure how I missed this originally, but I only noticed it last night while making the above reply, sorry about that! :(

I presume you tried disabling the GearDownMode as well? Though it no doubt is needed for that much RAM.

Also, how high did you try on the RAM Voltage? And what's your SoC (CPU_SOC or CPU_NB) voltages that you had tried?

Beyond that, a few of those sub-timing suggestions I made to Rauelius would apply to you, though as I"m sure most of what you have in the screenshot are already dialed in by you, I'd personally probably only be attempting to lower: tRC, tFAW, tWR and tRTP. Mine are: 54, 25, 11, and 9, respectively.

I've dropped those values accordingly, and a few others.

3000 MHz at anything less than CL16 is not possible. CL15 probably WOULD be possible, except that my board (and as I understand it, this may be an architectural quirk of Zen) automatically rounds up to nearest even CL number north of 14. So CL14 or CL16. Setting CL15 really sets it to CL16. No voltage increases on either the RAM or the SOC is sufficient to get around this limitation. I am already at SOC 1.05v and DRAM 1.365 for 2933 @ CL14 and 3000 @ CL16.

I suspect this is because Hynix M die RAM is kind of shitty, and I'm running high capacity (32GB) in a dual rank configuration. Literally the worst possible combination for Ryzen short of running 4 sticks instead of 2.
 
Overclocking is a cutthroat competition? Lolwut?
Sad to hear, ain't it?

I wouldn't be at ALL surprised if 99.5% of the competitors at the overclocking competitions are male (0.05% is me giving benefit of the doubt, that surely there are females who get enough of a thrill from it to compete), as it'd pretty much have to be for there even being monetized competitions to exist in the first place... Why? Not because women are in any way inferior... Nope, and quite the opposite! It's purely because women aren't about comparing dick size, and that's exactly what these competitions are about *sigh* All about who has the biggest dick dewar. heh

I've dropped those values accordingly, and a few others.

3000 MHz at anything less than CL16 is not possible. CL15 probably WOULD be possible, except that my board (and as I understand it, this may be an architectural quirk of Zen) automatically rounds up to nearest even CL number north of 14. So CL14 or CL16. Setting CL15 really sets it to CL16. No voltage increases on either the RAM or the SOC is sufficient to get around this limitation. I am already at SOC 1.05v and DRAM 1.365 for 2933 @ CL14 and 3000 @ CL16.

I suspect this is because Hynix M die RAM is kind of shitty, and I'm running high capacity (32GB) in a dual rank configuration. Literally the worst possible combination for Ryzen short of running 4 sticks instead of 2.
Hopefully those subtimings help a tiny bit then :)

I was also very irked initially when Ryzen released with the exact same "No Odd CLs", which was ultimately addressed. So I'm perplexed that it's back again!

Though... You know what... A couple synapses just randomly fired in my brain and I suddenly seem to recall that GearDownMode is what allows for using Odd CLs! With it Enabled it prevents that, but Disabled allows it...

I'll research and edit or post back what I can dig up!
 
Sad to hear, ain't it?

I wouldn't be at ALL surprised if 99.5% of the competitors at the overclocking competitions are male (0.05% is me giving benefit of the doubt, that surely there are females who get enough of a thrill from it to compete), as it'd pretty much have to be for there even being monetized competitions to exist in the first place... Why? Not because women are in any way inferior... Nope, and quite the opposite! It's purely because women aren't about comparing dick size, and that's exactly what these competitions are about *sigh* All about who has the biggest dick dewar. heh

Agree with the 99.5% thing. Disagree to some extent with the reason. Yeah, dick measuring is a thing in any hobby to some degree. "I make the Washington Monument look like a lawn gnome" and all that jazz. But it's also fun, for the lulz, and because why not? We love to tinker with stuff, without any reason or justification for doing so.

I don't want to start a gender war on [H]ardOCP, but if I were spitballing, I'd say women just generally have better things to do than screwing around with machines all day - when they aren't getting paid to do it, anyway. There are exceptions, of course. NAXALT and Your Mileage May Vary. Female engineers are rare enough still, that Scott Adams once said something like 'male engineers are as likely to be lifelong celibates as not. Female engineers become hot items at the age of consent, and remain such until 30 minutes after clinical death. Longer on a warm day.'

Hopefully those subtimings help a tiny bit then :)

I was also very irked initially when Ryzen released with the exact same "No Odd CLs", which was ultimately addressed. So I'm perplexed that it's back again!

Though... You know what... A couple synapses just randomly fired in my brain and I suddenly seem to recall that GearDownMode is what allows for using Odd CLs! With it Enabled it prevents that, but Disabled allows it...

I'll research and edit or post back what I can dig up!

The odd subtimings thing has never worked on this board. Regardless of GearDownMode, or any other setting. I don't know how it is in the wider Ryzen ecosystem, but with this board, it has never worked north of CL14. Always rounds to next highest even value.

Then again, maybe it's tied to GearDownMode AND some other setting I'm not aware of. If you find out anything, let me know.
 
Arg... Short of literally reading over every post I've made on here and/or XtremeSystems, I can't find where I came up with my Eureka! moment on this! :mad:

The things flying around my brain are that Odd-CL timings are tied to GearDownMode. Enabled makes it operate on a full tick (or whatever the DRAM is programmed for), where as Disabled allows for half-tick. This in turn determines being able to run at CR 1T or 2T. In my experience, which again keep in mind that I've stuck with a BIOS version that only has AGESA 1.0.0.4a, I feel like I had tested this once and wasn't able to get 1T to lock in unless it was Disabled.

Though, another is that the Command Rate can also allow you to get Odd working by changing it to 2T; however, that's not ideal since it means you are taking a performance hit. So unless you're able to increase clocks with CR 2T (which is likely to happen), then there's little point in doing it just to gain tCL 15 ability.


Since I need to restart my desktop ANYways, I'm just going to go tinker quick and see what I can re-discover heh

EDIT #1: Ok so on mine, to my surprise, I have GearDownMode set to Auto, and it runs disabled. I also have manually set both BankGroupSwap options to Disabled, and ProcODT is 53.3 Ohm (just a hold-over, but runs well so I left it).

All other drive strengths or Bus timings, or terminations are set to Auto. ALL timings are manually entered, this includes CR, and are running at what I've input.

Test one, I changed CL to 15 and restarted. It is running at 15. If it didn't set, it would show being set at 15, but the readout would show 16.

EDIT #2: BINGO. Set GearDownMode to Enabled and restarted... tCL set to 15, running at 16! So now to see if setting it manually to Disabled will allow for 15 again or if Auto is required for some reason.

EDIT #3: Alright, so that's weird but, confirmed for my board to be GDM as the cause. The weird part was that it would fail to POST (code F9) only the first time, but repeatable, with GDM manually set to Disabled. After the first fail the "Retry" feature would kick in and shut down for a moment before restarting, which would POST fine. *shrug*
Either way, with manually Disabled, just like Auto, tCL 15 works.

As such, I'm not going to bother seeing if manually setting the CR to 2T will also allow for Odd timings.
 
Last edited:
I've dropped those values accordingly, and a few others.

3000 MHz at anything less than CL16 is not possible. CL15 probably WOULD be possible, except that my board (and as I understand it, this may be an architectural quirk of Zen) automatically rounds up to nearest even CL number north of 14. So CL14 or CL16. Setting CL15 really sets it to CL16. No voltage increases on either the RAM or the SOC is sufficient to get around this limitation. I am already at SOC 1.05v and DRAM 1.365 for 2933 @ CL14 and 3000 @ CL16.

I suspect this is because Hynix M die RAM is kind of shitty, and I'm running high capacity (32GB) in a dual rank configuration. Literally the worst possible combination for Ryzen short of running 4 sticks instead of 2.

You have to disable geardown mode to get odd CL timings to work. I have the same issue but haven't bothered to change it as I'm trying to see how stable my system is - so far I haven't rebooted since I plopped the 2700X in on the 20th. Probably safe to call it stable at this point, but I had a moment of insanity today and ordered a CHVI and a new case, so it's going to get shut down in a day or two when all of that comes in, and then I'll start ram tweaking in earnest.
 
Man, look at you go! That's tighter than a >insert something inappropriate here relating to nuns<! :D

Did it bench with any better speeds and latency?
 
Back
Top