#Gpu z perfcap reason driver
#Gpu z perfcap reason windows

Thanks for taking time to look into this issue and I will modify the thread title to reflect the possible case.Щ†ШіШ®Щ‡ Ш¬ШЇЫЊШЇ Щ…Щ†ШЄШґШ± ШґШЇ : TechPowerUp GPU-Z v2.31. (He refers to 'Furmark actually has its own settings ' which I believe is the temprature alarm feature, not a limit.) I am pretty sure that this threads's OP has experienced the same problem.

#Gpu z perfcap reason windows

Here is screen from Rise of Tomb Raider ( i added black arrows and you can see util in this moment ): In previous Windows version ( 1511 ) i dont had that problem. During this moment there is GPU LOAD,Core clock and voltage drop.GPUZ shows as reason UTIL.

#Gpu z perfcap reason driver

Some also say that it kicks in because the driver thinks the fan is clogged and it cant handle the heat. During fps dip there is core clock drop for example from 1975mhz to 291mhz. Based on what I read online, this could be a driver mechanism to prevent the unit from damaging itself/catching fire. So it does seem that NVIDIA firmware or driver is not very solid regarding temp limit operation.ДЄlso I've found this thread. GPU-Z says that the perfcap reason is 'Util'. A negative clock offset exceeding minus 200MHz would practically render the temp limit ineffective. For example, a negative clock offset will decrease the 'responsiveness' of temp throttling. This is very likely since I've observed other quirks with NVIDIA temp limits. Due to this problem temperature limit would be ineffective during particular workloads, such as when the workload is cleverly designed to max out TDP. Thanks for the quick response! If this is the case, then it's highly likely that there is some sort of problem with either the NVIDIA card firmware or the NVIDIA driver. Some other time Perfcap Reason will not include 'Thrm' at all even if temp has already reached 68C. Most of the time it's as described above, 'Perfcap Reason' will include 'Thrm' but no actual throttling. After FurMark stress test and the temp limit fails, there are different symptoms also. It is natual to suspect furmark since I also observed that furmark itself does not respect temp limit during stress test as if it has overriden any previously set temp limit, so it might be the case that it fails to restore temp limit and somehow borked the GPU driver temp limit algorithm.ДЈ. Please notice that 'temp limit' does not work means that Voltage and Clock are not being actively throttled back once the temprature hit 65C which can be easily observed via various hardware monitoring tool.Дў. Temp would rise all the way up to 67C~68C with no throttling observed.(normally it would throttle back to Try re-applying 65C temp limit in MSI AB, it still does not work. Voltage and Clock are not being actively throttled back once 'Perfcap reason' turns to 'Thrm' in GPU-Z. Play some game and notice that temp limit does not work anymore, i.e.Launch FurMark stress test with the following setting: 1024x768 windowed mode, 0xMSAA.Voltage and Clock are being actively throttled back once 'Perfcap reason' turns to 'Thrm' in GPU-Z Play some game and notice that temp limit does work, i.e.Set temp limit = 65 degrees C via MSI AB or NvidiaInspector.Steps to reproduce: (Not 100% reproducible) During FurMark stress test, temprature limit is not effective.ДЄfter running FurMark stress test, temperature limit might remain ineffective in subsequent gaming or GPU intensive applications.

Gpu-z perfcap reason