Search results

The special board type has to be activated by Martin to get this feature in new boards. But you should be careful. With my Clevo board the EC readout is very instable and so I deactivated it. The fan speed is one of the things, monitoring is only a nice to have because ears can monitor...

Hello Martin, I made a firmware update to the modded Prema-FW and the Clevo-sensor hasn't been shown any more due to the changed board identification. In this FW the identifier of the clevo has changed to "Clevo W370ET". Could you please add this board /identifier as well? And the identical 15"...

Everything is set correct now and works. This Release sets nearly everything as I would do! Just "configurated for" is set to "Windows Vista, Windows Server 2008" as before. But as I mentioned, I don't see a problem here. Thanks!

Great! :)

And there are three other issues (I checked the created task on my office Notebook): I don't know the english text and try to translate because I have a german Windows 7 Enterprise (64bit) here. 1. On the 1st Tab (General) there is at the bottom a selectbox with "configurated for" and this is...

So it perhaps was a special problem with my notebook. I've tested so much the last days, so this may be possible. Thanks.

Hello, on my Notebook I had the problem, that the autostart feature seemed not to work any more. I checked different versions of HWinfo but this doesn't solve the problem. Now I found in the task scheduler, where the autostart is defined, that the autostart feature is configured only to...

This configuration menu with "General / User Interface" you can also access with right-click on the tray icon when the program is fully launched! There are two different config screens: One in the sensor screen and one with right click on tray icon.

I have to say thanks to all the work you had with this problem! It is a great thing, that the Fan sensor now works and I can log this on demand. You do a great job here. Thank you!

Tested the 423_1990 at first with cold boot. The Clevo Sensors came up instantly. VID behaves as usual. Checked with update interval of 200ms -> no change. Sometimes there is another value seen, but mostly it's 0. Then the 423_1991 beta: GPU VID at first isn't seen but there was a blank...

At first start (with the debug logs), the value was approx. 4/5 the cycle on 0 and 1/5 on the correct value. Some times 7 cycles on 0 and sometimes only 1. But after that, I started with "sensors only" for normal use and I never saw a value different from 0 for 2 hours until shut down of PC...

I don't think, it's a good idea to leave the 20 times rereads in the release version of HWinfo. Now, in actual session, the value of GPU VID stucks for a long time on 0. 1 or 2 times in release version are ok and for testing the 20 retries were ok to see, if it helps. If my or the board is the...

Tested the new Beta and try to describe as much as possible: Fresh start of the cold Notebook. HWinfo not in Autostart. updated hwinfo64.exe and .ini to default beta version started hwinfo gadget start of hwinfo 64.exe configured debug-log started sensors closed hwinfo overview GPU VID came up...

No. The value is always "0" during runtime. It never changes to another value over hours. But the very first value sometimes is different (0.9V or 0.4V). As I remember, this (correct) value is only displayed, when I start HWinfo the first time after reboot or have a longer pause between stop...

Have a look on the attachment of this previous post: ;) http://www.hwinfo.com/forum/Thread-Solved-Monitor-CPU-and-GPU-fan-RPM-on-Clevo-laptops?pid=4706#pid4706 Edit: If I press "restore original order of the sensors" with the nVidia Sensors are at 0-state, the NV-Sensors go away. And GPU-VID...

I made a COMPLETE reset of HWinfo by deleting all preferences in gadget (json-files were empfty) an overwriting hwinfo64.ini with the default ini-file. Then: -> startet hwinfo. -> after some cycles GPU VID appears. -> activating nVidia-GPU -> NV-sensors appear in sensor screen and gadget...

When NVidia GPU is used, the GPU VID sensor disappeares completely. And GPU VID never comes back in sensors screen. The NVidia-sensors remain displayed but then set to 0 when NVidia GPU is disabled! I have to restart HWinfo to see GPI VID again with deactivated NVidia GPU. My idea was, that...

I will test the reordering of the values, when the problem is seen again. But you are right, I have changed the order to suit my needs. Hmm - but the sensors value is always "0". Only when starting HWinfo the first value is sometimes ~0,9V for the first cycle. So I thought, it was an...

Puh ... I found another mysterious bug. It was the 3rd time now, that some sensorsettings in the Gadget got lost. Now I figured out the reason. I checked the "prefMonitors_0.json" file and the id of the sensors have changed (from something like 7xxxxx to 8xxxxx - this time it have been the...

You recogniized my edit of the previous post with the 2nd debug log? Suspending to ram seems to be a good way to reproduce the error. But if I understand you right, you plan to enhance the debugging infos with further output. I stay tuned ... ;)