Some NVidia cards not being detected. GPUz not useable but HWinfo mostly ok.

[Joseph Stateson]

I have 6 P102-100 cards, these are equivalent to GTX-1080Ti, but are in the $40 USD range.
They can be force installed in Win11 as P104-100 or using an unsigned driver as P102-100.  They are  not recognized by tthrottle except using GPUz or HWinfo32

1 - GPU-z (looking at Tthrottle display)
I ran 4 instances of GPU-z and set each instance to a different GPU. Tthrottle shows 4 GPUs in the external tab but only one temperature (the first instance) was available.  Possibly there is a setting to force 4 GPUs in tthrottle.xml but I do not know how to configure it.

2 - HWinfo (looking at Tthrottle display)
HWinfo Pro shows all 4 GPU temperatures in Tthrottle but only good for 12 hours.  The temperatures matched that revealed by the nvidia-smi app.  I uninstalled Pro and put in HWinfo32 and there was a notice that not all items were uninstalled.  TThrottle's GPU2 showed 1100c using HWinfo32.  All the other temps in TThrottle were ok and matched nvidia-smi.  BT reported the 4 temperatures but put in 0c for the problem 1100c temperature.

I brought up GPU-z and set instance to the GPU2 and got the correct temperature (in Tt).  In Tthrottle, I was going to disable GPU2 in HWinfo and enable it for GPUz.  I noticed that GPU2 in HWinfo now had the correct temperature. I closed GPUz and the temperature momentarily went back to 1100c.  While looking this strange problem the temperature toggled between the correct temperature and the 1100c temp.  Eventually everything in tthrottle "external" stabilized to the correct temperatures that matched nvidia-smi.

I am guessing that the left over setting from HWinfo64 Pro caused the problem in HWinfo32.  If I had known the uninstall would not be clean I would have used REVO to do the uninstall.

It would be nice to avoid using GPUZ or HWinfo.





[edit] I think I found the problem with HWinfo32:  While I had uninstalled HWinfo64 Pro, I had failed to close it and the uninstall did not bother terminating it.  I was running both the 32 and the 64 bit version of the app at the same time.  Probably was a coincidence the problem became fixed when running GPUz.  I have since rebooted and all is working OK with HWinfo32