Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HWiNFO32 and HWiNFO64 v5.11-2712 Beta released
#1
HWiNFO32/64 v5.11-2712 Beta available.
 
Changes:
  • Improved drive scan safety.
  • Improved sensor list color notification of alarms.
  • Enhanced support of Intel Kaby Lake.
Reply
#2
Hi Martin

Just trying to change unit for sensors and notice that unit text on sensor graphs not the same as on sensor windows. Example on screen shot i've attached


Attached Files Thumbnail(s)
   
Reply
#3
Ah, I forgot that, thanks for letting me know. Will check it...
Reply
#4
(12-22-2015, 05:44 PM)Martin Wrote: Ah, I forgot that, thanks for letting me know. Will check it...

you're welcome..

Btw I am getting weird values on sensors bellow GPU [#0]: ATI/AMD Radeon R7 260/HD 7790: On Semi NCP81022 header and VR T3 sensor appear as it was never before, pic attached for first case.


Attached Files Thumbnail(s)
   
Reply
#5
Are you maybe running some other hardware monitoring tool with HWiNFO? That might be caused by a conflict.
Can you try to capture those erratic values while running in Debug Mode and then attach the HWiNFO64.DBG file produced ?
Reply
#6
(12-22-2015, 07:29 PM)Martin Wrote: Are you maybe running some other hardware monitoring tool with HWiNFO? That might be caused by a conflict.
Can you try to capture those erratic values while running in Debug Mode and then attach the HWiNFO64.DBG file produced ?

I am not  running another hw mon. tools.
I couldn't reproduce in 1 dbg file for erratic values and VR T3 sensors appearence, so i made 2 dbg files for each.
Thanks in advance.


Attached Files
.zip   1st_2ndcase.zip (Size: 1.09 MB / Downloads: 1)
Reply
#7
Thanks. It looks like a wrong readout from the GPU VRM. I'll try to filter them out, but it's possible that there will be other invalid ones.
Reply
#8
(12-22-2015, 09:10 PM)Martin Wrote: Thanks. It looks like a wrong readout from the GPU VRM. I'll try to filter them out, but it's possible that there will be other invalid ones.

How about on Mainboard VRM? seems too.. are these effect of using new windows so giving wrong read out?

EDIT - Debug file attached


Attached Files Thumbnail(s)
   

.zip   newdebugfile.zip (Size: 204.7 KB / Downloads: 5)
Reply
#9
Well, that's really odd - it looks as if the VRMs sometimes return contents of other registers than those requested by HWiNFO.
My guess would be a conflict with another monitoring application, but if you say you are not using another one, I'm afraid I don't know what might be causing this Sad
Reply
#10
(12-22-2015, 10:21 PM)Martin Wrote: Well, that's really odd - it looks as if the VRMs sometimes return contents of other registers than those requested by HWiNFO.
My guess would be a conflict with another monitoring application, but if you say you are not using another one, I'm afraid I don't know what might be causing this Sad

Big Grin
I think since I forgot to signed out another user with HWiNFO still running (running automatically from task scheduler) then started another HWiNFO (manually from windows explorer/automatically from task scheduler) with another user account, so there are multiple instances of HWiNFO running..

HWiNFO runs OK now, but first i had to end task another HWiNFO instance Big Grin


Attached Files Thumbnail(s)
   
Reply
#11
Smile
I'm wondering how could that work, HWiNFO should avoid running multiple instances. It was probably because it was launched under a different user...
Reply
#12
The issue with graphs should be fixed in Build 2715.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)