The Ryzen 5 3600 struggles more with overclocking compared to the Ryzen 5 1600.
The Ryzen 5 3600 struggles more with overclocking compared to the Ryzen 5 1600.
At first, my setup ran smoothly with a Ryzen 5 1600 and four Corsair LPX 4GB modules on an MSI B350 Tomahawk board. Memtest confirmed stability at 2933MHz and 1.26v. When switching to a Ryzen 5 3600, performance dropped sharply—cannot exceed 2733MHz even at 1.35v without frequent errors and blue screens. At 2733MHz, memtest achieved full coverage with zero issues. I noticed the system would overvolt the SoC for memory stability with the Ryzen 3000 series, defaulting to around 1.01v. I adjusted it in small steps up to 1.25v, but still struggled at 2800MHz. It appeared to reduce errors slightly. Could this be due to a faulty CPU or an overlooked setting? Perhaps this is normal behavior? Any feedback would be helpful.
Run the DRAM calculator to check the results. It may indicate incorrect timing settings.
I shared a 4-year-old screenshot of my earlier settings, and it's clear my timing was different now. @boggy77 the instructions are really useful for staying on track. Right now I'm running at 2933 MHz again, with about 15% coverage so far from memtest, hoping for success. Previously, it wouldn't even pass at that frequency, which is encouraging! The only problem is I can't use the "Fast" preset for DRAM Calculator—it shows an error message. I'm feeling hopeful, but I'll run some benchmarks soon. My infinity fabric seems happy with this setup.
Seems like this might not fit neatly into any standard category. I ran several tests on memtest and noticed all my fixed allocation settings stuck at 2081.1% coverage for over 20 minutes. Once I wrote this down, they gradually improved. No errors were logged, but there’s a chance it could still be an issue. The tabs didn’t freeze—they just didn’t grow in coverage. Cyberpunk wouldn’t even make it past the title screen at 3200 MHz, though memtest, cinebench, and the desktop stayed stable. At 3066 it crashed after about 15 minutes. A big update to the game a day earlier caused more crashes, making it hard to pinpoint the problem.