DRAM Voltage for MSI B350m Mortar??

[buddywh]

Is there a way to display the DRAM voltage for MSI's B350M Mortar motherboards?  If there is I don't see it or how to turn it on.  I am using beta version v5.59-3260.  There are quite a few voltage readouts, most being unused sensors lines with random values displayed, and while Vsoc is there (very nice) I can't find one that co-relates to DRAM voltage.  It should be available because I've noted it displays in HWMonitor utility.

It should be the same situation as with MSI's B350 Tomahawk motherboards, and maybe others, since they're very similar in design.

 

[Martin]

It should be displayed as the DIMM voltage. Can you please attach a screenshot of the sensors displayed in HWiNFO ?

 

[buddywh]

It should be displayed as the DIMM voltage. Can you please attach a screenshot of the sensors displayed in HWiNFO ?

Here it is.  The disabled are some temp sensors that seem to either be duplicating something else or display random stuff.
[attachment=2481]

 

[Martin]

I see there's some problem in HWiNFO adjusting sensor values for this mainboard.
So I will need more details - please also attach the HWiNFO Debug File with sensor data.

 

[buddywh]

I see there's some problem in HWiNFO adjusting sensor values for this mainboard.
So I will need more details - please also attach the HWiNFO Debug File with sensor data.

How do i get it to generate a Debug File with sensor data?

Sorry...i found how to generate Debug File and it should be attached to this.  I'm not sure how to get the sensor data though so I'll look further for that.

 

[Martin]

https://www.hwinfo.com/forum/Thread-IMPORTANT-Read-this-before-submitting-a-report

 

[buddywh]

https://www.hwinfo.com/forum/Thread-IMPORTANT-Read-this-before-submitting-a-report

OK...I'm not sure I got it all right for the sensor data so I included a Logging file in case that's what you meant.

Hopefully this will help!

 

[Martin]

Thanks, I found the bug
This will be fixed in the next (Beta) build.

 

[buddywh]

Thanks, I found the bug
This will be fixed in the next (Beta) build.

Sounds great; glad I could help improve the tool!