Is my RAM overclocking accurate for the first time?
Is my RAM overclocking accurate for the first time?
I chose to use the Ryzen DRAM calculator because I had no prior experience with this. I entered the correct details and then chose the SAFE option. The reason for doing an overclock was that it was set at 2133MHz by default, even though it was rated for 3200MHz.
You don't have to rely on Ryzen Dram Calc for DIMMS to operate at its full capacity. Just set XMP/DOCP mode for 3200mhz and leave other BIOS settings unchanged. XMP is the proper method to ensure DIMMS functions correctly. Dram Calc is mainly for overclockers aiming to push performance further.
On Asus systems, enable DOCP (direct over clock profile), which serves as the equivalent of XMP on those boards. Choose the desired memory speed, and your RAM will operate according to its specifications. This approach will yield better results than manual adjustments.
You don't have to rely on Ryzen Dram Calc for DIMMS to operate at its full capacity. Just set XMP/DOCP mode for 3200mhz and leave other BIOS settings unchanged. XMP is the proper method to ensure DIMMS functions correctly. Dram Calc is mainly useful for overclockers aiming to maximize performance.
On Asus systems, enable DOCP (direct over clock profile), which serves as the equivalent of XMP on those platforms. Choose the desired memory speed, and your RAM will operate according to its specifications. This approach will yield better results than manual adjustments.
I attempted to adjust the configuration to d.o.c.p and set the frequency to 3200mhz. However, I think the voltage for four sticks was too low by default (1.2v), especially after my PC crashed previously. After that, I decided to use the Ryzen Drm calc.
#2
To be truthful, the main reason I purchased the 2x8 kit twice was because I noticed they were on sale at that time and it appears more appealing when all slots are filled.
😛
Edit: The only motivation for this thread was that I had no clue what any of the changes meant—I simply followed the calc program, changed only what it suggested, and left the rest as the program set automatically. I’m just asking if the adjustments I made were correct, since I assumed you’d know better than me what they should be.
Also, I’m curious whether settings I missed in BIOS are relevant, as I couldn’t modify them due to that situation.
Another error occurred.
Ram is sold in kits for a reason.
A motherboard needs to handle all the RAM according to the same voltage, case, and speed specifications.
The internal design is tailored for the capacity of the kit.
Ram from the same manufacturer and part number may have different manufacturing parts over time.
Some motherboards are particularly sensitive to this issue.
It becomes more challenging when multiple sticks are used.
That’s why RAM manufacturers won’t support RAM that isn’t purchased in a single kit.
Luckily, your setup is still functional.
For improved stability, consider slightly increasing the RAM voltage.
My DRAM voltage is at 1.360v, which matches the recommendation for my RAM configuration in the Ryzen Dram calc tool. The range was between 1.35 and 1.390, so I chose the middle value of 1.360v. It looks normal to me so far. I'm just worried about whether I've adjusted the other settings properly :/
Execute run memtest86 to test your memory. You should be able to finish a complete pass without any mistakes. You might notice a balance exists between CPU overclocking and memory performance. I'm unsure if it's worth spending time adjusting things when everything seems fine.
Okay i'll run the test just out of curiosity and hopefully it's gonna stay stable
however i decided i'll keep the ram at 3200mhz d.o.c.p preset for now since theres a 20 score difference in cinebench and the voltage increased to 1.350v when i picked the profile. I guess i was doing something wrong when i did the d.o.c.p in the past that made it crash. Thanks for all the help guys
😀
Yes, most OC dims operate efficiently at 1.35v for the XMP setting.
They are functioning at their best, so no adjustments needed. You could potentially shorten the runtimes slightly more.