Ballistix Sport LT Overclocking

Man of Honour
Joined
26 May 2012
Posts
16,459
@chris74 this is what i do (others may have a better/more efficient way though)

1) run the ram at stock, set soc voltage to 1.1v (can run vsoc at 1.2v max, but ideally < 1.15v, and best is <1.125v)
2) bump up the IF to 1900 and test stability - if unstable then run IF at 1867 and then test stability (most chips will do 1900, all chips will do 1867 iirc)
3) once you've confirmed the max possible IF clocks -> then start playing around with the ram
4) few ways of doing this - either start high and then go down if fails stability test (high = 1900 DDR + 1.45V + looser timings eg C20)
5) if passes, then keep dropping latencies until becomes unstable then go back to last stable config

(4+5) ryzen dram calc should give a reasonable indication of what to expect, but it's not that accurate for e-die, so there will be a bit of variation
 
Associate
Joined
18 Jul 2019
Posts
59
Having mixed results with these. I've got the 2x16GB kit and seems there is one good stick and one not so good. Can run memtest86 for 12 hours at XMP timings at 3400 (1.37v), but 3533 has a few errors even at 1.4v. 3600 just doesn't seem to work no matter the voltage with XMP timings. Several times had complete post failure leading to a messy BIOS clear (and changing what port the monitor was plugged into). Tried taking just one stick out after a post failure and found that one of the sticks would work on its own but not the other.

Fairly happy with 3400 @XMP but shame considering the heights others are getting. Some interesting timings from others in this thread though so will try some more tweaking...
 
Associate
Joined
8 Oct 2013
Posts
868
Having mixed results with these. I've got the 2x16GB kit and seems there is one good stick and one not so good. Can run memtest86 for 12 hours at XMP timings at 3400 (1.37v), but 3533 has a few errors even at 1.4v. 3600 just doesn't seem to work no matter the voltage with XMP timings. Several times had complete post failure leading to a messy BIOS clear (and changing what port the monitor was plugged into). Tried taking just one stick out after a post failure and found that one of the sticks would work on its own but not the other.

Fairly happy with 3400 @XMP but shame considering the heights others are getting. Some interesting timings from others in this thread though so will try some more tweaking...

What CPU is this paired with ?

You may need to bump TRFC to like 620 (I had to start pushing up on mine after 3533)
 

Ree

Ree

Associate
Joined
22 Aug 2016
Posts
2,478
new to messing with ram. used the calculator and set the bar low with 3466 (safe) to start and its done it with no errors on memtest during the night so will try out 3600 when i get a chance to see if they can reach that far. just kinda interested to see what they can do.
 
Associate
Joined
18 Jul 2019
Posts
59
What CPU is this paired with ?

You may need to bump TRFC to like 620 (I had to start pushing up on mine after 3533)

It's paired with a 3900x. I tried bumping up the TRFC to 620 and voltage to 1.45 and got it stable at 3733 16-20rd/18wr-18-38 so far. Bandwidth is 57GB/s and latency 68ns so pretty happy with that. Will see if I can start dropping the voltage. Is 1.45 too high for general usage?
 
Man of Honour
Joined
26 May 2012
Posts
16,459
Is 1.45 too high for general usage?
1.45v is okay. of course ideally as close to 1.4v as possible...
also do check what the mobo reports the memory voltages.
some mobos give an extra 0.02-0.03v randomly, so your 1.45 can actually be 1.47-1.48v
at least i've seen reports of some gigabyte aorus x570 boards doing just that, and so does mine (aorus x570i) lol
 
Associate
Joined
8 Oct 2013
Posts
868
It's paired with a 3900x. I tried bumping up the TRFC to 620 and voltage to 1.45 and got it stable at 3733 16-20rd/18wr-18-38 so far. Bandwidth is 57GB/s and latency 68ns so pretty happy with that. Will see if I can start dropping the voltage. Is 1.45 too high for general usage?

1.45 should be fine, tho of course lower the voltage at that point the better
 

Ree

Ree

Associate
Joined
22 Aug 2016
Posts
2,478
got errors on 3600 (safe) pretty much right away but 3533 c16 (safe) passed with no errors. pretty happy with that.
 
Soldato
Joined
12 Jan 2009
Posts
2,572
These are my final settings, I did all this testing on 3466mhz as 3600mhz was a no go. If I raise mem to 1.42v and SOC to 1.1v then 3533mhz survives 3 mins in a stress test, I could lower something but I have no idea what and I don't want to raise voltages any more so I think I'm sticking with this.
Edit: Soc is showing 1.1v for some reason despite me setting it as 1.075.


5UihH94.png
 
Soldato
Joined
1 Feb 2006
Posts
3,396
These are my final settings, I did all this testing on 3466mhz as 3600mhz was a no go. If I raise mem to 1.42v and SOC to 1.1v then 3533mhz survives 3 mins in a stress test, I could lower something but I have no idea what and I don't want to raise voltages any more so I think I'm sticking with this.
Edit: Soc is showing 1.1v for some reason despite me setting it as 1.075.

I run @3600, i use different ram(g-Skills) and the xmp did not work properly but this is how i got it to run @3600:
 
Soldato
Joined
1 Feb 2006
Posts
3,396
I'll try that tomorrow, I don't think it will work for mine but maybe. Wouldn't the lower timings off-set the speed difference?
I don't know, I just wanted it to run @3600 as it's 3600 ram rated @CL17,18,18,18 but it's 2 kits so 4*8GB. I tried it @3200 CL 14 and 3600 CL 16 is faster in benchmarks but am on a beta BIOS so things have been strange. Could not get CL17 to stick, it would use CL18 so I tried 16 and added .1volts it its been working ok so far. Also, think IF runs in sync with ram up to 3733 so that should help performance a tiny bit as it is 1800Mhz with 3600 ram.
 
Last edited:
Soldato
Joined
12 Jan 2009
Posts
2,572
I don't know, I just wanted it to run @3600 as it's 3600 ram rated @CL17,18,18,18 but it's 2 kits so 4*8GB. I tried it @3200 CL 14 and 3600 CL 16 is faster in benchmarks but am on a beta BIOS so things have been strange. Could not get CL17 to stick, it would use CL18 so I tried 16 and added .1volts it its been working ok so far. Also, think IF runs in sync with ram up to 3733 so that should help performance a tiny bit as it is 1800Mhz with 3600 ram.
Interesting. I don't know either but the benchmarks usually pit cl14 3200 against cl16 3600 and it comes out almost even. I'm going to test your timings tomorrow but my experience with with this ram is it just doesn't like 3600 and the amount you'd need to give up for it doesn't seem worth it.
 
Associate
Joined
18 Jul 2019
Posts
59
Also, think IF runs in sync with ram up to 3733 so that should help performance a tiny bit as it is 1800Mhz with 3600 ram.

For me with the IF speed set to auto in the BIOS it ran in sync with the RAM up to 3600 and then halved for 3733. I had to set it manually to match the speed at 1866. Made a large difference on latency.
 
Associate
Joined
18 Jul 2019
Posts
59
Interesting. I don't know either but the benchmarks usually pit cl14 3200 against cl16 3600 and it comes out almost even. I'm going to test your timings tomorrow but my experience with with this ram is it just doesn't like 3600 and the amount you'd need to give up for it doesn't seem worth it.

It depends on the application. Some are more sensitive to latency, others to bandwidth. If your ram will run at 3200 cl14 and 3600 cl16 then you are better off with running 3600 as the latency will be virtually the same and you'll get the extra bandwidth for free. I got mine running well after lots of issues like you had by following the advice of tamzzy and Apache14. DRAM Calc didn't work and non of the typical suggestions worked. I followed this procedure to get my timings:
  • Set tRFC to 620, enable Gear Down Mode, up dram voltage to 1.45v, (possibly also set procODT to 53ohm)
  • Loosen timings to tCL 20, tRCDWR 22, tRCDRD 22, tRP 22, tRAS 44 everything else set to auto
  • Start at 3200 and up speed till you hit your target or it is producing memory errors. If errors back off one step.
  • Find best tCL by decreasing 1 step at a time till target hit or errors occur. If errors back off one step.
  • Do the same for tRCDWR, tRCDRD, tRP
  • For tRAS set to tCL + (greatest of tRCDWR & tRCDRD) + 2
  • Decrease voltage by 0.1v until memory errors occur and then increase by 0.1v until long runs in mem test are good.
That got me from not being able to run above 3466 cl16 to 3733 16-20rd/18wr-18-38 @ 1.38v stable for 18 hour MemTest86.
 
Last edited:
Associate
Joined
9 Nov 2004
Posts
592
Location
Northern Ireland
Mine just arrived this morning and so far a big improvement on the Corsair Vengeance which was a struggle to get stable at its rated speed. Have been playing around and have booted at 3200 fast DRAM calculator settings and now on 3600 safe settings. Using aida memory stress test for a quick check. Interersted to see how much I can get out of them.
 
Back
Top Bottom