HWiNFO64 throttling my gpu?

Hey guys I have a 7970m and for a couple of weeks now I've been monitoring my utilization and games because of all the different drivers that are coming out at the moment however I seem to be having issues in certain games where running HWinfo seems to actually be bringing the performance of the the game and therefore no giving an accurate reading, Saints row the third and GTA 4 seems to be affected by it most although it's affecting some of my other games as well, sorry if this is a known issue I've never used the program until 2 weeks ago

 

I do agree that there seems to be something going on with HWinfo. Was playing TSW with everything maxed out at 50 fps, and could alt tab without any problem. But when I try to use hwinfo while playing, the fps drop to 12-13 fps even if I remove the tessellation and the anti aliasing. I don't know why though, it only happens with HWinfo. :S Also quite inaccurate readings from hw info at first, had to let it run a minute before it started being realistic with the temperatures... I'm suspecting the first reading is inaccurate (and overestimating the actual temperatures), but because of that, hwinfo will throttle. But I'm also rather doubtful about whether hwinfo can really throttle or not...

 

Make sure you disable monitoring of the "Clevo EC" sensors in HWInfo64. There's a lot of overhead to poll these Clevo-specific EC related sensors which can bog down the system (Clevo Fan RPMs, CPU and GPU temps).

 

HWINFO by default does not throttle anything. It's purely a hardware monitoring program. If you're experiencing performance drop, it may be because it's pulling resources and monitoring/providing feedback in real time, while your game is also utilizing hardware resources.

I don't think you should see THAT drastic of a drop in FPS, but then again, I don't know what specs you're running.

 

Do you mean "EC support" or "EC ACPI sync" ? Also, not really related and I guess it's due to the intel RST drivers, my SSD isn't displayed in hwinfo under smart (it's written smart but nothing is listed, however the hdd is listed correctly). Thanks !

 

You can try un-checking "EC support" to see if that changes anything. It probably also deactivates "Clevo EC" monitoring.

However, I meant "Clevo EC" category in the Sensors table. If you don't see "Clevo EC" the the sensors table then that's probably not the problem. If you see "Clevo EC" category with sensors under it (e.g. CPU & GPU fans RPMs and Temperatures), then right-click on the the "Clevo EC" category and click "Disable Monitoring". This will turn-off polling sensors from EC.

 

Simply using Fraps just for monitoring FPS causes BF3 to stutter every 5-10 seconds. I stay away from monitoring programs because you never know how they may be hurting the game's performance.

 

I wonder if I'm not having a general issue with hardware detection as Nvidia inspector won't work (something about dividing by 0 and it detects my cards as Schenker...).

Spoiler

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.DivideByZeroException: Attempted to divide by zero.
at .(Int32 
at .(Int32 
at .(Int32 
at System.Windows.Forms.ListControl.OnSelectedValueChanged(EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedValueChanged(EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at .()
at .(Object , EventArgs 
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at .WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[blablabla not needed as it contain personal info]
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

need moar details. how is gameplay affected? fps drops? what are you noticing? was it not doing whatever it is at first, but now it is? how do you know the readings are inaccurate? are you comparing it with another monitoring utility running simultaneously?

agreed, something else going on.

 

Just bumping.

 

Thanks dude played around with a few games tonight and the utilization seems back to normal after unchecking the Clevo EC box monitoring box in the configuration, I would recommend this to any EM owners if they're getting performance issues whilst monitoring their system with this software, now I can go back to just worrying about Enduro issues!

 

The debugging dialogue is a bit over my head, but if you've played with drivers and still encounter the problem, then I would consider contacting NVidia and/or Microsoft support to see if they have a known issue and resolution. The mismatch in hardware recognition will undoubtedly cause problems.

 

Yeah I'm gonna update to the last drivers and see what happens.
Edit : nope, not working.

 

Well, at least you have no issues when NOT using HWINFO. I wonder if the developer(s) know?

Have you tried using any extensions to HWINFO, such as Riva Tuner?