HELP OC G.SKILL 2X16 GB -04320X8820C

[noobzin]

Right on B1s.

I'd be surpassing the idea of daily clocks at suck low frequencies though.... But hey everyone is different.

4200mhz CL-19-19-19-19-39 Enable the memory training (if board is equipped) and leave everything else on auto. 1.45v and Uncouple the Infinity Fabric. command rate 2T. Curious if it would just post right up. Compare your numbers linked lower frequency VS Unlinked higher frequency.

BUT Man!! - You've got B-Die!!!!! You are either going to just set this up and go gaming OR you have weeks of tweaking to do. HAHA!!!

So many people jam B-Die and so many configurations.... just how deep is that rabit hole?

Oh and enable "Gear Down mode" in the timings menu as well. You can do Power Down mode disabled, but they might run warmer from it.

Vote #3 for a fan directly on them sticks. (enables spank dimm mode) View attachment 261119

ok, i tried.. dimm 1.45v , put everything on auto. tried 4000. no boot
tried different ways , nothing
tried tight tRFC , blue screen
i wanted to ask do i set all trdc 2-4?

 

[Deleted member 185158]

ok, i tried.. dimm 1.45v , put everything on auto. tried 4000. no boot
tried different ways , nothing
tried tight tRFC , blue screen
i wanted to ask do i set all trdc 2-4?

The best thing I can suggest is watching and reading some DDR4 OC guides. But if anything 3800mhz is a good place to be CL16.

 

[noobzin]

tRFC scales with VDIMM......up to a point. You're still pretty low on the volts, bump it up a notch to see if you can do 140ns. 140 is probably where I'd stop for a daily if don't want to pump too many volts.

At some point you'll bottom out with your tRFC number (not ns) and it won't boot regardless how much volts. I think mine are 138ns at 4200 (A0 Viper Steels) to 131ns at 4333 (A2 Viper Steels). I don't think I've bothered to explore my limit on my dual rank 3600CL14 Trident Z as it's my daily but I have a feeling it outperforms both Patriot kits.

Temp threshold (point at which B-die destabilizes due to heat) primarily is to do with tRFC I think. And also VDIMM like shrimpbrine said. 50C seems generally fine at 140ns but once you get down in the low 130s or 120s I wouldn't be so sure anymore, that threshold may come down. 120 is a bit too hardcore for most people and their kits anyway.

55ns isn't bad at all for a mild 3800CL16 setup on 5600X.



Not lying down. That's just blowing the flow-through hot exhaust from the GPU upwards. I meant standing up a fan on the video card, vertically. So that it blows cool air directly onto the DIMMs.

Hence the suggestion for a small 80 or 92mm fan. Doesn't have to be big, bigger can be hard to fit in there.

i think i did try @ 1.45v , same results.

 

[tabascosauz]

ok, i tried.. dimm 1.45v , put everything on auto. tried 4000. no boot
tried different ways , nothing
tried tight tRFC , blue screen
i wanted to ask do i set all trdc 2-4?

i think i did try @ 1.45v , same results.

You tried 1.45V for 3800CL16 or 4000CL16? For 4000CL16 an average quality kit would be more like 1.5V. Then for tighter tRFC that's even more VDIMM on top of that. How's the new airflow solution working out?

If you want to shoot for 4000, chances are you'll need to step up VSOC and VDDG_IOD as well. At this point 4000 not booting doesn't shed much light on why.

You don't need to touch tRFC2 and tRFC4, they are irrelevant.

MemTestHelper/DDR4 OC Guide.md at oc-guide · integralfx/MemTestHelper · GitHub

 

[noobzin]

You tried 1.45V for 3800CL16 or 4000CL16? For 4000CL16 an average quality kit would be more like 1.5V. Then for tighter tRFC that's even more VDIMM on top of that. How's the new airflow solution working out?

If you want to shoot for 4000, chances are you'll need to step up VSOC and VDDG_IOD as well. At this point 4000 not booting doesn't shed much light on why.

You don't need to touch tRFC2 and tRFC4, they are irrelevant.

MemTestHelper/DDR4 OC Guide.md at oc-guide · integralfx/MemTestHelper · GitHub

i tried to tight the TRFC under 3800 1.45v. but didnt work..
i also try to book under 4000, looser timings , 1.45 v, nothing.
fan part working good i got it in there vertically , honestly best tip i have had in a while.. not sure how i didnt think of that LOL
ill play around more once i get home from work but from my understanding

to reach 4000, i need to increase vdimm for 1.5v at 1.55 right? how about vsoc and vddg? i don tknow if i wanna push that much.
but i would like to tighten for 3800 to better latency but overall im already pretty happy

 

[Zach_01]

got it today!
8810B

okay here it is. out of the box. im looking into what i can do now

Same sticks here...

 

[tabascosauz]

i tried to tight the TRFC under 3800 1.45v. but didnt work..
i also try to book under 4000, looser timings , 1.45 v, nothing.
fan part working good i got it in there vertically , honestly best tip i have had in a while.. not sure how i didnt think of that LOL
ill play around more once i get home from work but from my understanding

to reach 4000, i need to increase vdimm for 1.5v at 1.55 right? how about vsoc and vddg? i don tknow if i wanna push that much.
but i would like to tighten for 3800 to better latency but overall im already pretty happy

I'm not saying you need 1.5V for 4000CL16, but it wouldn't be unreasonable to assume so. 1.55V would be on the high side for 4000CL16, if your kit scales like that then I'd just run 3800.

I need 1.42V for 3600CL14, 1.42V for 3800CL15, and 1.54V for 3800CL14 (all flat primaries). But last time I tried 4000CL16, I needed somewhere between 1.45V and 1.5V.

In my experience, it's harder to run tighter tRFC (ie. lower ns) at lower speeds (below 4000).

 

[Zach_01]

i tried to tight the TRFC under 3800 1.45v. but didnt work..
i also try to book under 4000, looser timings , 1.45 v, nothing.
fan part working good i got it in there vertically , honestly best tip i have had in a while.. not sure how i didnt think of that LOL
ill play around more once i get home from work but from my understanding

to reach 4000, i need to increase vdimm for 1.5v at 1.55 right? how about vsoc and vddg? i don tknow if i wanna push that much.
but i would like to tighten for 3800 to better latency but overall im already pretty happy

Going on high speed FCLK/UCLK you may want to look closely on WHEA errors/warnings
You dont want to see a WHEA Event ID 19 (warning = correctable error) or have a crash under Event ID 18 (error = uncorrectable error)

You can see warnings either with HWiNFO64 or in Windows Event Viewer (Create a WHEA custom view for errors/warnings)





Right click Custom View >> Create Custom View
...and set it like this:

 

[noobzin]

Interesting
Now I’m curious if I can boot under 4000

 

[Zach_01]

Also the membench below can put some stress on FCLK, not so much on RAM.
Traditional RAM (stress) tests dont put too much stress on FCLK

This one does a bit, and also gaming does...

 

[noobzin]

Going on high speed FCLK/UCLK you may want to look closely on WHEA errors/warnings
You dont want to see a WHEA Event ID 19 (warning = correctable error) or have a crash under Event ID 18 (error = uncorrectable error)

You can see warnings either with HWiNFO64 or in Windows Event Viewer (Create a WHEA custom view for errors/warnings)

View attachment 261220

View attachment 261221

Right click Custom View >> Create Custom View
...and set it like this:

View attachment 261224

in case i do see either error 18 or 19. what does that mean?

 

[The King]

Interesting
Now I’m curious if I can boot under 4000

To boot 4000 you may need to play around with ProcODT.

Save your current profile first.
Reset your BIOS to stock
Change RAM frequency to 4000.
Then manually adjust primary timings only to 16-16-16-32-48. can also try 16-18-18-36-54.
Set FCLK to 2000 and UCLK = MCLK
VDIMM 1.45V-1.5V
My VSOC is on AUTO (1.10V) but you can set between 1.10V to 1.15V manually. (upto 1.2V is considered "safe" but read *)
Manually set ProcODT to 32 if no boot then try 36.2 then 43.6 and so on if you reach 60 and no boot then I would just run 3800 with FCLK 1900.

* None of the above should cause any issue or damage anything but remember with OCing there is always some risk you may break something so do at your own risk.

 

[noobzin]

Thanks for the help . It really didn’t do it unfortunately. But I was able to reach 3866 as of right now .
I followed your advise and went working my way with the procODT and was not successful booting.

 

[Zach_01]

I had some events ID 18 with crashes/restarts during gaming.
Seem to stop now with increased voltages on VSOC, CLDO VDDP, VDDG CCD/IOD.

I had also a lot of warnings (ID 19) with my previous 5900X when trying to run 1900MHz. At 1866 they were stop.
After a week that CPU started to produce artifacts on videos, pictures, thumbnails, some games run, others not…
I RMA it and now this one is fine and can run 1900MHz so far.

Description (type) of those events are:
ID 18: Cache Hierarchy error
ID 19: Bus/Interconnect error

 

[noobzin]

FINAL Update, just to follow up!

 

[The King]

FINAL Update, just to follow up!

Does RTP 6 not boot?

 

[noobzin]

Does RTP 6 not boot?

Im sure it does

 

[The King]

Im sure it does

That should be better for performance then. If you want to fine tune your RAM then you can try something like this.

 

[noobzin]

THATS A F4-4266C19D, its pretty stable now so im not messing with it anymore

 

[Deleted member 185158]

THATS A F4-4266C19D, its pretty stable now so im not messing with it anymore

Yeah, he's a bit underclocked, but that's from running AMD with IF 1:1 causes this. He'd be well over the rated speed on an Intel system, which is what XMP is designed for. Gotta pick your battles I guess.

 

[The King]

Yeah, he's a bit underclocked, but that's from running AMD with IF 1:1 causes this. He'd be well over the rated speed on an Intel system, which is what XMP is designed for. Gotta pick your battles I guess.

No issue running at XMP only problem is the performance sucks because its not 1:1:1 no point in running higher frequency then. FCLK 1900/1933/1966/2000 if you dont have WHEA 19 is best for AMD in most cases. Runing XMP is not