Running on four sticks is causing me discomfort.
Running on four sticks is causing me discomfort.
I continued the RAM saga, so it's time to message @RONOTHAN##, @WereCat, @Somerandomtechyboi, and @freeagent. With the health insurance refund, I chose to skip the 2x16GB path and opted for the same 2x8 kit I already own (Team T-Create Expert 3200C16 2x8GB). It bears the "Team" logo on the die label and is a Samsung B/C/D Die on the Thaiphoon Burner. I connected it to slots 1 and 3, then applied XMP to boot. It started with Command Rate 2T and GDM disabled. I attempted to overclock it for better performance, but it crashed my Windows install right away. On a weekday, I left it alone—just turned XMP off and boosted the voltage. It booted normally with tCWL at 16. This was the first step in DDR4 OC according to the guide I found. https://github.com/integralfx/MemTestHel...guide/DDR4 OC Guide.md#overclocking After a quick Windows reinstall to prepare for the call, I plan to try again this weekend. But then I noticed only 18/32GB is available for Windows in Task Manager. I’m really puzzled about this kit: how should I resolve the frustrating RAM issue? I’m confident I can fix it myself, but I feel overwhelmed. I’ve confirmed the RAM is properly seated and Windows isn’t the problem. Should I proceed with overclocking on just one die, keep speed low, or test the full 4-die setup? What about the IMC considerations for a multi-die configuration?
I just won't do it. If XMP is working and stable, stick with it. Trying to overclock mixed RAM setups usually leads to problems, so it's not worth the trouble. To be clear, having the new RAM in slot 1/2 and the old one in slot 3/4 makes more sense, allowing each chip to use its own memory path. In real tests I haven't seen any improvement on AMD boards, only on some Intel ones—so it's possible they don't fully support this. You might want to give it a try anyway. This suggests the issue is likely with the Samsung die, as it behaves differently above 1.35V. For the memory glitch, first re-seat the sticks and reset the CMOS (especially those slots), that should likely resolve it.
I noticed that issue when I tried to optimize this build alone—it didn’t exceed 3200. That’s why I’m leaning toward using XMP instead. It’s a bit disappointing since T-Create lags behind in latency, around 83ns. Thanks for the helpful advice! I’ll try your suggestion and keep you posted.
I only have the rams I own—three pairs of B-Die and a collection of Adata 3200C16 units. I’d put the weaker pair in the main slots, save the better ones for the secondary slots. I’ll clear the CMOS and start it up to see how it behaves. If you have XMP support, I’d be glad to try it.
Update brief, the 6GB is now missing. Is this typical or should I take action? I didn’t keep track of which stick serial matches which die. Could try swapping them again. @RONOTHAN##