#Is task manager Ram speed accurate?

1 messages · Page 1 of 1 (latest)

agile apex
#

When I go into BIOS it says I have XMP Profile 1 selected and my Ram is running at 3000MHz, and when I open command prompt and enter 'wmic memorychip get speed', it says 3000, but when i go into task manager, hit performance tab, then select memory the speed says 1500MHz. Anyone know why?

primal oak
agile apex
primal oak
#

👍

wraith timber
# agile apex When I go into BIOS it says I have XMP Profile 1 selected and my Ram is running ...

The discrepancy in memory speed readings between the BIOS, the command prompt, and the task manager could be caused by a few different things.

One possibility is that the XMP (Extreme Memory Profile) setting in the BIOS is not properly configured, which is causing the memory to run at a slower speed. XMP is a feature that allows the motherboard to run the RAM at its advertised speed, rather than at the default speed. Make sure that the XMP Profile 1 is selected in your BIOS and the RAM is running at the correct speed (3000MHz).

Another possibility is that the operating system or the task manager is not properly reporting the memory speed. This could be caused by a driver issue or a software bug. To CONFRIM the memory speed, you can run a memory benchmarking software that can give you an accurate reading of the memory speed.

Finally, it could be also be possible that the system is running in a dual-channel or triple-channel configuration and the memory is actually running at the correct speed, but being displayed incorrectly in the task manager.

(It is NORMAL that this happens sometimes, but if you notice any performance issues or errors, it's recommended to check the XMP profile settings again and run a memory benchmarking software to confirm the memory speed. If everything seems fine, it's not something you should worry about).!! You should be fine tho:)

agile apex
#

does this mean it is not running at the rated 3000?

primal oak
#

It's running at 3000

#

Again, DDR.

#

1500 isn't even a DDR4 Jedec speed

agile apex
primal oak
#

Task manager (In the default view, as pictured) Automatically applies the DDR math to show you the DDR Speed. Technically, the RAM is at 1600mhz though, rather than 3200, due to DDR

image.png
agile apex
#

So this video is what spurred the whole thing for me

#

is his ram running at 7200 then?

primal oak
#

Go to your RAM speed.

#

Does it Show 3000, or does it show 1500

agile apex
primal oak
#

Okay in that case, you need to enable XMP.

agile apex
#

It is enabled

primal oak
#

I was under the impression that it read 3000 there for you

agile apex
#

maybe my bios is f'ed up? Should I try and update it?

primal oak
#

What you'll want to do is shut down, go to Bios, and enable XMP. This varies Bios to Bios, so google the way to do it for you

agile apex
#

A-XMP is on profile 1 currently which is 3000MHz

primal oak
#

Hmmm.

#

Just noticed:
You have a Corsair Vengeance Kit?

agile apex
#

Pretty sure yeah

primal oak
#

So, Vengeance Fails XMP at a Higher Proportion than Other RAM kits.
As the Saying goes, "RAM is RAM, unless it's Corsair Vengeance DDR4"

agile apex
#

really? lol

primal oak
#

So that is, also a possibility

#

That it's Corsair RAM being, well, Corsair RAM

#

One thing we can try is in Bios, you can attempt to manually tune the timings

agile apex
#

is it corsair ram altogether or specifically vengeance?

primal oak
agile apex
#

I did buy it because it was the cheapest

primal oak
#

Vengeance DDR4 is the One RAM kit we avoid

agile apex
#

I wish I would've heard that when I bought the ram

#

lol

primal oak
#

Well, how long ago did you buy it
It's a complete potentiality that you could Get a Refund for a Failed Product

#

And then go Buy SP, Teamgroup, Gskill, Oloy, anyone else, all of which can typically be found $10-20 cheaper than Vengeance

#

I understand that's an inconvenience, so we would want to try to manually tune the timings first

agile apex
#

To manually set it, would I just click this and set to 3000?

rn_image_picker_lib_temp_6bec4586-2032-4379-aa2e-4ffc6a8cd81d.jpg
primal oak
#

That would be the manual timings, yes
Although there will be many CL Latencies

agile apex
primal oak
#

In that case, just set it to 3000

agile apex
#

Leave everything else?

rn_image_picker_lib_temp_eb2f97eb-9e43-4291-8aca-2b5fe36a7f05.jpg
primal oak
#

Should be fine

#

Do note: When manually timing, there is the potential for a BSOD

#

Won't kill your system, just means that particular setting won't work

agile apex
#

I bought the ram in 2019 so a refund is probably not possible lol

primal oak
#

That's a rip

#

If this 3000 doesn't work, we can try manually timing to 2933, lower, etc

agile apex
#

The only reason I really care is cuz I just started getting into tarkov

primal oak
#

Just get it as high as we can without a BSOD or Failed XMP

agile apex
#

just booted in

#

same result

primal oak
#

Alright so shut it down, try going one step lower on the Manual Tunings

#

We'll just have to push it as High as It Will go

agile apex
#

ok so i set it to 2133 and now this is what it reads

#

so maybe is is doing the ddr thing

#

for some reason

primal oak
#

Typically Task Manager doesn't read like that by default
One moment

agile apex
#

even though the benchmark said it was 1500

primal oak
#

My best Guess is
A) Task manager just having a stroke, 1500 is what we want then (so DDR speed is 3000)

#

Thats my only guess atm

agile apex
#

thanks for the help, maybe lil mosey has some insight but at the end of the day it isn't a big deal

primal oak
#

Well, we can check some things

#

Hit the Windows Key, type in "System Information"

#

We're going to look on the first page that loads for you SMBIOS version

agile apex
#

Ok

#

2.8

#

is what it says

primal oak
#

Okay, so 1500 = 3000 then, in this case

#

So 1500 was correct

#

SMBIOS versions Prior to 3.0 Report in MHZ, SMBIOS Versions after 3.0 report in MT/s, but Misreport it labelled as MHZ (DDR = ~MT/s)

agile apex
#

Ok

primal oak
#

So you can set it back to 3000 or Auto in BIOS, sorry about the Wild Goose chase, we should've checked SMBIOS first

agile apex