Friday, March 14th 2014

TechPowerUp GPU-Z 0.8.2 Released

TechPowerUp released the latest version of GPU-Z, the popular video hardware information and diagnostic utility. Version 0.8.2 brings with it a vast number of changes, support for new hardware, and bug-fixes. To begin with, the user-interface of GPU-Z received a major update, with the addition of a "Lookup" button that takes you to our GPU Database page corresponding to your GPU. The app can now tell you if your drivers are WHQL-signed. GPU manufacturer logos are updated.

Among the new hardware supported includes NVIDIA GeForce TITAN-X, GTX 980M, GTX 970M, GGTX 965M, GTX 845M, GTX 760 Ti OEM, GTX 660 (960 shaders), GT 705, GT 720, GT 745M, NVS 310, and Grid; AMD Radeon R9 255, FirePro W7100, HD 8370D, AMD R9 M280X, and R9 M295X; and Intel "Broadwell" integrated graphics. Specifications are revised for GeForce GTX 970.

A large number of bugs were fixed, and overall usability improved, including notably GPU-Z now supports Windows 10. We implemented a new working way of extracting BIOS from NVIDIA GPUs on systems with WIndows 8 and higher, to avoid a system hang. A large number of bugs were fixed, and overall usability of the app improved, as detailed in the change-log.
DOWNLOAD: TechPowerUp GPU-Z 0.8.2 | GPU-Z 0.8.2 ASUS ROG-themed

The Change-log follows.

  • Added graphics card lookup button
  • Added Windows 10 support
  • Added support for NVIDIA Titan X
  • Added support for AMD R9 255, FirePro W7100, HD 8370D, AMD R9 M280X, R9 M295X
  • Added support for NVIDIA GTX 980M, GTX 970M, GTX 965M, GTX 845M, GTX 760 Ti OEM, GTX 660 (960 shaders), GT 705, GT 720, GT 745M, NVS 310, Grid K200
  • Added support for Intel Broadwell Graphics
  • Improved Intel GMA3600 support
  • Improved hardware access stability on AMD Kaveri
  • Fixed GTX 970 ROP count
  • The driver version readout will now display WHQL status
  • Added AMD APU logo and updated other logos
  • Added PCI-Express bus usage sensor on NVIDIA
  • Added registry key (Force_WDDM_Mem_Sensor=1) to bypass NVIDIA driver memory monitoring and use WDDM monitoring instead
  • Web links now opened in default browser
  • Fixed NVIDIA BIOS save hanging system on Windows 8 and newer
  • Show N/A on Intel IGP memory size
  • Fixed GPU-Z icon disappearing on shortcuts
  • Fixed blank line between sensor logfile entries
  • GPU-Z can now start properly from encrypted system drive
  • Displayed Catalyst version only includes version number
  • Fixed OpenCL detection on HD 7970M
  • CrossFire on AMD cards no longer displayed as ATI CrossFire
  • Disabled memory vendor detection on future APUs
Add your own comment

43 Comments on TechPowerUp GPU-Z 0.8.2 Released

#1
VulkanBros
Is GPU-Z built-in in GPUTweak?? Do I have to wait for ASUS to update GPU-Z??
I know that I just can run GPU-Z alone ....
Posted on Reply
#2
W1zzard
VulkanBros said:
Is GPU-Z built-in in GPUTweak?? Do I have to wait for ASUS to update GPU-Z??
I know that I just can run GPU-Z alone ....
You will have to wait for an update, the GUI in GPUTweak is independent of GPU-Z, so you won't see the lookup button for example, but they use the same underlying detection engine.
Posted on Reply
#3
T4C Fantasy
CPU & GPU DB Maintainer
all that hard work on the gpudb is now paying off more and more :)
Posted on Reply
#4
qubit
Overclocked quantum bit
bta, I swear man you should use the Press Release icon instead of the Featured icon for these types of news posts. It would look so cool. :cool:

Downloading now.
Posted on Reply
#5
Maban
Still not showing PerfCap without installing.
Posted on Reply
#6
AlienIsGOD
lookup button takes me to a Galaxy GTX 680 SOC, i have a MSI 680 reference ... at least according to the stock cooler i took off it was. Just saying :D
Posted on Reply
#7
Maban
AlienIsGOD said:
lookup button takes me to a Galaxy GTX 680, i have a MSI 680... at least according to the stock cooler i took off it was. Just saying :D
What does GPU-Z say your subvendor ID is?
Posted on Reply
#8
thevoiceofreason
Yeah, I have MSI HD 7850 OC 2 GB but the lookup takes me to MSI HD 7850 Twin Frozr III OC. I guess it would be difficult to make it very reliable across similar models.
Posted on Reply
#9
Maban
thevoiceofreason said:
Yeah, I have MSI HD 7850 OC 2 GB but the lookup takes me to MSI HD 7850 Twin Frozr III OC. I guess it would be difficult to make it very reliable across similar models.
Seems like both of those cards have the same subsytem ID of 2730. The database/GPU-Z has no way to distinguish between them. This will happen for some cards. Barring the occasional mistake by our resident maintaininator, these misidentifications are the fault of the manufacturer.

The following is how cards are identified by GPU-Z. If different cards have the same identifying numbers, there will be mistakes in the process.

Posted on Reply
#10
zmeul
  • Fixed GTX 970 ROP count
fixed, how exactly? forced to display the right count or the method of reading is different ??
Posted on Reply
#11
MxPhenom 216
Corsair Fanboy
hey @W1zzard I'm curious. What language is GPU-z coded in? C++?
Posted on Reply
#12
W1zzard
MxPhenom 216 said:
hey @W1zzard I'm curious. What language is GPU-z coded in? C++?
C++ with MFC

zmeul said:
fixed, how exactly? forced to display the right count or the method of reading is different ??
The reading method I use can only count partitions, ie. not half-disabled partitions. So for GTX 970 only I use a hardcoded value. NVIDIA has recommended to use Level 2 Cache Size as indicator of ROPs, but that method requires CUDA, which adds another 0.5 seconds of startup time to GPU-Z.

Maban said:
Seems like both of those cards have the same subsytem ID of 2730. The database/GPU-Z has no way to distinguish between them. This will happen for some cards. Barring the occasional mistake by our resident maintaininator, these misidentifications are the fault of the manufacturer.

The following is how cards are identified by GPU-Z. If different cards have the same identifying numbers, there will be mistakes in the process.


Exactly what Maban said. I could imagine that we add some kind of arbitration mechanism further down the road. ie "multiple possible cards detected, please select". Right now the focus is to figure out how many people are interested in the lookup feature, what the number of unknown boards is, how we can add those.
Posted on Reply
#13
m0nt3
New version show my video card @ PCI-E x1 V1.1

The old version shows PCI-E x16 2.0


Edit: Odd, when I took the screenshot it said PCI-E@ x16 2.0(0.8.1), but opening it up I can watch it change, on old version only. New vresion does not, launching game to see if it changes. Power saving feature?
Posted on Reply
#14
W1zzard
m0nt3 said:
New version show my video card @ PCI-E x1 V1.1

The old version shows PCI-E x16 2.0

Both show exactly the same. After a while your card will return to a lower PCIe speed to conserve power
Posted on Reply
#15
m0nt3
Yes, see edit. I just monitored it during a quick game and noticed the it change, even version number I guess depending on bandwidth demands. Interesting. Guess I never played close enough attention before. Thanks.
Posted on Reply
#16
kn00tcn
what is the kaveri stability thing, was gpuz causing hard locks/resets/bsods before? (i have a kaveri that acted funny in august when gpuz was open, but i RMA'd the motherboard & i'm pretty sure 14.9 onward has been stable)

why is the screenshot GIF instead of PNG! :shadedshu:
Posted on Reply
#17
thevoiceofreason
Maban said:
Seems like both of those cards have the same subsytem ID of 2730. The database/GPU-Z has no way to distinguish between them. This will happen for some cards. Barring the occasional mistake by our resident maintaininator, these misidentifications are the fault of the manufacturer.

The following is how cards are identified by GPU-Z. If different cards have the same identifying numbers, there will be mistakes in the process.


Maybe you could distinguish them by the BIOS version, since you have that information in the database as well? Or is it also the same between both cards?
Posted on Reply
#18
Maban
thevoiceofreason said:
Maybe you could distinguish them by the BIOS version, since you have that information in the database as well? Or is it also the same between both cards?
Wiz would have to chime in on that but I believe it's not a reliable option and/or too complex too implement.
Posted on Reply
#19
Solaris17
Dainty Moderator
This displays windows 8 in build 9926 enterprise edition of win 10 beta.
Posted on Reply
#20
Pehla
how come cuda cores are not available on gpu.z??
Posted on Reply
#21
btarunr
Editor & Senior Moderator
Solaris17 said:
This displays windows 8 in build 9926 enterprise edition of win 10 beta.
The driver you're using (WDDM 1.2) was coded for Windows 8/8.1.
Posted on Reply
#23
Solaris17
Dainty Moderator
btarunr said:
The driver you're using (WDDM 1.2) was coded for Windows 8/8.1.
Then is the update simply optimizations to run on Windows 10? As far as iv seen their are no Windows 10 display drivers for AMD. What exactly is Windows 10 support?
Posted on Reply
#24
Ferrum Master
Solaris17 said:
Then is the update simply optimizations to run on Windows 10? As far as iv seen their are no Windows 10 display drivers for AMD. What exactly is Windows 10 support?
Then what are those mate?
Posted on Reply
#25
Solaris17
Dainty Moderator
Ferrum Master said:
Then what are those mate?

the Windows pre-installed drivers. I guess your post answered my question their are not. At least GPU-Z will work when AMD releases a package for WDDM 2
Posted on Reply
Add your own comment