Ballistix Sport LT Overclocking

keenan said:
"trcdrd" is the problem! It's really too low to be stable at 3600Mhz.
Click to expand...
Unfortunately at 3617Mhz the pc does not start, I made many attempts.
Now it is stable at 3549Mhz with 1.43v ram and 1.1v vsoc (I try to lower the vsoc).
I have used the timings of 3533 Manual, with reduced timings I always get errors.
Next attempt will be to lower the frequency to reduce the timings and ram voltage.
 
Mikkinen said:
Unfortunately at 3617Mhz the pc does not start, I made many attempts.
Now it is stable at 3549Mhz with 1.43v ram and 1.1v vsoc (I try to lower the vsoc).
I have used the timings of 3533 Manual, with reduced timings I always get errors.
Next attempt will be to lower the frequency to reduce the timings and ram voltage.
Click to expand...

Trcdrd is still the problem!!
 
One of those changes in your bios is causing issues.

Set clock control at 100
CPU voltage at 1.3v
SOC to 1.1v
DRAM 1.45v

Set these timings..

tCL - 16
tRCDWR -18
tRCDRD - 21
tRP - 18
tRAS - 36
TRC - 60
TRFC - 600
 
Last edited:
DeliciousStorage said:
Is Kahru RAM Test worth the €10? I was thinking about getting it but this suggests that TM5 with the extreme config by anta777 is faster at finding errors and it's free.
Click to expand...

I used TM5 some time ago, may have been around 2700X launch time. It wouldn't error on a profile I was testing at the time, but HCI/GSAT/Kahru would.

GSAT is sound if your not willing to pay for HCI/Kahru. I bought Kahru at the time when HCI required you to launch multiple instances to test memory, latest paid version doesn't.
 
3466-14-17-14-31-1200---Copy.png


My best effort so far. really struggling with some timings. tWTRS+tWTRL tRDWR+tWRRD (trying 5,13,7,2 atm 220% and counting) and surprisingly tCKE which doesn't want to lower to less than 5 atm. Its beginning to turn into a chore :mad:

I haven't played around with the resistances and its not stable without GDM.

Ignore the time for memtest; I tried to put the computer to sleep after 6 hours but it hadn't quite finished.

Oh its a 1600 AF and flck seems limited to 1733. 1768 flakes out with loose timings and high volts.

Thanks to everyone I've stolen titbits and timing comparisons from.
 
Mikkinen said:
I tried with everything by default, pbo enabled, only the timings indicated but I get an error at 3600mhz.
What other test can I do?


Click to expand...

Personally I like to keep tRCDRD & tRCDWR in sync. Lowering one below the other isn't going to make a perceivable difference outside of benching, probably for certain benches and not all. Use this calculator to see ns of any timing, 18 = ~10ns, 21 = ~11.6ns.

tRAS is too tight IMO, tRAS = tCL + tRCD + tRTP, stick to calc. Again going lower may not really see you gain much outside of specific benchmark. Let's look at your timings for this, 16+18+13=47 or 16+21+13=50 depending on if tRCDRD or tRCDWR is used and your using tRAS of 36. This is also a reason why I keep tRCDRD & tRCDWR in sync.

Your best off targetting the timings that give best gains first.

Below is what I used to [email protected]:-

DRAM CAS# Latency [16]
DRAM RAS# to CAS# Read Delay [19]
DRAM RAS# to CAS# Write Delay [19]
DRAM RAS# PRE Time [19]
DRAM RAS# ACT Time [45]
Trc [64]
TrdrdScl [4]
TwrwrScl [4]
Trfc [589]
Trtp [10]

Later I set tRP a notch lower, which in turn would mean tRC can be notched lower. I also then knocked tWR from [Auto] 26 to 24.

DRAM RAS# PRE Time [18]
Trc [63]
Twr [24]

These further tweaks gave minor gains in AIDA64 and nothing in say a game benchmark.

The profile has been sound for mixed testing of continuous testing for ~15hrs 1st run, ~5.33hrs 2nd run, ~58hrs 3rd run, ~25hrs 4th run.
 
Mikkinen said:
I also tried your times but I don't get errors, do you have 2x8 or 2x16 ram?
Click to expand...

2x16GB, the method I stated is relevant to use regardless of RAM density in use.

I have now also tweaked tRRDL & tFAW, [Auto] was 10 & 40, now using 9 & 38.

Timings set in UEFI

DRAM CAS# Latency [16]
DRAM RAS# to CAS# Read Delay [19]
DRAM RAS# to CAS# Write Delay [19]
DRAM RAS# PRE Time [18]
DRAM RAS# ACT Time [45]
Trc [63]
TrrdL [9]
Tfaw [38]
Twr [24]
TrdrdScl [4]
TwrwrScl [4]
Trfc [589]
Trtp [10]

3x AIDA64 3800C16R3

2c6Ecnw.jpg

Negible gains in a benchmark which is sensitive and shows best case results for tweaks AFAIK.

Stability testing so far for this profile

So far profile has shown no issues for POST on:-

- Cold POST (ie no standby power to mobo)
- Full POST (ie standby power to mobo)
- Warm POST (ie restart from OS)

Kahru RAM Test run of 2000% so far.

RCXLyM7.jpg
 
gupsterg said:
2x16GB, the method I stated is relevant to use regardless of RAM density in use.

I have now also tweaked tRRDL & tFAW, [Auto] was 10 & 40, now using 9 & 38.

Timings set in UEFI

DRAM CAS# Latency [16]
DRAM RAS# to CAS# Read Delay [19]
DRAM RAS# to CAS# Write Delay [19]
DRAM RAS# PRE Time [18]
DRAM RAS# ACT Time [45]
Trc [63]
TrrdL [9]
Tfaw [38]
Twr [24]
TrdrdScl [4]
TwrwrScl [4]
Trfc [589]
Trtp [10]

3x AIDA64 3800C16R3

2c6Ecnw.jpg

Negible gains in a benchmark which is sensitive and shows best case results for tweaks AFAIK.

Stability testing so far for this profile

So far profile has shown no issues for POST on:-

- Cold POST (ie no standby power to mobo)
- Full POST (ie standby power to mobo)
- Warm POST (ie restart from OS)

Kahru RAM Test run of 2000% so far.

RCXLyM7.jpg
Click to expand...

I gather you just leave the other settings on auto?
 
gupsterg said:
Yes :) , 3800C16R3 setup had now done ~9.75hrs mixed testing:-
  • ~5000% Kahru RAM Test
  • ~235% HCI v6.0
  • ~2hrs Y-Cruncher stress test mode
  • ~2hrs P95 non AVX Custom (4K 4096K 26GB)
Organise files by time, screen video capture ZIP.
Click to expand...

Nice!
I'll give it a whirl when I get home from offshore and see how I get on with your suggestions.
 
michty_me said:
Nice!
I'll give it a whirl when I get home from offshore and see how I get on with your suggestions.
Click to expand...

Cheers :) , NP, look forward to reading how it goes for you.

Yesterday I tried more tweaking. It seems on 3800MHz when using 2x16GB (dual sided/rank dimms), setting tRTP below 10 does not take, see right screenie, left screenie is 4x8GB (single sided/rank dimms).

It would have been handy if tRTP could have become 9, in turn this would have allowed me to knock down tRAS and tRC as well.

tRAS = tCL + tRCD + tRTP
tRC = tRAS + tRP

I have instead further tweaked tFAW & tRFC, still keeping to voltages used before, will share how it goes :) .
 
You must log in or register to reply here.
Back
Top Bottom