Chloe's RAM OC thread for everyone

[Keullo-e]

So let's see..

 

[tabascosauz]

So let's see..

dude stop being a tease, tRCD tRP 19 and just punch in 3600 if it's half-decent CJR and no weird CPU problems it should be able to POST 3733 at least at 16-19-19

@xrror classic wacky DRAM calc recommendations, try running these? It's nothing special but you should notice at least a benchmark difference from those timings.

Additionally try tRFC 494 at 3800.

 

[Keullo-e]

dude stop being a tease, tRCD tRP 19 and just punch in 3600 if it's half-decent CJR and no weird CPU problems it should be able to POST 3733 at least at 16-19-19

Not yet bro a step by step

 

[xrror]

dude stop being a tease, tRCD tRP 19 and just punch in 3600 i

Watch it be Kingston somehow got a hold of "don't know why this boat docked at the wrong harbor" SPECX ghost shift memory lol

also, (hey! remember Chloe it was YOU who brought up BH-5) remember the crazy UTT and TCCD days??? Where like the memory makers would just rip out untested wafers out of their FABs untested to keep the lines running and the (can't remember the term) like the integrators like Corsair, Kingston, bascially anyone would buy raw wafers and then bin them themselves? Some crazy sticks came outta that haha.

Anyways like, the current DDR4 market and hynix just blasting IC's out really feels a bit like that - where people are specifically buying 3200 to save a few bucks to run at 3600+. What's more nuts is true 3600 or even 4000 isn't crazy more - only if you want low CAS (which now is like CAS14 @ 3800).

I guess why that story comes to mind is that... even though we don't know exactly know what your Kingston set is.... we have like an 85% chance it's probably gonna act like Hynix CJR - and that's a good thing lol.

It just cracks me up, because I never expected DDR4 to go out with such an awesome bang as this, after how early DDR4 was such a PITA to get anything over 3000 (it was Samsung B-die or get F'ed) to now where if it doesn't do like 600Mhz over spec it must be defective!

 

[Bones]

Wait for me to get sober and I accept ur challenge aka we have a battle on tuesday!

I'll go ahead and set a goal for you to reach.

You should be able to.

 

[xrror]

I'll go ahead and set a goal for you to reach.

You should be able to. [2200 FCLK]

So, my processor called, and all it sent me was a picture of a middle finger and something about WHEA_NOTGONNAHAPPEN



EDIT: so... you know, I'm just gonna suck it up and admit I mis-read that NB freq. I blame the fact that coming from YOU, Bones... would be someone bad-ass enough to be able to pull off 2232 at 1:1. It would either be you or Mr. Scott causually going "hey, see these crazy numbers? verified beoch" lol

 

[tabascosauz]

So, my processor called, and all it sent me was a picture of a middle finger and something about WHEA_NOTGONNAHAPPEN



EDIT: so... you know, I'm just gonna suck it up and admit I mis-read that NB freq. I blame the fact that coming from YOU, Bones... would be someone bad-ass enough to be able to pull off 2232 at 1:1. It would either be you or Mr. Scott causually going "hey, see these crazy numbers? verified beoch" lol

Well........................................33MHz is close enough......right?



If I COULD be arsed to put in any one of my shitty low profile GPUs I'd bet money on 2233 1:1. But I can't be arsed so the whole thing is like half the size of a shoebox and i am just way too lazy

 

[xrror]

So to close out my drunken stupor for tonight. Thanks all for being kind with my ramblings.

its in theroy the same kind of ram which is the confusing part

Yea Isaac - despite our best intentions you may want to start your own thread asking about getting some more performance out of your memory. Personally, I wanna know more about your system and why you think it's the memory holding you back... plus the fun mystery of the "G.Skill says these 2 (wildly different) sticks are the same part number."
Plus .... I mean... I haven't looked at your post history but you obviously know enough to bring these things up front (awesome!) so just saying, it'll be a fun thread (vs. someone who squeezing relevant info from is like blood from a stone).

For Chole's mem-clock adventures on (probably Hynix CJ... something.. except, 2x16GB !) would be a good story to fully lay out, in that with (2x16GB) 32GB kits becoming the "de-facto" standard this could be an awesome reference to see just how far the "average 32GB kit" can be pushed!

I mean, hey in this case Kingston has done us a favor in making the study "double-blind" lol.

But it is time for me to take my last sip of the night, and stfu lol.

 

[lexluthermiester]

I'll go ahead and set a goal for you to reach.

You should be able to.

View attachment 200605

How in hell are you pulling off 0.320V on that 3600X? And at 4.2ghz even...

 

[Keullo-e]

I'll have a nap soon and I'll let MT5 run for a while.... if this 3466 is stable, then it's time for a boot and for 3533..

And hell no I don't loose timings, no no and no.

 

[Bones]

How in hell are you pulling off 0.320V on that 3600X? And at 4.2ghz even...

TBH I had it set manually for more voltage, even I know it's not gonna run 4.2 with that kind of undervolt.
I can't recall ATM exactly what it was set for but it was north of 1.35v's for sure so it would run at that speed.
I saw it and figured CPU-Z was mis-reporting it in the sceenie.

This is the actual validation link for the sub and it shows what appears to be the correct voltage or close to where it was set manually:
AMD Ryzen 5 3600X @ 4224.02 MHz - CPU-Z VALIDATOR

And don't ask about RAM voltage I had to use - Most here would balk at where it was but I know it was above 1.60v's just to get it.

So, my processor called, and all it sent me was a picture of a middle finger and something about WHEA_NOTGONNAHAPPEN



EDIT: so... you know, I'm just gonna suck it up and admit I mis-read that NB freq. I blame the fact that coming from YOU, Bones... would be someone bad-ass enough to be able to pull off 2232 at 1:1. It would either be you or Mr. Scott causually going "hey, see these crazy numbers? verified beoch" lol

Believe me when I say I had to work for it.
I don't know what your setup is but I'd bet once you really get into things you'll probrably acheive whatever speed you were shooting for.

Guys I'm taking this thread as more than just to show what you can do, it's also about giving advice and seeing just what's possible to get.

 

[Keullo-e]

Probably just idle voltage or a bug on CPUZ?

 

[Bones]

Probrably.
The MEG ACE sometimes acts like an old NF4 DFI, has a mind of it's own.

I will say right now the board used of course has a huge effect on what you get.
For example those same exact sticks and CPU will not go over 3333 no matter what in this X470 Tachi Ultimate but in the X570 MEG ACE it just flies in comparison as the screenie and validation shows.

 

[Keullo-e]

3533, dunno is this stable..

 

[Bones]

These are the exact sticks I was using: G.SKILL TridentZ Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3600 (PC4 28800) Intel Z170 / Z270 / Z370 / X299 Desktop Memory Model F4-3600C16D-16GTZSW - Newegg.com

I also have a set of Flares that does well: G.SKILL Flare X Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3200 (PC4 25600) AMD X370 / B350 Memory (Desktop Memory) Model F4-3200C14D-16GFX - Newegg.com

Took these to about the same speed with their stock timings too in my Maximus IX Apex board running a 7700K chip.
I've got that setup for runs later this week (I hope) and maybe I'll get something good out of it once I freeze it.

 

[dont whant to set it"']

@Chloe Price I want to say that surely yours can do better in terms of latency , I've just set the multiplier to 42 on mine for comparison sake. And yes CR2 because as it is , it is equipped with 4 8GiB dual rank dimms.

 

[Taraquin]

Chloe: Why don't you loosen primaries to 18-22-22-22-40, set everything else to auto, set volts to 1.4V, try 3733/1866. If that works try 3800/1900. If one of those work start tightening from there. If sky is the limit, why not just fly to the sky right away instead of building your way up brick by brick?

 

[Bones]

Chloe: Why don't you loosen primaries to 18-22-22-22-40, set everything else to auto, set volts to 1.4V, try 3733/1866. If that works try 3800/1900. If one of those work start tightening from there. If sky is the limit, why not just fly to the sky right away instead of building your way up brick by brick?

This is not the right way to really learn what it takes to get them up in speed.
I agree that not going for it isn't the way but at the same time it's a process of Failure+Failure+Failure+Failure+Failure=Success.

I've done that before and admit I did acheive it a few times but the thing was I didn't "Know" what was going on for being able to repeat what I had done. It just happened and although I was happy, I didn't honestly know how it happened.
Since those days I've adopted a methodical approach and can now repeat what I had done before with a very reasonable chance of success everytime, that what it takes.

That's why I was able to go out just a few ago and do this instead of having to spend time figuring it all out to get it. For RAM voltage I used 1.77v's set manually in the BIOS for this attempt.
Did this in one shot for the thread to show what these Flares can do since I did say earlier they could clock - And they do:

Yes I misspelled Chloe....

 

[xrror]

NOTE: I typed this out before I saw Bones reply above. I'm going to sleep now lol.

Again, in my drunken slur before I pass out... remember Chloe is running 32GB kit in 2 x 16GB sticks. Ya'll probably already know that but I'm just projecting my aggravation that all advice on the interwebs assumes two 8GB sticks. That said after my stumbling upon "don't set tWRRD under 2" will at least let most 8GB stick timing recommendations given to you at least POST, and in fact you can actually run many of them.

For my old school self, the fact you can even tempt timings that are "tight" for mem sticks half the size that you're running... it feels like (awesome) witchcraft lol.

Yes I misspelled Chloe....

You also misspelled "Ryzen" as 7700 LOL. (I kid I KID! don't kill me lol)

 

[Bones]

You also misspelled "Ryzen" as 7700 LOL.

I can believe it - Between my apparent dylexia and all else as of late I've no doubt about it.
Not to mention I need some shut-eye myself right now.

Yeah, this is about Ryzen which is a different animal, all I'm saying here is it's possible.

BTW @Chloe Price Are you using the stock timings for those sticks ATM with your attempts?

 

[Taraquin]

This is not the right way to really learn what it takes to get them up in speed.
I agree that not going for it isn't the way but at the same time it's a process of Failure+Failure+Failure+Failure+Failure=Success.

I've done that before and admit I did acheive it a few times but the thing was I didn't "Know" what was going on for being able to repeat what I had done. It just happened and although I was happy, I didn't honestly know how it happened.
Since those days I've adopted a methodical approach and can now repeat what I had done before with a very reasonable chance of success everytime, that what it takes.

That's why I was able to go out just a few ago and do this instead of having to spend time figuring it all out to get it. For RAM voltage I used 1.77v's set manually in the BIOS for this attempt.
Did this in one shot for the thread to show what these Flares can do since I did say earlier they could clock - And they do:
View attachment 200619
Yes I misspelled Chloe....

Point is: It's worth finding out what speed the ram and mobo can do first, the tune subs, almost every guide on ram clocking/tuning advices this. If this is Hynix CJR dr if I read correctly 3733 or 3800 should be no problem depending on how goid the I/O-die is.

 

[dgianstefani]

 

[freeagent]

3533, dunno is this stable..

View attachment 200614

Is this dual rank? Your reads and copies are pretty tight..

 

[Bones]

Point is: It's worth finding out what speed the ram and mobo can do first, the tune subs, almost every guide on ram clocking/tuning advices this. If this is Hynix CJR dr if I read correctly 3733 or 3800 should be no problem depending on how goid the I/O-die is.

I believe I know what you're getting at here, of course if it's not going to do it period you'd want to know that before spending hours in frustration just trying.
However just slamming the pedal to the floor right at the start isn't the right way either, that was my point from earlier.

Work things up to speed first, THEN try and tweak for the same with tigher timings.

There are four basic factors instead of just two;
RAM, board, CPU and the board's BIOS.

 

[Taraquin]

I believe I know what you're getting at here, of course if it's not going to do it period you'd want to know that before spending hours in frustration just trying.
However just slamming the pedal to the floor right at the start isn't the right way either, that was my point from earlier.

Work things up to speed first, THEN try and tweak for the same with tigher timings.

There are four basic factors instead of just two;
RAM, board, CPU and the board's BIOS.

Yes, basically, lax timings or all on auto to find the speed-limit. Then tweak subs. On Ryzen 3600X there is basically 2 limits: Infinity fabric/I-O-die and what die your ram is (all new dies like Hynix C/D, Micron E/B and the classic Samsung B-die can run 3733 with no problem, old dies like Hynix A or Micron M can struggle above 3400, but they are rare to find). Viritually all CPUs and mobos are able to run 3733/1866 and many can do 3800/1900. This is the universal agesa 'limit' for zen 2. If you wanna run unsynced to 4000+ ram the CPU and MB can affect support, but the latency penalty is so high running IF at 1/4 speed so not worth it.