F5F Stay Refreshed Hardware Desktop Your Ram XMP appears to be malfunctioning.

Your Ram XMP appears to be malfunctioning.

Your Ram XMP appears to be malfunctioning.

T
tototisbaby
Member
55
10-07-2017, 02:28 PM
#1
Hi there, I posted this for my German friend. Sorry if some of the pictures are in German – you understand what you're seeing. The reference images are here: https://imgur.com/a/y5t3Hn2. He upgraded from a single 8GB Crucial RAM stick to a Patriot Viper 3200MHz 2x8 Gb module, using an MSI B350 PRO-VDH AM4 with a Ryzen 5 1400 processor. I’m not very experienced with computers, but compared to me he’s completely new. I guided him on enabling XMP in the BIOS, and the motherboard confirmed it by showing 'DDR Speed 3200'. When he restarts Windows, Task Manager lists 'Memory Speed: 1600'. I thought this made sense since DDR means double data rate, so 1600 x 2 equals 3200. It still seemed odd because Task Manager on my machine shows 'Speed: 3200'. I asked him to check his RAM speeds in Command Prompt, and it read 'DIMM 1 1067, DIMM 1 1067'. My own command prompt also lists 3200 for both. If anyone can clarify why this isn’t working, that would be really helpful. Thanks!
T
tototisbaby
10-07-2017, 02:28 PM #1

Hi there, I posted this for my German friend. Sorry if some of the pictures are in German – you understand what you're seeing. The reference images are here: https://imgur.com/a/y5t3Hn2. He upgraded from a single 8GB Crucial RAM stick to a Patriot Viper 3200MHz 2x8 Gb module, using an MSI B350 PRO-VDH AM4 with a Ryzen 5 1400 processor. I’m not very experienced with computers, but compared to me he’s completely new. I guided him on enabling XMP in the BIOS, and the motherboard confirmed it by showing 'DDR Speed 3200'. When he restarts Windows, Task Manager lists 'Memory Speed: 1600'. I thought this made sense since DDR means double data rate, so 1600 x 2 equals 3200. It still seemed odd because Task Manager on my machine shows 'Speed: 3200'. I asked him to check his RAM speeds in Command Prompt, and it read 'DIMM 1 1067, DIMM 1 1067'. My own command prompt also lists 3200 for both. If anyone can clarify why this isn’t working, that would be really helpful. Thanks!

Z
zelink12
Member
59
10-07-2017, 11:20 PM
#2
He didn't place the second stick in the right position for matching.
Z
zelink12
10-07-2017, 11:20 PM #2

He didn't place the second stick in the right position for matching.

Y
yKanekiPvP
Junior Member
41
10-08-2017, 12:40 AM
#3
His CPU and motherboard are near their limits, struggling to handle 3200. The 1400 only officially allows up to 2667, while the motherboard supports 3200 as its maximum overclocking level.
Y
yKanekiPvP
10-08-2017, 12:40 AM #3

His CPU and motherboard are near their limits, struggling to handle 3200. The 1400 only officially allows up to 2667, while the motherboard supports 3200 as its maximum overclocking level.

Y
Yarrick7481
Junior Member
25
10-15-2017, 11:22 AM
#4
The two sticks are placed accurately in positions A2 and B2
Y
Yarrick7481
10-15-2017, 11:22 AM #4

The two sticks are placed accurately in positions A2 and B2

T
tankdestroyer6
Junior Member
3
10-15-2017, 11:42 AM
#5
Thanks for the update, I knew the 3200 cap was the maximum for the motherboard, but that’s just the limit—just pushing performance. It should still function. Other forums say everything appears normal and speeds are being shown correctly. I’ll ask him to verify with CPU-Z later.
T
tankdestroyer6
10-15-2017, 11:42 AM #5

Thanks for the update, I knew the 3200 cap was the maximum for the motherboard, but that’s just the limit—just pushing performance. It should still function. Other forums say everything appears normal and speeds are being shown correctly. I’ll ask him to verify with CPU-Z later.

P
Picoday
Member
57
10-17-2017, 04:35 AM
#6
The speed boosts aren't assured, and the processor doesn't offer any reliability beyond 2667.
P
Picoday
10-17-2017, 04:35 AM #6

The speed boosts aren't assured, and the processor doesn't offer any reliability beyond 2667.

M
Magic_Wolf_
Senior Member
530
10-18-2017, 01:58 AM
#7
I understand what caused the mix-up. The issue was with the command prompt he used. It seems the command he entered might not match what I instructed. It could be checking DIMM specs instead of their current condition. I think it would help to run additional checks like CPU-Z and use the proper command: wmic memorychip get speed
M
Magic_Wolf_
10-18-2017, 01:58 AM #7

I understand what caused the mix-up. The issue was with the command prompt he used. It seems the command he entered might not match what I instructed. It could be checking DIMM specs instead of their current condition. I think it would help to run additional checks like CPU-Z and use the proper command: wmic memorychip get speed