F5F Stay Refreshed Power Users Overclocking Check Ram OC scores two days later to see how they differ.

Check Ram OC scores two days later to see how they differ.

Check Ram OC scores two days later to see how they differ.

A
alllymiller10
Junior Member
14
04-26-2026, 04:59 AM
#1
Hello everyone, here is my setup: Ryzen 5 3600 Stock RAM, Tomahawk B450 Motherboard, Asus Atheros 1.0.0.4 Chipset, and a Cruxial Ballistic sport LT 3200CL16 stick. I had done an overclock on my RAM before but wasn't happy with it because the XMP settings were too slow. This week, I wanted to try again to get better performance, so after trying many times to reset the CMOS settings, I finally found a setting that works for me and is very good. But now I have two different results: one shows 65.9 ns latency (link A) and the other shows 67.2 ns latency (link B). When I turned off my computer on Monday, I woke up to find the next day had a latency of 67.2 ns instead of my good number, and almost all my readings were missing. To fix it, I have to go into the BIOS and change something or reset the system completely. If I do that by backing up settings to Windows and then shutting down or rebooting, my PC works fine without losing any latency or data for a long time. But this problem only happens when the date changes on the computer. For example, if I fix my 65.9 ns setting by changing the date, I can shut down or restart my PC for 3-4 hours, but if I just keep waiting around the same day (like from 13h to 17h), my latency goes back to 67.2 ns. Another example: If I sleep at 22h and wake up tomorrow at 7h because of a new date, the latency becomes 67.2 ns again. Even if I go into sleep mode and turn it off manually, the latency comes back to 65.9 ns only when the computer shuts down or restarts normally. But if I do anything else like shut down or restart, it goes back to 67.2 ns (which is useless). I don't remember what happened exactly on my first overclocking attempt; I'm scared that something broke inside my RAM. The only thing I've changed recently is updating my motherboard BIOS from version 1.0.0.4 to 1.0.0.5, but I also updated Windows from version 1903 to 2004 on some days. However, when I tried all my tests at version 1903, they didn't work for me anymore; the latency is still bad because I recently just upgraded Windows and used AMD drivers instead of the MSI site.
A
alllymiller10
04-26-2026, 04:59 AM #1

Hello everyone, here is my setup: Ryzen 5 3600 Stock RAM, Tomahawk B450 Motherboard, Asus Atheros 1.0.0.4 Chipset, and a Cruxial Ballistic sport LT 3200CL16 stick. I had done an overclock on my RAM before but wasn't happy with it because the XMP settings were too slow. This week, I wanted to try again to get better performance, so after trying many times to reset the CMOS settings, I finally found a setting that works for me and is very good. But now I have two different results: one shows 65.9 ns latency (link A) and the other shows 67.2 ns latency (link B). When I turned off my computer on Monday, I woke up to find the next day had a latency of 67.2 ns instead of my good number, and almost all my readings were missing. To fix it, I have to go into the BIOS and change something or reset the system completely. If I do that by backing up settings to Windows and then shutting down or rebooting, my PC works fine without losing any latency or data for a long time. But this problem only happens when the date changes on the computer. For example, if I fix my 65.9 ns setting by changing the date, I can shut down or restart my PC for 3-4 hours, but if I just keep waiting around the same day (like from 13h to 17h), my latency goes back to 67.2 ns. Another example: If I sleep at 22h and wake up tomorrow at 7h because of a new date, the latency becomes 67.2 ns again. Even if I go into sleep mode and turn it off manually, the latency comes back to 65.9 ns only when the computer shuts down or restarts normally. But if I do anything else like shut down or restart, it goes back to 67.2 ns (which is useless). I don't remember what happened exactly on my first overclocking attempt; I'm scared that something broke inside my RAM. The only thing I've changed recently is updating my motherboard BIOS from version 1.0.0.4 to 1.0.0.5, but I also updated Windows from version 1903 to 2004 on some days. However, when I tried all my tests at version 1903, they didn't work for me anymore; the latency is still bad because I recently just upgraded Windows and used AMD drivers instead of the MSI site.

E
emilyw9899
Junior Member
4
04-26-2026, 10:02 AM
#2
How much voltage do you need now that your RAM is overclocked? You probably want to update your BIOS first, like using an AGEsa version. Then try the same overclock, but maybe add a tiny bit more power—like going from 1.35v up to 1.4v if needed.
E
emilyw9899
04-26-2026, 10:02 AM #2

How much voltage do you need now that your RAM is overclocked? You probably want to update your BIOS first, like using an AGEsa version. Then try the same overclock, but maybe add a tiny bit more power—like going from 1.35v up to 1.4v if needed.

J
JarlSir
Junior Member
8
05-07-2026, 07:45 PM
#3
Hey Lutfij Dram Voltage: 1.39 volts (everything is fine after 5 hours). Soc is at 1.1v. I tried Agesa 1.0.0.5 but games stopped working, so I went back to 1.0.0.4
J
JarlSir
05-07-2026, 07:45 PM #3

Hey Lutfij Dram Voltage: 1.39 volts (everything is fine after 5 hours). Soc is at 1.1v. I tried Agesa 1.0.0.5 but games stopped working, so I went back to 1.0.0.4

E
emstay26
Senior Member
441
05-19-2026, 02:36 PM
#4
Wait, how can I get stable 47.0ns memory latency on my DDR3 running at 2000 / 2133 / 2400mhz? There must be something wrong or the latency is really bad with ddr4. I'm always getting 45-50ns memory latency on memory above 2133mhz on ddr3. This has been tested on about 10 different systems.
E
emstay26
05-19-2026, 02:36 PM #4

Wait, how can I get stable 47.0ns memory latency on my DDR3 running at 2000 / 2133 / 2400mhz? There must be something wrong or the latency is really bad with ddr4. I'm always getting 45-50ns memory latency on memory above 2133mhz on ddr3. This has been tested on about 10 different systems.