1. Not really, merely guessing so, based on frequencies and temps (in my case 135 Mhz seems to be the idle freq)
2. Tried with 10 sec, it only seems to delay the moment when sensors show up
3. Exactly, they remain stuck at those values which were being displayed when G was closed.
What I found...
Let G = any software which uses Nvidia chip
a) start hwinfo
b) start G
c) quit G
same picture as b)
a) start G
b) start hwinfo
c) quit G
same picture as b)
I meant that in both cases after the G is closed,
hwinfo might revert back to
IMHO, this might be an...
Sure! I meant so that when the gpu is not in use anymore, its sensors might disappear from view. (in SIV, the 'N/A' is displayed in this case instead of clock frequency). I referred to this state as initial because when hwinfo is launched and there's no load on gpu, it displays only the gpu's...
you've nailed it! :) now it displays all the sensors when my gt650 is in use.
optimus users are giving you huge hugs!
I suppose it's too much to ask, but if an option to return to initial state (as in SIV, where it returns to n/a when gpu is not in use) would make it to the final release, I...
Thank you Martin,
thank you, Ray,
you and your creations are both awesome :)
Martin, the newest beta works almost as intended, with a minor remark:
If I run something that utilizes nvidia gpu, for instance, photoshop, first, and then hwinfo, the whole bunch of sensors would show up (15...
I absolutely second the original post!
Martin, just to let you know, some other programs don't cause the nvidia cards that use optimus to run at full clock, for example, gpu-z: when I run it explicitly on nvidia, the clocks displayed are initially high (835 Mhz) and then drop to 135 Mhz. If I...
I've just tried launching it in summary-only mode, with various safety options on and off, the result is the same.
To make things even more mysterious: I discovered the following (I'll try to describe it schematically, because too much words are not good for understanding, given...
I would like to ask you as you are the only one who's intimately familiar with HWiNFO's inner workings..
First, let me describe my problem, which is not the HWiNFO's fault, it rather helps to bring the issue to surface.
I've got a USB audio interface, namely Focusrite...
Martin, a fact to consider:
i tried it several times and there can't be coincidence: when i start hwinfo or cpu-z, the gpu temperature starts climbing steadily from 40s to 50s. there are no other programs utilizing gpu at that moment. which means gpu was running cool and idle clocked before...
yes, the same story with gpu-z 0.6.4...
strange. can't find any more reports on this issue in the internet..
i checked pci link power state setting in power options to no avail.
if it is relevant in any way, my driver version is 296.67, the oem one from asus site (i've got an asus n56vz...
Martin, i've tried the 403_1718 version.
the only difference i noticed is when i run it on nvidia gpu explicitly (via context "run using high-perfomance gpu"), the nvidia sensors won't appear alltogether. they will only show if something is already using the gpu prior to starting the hwinfo...
Martin, thanks for quick reply!
i tried the following:
1) launched a 3d modeller on gt650m
2) started hwinfo (nvidia sensors detected)
3) while i performed various actions in the modeller, move, rotate the scene etc, the clocks varied depending on load, then fell back to minimal when idle...
first off, thanks for such a useful and free monitoring tool :)
i've already read the known issues, but still have a question not being covered there.
i'm running hwinfo using high-perfomance gpu (gt650m in my case), either through context menu "launch using... " or by directly...