[Humbleweed]

Hi all,
I have a HP Pavilion TG01-0021no from 2019. A prebuilt gaming pc that I´ve modded quite a lot. Specs listed below.

SPECS:
MOBO: HP Erica, has only 2 RAM slots, dual channel
CPU: Ryzen 5 3400g, no OC, HP original stock cooler
GPU: Asus Geforce 1070
Storage: NVME M2 WD Black 1Tb
RAM: Corsair Vengance DDR4 3000 Mhz 2x8Gb
650w PSU

I first looked in task manager on the memory page and saw it was set at 1066 Mhz.

-- Actions:
BIOS on these computers are very locked, so to increase my RAM speed I used Ryzen Master.
I went into the program as administrator. Increased the speed to 1500 and the CL to 16, then had to increase that to 17 to get PC to boot (in between reseted bios by pulling the battery out for a few min) every setting besides this is on Auto.

Now it boots perfectly and the system seems stable and passes stress test.

-- Question:

HOWEVER, now to my question. I cannot for the life of me figure out if the RAM speed really is changed.

• In task manager; the speed row has vanished (?)
• In CPU-Z, it says DDR 1500 Mhz
• In BIOS, it says 16 GB 2133 Mhz
• In Ryzen Masters Home page it says 1500 Mhz
• When I type "wmic memorychip get speed" in command prompt - it says: 2133 Mhz 2133 Mhz

What speed do I have them set to, and what can I do to set them to 3000 Mhz instead of 2133 Mhz if they aren´t increased?

 

[TwoCables]

Hi all,
I have a HP Pavilion TG01-0021no from 2019. A prebuilt gaming pc that I´ve modded quite a lot. Specs listed below.

SPECS:
MOBO: HP Erica, has only 2 RAM slots, dual channel
CPU: Ryzen 5 3400g, no OC, HP original stock cooler
GPU: Asus Geforce 1070 NVME M2 WD Black 1Tb
RAM: Corsair Vengance DDR4 3000 Mhz 2x8Gb
650w PSU

I first looked in task manager on the memory page and saw it was set at 1066 Mhz.

-- Actions:
BIOS on these computers are very locked, so to increase my RAM speed I used Ryzen Master.
I went into the program as administrator. Increased the speed to 1500 and the CL to 16, then had to increase that to 17 to get PC to boot (in between reseted bios by pulling the battery out for a few min) every setting besides this is on Auto.

Now it boots perfectly and the system seems stable and passes stress test.

-- Question:

HOWEVER, now to my question. I cannot for the life of me figure out if the RAM speed really is changed.

• In task manager; the speed row has vanished (?)
• In CPU-Z, it says DDR 1500 Mhz - In BIOS, it says 16 GB 2133 Mhz
• In Ryzen Masters Home page it says 1500 Mhz
• When I type "wmic memorychip get speed" in command prompt - it says: 2133 Mhz 2133 Mhz

What speed do I have them set to, and what can I do to set them to 3000 Mhz instead of 2133 Mhz if they aren´t increased?

You have them set to 2133 MHz.

There's no hope in overclocking memory in a prebuilt system like that. You'd need a high-end system that you built yourself with a carefully selected motherboard and carefully selected memory if you want to overclock memory that far above stock (the motherboard you choose is more important than the memory). You see, it's not just the memory that needs to be overclockable. The motherboard has to be good at overclocking memory as well.

I can tell you with 100% certainty you'd be much happier with a system that you've built. You already have the aptitude for it.

 

[Humbleweed]

That´s just not fun to hear. Considering that I´ve invested some energy into this can =)
FIrst of, the 310w PSU was proprietary and motherboard has no 24-pin socket, but instead other really random other connections. So I´ve measured voltage in each wire, bought an 650 ATX PSU and a 24-pin extension cable and built a working adapter. Then cut away some metal in the case to fit that new PSU. Then cut holes into the side of the metal chassi and installed intake fans.

Motherboard and chassi are OEM as well so I would also need a new case to change motherboard.

I get what you´re saying. Although because of the above I must ask; There is no other way to force the motherboard to run the RAM with 3000 Mhz?

 

[Blameless]

If you really want to be sure, benchmark it.

A lot of high speed memory is built with 2133 OEM speed bins and most modern DDR4 ICs will do 3000MT/s no matter what it was rated for.

Memory rebranders usually do additional rounds of binning so anything they put in slower bins is typically a binning reject, but this does not apply to OEM first-party memory.

 

[Humbleweed]

If you really want to be sure, benchmark it.

A lot of high speed memory is built with 2133 OEM speed bins and most modern DDR4 ICs will do 3000MT/s no matter what it was rated for.

Memory rebranders usually do additional rounds of binning so anything they put in slower bins is typically a binning reject, but this does not apply to OEM first-party memory.

Sure, allright I will.
What would be good to use to read the results? I’ve heard of aida64 membench but never used it.

I have replaced the original memories with corsairs, only the motherboard left that is from the original PC.

I know that others have done this successfully on this computer so this is my reason for continuing.

 

[Blameless]

What would be good to use to read the results? I’ve heard of aida64 membench but never used it.

AIDA64 cachemem is popular, but anything that gives consistent results and is memory performance dependent will work. That large a differential in memory clock should show up very clearly in something like 7-Zip, for example.

 

[UltraMega]

You have them set to 2133 MHz.

There's no hope in overclocking memory in a prebuilt system like that. You'd need a high-end system that you built yourself with a carefully selected motherboard and carefully selected memory if you want to overclock memory that far above stock (the motherboard you choose is more important than the memory). You see, it's not just the memory that needs to be overclockable. The motherboard has to be good at overclocking memory as well.

I can tell you with 100% certainty you'd be much happier with a system that you've built. You already have the aptitude for it.

I'm not sure that's true. If CPUz is reporting 1500mhz the his ram is running at 3000mhz, correct? CPUz wouldn't report the wrong speed just because ryzen master wants it to if the ram isn't actually running at that speed.

OP, since you are overclocking with software, your setting are not part of the bios at all. Ignore the bios. Your ram settings would only be applied after your computer boots up into windows so the software can run.

 

[Humbleweed]

I'm not sure that's true. If CPUz is reporting 1500mhz the his ram is running at 3000mhz, correct? CPUz wouldn't report the wrong speed just because ryzen master wants it to if the ram isn't actually running at that speed.

OP, since you are overclocking with software, your setting are not part of the bios at all. Ignore the bios. Your ram settings would only be applied after your computer boots up into windows so the software can run.

AIDA64 cachemem is popular, but anything that gives consistent results and is memory performance dependent will work. That large a differential in memory clock should show up very clearly in something like 7-Zip, for example.

Thank´s very much for your replies. Now done with the Aida memory benchmark. What do you make of the results, 1498,7 Mhz says it works, right?

 

[o1dschoo1]

Thank´s very much for your replies. Now done with the Aida memory benchmark. What do you make of the results, 1498,7 Mhz says it works, right?

View attachment 2481320

Id say its running 3000.

 

[Asmodian]

It does look like it is running at DDR4-3000 but 80ms latency is a big higher than I would like to see.

Can you mess with the timings in Ryzen Master? I would try for better than 18-21-21-50. (is 15-17-17-35 possible?)

Edit:
Reading across try 15-17-17-17-35 at 1.35V or 1.40V (if you can adjust memory voltage?)

 

[Humbleweed]

It does look like it is running at DDR4-3000 but 80ms latency is a big higher than I would like to see.

Can you mess with the timings in Ryzen Master? I would try for better than 18-21-21-50. (is 15-17-17-35 possible?)

Edit:
Reading across try 15-17-17-17-35 at 1.35V or 1.40V (if you can adjust memory voltage?)
View attachment 2481375

Thank you so much!

Is MEM VDDIO the one to be changed then? That is automatically set to 0,79 Volt.

 

[Asmodian]

I am not sure I would mess with any of those voltages unless you needed to increase SOC and/or VDDP slightly. MEM VDDIO should be the memory voltage, except 0.8V for your RAM isn't going to work so I am not sure what to set there. Was it in a power down state and do you ever see MEM VDDIO show 1.2V? I think you should set MEM VDDIO to 1.35 Volts and MEM VTT to 0.67 V.

I would set the CAS and the rest to 15-17-17-17-35 and see if it works without changing SOC or VDDP voltages first. 3000 MHz should be easy for the memory controller so you probably won't need to give it extra voltage, but the DRAM itself probably does need the 1.35V instead of 1.2V to run at the tighter timings.

MEM VTT should be one half of MEM VDDIO, but some undershoot is also normal, so 0.54V makes me think the ram is currently running at 1.2V.

 

[Humbleweed]

I am not sure I would mess with any of those voltages unless you needed to increase SOC and/or VDDP slightly. MEM VDDIO should be the memory voltage, except 0.8V for your RAM isn't going to work so I am not sure what to set there. Was it in a power down state and do you ever see MEM VDDIO show 1.2V? I think you should set MEM VDDIO to 1.35 Volts and MEM VTT to 0.67 V.

I would set the CAS and the rest to 15-17-17-17-35 and see if it works without changing SOC or VDDP voltages first. 3000 MHz should be easy for the memory controller so you probably won't need to give it extra voltage, but the DRAM itself probably does need the 1.35V instead of 1.2V to run at the tighter timings.

MEM VTT should be one half of MEM VDDIO, but some undershoot is also normal, so 0.54V makes me think the ram is currently running at 1.2V.

Incredibly eloborate answer - thank you friend. I´ll post the results again in a little while.

 

[Humbleweed]

I am not sure I would mess with any of those voltages unless you needed to increase SOC and/or VDDP slightly. MEM VDDIO should be the memory voltage, except 0.8V for your RAM isn't going to work so I am not sure what to set there. Was it in a power down state and do you ever see MEM VDDIO show 1.2V? I think you should set MEM VDDIO to 1.35 Volts and MEM VTT to 0.67 V.

I would set the CAS and the rest to 15-17-17-17-35 and see if it works without changing SOC or VDDP voltages first. 3000 MHz should be easy for the memory controller so you probably won't need to give it extra voltage, but the DRAM itself probably does need the 1.35V instead of 1.2V to run at the tighter timings.

MEM VTT should be one half of MEM VDDIO, but some undershoot is also normal, so 0.54V makes me think the ram is currently running at 1.2V.

Allright, here are the results. Seems the latency only decreased by 3 from 79 to 76 though.

MEM VDDIO now set to 1,35V
MEM VTT is maxed on 0,66V and cannot be increased more in the program.

You can see the other parameters are 17-17-17-17-35.

 

[Asmodian]

Try 16 for CAS, not 17. Your RAM is likely to be stock at 15-17-17-35 @ 1.35V but with Gear Down Mode enabled CAS has to be even, so 16 instead of 15.

Any improvement is good, but I was hoping for a little better.

I guess your secondary timings are also too high, but figuring out good values for all the other timings is tricky. You need to figure out exactly what type of DRAM you have (make and model).

 

[Humbleweed]

Try 16 for CAS, not 17. Your RAM is likely to be stock at 15-17-17-35 @ 1.35V but with Gear Down Mode enabled CAS has to be even, so 16 instead of 15.

Any improvement is good, but I was hoping for a little better.

I guess your secondary timings are also too high, but figuring out good values for all the other timings is tricky. You need to figure out exactly what type of DRAM you have (make and model).

Putting the CAS down to 16 made the system unable to boot. Needed to put it back to 17 which automatically becomes 18. So guess we´re done, and a at dead end then?

Or does increasing the voltage further make it possible to lower the CAS to 16? However MEM VTT is maxed and will loose it´s "half MEM VDDIO ratio" if I increase MEM VDDIO further.

 

[Asmodian]

I would be comfortable setting the MEM VDDIO up to 1.45V, leaving MEM VTT at its max is fine.

 

[Humbleweed]

I would be comfortable setting the MEM VDDIO up to 1.45V, leaving MEM VTT at its max is fine.

Thanks I´ll try that. So increasing the voltage makes room for the latency decrease? Thank you overall, feels like I kidnapped your attention.

 

[Asmodian]

Thanks I´ll try that. So increasing the voltage makes room for the latency decrease? Thank you overall, feels like I kidnapped your attention.

Yes, generally extra voltage helps but 1.5V is arguably the max safe voltage for DDR4 so 1.45V is the recommended limit unless you really want to push it (higher risk). It also depends on the memory chips how much extra voltage helps. It is common to hit a wall at some point where extra voltage does not help anymore.

Happy to help.

 

[jimj]

I have a "HP Pavilion Gaming Desktop TG01-2003w PC" which uses the Erica6 (SSID: 8906) motherboard. When trying to research my motherboard's weirdness I came across this thread which helped. In case anyone else in a similar situation stumble's across this thread I'll summarize some of what I've discovered. Our motherboards share some quirks like:

The BIOS boot screen and 'wmic memorychip get speed' always report the stock/default RAM speed, not the configured/running speed. You can verify the true running speed in task manager or by running 'wmic memorychip get ConfiguredClockSpeed' (to see all the RAM info run 'wmic MemoryChip get /format:list' instead). The best way to check (and verify your RAM is stable) is to boot into MemTest86. MemTest86 will show the RAM's configured speed and other details. Of course it also checks if your RAM is stable.

Ryzen Master does write its settings to somewhere in the BIOS/UEFI/motherboard's memory (otherwise the configured RAM speed wouldn't be applied when you boot into another OS like MemTest86). If you mess up your RAM settings with Ryzen Master shorting the motherboard's CLR_CMOS pins says it clears the CMOS settings, but it does NOT clear out the RAM settings. To clear the RAM settings you must unplug the computer, remove the button battery, hold the power button in for five seconds, reinstall the battery, plug the computer back in and turn it on (first boot after clearing is longer, takes about a minute for me).

My RAM is stable at 1600 (DDR4-3200) when it auto selects 24-23-23-52 timings. If I try to improve my timings it won't boot. I believe this is because my motherboard's RAM voltage is locked to 1.2V. "MEM VDDIO" always reports 0 in Ryzen Master. If I change my voltage and then boot into MemTest86 it still shows it set to 1.2V.

With my 32GB of RAM running at 1600 (DDR4-3200) it completes four passes of MemTest86 in 4 hours 15 minutes. When it's running at the default speed of 1333 (DDR4-2667) it takes 4 hours 45 minutes.

I'm using "Crucial Ballistix 3200 MHz DDR4 DRAM Desktop Gaming Memory Kit 32GB (16GBx2)"