high speed ram OC

[porina]

A while back I got some TridentZ 3000C14 2x8GB kit as the cheapest Samsung B-die I could find at the time. After some playing I got it working at 3600 16-16-16-??, 1.35v, IO 1.05v, SA 1.15v. At the time, no matter what, I couldn't get it to run at 3700. Today, I tried again without success, and just before giving up, I tried 3733 and that worked! For whatever reason, the system doesn't like 3700. I pushed higher, and below is a summary of where I'm at, at the time of posting. 

 

3866 18-22-22-44 1.40v, IO 1.05v, SA 1.15v - failed in Windows
3866 18-22-22-44 1.40v, IO 1.05v, SA 1.17v - failed in Windows
3866 18-22-22-44 1.40v, IO 1.07v, SA 1.15v - ok for 14 minutes in aida64
4000 18-22-22-44 1.40v, IO 1.07v, SA 1.15v - starts, too unstable to do anything in bios
4000 18-22-22-44 1.40v, IO 1.10v, SA 1.15v - failed in Windows
4000 18-22-22-44 1.40v, IO 1.13v, SA 1.15v - failed in Windows
4000 19-22-22-44 1.40v, IO 1.13v, SA 1.15v - failed in Windows
3866 18-22-22-44 1.35v, IO 1.10v, SA 1.15v - ok for 39 minutes in aida64
3866 18-18-18-44 1.35v, IO 1.10v, SA 1.15v - ok for 38 minutes in aida64
3866 17-17-17-44 1.35v, IO 1.10v, SA 1.15v - ok for 11 minutes in aida64
3866 17-17-17-38 1.35v, IO 1.10v, SA 1.15v - under testing

 

I touched 4000 in Windows but it was unstable. Now I'm just seeing how tight I can get it at 3866. For those who have been there previously, any tips for trying to stabilise at 4000? I could blindly throw more voltage at it...

 

CPU: i3-8350k currently at stock

Mobo: Asrock Z370 Pro4 bios 1.30

I turned on XMP then vary settings from there.

 

[CyberFern0]

4 minutes ago, porina said:

A while back I got some TridentZ 3000C14 2x8GB kit as the cheapest Samsung B-die I could find at the time. After some playing I got it working at 3600 16-16-16-??, 1.35v, IO 1.05v, SA 1.15v. At the time, no matter what, I couldn't get it to run at 3700. Today, I tried again without success, and just before giving up, I tried 3733 and that worked! For whatever reason, the system doesn't like 3700. I pushed higher, and below is a summary of where I'm at, at the time of posting. 

 

3866 18-22-22-44 1.40v, IO 1.05v, SA 1.15v - failed in Windows
3866 18-22-22-44 1.40v, IO 1.05v, SA 1.17v - failed in Windows
3866 18-22-22-44 1.40v, IO 1.07v, SA 1.15v - ok for 14 minutes in aida64
4000 18-22-22-44 1.40v, IO 1.07v, SA 1.15v - starts, too unstable to do anything in bios
4000 18-22-22-44 1.40v, IO 1.10v, SA 1.15v - failed in Windows
4000 18-22-22-44 1.40v, IO 1.13v, SA 1.15v - failed in Windows
4000 19-22-22-44 1.40v, IO 1.13v, SA 1.15v - failed in Windows
3866 18-22-22-44 1.35v, IO 1.10v, SA 1.15v - ok for 39 minutes in aida64
3866 18-18-18-44 1.35v, IO 1.10v, SA 1.15v - ok for 38 minutes in aida64
3866 17-17-17-44 1.35v, IO 1.10v, SA 1.15v - ok for 11 minutes in aida64
3866 17-17-17-38 1.35v, IO 1.10v, SA 1.15v - under testing

 

I touched 4000 in Windows but it was unstable. Now I'm just seeing how tight I can get it at 3866. For those who have been there previously, any tips for trying to stabilise at 4000? I could blindly throw more voltage at it...

 

CPU: i3-8350k currently at stock

Mobo: Asrock Z370 Pro4 bios 1.30

I turned on XMP then vary settings from there.

 

3000Mhz isvworyhless. RAM speed doesn't matter.

[porina]

15 minutes ago, CyberFern0 said:

3000Mhz isvworyhless. RAM speed doesn't matter.

If your use cases are undemanding enough for it not to matter, don't assume that applies to everyone.

[porina]

3866 17-17-17-38 1.35v, IO 1.10v, SA 1.15v - ok for ?? minutes in aida64 (got distracted and forgot exactly, over 20 mins)
3866 16-17-17-38 1.35v, IO 1.10v, SA 1.15v - no boot
3866 17-17-17-36 1.35v, IO 1.10v, SA 1.15v - ok for 62 minutes in aida64

I'm now taking a break from pushing the ram and will take some benchmarks in this configuration. Then I'm undecided if I'll either try 4000 again, or start playing with secondary/tertiary timings at 3866. I can already see a good progression in throughput using Prime95 benchmark at 4096k FFT, which is a good representation of my typical compute workloads.