Dave-H
New Member
- Joined
- Nov 19, 2019
- Messages
- 12 (0.01/day)
Just a heads up that there seems to be a problem now with GPU-Z on the XP side of my dual boot system.
It's always worked fine for years, and has been regularly updated, but when I recently updated to the latest version (2.27.0) I ran into a severe problem.
I had been using version 2.20.0 previously, and hadn't updated for quite a while.
I have two graphics cards fitted, an old ATI X600, and a more recent nVidia Quadro 2000.
I can use both on XP as there are drivers for both of them.
Now when I run GPU-Z, it defaults to the Quadro 2000, which is fine, but if I try to select the ATI X600, which is the card I'm using, the program immediately locks up and prevents the whole display updating properly.
It does display the data for the ATI card after a long delay, but is completely unresponsive, as is the rest of the desktop, until I forcibly kill it.
By process of elimination, this issue seems to have first appeared with version 2.23.0. Version 2.22.0 is fine, and doesn't have the problem.
Could it be something to do with the high DPI support which was added in 2.23.0?
All versions including the current one, are fine on the Windows 10 side of the machine, needless to say!
I thought this should be mentioned in case others with older systems run into the same problem.
Is this something that can be fixed, or should I just stick with 2.22.0?
Thanks, Dave.

It's always worked fine for years, and has been regularly updated, but when I recently updated to the latest version (2.27.0) I ran into a severe problem.
I had been using version 2.20.0 previously, and hadn't updated for quite a while.
I have two graphics cards fitted, an old ATI X600, and a more recent nVidia Quadro 2000.
I can use both on XP as there are drivers for both of them.
Now when I run GPU-Z, it defaults to the Quadro 2000, which is fine, but if I try to select the ATI X600, which is the card I'm using, the program immediately locks up and prevents the whole display updating properly.
It does display the data for the ATI card after a long delay, but is completely unresponsive, as is the rest of the desktop, until I forcibly kill it.
By process of elimination, this issue seems to have first appeared with version 2.23.0. Version 2.22.0 is fine, and doesn't have the problem.
Could it be something to do with the high DPI support which was added in 2.23.0?
All versions including the current one, are fine on the Windows 10 side of the machine, needless to say!
I thought this should be mentioned in case others with older systems run into the same problem.
Is this something that can be fixed, or should I just stick with 2.22.0?
Thanks, Dave.
