TechPowerUp GPU-Z v2.26.0 Released

[btarunr]

Today we released the latest version of TechPowerUp GPU-Z, the popular graphics subsystem information, monitoring, and diagnostic utility. Version 2.26.0 adds support for new GPUs, introduces new features, and fixes problems with existing ones. To begin with, support is added for AMD Radeon RX 5500 and RX 5500M, TU104-based NVIDIA GeForce RTX 2060 (non-Super), and Quadro P520. Fake detection has been added for various "Kepler" based GTX 10-series knockoffs.

With this release we fixed an application crash during BIOS extraction on nearly all NVIDIA GPUs. Another crash that appears when the application is launched on machines with AMD "Navi" GPUs without drivers installed. The ASUS ROG skin has been fixed to properly show the "Close" button in the bottom. We also improved the memory junction temperature tooltip on AMD "Navi" to denote that the hottest chip's junction temperature is being reported, and not an average across all chips. Last version's AMD Navi fan-stop fix has been reverted since AMD fixed the issue since their 19.9.1 drivers. PCIe and CrossFire state detection has been fixed for AMD "Navi" and "Vega 20" based graphics cards. Grab it from the link below.

DOWNLOAD: TechPowerUp GPU-Z v2.26.0



The change-log follows.

• Fixed GPU-Z crashing during BIOS save on nearly all recent NVIDIA cards
• Fixed crash on startup on Navi when no driver installed
• Fixed ASUS ROG window getting cut off at bottom, hiding the "Close" button
• Added support for AMD Radeon RX 5500 & RX 5500 Mobile
• Updated the AMD memory temperature tooltip to clarify that it shows memory junction temperature, and that the value is the temperature of the hottest chip (not average)
• Moved reset button on sensors tab by one pixel to properly align it
• Reverted AMD fan-stop-detect-workaround, which was added in last version, because it introduced misreadings. AMD has fixed their driver since 19.9.1
• Fixed PCIe idle speed reported for Vega 20
• Fixed CrossFire detection on Navi and Vega 20
• Fixed NVIDIA Quadro NVS 300 getting reported as fake
• Added fake detection for cards using NVIDIA GK107 & GK208
• Added fake detection for GeForce GTX 1050 Ti based on GK107
• Added support for TU104-based RTX 2060 and Quadro P520

View at TechPowerUp Main Site

 

[Deleted member 50521]

I am really digging these "fake detection" functions. It is a god send to people trying to get used GPU without being scammed.
Good job!

 

[Sequence]

TU104 is not for RTX 2060. how is this possible?

 

[potato580+]

downloaded

 

[W1zzard]

TU104 is not for RTX 2060. how is this possible?

It's a new SKU

 

[Sequence]

It's a new SKU

Not anything I think NVIDIA has announced

 

[W1zzard]

Not anything I think NVIDIA has announced

That's correct

 

[ScaLibBDP]

I stopped using new versions of GPU-Z since they are too many bugs.

GPU-Z version 2.14.0 is what I consider, to some degree, a stable version.

Unfortunately, every time when a GPU-Z developer introduces some new functionality new errors are made as well and this is a typical junior-like style of programming.

One of the most disturbing bugs is when GPU-Z fails to initialize completely, Splash screen is left on the screen, the main dialog-box is Not displayed and it is Not possible to kill incompletely initialized executable ( only reboot helps ).

UI-features are also Not taken care of. That is, I use a portable multi-GPU setup on a mobile workstation for R&D and software development and this is what I'd like to see as a new feature of GPU-Z.

 

[W1zzard]

Thanks for your feedback

since they are too many bugs.

There's just too many hardware and software combinations to test. Why don't you report bugs that you encounter?

One of the most disturbing bugs is when GPU-Z fails to initialize completely, Splash screen is left on the screen, the main dialog-box is Not displayed and it is Not possible to kill incompletely initialized executable ( only reboot helps ).

First time I hear about this. Never saw it in development either, killing in Task Manager works fine

and this is what I'd like to see as a new feature of GPU-Z.

The "name" in GPU-Z is the same name as in Windows Device Manager. What mechanism do you suggest to pick "#1" and "#2"?