Memory reporting is off

[Jacob-S]

So, just started using this today. The memory reporting seems really off.

All four sticks are from a single kit (ie all came in one package box, all the same size/should be identical).

They are all 16GB sticks for a total of 64GB.

CUPID HWmonitor seems to view them correctly.



Is this a result of a wonky setting in HWinfo?

Also, a few weeks ago, i did run an overnight test with Memtest86 and it all came back clean and ok.

Motherboard Model: ASUS ROG CROSSHAIR VIII HERO
Processor Name: AMD Ryzen 9 5950X

Memory is G-Skill Trident Royal (specifically, this one)

 

[Martin]

It could be due to a conflict with other monitoring/tweaking software that's blocking/messing up with HWiNFO.
Please post the HWiNFO Debug File so I can check in detail why it's reported wrong.

 

[Jacob-S]

It could be due to a conflict with other monitoring/tweaking software that's blocking/messing up with HWiNFO.
Please post the HWiNFO Debug File so I can check in detail why it's reported wrong.

I'll try, but the forum says the file is too large for the server to process. (its 4.2MB)
Ok.. got it compressed.

 

[Martin]

Some other software seems to be blocking HWiNFO.
Are you running any other monitoring/tweaking tools including ASUS AI Suite? If yes, try to upgrade them to the latest version.

 

[Jacob-S]

Some other software seems to be blocking HWiNFO.
Are you running any other monitoring/tweaking tools including ASUS AI Suite? If yes, try to upgrade them to the latest version.

I shouldn't be. I specifically removed all the Asus crap so OpenRGB and Fan Monitor could take control more easily. Nothing else should really be messing with the RAM.

 

[Martin]

Ah, both OpenRGB and Fan Monitor could be the culprit. Try to close them and then check.

 

[Jacob-S]

Ah, both OpenRGB and Fan Monitor could be the culprit. Try to close them and then check.

Ah.. You were right. Closed them both, ran again. Memory showed up fine. Then ran each individually.
With just Fan Control running, then launching HWi, the memory shows up correctly as it should.
OpenRGB however, seems to be the culprit. When I just run it, then launch HWinfo, that's when the memory shows wonky.

 

[Fr0stX76]

OpenRGB has a "share SMBus access" option in the settings for this. Its a bit flawed and can increase CPU usage slightly on weak CPU (should be fine on yours), but you might want to give it a shot.

 

[Jacob-S]

OpenRGB has a "share SMBus access" option in the settings for this. Its a bit flawed and can increase CPU usage slightly on weak CPU (should be fine on yours), but you might want to give it a shot.

Looks like it was already enabled.

 

[Martin]

If they would implement the mutex properly then there should be no issues. A lot of other tools do that and work well.

 

[Fr0stX76]

Yep. But they won't. It took many ppl complaining to get this flawed version, I don't see them re-opening this. The project is very Linux oriented, and the devs don't care much about Windows specific issues.