HwInfo causing FPS drop anomalies on Nvidia GPUs with VSync

maffle

Well-Known Member
There is a weird bug since months in combination of Nvidia drivers on Windows 11 and HwInfo running, causing FPS not be stable at VSync cap.

If you have a monitor which doesnt support Gsync, so it just uses VSync, and have HwInfo running, there is a weird glitch happening, that the FPS is not stable at for example 60, 120 or 144Hz/FPS, but randomly jumps down to 50-57, 110-117, 120-135. If you force global VSync off in Nvidia panel and set a FPS cap which is equal to the monitor refresh rate, the issue stops. The issue also stops (not 100% though it seems) if you close HwInfo. You can test this with https://www.testufo.com/

The issue is also debated in this post:



HwInfo: 7.68-5300
Nvidia driver: 546.33
Windows 11: 23h2 22631.2861
 
This problem is affecting also other tools like MSI Afterburner so I'm quite sure that it's an issue in NVIDIA drivers and not on our side.
You should be able to workaround this by disabling monitoring of the NVIDIA GPU sensor. If that fixes it, then it's a problem in GPU drivers and it should be reported to NVIDIA.
 
Disabling the Nvidia GPU sensor in HwInfo does not fix it, just closing HwInfo entirely.

FPS randomly jump below 120 with HWInfo running in the background:

1703159669966.png

Few seconds after closing HwInfo in Systray:

1703159727128.png
 
Have you also disabled the NVIDIA GPU sensor title row?
If that doesn't help, try to disable other sensors to see which one is causing this. It could be the EC or S.M.A.R.T. sensors.
 
Have you also disabled the NVIDIA GPU sensor title row?
What you mean with that? I would assume if you click "disable monitoring" on the sensor, it is off, no?

These sensors are running:

1703160167133.png

Disabling all also doesnt fix it:

1703160281944.png
 
Yes, disabling the sensor title will completely disable monitoring of that sensor.
Which HWiNFO version are you running, the latest one?
Try to also disable the "PresentMon Support" option in main settings of HWiNFO and restart it.
 
I have tested to set EC and PresentMon support off, restart HwInfo, doesnt change anything:

1703160952730.png
1703160964231.png

1703161027869.png
Closing HwInfo from Systray fixes it after a few seconds:

1703161098640.png

Starting HwInfo again and wait about 10-20 seconds, issue starts to happen again randomly.

Latest HwInfo 7.68-5300.
 
That's weird then. I that case HWiNFO shouldn't be accessing any sensors.
Is MSI Afterburner affected the same way?
Still looks like an issue in NVIDIA drivers...
 
For me right now, no MSI AB doesnt seem to trigger it and FPS stay stable even with MSI AB / RTSS running in systray with monitoring on:

1703161677110.png

Starting HWInfo again, broken:

1703161734466.png
 
Checked and HWiNFO isn't doing anything in that case - not accessing any sensors, devices.
So I don't understand what's causing this but I don't think it's an issue in HWiNFO.
 
The issue is happening while HwInfo is running, and not happening while not running. I can repeat this infinite times with 100% chance. Maybe it is the driver loaded when HwInfo runs causing this. Or the Nvidia driver or Windows is detecting HwInfo is running and does something weird, but why should it do that. I dont see an app profile in the Nvidia control panel for HwInfo.
 
Could be anything else indirectly affecting this. Also the fact that it started to happen since a certain NVIDIA driver version would point there...
Try to perhaps run HWiNFO in normal mode (disable Sensors-only) and then check if it happens with the Summary screen active or only with the main window.
 
Does not happen with just stats and sensors off selected in welcome screen:

1703164902286.png

1703164867363.png
 

Attachments

  • 1703164841845.png
    1703164841845.png
    305 bytes · Views: 2
Disable also the "Summary-only" option and start again. Then check before opening the Sensors window from main and after closing the sensors.
 
still working
1703165389585.png

still working
1703165574936.png

opening sensors, broken
1703165625346.png

Issue stays broken even with sensor window closed, until closing HwInfo.
 
And when you close the sensors window so that the main one remains, does it revert back to OK state?
I'm testing this as well but can't reproduce the problem - maximum I can see is occasionally 1+ while most of the time it's READY.
 
That's weird.. Try to disable some options in HWiNFO like NVML Support or SMBus Support.
 
Back
Top