Your memories might not sync properly because the XMP profile isn't being applied correctly.
Your memories might not sync properly because the XMP profile isn't being applied correctly.
Ryzen 5600, Stepping VMR-B2, codenamed Vermeer. Previously I owned a 3600X and it behaved similarly. Mobo: GIGABYTE B450 AORUS M, firmware version F63a (the issue occurred with various BIOS updates; I updated the firmware three times, resulting in problems across three versions). 2x8GB (F4-3000C15-8GVKB), XMP profile: 15-16-16-35 (CL-RCD-RP-RAS) at 1.35v. The spoiler module is from G.Skill, part number F4-3000C15-8GVKB, series Ripjaws V Black. DRAM details: Hynix DRAM, H5AN8G8NCJR-TFC, revision C / 18 nm. Manufacturing info: Taipei, Taiwan, serial 00000000h, PCB revision 00h. Many factors are involved—when I enable XMP, the system crashes during Windows boot and generates numerous errors in memtest86. I've adjusted VRAM voltage from 1.2v to 1.36v without success, manually set multiplier to 29.33 for perfect boot, but changes happen automatically. The memory settings shift unexpectedly; what was "15-16-16-35" now reads "16-16-16-35" without explanation. I've experimented with precise calculations using a calculator, yet the PC won't even POST. I've tried safe configurations and still face difficulties. Any advice or checks you could suggest? I'm new to this and might have overlooked something obvious.**
The BIOS is more than a year outdated. You need to upgrade to the newest release first.
Because GDM is activated, Gear Down Mode enhances memory stability on AMD chips but introduces some latency and limits certain timing options, especially around CAS Latency. Those "Safe" settings are quite restrictive for CJR, which makes it unlikely they will function properly. For reliable CJR performance, use 3600 CL16-19-19-39 @1.4V—this should work if your BIOS supports it. It’s possible your BIOS either completely disables memory overclocking or has a faulty 3000MT/s setting. If you have CJR, consider increasing RAM speeds, as the chip can handle higher frequencies. Also verify with Thaiphoon that both RAM sticks are identical, as mismatched models can cause problems.
It's good to know about GDM, but I'm not sure what you're referring to. Why is it an issue to use even timings? Your 3000MHz frequency is fine, but if your motherboard has a 3000MT/s problem, running at 3600MHz might still cause trouble. You've already experimented with similar setups and found them unsuccessful. I checked both sticks multiple times with various programs, but I'm not sure they match exactly. It would be helpful to verify everything now.
Uncertain about AMD's documentation availability. The CAS latency seems tied to the Ryzen 3000/5000 memory controller; some boards handle it, while others with CL15 or CL17 models fail entirely. It might be the 3000MT/s ratio is incorrect, which could explain the issue—especially on my Z690 Unify-X where I can boot 8200 and 8400 but not 8266 in A9 BIOS. No recent BIOS updates show a broken 3600 ratio, so testing it wouldn't be risky. If it doesn't work, simply reset CMOS and retry the 3000MT/s setting. It could just be a display error with the model number. Still worth checking briefly—it's quick and won't delay your build.
Need to test your ideas too. Checking for any updated BIOS releases and seeing if others are facing the same issue with this motherboard.
I've tested the 36 multiplier at 3600mhz without any luck. I've reduced each timing by two points to allow more breathing room, but it still doesn't post. Could you consider adjusting the settings further or try different approaches to increase the multiplier until you find a suitable setting?
Begin by verifying a different BIOS revision; it might simply be a compatibility issue with your current setup. If that doesn’t resolve the problem, consider these adjustments: adjust the SOC voltage to 1.15V, which generally optimizes performance across most Ryzen 3000/5000 models. This setting is stable for extended use and should help address memory controller concerns. Experiment with the ProcODT configuration—most systems auto-set it well, but tweaking it slightly could boost boot speeds beyond 3000MT/s. Also, play around with DRAM voltage; while I wouldn’t recommend exceeding 1.45V for daily operation, a higher voltage might be needed to stabilize the controller. Other tweaks like RTT and drive strength settings exist, but they usually require significant effort and aren’t worth it unless you’re deeply invested.