Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HWInfo Vcore Reads min and Max 0/4.064
#1
Hi Martin,
Thank you so much for all you do. I am trying to track down a problem I am having in HWInfo64 5.85 Beta, also had it in 5.84, thought updating might fix. My max and minimum VCore are occasionally dipping to 0 and jumping to 4.064. I was wondering if this is an issue with the sensors on my motherboard or maybe a glitch in HWinfo? Please let me know when you get get a chance. I attached my log file that shows the problem. I was not running any software when this happened other than Chrome and HWInfo64.

Thank you!
Environmental_Act
Reply
#2
There seems to be a lot of hiccups (invalid readouts) on Vcore.
What mainboard is this? Attaching the HWiNFO Debug File might be helpful too.
Reply
#3
(05-31-2018, 12:14 PM)Martin Wrote: There seems to be a lot of hiccups (invalid readouts) on Vcore.
What mainboard is this? Attaching the HWiNFO Debug File might be helpful too.

Hi Martin,
My apologies that I did not attach the Debug file. This is an Asus Prime Z370-A. This is the debug file from the most recent time I opened HWInfo64, I did experience a Vcore of 0 but not of 4.064 in this time frame. I cannot attach to this post as it keeps getting rejected for size requirements (8mb file). Please find the file at this link

Debug File

Please let me know if there is a different way you would like me to try to submit the file to you.

Thank you again for your help with this!
Reply
#4
That's looks like some problem of the Vcore monitoring or mainboard logic. What values does the BIOS or ASUS AI Suite show?
Reply
#5
(05-31-2018, 07:15 PM)Martin Wrote: That's looks like some problem of the Vcore monitoring or mainboard logic. What values does the BIOS or ASUS AI Suite show?

Bios shows normal stable Vcore around .97 when I open it. Almost never varies when I am viewing and when it does only by a few hundredths. Asus AI suite does show a drop in Vcore to 0 but none of the jumps to 4.064.
Reply
#6
They might be reporting CPU VID instead of measured Vcore.
Reply
#7
(05-31-2018, 07:44 PM)Martin Wrote: They might be reporting CPU VID instead of measured Vcore.

I havent experienced any crashes or blue screens that werent from a failed OC and my machine appears to run fine... Would you say this is just a bad sensor on the motherboard? Do you think I should RMA it?
Reply
#8
Yes, it might be some problem with the sensor. But I'm not sure if this is worth an RMA.. Try to check on some forums (i.e. overclock.net) with users of the same mainboard and their experience.
Reply
#9
(05-31-2018, 08:12 PM)Martin Wrote: Yes, it might be some problem with the sensor. But I'm not sure if this is worth an RMA.. Try to check on some forums (i.e. overclock.net) with users of the same mainboard and their experience.

Thank you so much for your input and time on this. I really appreciate your help!
Reply
#10
No problem, you're welcome.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)