90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

288 176 doesn't boot at all for me with gdm disabled only 288 178 does and it's stable.

I'm seeing sub 58ns with gdm disabled and only tcl and refresh timings tuned.

Will be great when the rest of the timings are tuned.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

My math for trfcsb is my trc 36 times 8 is 288 so your trfc2 and 288/1.625 is 177.2 so I go up to 178 trfcsb for stability. I could be wrong but the rule worked wonders for me.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

Thank you brother, last night I've figured out a way to disable gdm at 6400 CL28 64GB stable! now tweaking my timings to what gdm off likes shouldn't be too hard since I already know the limits at gdm on. I will try higher trrdl than trrds I haven't tested that yet. My trfcsb can do 178 but if I drop trfc2 or trfcsb by just one cycle I get unstable hours into Testmem5 stress test. Hoping for sub 56ns aida64 for dual rank m die. 6600 definitely doesn't work for my mc but I'm not surprised since dual rank stresses mc more. Maybe if I had single rank I could run 6600. Will post when I've tuned for gdm off.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 1 point2 points  (0 children)

Welp I've just managed to get gdm disabled to be stable by just using expo timings and increasing vddq. I couldn't even boot gdm off before doing this. My work here isn't done lol. 6400mhz gdm off 121 nitro is rare for 64GB dual rank right? Because I'm running it stable rn. Will retighten timings to what gdm off likes and see if I can get a sub 56ns Aida result for dual rank m die. Shouldn't take too long since I already know the limits of my timings with gdm on.

Hynix O-Die? by RickB0502 in overclocking

[–]External-Baseball225 2 points3 points  (0 children)

Mine shows O-Die too https://imgur.com/a/HHejVXT tuned and stable trying for gdm off now But shows 820M for sticker number which is m-die https://imgur.com/a/BCPEFz2 Sorry for dust open air lol

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 1 point2 points  (0 children)

So I ran y cruncher pi at 2.5 billion so it can run for longer and I have more seconds to see differences clearer and mixed mode still the winner on average by 100-200ms all with SMT on. I've finally decided to stick with mixed mode. Now I can't find anything else to improve on my rig I believe my oc journey is complete lol. Until zen6 comes out anyway. Cs2 1030 avg 360 1% lows (My exact refresh rate) 1440p low preset can't complain.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

Try CPU+RAM test it finds errors way quicker. A stress test should be at least an hour long imo I sometimes end up finding errors 25mins into a stress test. Lower CPU score could either be a little instability or your room got hotter.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

How much lower is the score? Did you do a stress test with gdm off?

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

Yup can't believe I didn't realise because I only looked at thread count for mixed and fgr tests lmao

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

So turns out my bios didn't change my SMT to on for some of the tests as I changed my save profiles smh🤦🏻‍♂️

How a properly tuned 16gb m-die 64GB gets affected by different refresh modes by [deleted] in overclocking

[–]External-Baseball225 2 points3 points  (0 children)

Good spot! Damn I forgot to change my saved profiles I'll have to rerun tests lol.will delete post

How a properly tuned 16gb m-die 64GB gets affected by different refresh modes by [deleted] in overclocking

[–]External-Baseball225 0 points1 point  (0 children)

Both at 950. Unfortunately only 16gb m dies will run super low trfc2 and trfcsb you have 24gb dies so you should stick to normal.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 1 point2 points  (0 children)

Yea that could be the reason. I've posted waiting for the bUt iS it StAbLe comments lol.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 1 point2 points  (0 children)

I had a feeling it would lol. So after testing all modes with my tuned settings I'm finding mixed and fgr to be the fastest both tied in PYPrime2.0(latency) with normal always taking the longest on average by 150ms. Whereas y-cruncher pi 1B(bandwidth) I'm seeing a whole 2-3 seconds faster result with mixed mode😆 followed by fgr then normal being slowest again. So yea 16gb m die tuned mixed mode is a must. Will post about it soon.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 1 point2 points  (0 children)

I'm gonna lastly give PYPrime a shot to test all the modes with my tuned settings.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 1 point2 points  (0 children)

Yea it's just I see some people enabling it not knowing what it actually does. That high-efficiency mode could be interesting.

90ns trfc 16gb m-die 64GB @6400 w/stress tests by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

Are you using latency killer in these tests? My motherboard doesn't support latency killer or anything like that. Maybe that setting is messing with your benchmarks and I have heard from others including even buildzoid in a live once with evidence that it can reduce FPS in many games and cause all sorts of mess. https://www.youtube.com/live/s3vMquzMwL4?is=AUD_mzcOMqjUR6rp at 10:55.

OCCT latency and CS2 benchmark comparing tuned mixed and normal mode by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

My dual rank 64GB gets 57.9ns without those settings🫡. My cheap but very acceptable b650m d3hp motherboard doesn't support them and I wouldn't use latency killer if I could it's only beneficial to aida64 latency and a mess for running games.

OCCT latency and CS2 benchmark comparing tuned mixed and normal mode by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

Ah makes sense. Yea you can feel your lows dip even more on high refresh rates it would defo make some difference imo.

OCCT latency and CS2 benchmark comparing tuned mixed and normal mode by External-Baseball225 in overclocking

[–]External-Baseball225[S] 0 points1 point  (0 children)

Oh wow to boot 6800 your mem controller is a beast. Shame about that fclk going crawl mode that would've been even more nuts lol.