F5F Stay Refreshed Hardware Desktop XMP is active yet RAM remains locked at 2133MHz

XMP is active yet RAM remains locked at 2133MHz

XMP is active yet RAM remains locked at 2133MHz

M
MissPink09
Junior Member
16
09-10-2019, 02:42 PM
#1
I recently changed my RAM from a 16GB Vengeance LX3200MHz to a 32GB Vengeance RGB Pro SL 3600MHz. XMP is active but it shows only 2133MHz and I’m unsure what to do. My setup includes a Ryzen 3 3200G, B450 Aorus Elite v2, 32GB Vengeance RGB Pro SL 3600MHz, Evga XC 12GB, and a 2060 2TB HDD with a CX 750M drive.
M
MissPink09
09-10-2019, 02:42 PM #1

I recently changed my RAM from a 16GB Vengeance LX3200MHz to a 32GB Vengeance RGB Pro SL 3600MHz. XMP is active but it shows only 2133MHz and I’m unsure what to do. My setup includes a Ryzen 3 3200G, B450 Aorus Elite v2, 32GB Vengeance RGB Pro SL 3600MHz, Evga XC 12GB, and a 2060 2TB HDD with a CX 750M drive.

V
Velizar06
Posting Freak
865
09-11-2019, 09:34 PM
#2
Welcome to the discussions! Have you attempted to reset CMOS to enable BIOS memory training with your new RAM? This is typically recommended before changing RAM modules. Reset CMOS and turn on XMP settings in BIOS to verify if you're achieving 3200MHz.
V
Velizar06
09-11-2019, 09:34 PM #2

Welcome to the discussions! Have you attempted to reset CMOS to enable BIOS memory training with your new RAM? This is typically recommended before changing RAM modules. Reset CMOS and turn on XMP settings in BIOS to verify if you're achieving 3200MHz.

P
poezenkop
Junior Member
36
09-11-2019, 11:16 PM
#3
Thank you for the welcome. I just completed the task and I don’t think it has altered anything.
P
poezenkop
09-11-2019, 11:16 PM #3

Thank you for the welcome. I just completed the task and I don’t think it has altered anything.

T
TussockyHarp98
Junior Member
14
09-12-2019, 07:19 PM
#4
Ensure Profile1 activates XMP support. Apply BIOS updates and restart the system. Use CPUID to confirm memory operates at 3200MHz.
T
TussockyHarp98
09-12-2019, 07:19 PM #4

Ensure Profile1 activates XMP support. Apply BIOS updates and restart the system. Use CPUID to confirm memory operates at 3200MHz.

T
TebrynArbandi
Junior Member
46
09-12-2019, 07:38 PM
#5
It seems the 3200g model is compatible with zen+ rather than zen 2, and it tends to struggle when running faster than 3200, particularly. I doubt this issue is just about the default memory speed after a boot failure; it’s likely the motherboard reverts to the standard RAM settings once it can’t start with the xmp profile.
T
TebrynArbandi
09-12-2019, 07:38 PM #5

It seems the 3200g model is compatible with zen+ rather than zen 2, and it tends to struggle when running faster than 3200, particularly. I doubt this issue is just about the default memory speed after a boot failure; it’s likely the motherboard reverts to the standard RAM settings once it can’t start with the xmp profile.

D
DannyTDM
Junior Member
42
09-22-2019, 07:08 AM
#6
I don’t really understand what I’m seeing with CPUID.
D
DannyTDM
09-22-2019, 07:08 AM #6

I don’t really understand what I’m seeing with CPUID.

T
71
09-25-2019, 08:15 AM
#7
It seems like you're wondering if your CPU might be restricting how fast your memory operates.
T
TheMagicalHerb
09-25-2019, 08:15 AM #7

It seems like you're wondering if your CPU might be restricting how fast your memory operates.

F
flarbi
Member
199
09-25-2019, 04:21 PM
#8
F
flarbi
09-25-2019, 04:21 PM #8

A
Angel_MP
Member
174
09-28-2019, 02:52 AM
#9
Previously had a R7 2700 with significant RAM stability problems; even at 3200 MHz it wasn't fully stable. Remember, the 3200G also had similar issues with IMC and underperformed compared to the 2700X. You could technically push it to 3200 MHz with a better CPU, but at Zen+ it was mostly out of the question.
A
Angel_MP
09-28-2019, 02:52 AM #9

Previously had a R7 2700 with significant RAM stability problems; even at 3200 MHz it wasn't fully stable. Remember, the 3200G also had similar issues with IMC and underperformed compared to the 2700X. You could technically push it to 3200 MHz with a better CPU, but at Zen+ it was mostly out of the question.