8 PACK MEMORY RANGE GROWING: SAY HELLO TO 8 PACK RIPPED EDITION & 32GB KITS!!!

I think so yes. It cant hurt to try.

I definitely gained from it.

But I was at around 70ns with just primaries and went down to 66ns with tweaked primary and secondaries.

You seem to be already at 67ns so hard to say if it will improve much on that. But its worth a go.

I've already altered tRC, tRFC and, tFAW and noticed a small improvement, tbh where it is now I'm very happy so will leave it at that (67ns is really fast compared to my old kit)
 
Hey all, seeing everyone overclocking their ripped 8pack ram I thought I'd finally after 4 months come off XMP and manually overclock my memory so far not too bad and i got some nice tight timings, it's great fun. I am a till envious about not having the new ones but I'm happy with my results,

Any idea why my write speed is 30.9? I mean it's higher than it was but seems lower than all of yours, I got a b450, 4x8gb Xtreme 8pack mem and a 3600.

umrZ9DT.png
 
Pre 1.7.2 the dram calc used to suggest me settings something like 14 14 14 14 28 which was WAY too fast for my ram. This is why I always complained that the fast timings do not work for me.

Then OcUK announced the 3600MHz CL14 kits at 14 15 15 15 35 and coincidently the dram calc was upgraded to 1.7.2 and the suggested timings then changed to 14 15 15 15 30 which is how I knew that they where good timings as they matched up with the official timings on the xmp profile for the new CL14 ram.
 
ySZ1Mkt
c16 set with the changes mentioned earlier (please let there be an image)

https://ibb.co/ySZ1Mkt




ySZ1Mkt

ySZ1Mkt
 
Last edited:
Pre 1.7.2 the dram calc used to suggest me settings something like 14 14 14 14 28 which was WAY too fast for my ram. This is why I always complained that the fast timings do not work for me.
...snip

Hah, post 1.7.0 the calculator suggests c16 for my RAM when previously it suggested c14! Though if I just chuck in the calculator timings 1.7.0 give me it was unstable. I thought my RAM was faulty as I couldn't get it stable even at 2933 with the calculator settings. I ended up learning what each timing does and which should be adjusted together, and tuned them myself. The timings which contribute to single errors after hours of testing, at least for me, are
tFAW
tWR
tRTP
Though from looking at the results some of you are getting on the MEMbench, some of you appear to have these timings set at board auto, yet have quicker completion times than those who have set them lower.

I would definitely suggest to those here who have dialed in low timings across the board, to test at least overnight, as I've managed to get an error at 15000% in Karhu before now, which some would be happy with, but an error is an error, and that could mean corruption down the line!

You will also find that setting some secondary and tertiary timings too low can negatively affect performance. Lower isn't always better :-)
 
Back
Top Bottom