- Joined
- Oct 22, 2020
- Messages
- 20 (0.01/day)
Hello! I'm doing a lot of GPU testing, mostly NVIDIA 3xxx series and I'm running GPU-Z for every card. I do not have GPU-Z auto-starting, I'm just manually launching it.
Several months ago I noticed quite strange behaviour: when I plug a new GPU or even re-plug existing GPU on another PCIe slot - then after automatic driver re-installation done by Windows - I can run ~all 3d apps just fine, but I can't run GPU-Z. It silently exits without showing splash screen, no matter how times I try. But after a reboot (so it would be a clean boot without driver reinstallation) - GPU-Z starts working perfectly fine.
A lot of other tools including GPUShark, Afterburner, do work fine just after driver install before reboot. But the Hwinfo64 tool suffers from same issue as GPU-Z. So, it may be some OS/driver special behaviour that is not handled in GPU-Z and hwinfo64. I didn't have this issue ~year ago but unfortuntely didn't notice when it appeared.I was initially suspecting GPU-Z update - but it is not the case: the all 2.x GPU-Z versions that worked fine earlier now has this same problem.
I gone earlier to just find that GPU-Z 0.4.6 starts fine, but the 0.4.7 does not work until reboot. The changelog says that 0.4.7 introduced some driver loading machinery changes, maybe it is related
By now I'm running R560.38 driver, but the issue appeared definitely earlier while I was using several older drivers.
The windows version is win10 22H2 10.0.19045.2251 (Nov 8 2022) with EFI boot.
Also, it it matters I have intel integrated GPU (problem appeared both with UHD 610 and HD P630) and during initial windows boot I have only intel GPU having driver attached, so the "GPU-with-driver" count switches from 1 to 2 during driver install.
Overall, the problem is a quite minor since only affects scenarios with often GPU replacements. Even more - maybe something changed in my system that lead to GPU-Z and hwinfo64 misbehaviour in the "driver installed without reboot scenario". Being a developer I understand that such kind of bugs without exactly known way to reproduce can be hard to fix, so I've created this thread mostly to start collecting other users feedback regarding similar problem.
I don't know if GPU-Z is writing some logs, so to make at least some light on the silent exit reason I launched it under the WinDBG tool. It seems that GPU-Z crashes nearly immediatlely after start with something like "NULL+4 pointer dereference". The exact GPU-Z version corresponding to the below offsets is GPU-Z 2.59.0
Several months ago I noticed quite strange behaviour: when I plug a new GPU or even re-plug existing GPU on another PCIe slot - then after automatic driver re-installation done by Windows - I can run ~all 3d apps just fine, but I can't run GPU-Z. It silently exits without showing splash screen, no matter how times I try. But after a reboot (so it would be a clean boot without driver reinstallation) - GPU-Z starts working perfectly fine.
A lot of other tools including GPUShark, Afterburner, do work fine just after driver install before reboot. But the Hwinfo64 tool suffers from same issue as GPU-Z. So, it may be some OS/driver special behaviour that is not handled in GPU-Z and hwinfo64. I didn't have this issue ~year ago but unfortuntely didn't notice when it appeared.I was initially suspecting GPU-Z update - but it is not the case: the all 2.x GPU-Z versions that worked fine earlier now has this same problem.
I gone earlier to just find that GPU-Z 0.4.6 starts fine, but the 0.4.7 does not work until reboot. The changelog says that 0.4.7 introduced some driver loading machinery changes, maybe it is related
By now I'm running R560.38 driver, but the issue appeared definitely earlier while I was using several older drivers.
The windows version is win10 22H2 10.0.19045.2251 (Nov 8 2022) with EFI boot.
Also, it it matters I have intel integrated GPU (problem appeared both with UHD 610 and HD P630) and during initial windows boot I have only intel GPU having driver attached, so the "GPU-with-driver" count switches from 1 to 2 during driver install.
Overall, the problem is a quite minor since only affects scenarios with often GPU replacements. Even more - maybe something changed in my system that lead to GPU-Z and hwinfo64 misbehaviour in the "driver installed without reboot scenario". Being a developer I understand that such kind of bugs without exactly known way to reproduce can be hard to fix, so I've created this thread mostly to start collecting other users feedback regarding similar problem.
I don't know if GPU-Z is writing some logs, so to make at least some light on the silent exit reason I launched it under the WinDBG tool. It seems that GPU-Z crashes nearly immediatlely after start with something like "NULL+4 pointer dereference". The exact GPU-Z version corresponding to the below offsets is GPU-Z 2.59.0