Memory performance remains unchanged at 3600MT/s despite D.O.C.P profile configuration.
Memory performance remains unchanged at 3600MT/s despite D.O.C.P profile configuration.
Hey there, I put this setup together using advice from a forum in 2021. At first, I had a 32GB stick but later bought another identical one to reach a 64GB total. When I checked the armoury crate, after opening it again, I noticed my memory speed was 2133MT/s instead of the expected 3600MT/s with DOCP enabled. I assumed DOCP was disabled. After restarting the PC and entering BIOS, the frequency listed was still 2133MT/s. What’s happening? Thanks for your help! Please feel free to share more details if needed.
Specs:
- Motherboard: Asus ROG Strix X570-E Gaming
- CPU: Ryzen 9 5900X
- RAM: G.Skill Trident Z Neo F4-3600C16D-32GTZNC
- Price: Dropped from 250 to 96 euros
Let me know if you want more info!
The task manager displays the list of running applications and processes, showing their names, icons, and status.
I switched to CPU-Z since Task Manager isn't giving accurate frequency data, though it's good to verify first. I also realized ASUS BIOS might be displaying memory speed oddly, which could mean XMP is active and the OP is only seeing the JEDEC speed numbers.
It's common for two kits to vary significantly, and employing four sticks frequently leads to complications.
It doesn't appear to be active. You might have adjusted it earlier or misinterpreted its status in the BIOS settings. If it shows 2133MT/s, it's off. There could be another menu immediately after the DOCP selection where you pick the exact profile—most manuals suggest enabling XMP/DOCP, but some boards require a multi-step setup to apply the correct speed. Another possibility is it was previously set to 3600 but failed to boot, so it defaulted for a successful start. You should have seen repeated crashes or debug messages when you tried to enable DOCP at 3600, which would prompt a reboot after saving and restarting from BIOS.
There are AMD AGESA versions where the safe boot functionality will kick in silently, meaning the only indicator that the system failed to train the requested settings is a slightly longer than usual boot time (a minute vs. 30 seconds only on the first boot) or a few looping POST codes if you're watching the POST code. On BIOSes with that behavior it's very easy to accidentally miss the baord reverting to stock settings because there's no "Memory OC Failed" splash screen or similar, and that's what I'd suspect happened here.