Confused about my Ram XMP - seems to not work

[Tofu]

Hi Guys,

Posting this on behalf of my German friend, so sorry about some of the linked pictures being in Deutsch, but you know what you're looking at anyway.

Images to reference - https://imgur.com/a/y5t3Hn2

He bought Patriot Viper 3200MHz 2x8 Gb as an upgrade from 1 single stick of 8gb Crucial ram.

He is using a MSI B350 PRO-VDH AM4 with a Ryzen 5 1400.

I'm far from the source of all knowledge when it comes to computers, but compared to me he has no clue. So I told him how to enable his XMP in his bios, which he did. The motherboard even confirms these changes by stating 'DDR Speed 3200' at the top. (See 2 images linked at top)

However when he boots into Windows, task manager says 'Memory Speed: 1600'. I wasn't too concerned about this, because obviously DDR means double data, and 1600 x 2 is 3200. Although I still found this strange, because in task manager on my computer it actually states 'Speed: 3200'. (See image linked at top)

Finally, I asked him to open is Command Prompt to check his memory speeds, and this reads: 'DIMM 1 1067, DIMM 1 1067'. Again, in my command prompt it shows me 3200, 3200.

If anyone could explain to us why this isn't working that would be amazing.

Thanks!

[Dr.Shadowds 🐉]

Everything correct from the image.

Also when using software tool like CPU z, or whatever, it will display ram frequency by half. 16+16 = 32.

[Tofu]

Originally posted by Dr.Shadowds 🐉:

Everything correct from the image.

Also when using software tool like CPU z, or whatever, it will display ram frequency by half. 16+16 = 32.

Thanks Doc,

Do you know why command prompt shows a speed of 1067? When my computer displays it correctly as 3200? I think this is the bit that confused me and made me feel like something was wrong.

Thanks!

[Dr.Shadowds 🐉]

What did you type in command prompt? That 1/3 of 3200 btw.

[Snow]

The command you entered asks the DIMMs about their specifications I guess, not their current state.

[Tofu]

Originally posted by Dr.Shadowds 🐉:

What did you type in command prompt? That 1/3 of 3200 btw.

It didn't cross my mind that 1067 is 1/3 of 3200. That makes it even more strange, as there is only the two sticks which are positioned correctly in A2 and B2. Looking at the image it looks like he typed in the command prompt: wmic memorychip get devicelocator, speed

[Tofu]

Originally posted by Snow:

The command you entered asks the DIMMs about their specifications I guess, not their current state.

Aaaaah I feel like we are getting closer to solve the mystery. Yes, this isn't the prompt I asked him to type, but thanks to Dr Shadowds asking this question I only just saw that.

[Dr.Shadowds 🐉]

Originally posted by Snow:

The command you entered asks the DIMMs about their specifications I guess, not their current state.

At this point I assume that the case from what OP said getting from the command prompt.

On Windows 10, you can just open task manager, click on performance, and click on memory, and it will tell you the frequency RAM is set, and apps like CPUz, or etc will display by half the amount, DDR = Double Data Rate.

[Snow]

Like, those are 2133 sticks that can run at 3200 using the XMP, something like that.

[Tofu]

Originally posted by Dr.Shadowds 🐉:

Originally posted by Snow:

The command you entered asks the DIMMs about their specifications I guess, not their current state.

At this point I assume that the case from what OP said getting from the command prompt.

On Windows 10, you can just open task manager, click on performance, and click on memory, and it will tell you the frequency RAM is set, and apps like CPUz, or etc will display by half the amount, DDR = Double Data Rate.

In task manager it displays his speed at 1600, whereas my task manager displays 3200. I guess I will have to get him to run more checks later such as CPU-Z

[Tofu]

Originally posted by Snow:

Like, those are 2133 sticks that can run at 3200 using the XMP, something like that.

The actual command prompt I asked him to use is:
wmic memorychip get speed

When I do this, it shows me
3200
3200

[Snow]

Originally posted by Maniac Jr:

In task manager it displays his speed at 1600, whereas my task manager displays 3200. I guess I will have to get him to run more checks later such as CPU-Z

CPU-Z will definitely give the correct result.
1600 vs 3200 is pretty typical. I guess it depends on how DIMMs/mobo report the speed - in some cases it reports real clock which is 1600, in some - effective clock which is 3200. No need to worry about this one, it just is how it works.

[Dr.Shadowds 🐉]

Originally posted by Maniac Jr:

Originally posted by Snow:

Like, those are 2133 sticks that can run at 3200 using the XMP, something like that.

The actual command prompt I asked him to use is:
wmic memorychip get speed

When I do this, it shows me
3200
3200

Then running as correctly.

[Tofu]

Originally posted by Dr.Shadowds 🐉:

Originally posted by Maniac Jr:

The actual command prompt I asked him to use is:
wmic memorychip get speed

When I do this, it shows me
3200
3200

Then running as correctly.

Yes but this is on my computer - that's how I know this is the correct command prompt. I need to get him to use this same command on his computer when he returns home

[Snow]

Originally posted by Maniac Jr:

Originally posted by Dr.Shadowds 🐉:

Then running as correctly.

Yes but this is on my computer - that's how I know this is the correct command prompt. I need to get him to use this same command on his computer when he returns home

There is actually no difference between the commands you entered, the one he used just also provides the info on where the DIMM is. The result will likely to stay 1067. But so far I'm convinced it just tells what DIMMs think of themselves, not how they actually work, as he's running XMP profile.

[Tofu]

Originally posted by Snow:

Originally posted by Maniac Jr:

Yes but this is on my computer - that's how I know this is the correct command prompt. I need to get him to use this same command on his computer when he returns home

There is actually no difference between the commands you entered, the one he used just also provides the info on where the DIMM is. The result will likely to stay 1067. But so far I'm convinced it just tells what DIMMs think of themselves, not how they actually work, as he's running XMP profile.

Thanks for all your help Snow. I will have him check CPU-Z asap and report back if things still look strange!