[HWiNFO32 Thread] - Questions, Reports, Suggestions, Discussions

This is possible only if they feature a DIMM Thermal Sensor. Are you sure they do? I can check that if you run HWiNFO32 in Debug Mode (enable in Configure), open Sensors, close all and then send/attach the HWiNFO32.DBG file.

 

HWiNFO32 v3.60 available.
Changes:

• Added automatic checking of updates.
• Improved support of Nuvoton NCT6776F LPC/HW monitor.
• Added nVidia GF104 models: GeForce GTS 455, GTX 470M.
• Added nVidia GF106 models: GeForce GT 440, GTS 450, GTX 460M, GT 445M, GT 435M, Quadro 2000.
• Added nVidia GF108 models: GeForce GT 420, GT 430, GT 415M, GT 420M, GT 425M, GT 435M, Quadro 600.
• Fixed a potential hang with black screen when opening sensors on certain ATI GPUs.
• Enhanced sensor monitoring on some ASRock mainboards.
• Added possibility to directly log sensor data into separate CSV file.
• Added support of SMSC EMC2301, EMC2302, EMC2303, EMC2305 and EMC2113 sensors.
• Added monitoring of CPU and GPU fan speeds for ASUS G73 notebooks.
• Fixed latency issue for EC sensors.
• Added additional temperature monitoring of Clevo models: M570RU, M570TU, M860TU, M980NU, W860CU, W870CU, W880CU.
• Enhanced Sandy Bridge support.

 

ok i hope i ve done everything right. have a look

thanks!

 

According to the data you sent, your memory modules don't seem to contain a DIMM Thermal Sensor, so it's not possible to read the temperature.

 

oh! thats sad. i really would like to watch their temps. But i can watch HyperX Ram modules temps. Once again great application. Keep up good work. thanks

 

HWiNFO32 v3.60-950 Beta available.
Changes:

• Minor fixes and updates (Win7 type, MX16xx Ext1 temp, GPU enum, SNB GFX clock).

 

I like to have HWInfo32 running in the taskbar but with time it starts using more and more RAM. I would like to have it most of the time on but because of this I have to shut it down.

I realize it probably wasn't meant to be permanently running, but is there a way I can stop it from doing this? Maybe disabling some type of logging or something?

Thanks by the way, awesome program.

 

You're right, this needs to be fixed. I'll add a switch to enable/disable the internal sensor logging (which consumes memory during time)..

 

Here a new Build to avoid consuming of memory during sensor monitoring over time:
HWiNFO32 v3.60-951 Beta
It's required to disable this option using a new switch:
1. Open Sensors
2. Click "Configure"
3. Disable "Log all values for Report"

Please provide feedback.

 

Man, that was quick. I'll leave it running and will let you know how it worked out.

Thanks buddy!

Edit: Alright, after running it for a little over an hour it seems to be perfect. I'll just let it running from now on. I'll post back if I find something strange.

One more thing, any chance we can decide how often it refreshes? Not a big deal at all really. It would just be nice to have it synchronized to my Rainmeter, which is every 3 seconds.

Anyway, two thumbs up for the fix bro.

 

Thanks for the feedback. Sure, let me know if you find any oddities..
I'll think about the configurable refresh cycle interval.. Maybe in future if I get more such requests

 

HWiNFO32 v3.60-965 Beta available.
Changes:

• Minor fixes and updates (Win7 type, MX16xx Ext1 temp, GPU enum, SNB GFX clock).
• Added possibility to disable sensor data logging for report file (avoids raising of memory usage during monitoring).
• Added support of ITE IT8728F, IT8781F, IT8782F, IT8783F LPC/Hardware Monitor.
• Improved enumeration of multiple GPUs via NVAPI.

 

Can your monitor be run by a Standard User (not admin)? Any plans to add that capability? You would have to run part of the code as a service to do that...

 

Access to hardware requires administrative rights.
At least for the first time when you launch HWiNFO32 you need to have Admin rights (make sure to have the Persistent Driver option enabled).
Then the driver will remain installed and for subsequent runs you don't need to have administrative rights.

 

HWiNFO32 v3.60-973 Beta available.
Changes:

• Minor fixes and updates (Win7 type, MX16xx Ext1 temp, GPU enum, SNB GFX clock).
• Added possibility to disable sensor data logging for report file (avoids raising of memory usage during monitoring).
• Added support of ITE IT8728F, IT8781F, IT8782F, IT8783F LPC/Hardware Monitor.
• Improved enumeration of multiple GPUs via NVAPI.
• Added monitoring of HP Envy 17 and Pavilion dv6 / dv7 EC.
• Fixed CPU clock measurement on certain Windows 7 systems.

 

HWiNFO32 v3.60-980 Beta available.
Changes:

• Minor fixes and updates (Win7 type, MX16xx Ext1 temp, GPU enum, SNB GFX clock).
• Added possibility to disable sensor data logging for report file (avoids raising of memory usage during monitoring).
• Added support of ITE IT8728F, IT8781F, IT8782F, IT8783F LPC/Hardware Monitor.
• Improved enumeration of multiple GPUs via NVAPI.
• Added monitoring of HP Envy 17 and Pavilion dv6 / dv7 EC.
• Fixed CPU clock measurement on certain Windows 7 systems.
• Enhanced sensor monitoring on ASUS Rampage III GENE.
• Added support of Alerts for Sensor values when reaching customizable thresholds.
• Enhanced sensor monitoring on MSI MS-7592.

 

HWiNFO32 v3.61 available.
Changes:

• Minor fixes and updates (Win7 type, MX16xx Ext1 temp, GPU enum, SNB GFX clock).
• Added possibility to disable sensor data logging for report file (avoids raising of memory usage during monitoring).
• Added support of ITE IT8728F, IT8781F, IT8782F, IT8783F LPC/Hardware Monitor.
• Improved enumeration of multiple GPUs via NVAPI.
• Added monitoring of HP Envy 17 and Pavilion dv6 / dv7 EC.
• Fixed CPU clock measurement on certain Windows 7 systems.
• Enhanced sensor monitoring on ASUS Rampage III GENE.
• Added support of Alerts for Sensor values when reaching customizable thresholds.
• Enhanced sensor monitoring on MSI MS-7592.
• Added reporting of BIOS Message for Award/Phoenix BIOS machines.
• Added possibility to report SMART data and monitor temperature for drives in Intel RAID Array.
• Added monitoring of HP Envy 15 EC.
• Improved sensor monitoring for Tyan S7025.
• Added preliminary Ivy Bridge support.
• Changed nVidia GPU I2C method to NVAPI by default (can be changed back to low-level via settings).

 

Mumak

Thanks for the latest version of your great tool.

 

always fans of new versions

 

Bro, how about letting us change the color/font of the numbers in the taskbar and not just the background?

By the way, it's been running constantly on since you fixed the memory issue and it runs flawless. Thanks.

 

That's not possible. Would that be important?

Nice to hear that..

 

No, not really actually... It's just that the numbers sometimes are a little too small for the resolution if I am a little far. It's fine though, I can tell a '6' from a '5' 99% of the time.

 

hy guy's,

i got some issues with my HDMI output, i try to figure out where this probleme could coming from since a while.

i did a fresh windows install and noticed my problem was gone untill i reinstall HWinfo (360 and highter) again.

is it just a coincidence or does someone else has experiencing the same issue ?

 

I can hardly imagine a relation between HDMI issues and HWiNFO32 installation. What version of HWiNFO32 did you have when you had the problems? Were the problems occuring during HWiNFO32 was opened, or just installed? Did the fresh system install not solve the issue? You need to describe more precisely..

 

my hdmi port works excellent with hwinfo installed. i doubt it has anything to do with one another.
please search the alienware forum for hdmi issues, there had been many threads dealing with those kind of problems. i bet you'll find your answers there.

good luck.

 

@Mumak,
after the fresh install the problem didn't came back untill i install hwinfo
i was running the 360 version and the programm was running when issue came back.
i can hardly imagine too, hwinfo caused this problem but i'am out of idea what could caused it and even i was pretty sure it was just a coincidence i have to ask

@mfractal,i did read the forum, i read all i can found about it since many weeks i only fount 2 treads speaking about the same issues, i also explain my problem in one of them. i will did a new tread if the issue came back, for now i just cross my finger.

thanks to your answer both

 

@Mumak,
can You pls tell me what the temperature sensor External1 is?
It gets under load(3DMark06) very hot. Should I worry about this?
The screenshot is from a HP 8530w.

 

Well, I don't know what this input is measuring. Might be CPU or GPU, depends on type of load..

 

HWiNFO32 v3.61-997 Beta available.
Changes:

• Added monitoring of fan speed on certain Toshiba notebooks (with TVALZ driver).
• Various minor fixes and updates.

 

what is this logitech lcd status by the way which is disabled on M17X?

could you make a better design gadget? meaning something extreme or something?

 

That LCD setting I'm guessing is for when you have one of those Logitech keyboards with the little LCD on them, then you can have the temps show down there.

 

Yep, it's for Logitech G15/G19 keyboards.
I don't have an advanced Gadget in short-term plan. There are plenty of free advanced Gadgets available, so if anyone wants to support them, the interface to HWiNFO32 is pretty easy and I can help with interfacing..

 

HWiNFO32 v3.61-1008 Beta available.
Changes:

• Added monitoring of fan speed on certain Toshiba notebooks (with TVALZ driver).
• Various minor fixes and updates.
• Fixed Multi-GPU support in case of different brand/model GPUs.
• Added nVidia GeForce GT 440, GeForce GT 555M, GeForce GTX 580, GF110/D13U.
• Enhanced support of Cedarview.

 

i am getting blue screen every time i try to run this new version..

 

Please enable Debug Mode and when it crashes, reboot and send me the HWiNFO32.DBG file it created. I'll check that.

 

ok here it is. it stucks my whole system (resulting in blue screen) during examining system configuration and loading-detecting sensors (during hwinfo startup) . When i use previous version everything works normally.

 

It might be (again) due to the ULPS issue with ATI Catalyst. I'm wondering that ATI is aware of such problem and they don't do anything about it
Could you please try to temporary disable the ULPS feature by:
In Registry under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000
or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0001
or 0002, etc until you locate that keys
set the key 'EnableUlps' key to 0
then please reboot the machine and try if HWiNFO32 still hangs..

 

i cant find this enableulps key

 

ok i found the key in both 0002 and 0003 and changed it in both from 1 to 0. now it can run!

however it takes too long to load sensors. ad of course gpu temps are three Celcius degrees higher

 

Thanks for the feedback! So indeed, ULPS is the cause of this crash !
I'll have to implement a workaround, but I'm also waiting on feedback from ATI if they know of a better solution. Best would be if they could fix this nasty issue, but I'm not sure if they are really willing to The only workaround for such applications is to ignore (don't touch) the secondary GPU if ULPS is active - and that will cause that you can't read any parameters/sensor values from such a GPU

In case you still have HWiNFO32 Debug Mode enabled, opening sensors takes considerably longer, so you need to turn it off.
Sure, the temperatures will be higher, since without ULPS the secondary GPU is not completely stut down if inactive.

 

I hope your workaround is optional since on my machine your software runs awesome. It's one of three programs that I run at startup, so it is pretty special, ha ha


Edit: Here is a picture of your program in action. Top-right hand corner, next to the clock.

Click for Large
​

Two-Thumbs up!

 

I'm still hoping that ATI will fix this issue since a system (GPU + drivers) shouldn't behave this way !
If not, I'll have to look for other solutions - it's not acceptable if a user gets a BSOD from a tool he wants to use for monitoring, even if that app is not the true cause of this problem.
Just a question: you don't have problems... What config do you have? Is it an ATI Dual-GPU with Win7 + Catalyst at least 10.1 + ULPS enabled and latest HWiNFO32 ? If yes, then you might be affected by this problem, however from my experience systems behave differently - some of them are more likely to crash and some run pretty stable. This whole ULPS is quite weird and I don't think it's properly implemented...

 

Dual GPU's, Win 7, Cat 10.1, and latest HWiNFO32. But, he has 5870's, I have 4870's. Maybe that is the cause?

 

AFAIK, both should be affected..
But I checked again and it seems Cat 10. 2 introduces ULPS, so maybe that's why the difference. You can try to install later Cat and watch the disaster

 

catalyst 10.10 here. it makes sense. War why you dont use the new dell driver for the 4870s?

 

Yeah, I'm on 10.10 also. I don't know. I always prefer the drivers directly from ATI (or should I say AMD?). They always give me good performance. I haven't tried the Dell drivers. I don't see the need to.

 

gotta add here that i don't bsod as well. i am on 4870, so it does seem that the reason is 5870s...

 

i have no idea. the exact previous version works flawlessly. The developer can figure this out.

 

The new HWiNFO32 build adds more communication to secondary GPU, so it raises the probability of crash with ULPS..

 

Might be the custom vbios Dell developed for those slave 5870 that is causing it.