Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Solved MSI X99 GAMING PRO CARBONE ring/sa voltages
#1
Hello,

Can I ask for add some enhanced monitoring in future version hwinfo64 for MSI X99 GAMING PRO CARBONE (NUVOTON NCT6792D+) ?
Want to see cpu system agent voltage in it. If it possible what information i should post here?

wbr. Oleksandr.
Reply
#2
He'd probably like the debug file.

See: https://www.hwinfo.com/forum/Thread-IMPO...g-a-report

It'll give him some information to work off of.
Reply
#3
Is the System Agent voltage reported by the MSI Command Center or BIOS as a monitored value (not a setting) ?
If yes, then a screenshot side-by-side with HWiNFO sensors would be helpful.
And the Debug File as @desgen already mentioned (thanks).
Reply
#4
(12-02-2017, 07:31 PM)Martin Wrote: Is the System Agent voltage reported by the MSI Command Center or BIOS as a monitored value (not a setting) ?
If yes, then a screenshot side-by-side with HWiNFO sensors would be helpful.
And the Debug File as @desgen already mentioned (thanks).

Thank you guys, for so quick response!

Here is some screenshots and dump file

.zip   hw001.zip (Size: 1.5 MB / Downloads: 1)
Reply
#5
Thanks for the data.
I have to admit, that I don't know where to read the CPU SA and Ring voltages.
I will check this with MSI, it might take a few days until I get a response.
Reply
#6
(12-02-2017, 09:03 PM)Martin Wrote: Thanks for the data.
I have to admit, that I don't know where to read the CPU SA and Ring voltages.
I will check this with MSI, it might take a few days until I get a response.

Thanks!
Just find that HWMonitor is showing many voltages but without "normal" labels (show like VIN1, VIN2 ...)

   
Reply
#7
OK, I think I found them Smile Will be fixed in the next build Wink
Reply
#8
(12-02-2017, 09:49 PM)Martin Wrote: OK, I think I found them Smile Will be fixed in the next build Wink

Omg, that's good news! I will wait for that build. Thank you!
Reply
#9
This issue should be fixed in the new v5.61-3297 Beta.
Reply
#10
(12-06-2017, 10:29 AM)Martin Wrote: This issue should be fixed in the new v5.61-3297 Beta.

Confirm! Great work! Thank you!  Big Grin

   
Reply
#11
Thanks for the feedback Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)