Windows 10: Windows 10 1903 causing Memory leaks and task manager showing wrong RAM speed.

After updating from windows 10 1809 to 1903, the task manager shows wrong memory speed as 2133Mhz. Earlier it used to show 2400 Mhz. Also, after updating to windows 10 1903, the was rapid and sudden spikes in RAM usage, like rapid ups and downs. After reboot, the system stays stable for 2 to 5 minutes but suddenly the error continues.



Earlier in windows 10 1809, the speed showed as 2400Mhz

:)

 

Task Manager console displays innacurate RAM speeds

I have corsair Vengeance pro 16 GB ram 1866 mhz installed, Bios cpu z show it at this speed but task manager shows ram speed at 1400 mhz. Is this a cosmetic error for win 10? How do I fix it?

Original title: Task manager and RAm speed

 

Memory speed might be wrong in Task Manager

Hi,

I guess the speed is from Speed of SMBIOS Type 17, but Speed of SMBIOS Type 17 Identifies the
maximum capable speed of the

device, but I think we shoud get from Configured Memory Clock Speed of SMBIOS Type 17, it's the configured clock speed to the memory

device.

If there are two memory slots in my system,

I plug 2400MHz in the slot 1 and 2166 in the slot2, the memory speed shows 2166MHz in Task Manager.

I plug 2166MHz in the slot 1 and 2400 in the slot2, the memory speed shows 2400MHz in Task Manager.

Microsoft shows the memory speed which is from the speed (Identifies the maximum capable speed of the device) of the
last SMBIOS Type 17 Memory Device.





Thanks

 

Wrong RAM speed in Windows Task Manager


I see, but I don't quite understand why it seems random that for some users the correct frequency is shown while for others it is not. That's why I thought it was a bug because I've seen users with similar Corsair memory modules show the correct speed in Windows 10. Could it be that it is very specific to what ID the RAM use? Or what mainboard is used? I'm sure I saw them at 2133Mhz in the task manager when I first built this PC. I think it got stucked at 2800 once I started playing around with the X.M.Ps. As long as this doesn't causes any errors or issues in the future then I can put my mind at ease.