- Mar 19, 2009
My current b-die won't do 1T unless I run them in gear 2, which is pointless. I think I have read somewhere it's just a b-die thing'm pretty sure this is about what I can get out of my system but there may be tweaks I don't know about. I have E-cores disabled but heat still keeps me from getting 5.2ghz without throttling. 5.1ghz @ about 1.25v with ram at 3600mhz cas15 1.4v and cpu SA at 1.2v but I can't do 1T for the life of me. I can live with it. I think somebody told me once that 32gb dual ram kits have a hard time with 1T and I couldn't do it on my last system either.
And since you also have g.skill those timings make me think you have a lower binned b-die.
My previous kit could do 1T at 4k but I just couldn't get it stable, and it wasn't b-die (never really looked into it) so I just sold them.
It really depends on the sticks.
With e-cores disabled you "should" be able to get 5.2 at 1.3 -> 1.35 (full load reading), for me that was the limit on air on my NH-D15, and you can't get any better cooling than that, still it was hitting over 90C, since I can get about 10C more ambient during the summer I just switched to an AIO.
One solution would be to enable TVB and downclock by 1 or 2 ratio over 60/70C, so you can safely game at low load and when you need to really pump you can do it at a more safe temperature and voltage.
I am running a low unstable voltage for 52x but it never crashes, not even with quick load transients as it goes down to 51x with stable voltage of 1.28
(with E-Cores enabled) and it averages a temp during gaming of 40C with max 60C spikes on a beefy 420 AIO and 75 to 80 during max load
To be 100% stable you would need to add an avx offset (I am aiming for 4.9 during avx that's an offset of 3x at 52 boost) in no way you will be stable during AVX workloads with that voltage, y-cruncher is a good way to test stability since it has a very mixed workload and will have different and quickly varying load scenarios, I was stable in an AVX stress tests, but not in y-cruncher, 1 level higher LLC fixed the issue.
You can skip this step, but I still recommend it as you never know where and how heavily these instructions are implemented and you won't know why you suddenly got a random BSOD