Overclocking RAM on Sabertooth X99

[eidairaman1]

I know. If I wait long enough and re-try, I might get it to 3000 MHz one day XD

From advertising on the site here they tend to do 2666 easily
http://www.hyperxgaming.com/us/memory/fury-ddr4

Edit:

This is the secret sauce you might be looking for

http://www.thinkcomputers.org/kingston-hyperx-fury-ddr4-2400-32gb-memory-kit-review/6/

 

[EarthDog]

I have the 3000 sticks with 6950x...


I...uh...am not entirely sure why I posted that... sorry...

 

[RejZoR]

I think I know why I'm having problems overclocking RAM. It's because it's HyperX. The thing they do is like XMP, but they somehow do it that system recognizes settings even without XMP. With normal RAM, if I set RAM frequency to AUTO, it'll just select 2133 MHz because that's the baseline for X99. But in this case, it always auto selects 2400MHz (the rated speed for these Fury sticks). And I think this feature interferes with the overclocking process. A reminder for future, if you want to overclock, take some other brand. If you want to just have best plug and play functionality, go with HyperX, coz it's easy to setup since it requires no tweaking or selection of XMP profiles.

 

[cdawall]

All XMP profiles work on plug and play. That is the point.

If you select auto it will default to your memories default which is 2400 hence why it selects 2400. That is how that works.

 

[FireFox]

@RejZoR practically you're Ocing the Ram using BCLK?

 

[RejZoR]

No, my CPU is purely overclocked by multipliers. 100x45. RAM is OC'ed on its own.

 

[MrGenius]

All XMP profiles work on plug and play. That is the point.

If you select auto it will default to your memories default which is 2400 hence why it selects 2400. That is how that works.

XMP is an overclocking profile. It's by defintition not default. If I select auto on my 2666 DDR3 they run @ 1333 default. XMP @ 2666 won't even boot if I select it. My 3570K can't run them any higher than 2600.

http://www.intel.com/content/www/us/en/gaming/extreme-memory-profile-xmp.html

 

[FireFox]

Set BCLK and strap to 100MHz, set DRAM ratio to 100:100.

You are talking about BCLK

 

[EarthDog]

XMP is NOT overclocking the memory sticks. They are RATED to run those speeds. Note how it doesn't say 2133/2400 on any box, but lists the XMP speeds as their default? It's the PLATFORM which boots to JEDEC standards and then you enable XMP.

You ARE overclocking the CPU IMC as that is rated at the 2133/2400 speeds, but NOT the sticks when using XMP.

 

[Aenra]

Reading the last two pages reveals either a lack in methodology, or perhaps your avoiding to state the obvious, which is understandable above a certain level of expertise.. just cannot know which. Am too new in all this, so this is more of a question than a comment O.K.?

So that said? Rej?
i) does your motherboard allow you to change the RAM ratio?
ii) have you seen Raja's post in Asus Rog regarding optimal ratios in Asus mobos?
iii) if the answer to i) is no, have you tried disabling XMP, keeping your modified BCLK, but changing the RAM frequency manually so as to clock it down to what it's supposed to run while in XMP?
iv) have you done any testing to see how much SA/vccio you need so as to have the RAM stable at said manually inserted (=XMP) frequency?

Because (again, this is more question than comment), my understanding is that unless you're right there, now, timings are the wrong thing to mess with.
You get the highest frequency you can get while stable and then you touch the timings, assuming you can afford the extra RAM voltage.

 

[cdawall]

XMP is an overclocking profile. It's by defintition not default. If I select auto on my 2666 DDR3 they run @ 1333 default. XMP @ 2666 won't even boot if I select it. My 3570K can't run them any higher than 2600.

http://www.intel.com/content/www/us/en/gaming/extreme-memory-profile-xmp.html

2400 is a jedec standard. Hence why when he sets auto it selects 2400.

 

[RejZoR]

I was just scrolling across page of my mobo and found this:
https://www.asus.com/Motherboards/SABERTOOTH_X99/#title-performance

(scroll a bit down)

The cache bus voltage adjustment. The second graph for "Memory" frequency" caught me attention. It's mentioning 2800 MHz and 3200 MHz. Are they implying increasing cache voltage might help RAM overclocking? I've never tried that in relation to RAM overclocking. Then again, apart from initial testing, I've always had it at stock 3GHz with stock voltages...

 

[cadaveca]

Yes, cache voltage can help in some situations, so it is worth trying. Just leave cache multi alone.

 

[RejZoR]

But muh megahurtz!

 

[RejZoR]

I always seem to have "luck" with RAM. Every single RAM that I had was basically non-overclockable. Either I always get the most garbage memory controllers or RAM sticks. Someone above posted same Fury RAM review to go to 3000MHz easily. Well, not in my case. Yesterday I've spent two and a half hours of fidling with all the parameters in sequences, more systematic way and from what I've seen, NONE of the voltage changes do anything. NONE. Neither amp threshold or timings.

I can't understand why damn system refuses to even post no matter what beyond certain point. There is no point where it posts and is unstable later. It's either stable or entirely unbootable. Setting voltage to 1.35 (from original 1.2V) does exactly NOTHING.

For example:

BOOTABLE and 100% stable:
2666 MHz
14-14-14-30-1T
100% DRAM current threshold (default)
1.25 V on all DIMM channels

WON'T EVEN POST:
2800 MHz
18-18-18-54-2T
140% DRAM current threshold
1.35 V on all DIMM channels (I've gone even to 1.4V for a quick test)

How the hell does this make any kind of sense? I've even tried disabling all POST DRAM tests just to make the damn thing at least post and boot into Windows as recommended for "crash" benching. Nope. Won't even post. It's why I never really gone into any real RAM overclocking, it has always been a totally dud experience for me. This is the first time I keep on retrying despite constant failures...

 

[cadaveca]

The problem is likely one of two things:

A: The memory simply is not stable somewhere between 2666 and 2800. Although this might not seem likely, some ICs are just this way.

B(the more likely reason): You are approaching the OC in the wrong way. You are adjusting voltage and primary timings, but you are not changing secondary and tertiary timings to match. Now, if you had an ROG board, and not a Sabertooth, many of those timings would be adjusted automatically for you, but not when XMP is enabled. This is why sometimes turning off XMP and just setting primary timings and then voltage can sometimes get "problematic" sticks to work. The "problem" is that the board doesn't like the timings specified by the XMP profile.

So here you are with XMP enabled, and because of that, the default timings for both secondary and tertiary timings may be forced to the XMP profile timings, which were for a much lower speed than what you are trying to push or the board doesn't change those timings automatically.

 

[RejZoR]

I'm not using XMP. It's disabled. I've also tried Tweaker Ai with AUTO and Manual with no real difference. Btw, I was fiddling with timing control setting that goes from 1 to 19 and corresponds to a different sets of DRAM timings (can't remember the name now). The thing is, they only say 1 coresponds to DRAM 800MHz, but I have no idea how the rest of 18 profiles are set.

I've looked at 2nd and 3rd tier timings, but I literally have no clue what they mean. Other than just blindly increasing them to make them loose...

EDIT:
There is apparently new BIOS for Sabertooth X99, version 3505. Gonna try it later today. The changelog list is significantly longer and it mentions imperoved performance and improved DRAM compatibility. Lets see...

 

[cadaveca]

Secondary And tertiary timing tweaking can be hard for sure, but you've got a base to start off of with your own sticks. try 2133 MHz JEDEC, and then your XMP profile. Compare the timings. The change in those timings corresponds to the increase in clockspeed. If xmp is 2400, that's 266 above 2133. a similar adjustment should allow proper increase to 2666 MHz, maybe. Then another increase half of the 266 change, might get you 2800 MHz.

But do keep in mind, you do need to change ALL secondary and tertiary timings. That is a lot of timings, so it is some work to find out the "formula", but once you have the "formula", you'll find this same formula may apply to other sticks and other types of memory as well.

People have asked me how I know what timings to use when OC'ing memory for 24/7 use... I have access to many different kits, and so, I have a large database of potential timing "formulas" to apply towards getting what I want out of a set of memory. It takes time and work to apply, test, and then tweak for better, but maybe that'll give you an approach to use to getting further.

.

 

[RejZoR]

Good thinking. If I figure out the timings jump between each DRAM clock iteration, I could probably do it. I miss the days when fiddling with primary timings was enough...

I'll certainly try this.

 

[basco]

plz where did you find bios 3505??
and my sabertooth is not very good in oc. 1 day it likes the oc next day not. first time i have trouble with asus mb

 

[RejZoR]

http://dlcdnet.asus.com/pub/ASUS/mb/LGA2011/SABERTOOTH-X99/SABERTOOTH-X99-ASUS-3505.zip

Changelog:

SABERTOOTH X99 BIOS 3505
1.Improve System Performance.
2.Improved DRAM compatibility
3.Fixed TPM issue
4.Add in turn-off function of LED under S3/S4/S5 status.
5.Fixed Samsung device (SM961, printer) issues.

BIOS link was sent to me by: @xkm1948

 

[RejZoR]

Ok, updated the BIOS, calculated the timings delta between 2133MHz and 2400MHz XMP profile, doubled the obtained delta and applied it to 2800MHz and it still just won't boot (also increased the DRAM voltage). There were some secondary timings that are always 0 (zero). Not sure what to do with these. Any other ideas why is my system so stubborn to overclock RAM?

 

[EarthDog]

I don't get this delta garbage...just give actual values.

What is System Agent and VccIO set at/reading currently?

 

[eidairaman1]

Long ago for me I trusted Corsair and Kingston. I liked Mushkin and Crucial. I now prefer GSkill

 

[RejZoR]

No, this was to elevate timings according to the timings jump between 2133 and 2400 mhz. And then I just applied it forward for higher frequencies in same jumps.