Ryzen AM5 Hynix 16Gb M-die DDR5 timings 2x16GB/2x32GB DDR5-6000 to DDR5-6400 V0.1
Added 2024-12-22 00:14:22 +0000 UTCAn expanded version of the original "easy Hynix timings". 16Gb M-die generally doesn't clock past 7000ish so all the settings here are for 1:1 mode since 2:1 mode at less tha 7600 doesn't perform well.
Comments
1.35V for both should work
Actually Hardcore Overclocking (Buildzoid)
2025-11-05 19:32:44 +0000 UTCwhat should i set vddq and vddio to? on my asrock mainboard there is no auto option and the default value is just 1.1
Np
2025-11-05 19:31:00 +0000 UTCthe 6400 timings are looser than the 6000 or 6200 timings.
Actually Hardcore Overclocking (Buildzoid)
2025-10-02 23:59:41 +0000 UTCHey BZ, I’ve gotten 6200 (BZ Lazy) to run stable at 2200fclk. I am unable to get 1:1 6400. Question, will adding in the timing from the 6400 section benefit my 6200 1:1 BZ lazy or do I leave as is?
Jordan Monsalve
2025-10-02 13:30:35 +0000 UTCthat's kinda weird to be getting errors at a temp that low. Maybe give it a tad more VDD
Actually Hardcore Overclocking (Buildzoid)
2025-09-21 17:44:41 +0000 UTCI got the 6000 BZ lazy settings working except for the max trefi setting of 65k, the hottest module reaches 47.7C at which point it errors. But i don't trust the the ram fully seems to me that should still be an ok temp? There is a fan on it but since i run an air cooler it's a bit more tricky to get proper airflow, one of the sticks is covered by the cooler. I used the V02 guide.
Riotvan
2025-09-21 10:28:07 +0000 UTCworks the same for 7000 and 9000 always use the newest version
Actually Hardcore Overclocking (Buildzoid)
2025-07-04 10:46:13 +0000 UTCHey, is this for ryzen 7000? Shoud I use v0.1 or v0.2. Thanks
8vasa8
2025-07-04 09:54:16 +0000 UTCHi. What value do you recommend to set for "Scalar" and "PBO Limits" parameters in Precision Boost Overdrive for AMD processors? I prefer "Motherboard" and "1X". Is it worth to set something else? (Games)
Jon
2025-06-15 17:03:08 +0000 UTCyeah 12 is sometime too tight. tRTP also doesn't affect performance much
Actually Hardcore Overclocking (Buildzoid)
2025-05-31 18:50:57 +0000 UTCWhy is tRTP 16 here when it was 12 on the old easy timings, is 12 sometimes not stable on m die?
KeinNiemand
2025-05-31 18:44:16 +0000 UTCBut thanks Buildzoid, absolutely would not have been able to figure this out on my own, and it's a noticeable and measurable performance difference over the EXPO settings.
Brian Wagner
2025-05-21 22:04:02 +0000 UTCFor anyone who ran into this issue: My RAM was running perfectly stable with EXPO (t-create CTCED532G6000HC30DC01) 6000@30-36-36-76, but would error out on TM5 Absolut even on the "easy" and even the "fallback" settings, which surprised me. After a lot of trial and error setting tRTP from 16 to 17 did the trick, and I can now run the Buildzoid "Fallback" settings. The "Easy" settings, or even just trying to get timings to 32-37-37-126 with DRAM VDD @1.43, will still error out within a few minutes of TM5 Absolut. It could be an unlucky ram kit, but I've also read sometimes ITX boards are more susceptible to this. FWIW I have an AsRock B650i Lightning and a 9600X.
Brian Wagner
2025-05-21 21:59:23 +0000 UTCYou have to look at the sticker on the RAM stick itself. 5.43.1 is A-die. 5.43.13 is M-die
Kyle Robertson
2025-05-09 20:15:12 +0000 UTCWhat die is CMH64GX5M2B6400C32 corsair Vengeance, I know it is hynix but a or m
Mr.WhatZitTooya69
2025-04-13 06:45:44 +0000 UTCfor 6000 and 6200 always for 6400 it might depend a bit on the workload(because 2133 is already really close to 2200 in bandwidth).
Actually Hardcore Overclocking (Buildzoid)
2025-02-24 11:02:22 +0000 UTCThat’s great info. I am going to try some of your timings for my gskill 64gb kit. Timings have always been a pain for me, so these quick solutions are an awesome resource. I’m very impressed with the 9800x3d so far. I can run 1.26v and hold 5.5ghz all core, no de lid, just a basic thermalright water to air. I don’t run the typical gambit of stability testing, instead run my cad workloads +/- the games I might play, and or web pages I might open. So having a decent ram timing guide to work from or just use, has been the final overclocking resource I have always needed.
Mike
2025-02-24 00:48:57 +0000 UTCin 1:1 mode it's generally gonna be faster. For 2:1 the latency penalty for desyncing usually out wieghs the extra bandwidth
Actually Hardcore Overclocking (Buildzoid)
2025-02-23 23:36:34 +0000 UTCIs there any downside to going above the FCLK’s listed? I found I can get to 2200mhz fclk on my 9800x3d without issue. I don’t see any where that fclk needs to be ratio’d with other speeds for these later zen chips. Or is there some kind of obvious detriment?
Mike
2025-02-23 22:53:06 +0000 UTCUnable to open the attachment :(
Raul
2025-02-14 17:25:44 +0000 UTCDid you try not copying the Primaries? Because the subtimings are pretty much the same as the old ez timings
Actually Hardcore Overclocking (Buildzoid)
2025-02-13 06:16:04 +0000 UTCUnfortunately I purchased this today, but for me and my 9800x3d, Asus x670e-i with Tforce 6000 30-36-36-76 1.35v M-die sticks, the 6000mhz pages fallback and easy columns either don't get into windows or aren't stable :( I used the original ez timings with same setup for a very long time?
Wongfamily
2025-02-13 04:37:30 +0000 UTCTried these timing on my Asus B650E-E / 7800X3D / 2x32GB GSKILL Trident Z CL30 Hynix M dies. I think I must have done something wrong. Shouldnt i be getting better performance with this? https://imgur.com/a/6kbt0wx
NotePad X
2025-02-04 19:12:29 +0000 UTCtyvm 💖 How do you change tRCDWR on Asus MB? they seem to be tied together?
EumelEumel
2024-12-23 16:32:38 +0000 UTCUse tRCDRD value
IamAmerican
2024-12-23 02:46:25 +0000 UTCHi. I need some help, please. I am like super new to all of this. In this guide AHO have included tRCDWR and RD values separately but in my bios (ASUS b650e itx) I only have tRCD. Which tRCD value should I use then?
Vasily Morozko
2024-12-23 00:20:19 +0000 UTCI have not isolated this in timespy extreme CPU. In Aida the difference in write of around 400mbps. I have however tested the combination of this tweak, wrrd 1, nitro tx 3 vs the best oc I had prior to this. We're looking at 4558 vs 4582 with a Ryzen 7500f at fixed 4.2GHz. . In any case your BZ lazy presents do fulfill this criteria. Just the fallback and "easy" does not. I am absolutely nitpicking here, there is no real world gain from any of those tweaks; they are just for the joy of pushing the oc. Rather I hope people who copy your timings do note that lowering some specific timings by just one tick may worsen performance. Especially when that timing ends up at a very odd fraction of a burst. . I could also note that the refi timing is best kept at 0xffff - 0x0fff * n - 1, such as 49154. Or ensuring that refi - rfc is a multiple of burst that is (refi + 1 - rfc + 1) % 8 = 0. But that has absolutely no measurable performance impact.
InkyBusiness
2024-12-22 21:59:42 +0000 UTCany non-AIDA benchmarks proving this?
Actually Hardcore Overclocking (Buildzoid)
2024-12-22 21:42:34 +0000 UTCFor WRITE operations you don't need the ACT to completely fully. So you can have very very low tRCDWR
Actually Hardcore Overclocking (Buildzoid)
2024-12-22 21:39:45 +0000 UTCA little sidenode on the command buffer configuration aka Nitro. Mobos default to rx 2, tx 3, cl 1. Lowering the read buffer ticks to 1, or disabled, improves latency drastically. Increasing it to 1 or 2 may theoretically yield a better rcdrd. I have not practically seen this have a postive effect on rcdrd. Lowering it below cl is useless though. . Leaving tx at 3 as it doesn't really have any adverse effect on latency or bandwidth, and lower values may worsen stability significantly. tx 3 may also enable wrrd 1 on systems that don't like it initially. All my DDR5 did do wrrd 1. Especially combining this with the two writes per read tweak does improve performance by a bit. . To the best of my knowledge, cl 1 is infact additive in latency to gear down mode, cl2 is gdm 1/4. 0 is gdm off. It should be the timings of the internal link between the umc and phy. But please do correct me here if I am incorrect.
InkyBusiness
2024-12-22 17:15:48 +0000 UTCI assume you made a mistake setting tRCDWR as 16 in the BZ lazy settings? Is it supposed to be 36?
Exostenza
2024-12-22 16:58:16 +0000 UTCI expect better performance for most of the presented preset with slightly higher timings, that allow execute within two writes per read
InkyBusiness
2024-12-22 13:34:48 +0000 UTCThe constellation wr=48 wtrl<=wr/2 rddl>=wtrl*2 rtp>=wtrl/2 rdrdscl=rrdl-rrds+1 allows DDR5 to execute two writes per read. This is configuration yields a lower latency than forcing timings a bit lower. Lower timings pay of when much tighter. Timings allowing for this are for example: RRDS 8 RRDL 12 WTRS 4 WTRL 24 RDRDSCL = 12-8+1 = 5 Generally we have convinient numbers of especially ras that are higher than the the buildzoid timings, but will likely perform better, such as ras 36 being a multiple of rtp and burst or at least burst/2: Lots of little tweaks can be applied according to the architecture of DDR5
InkyBusiness
2024-12-22 13:31:05 +0000 UTC
