Tuesday, September 5th 2017

TechPowerUp GPU-Z v2.3.0 Released

by
btarunr
 Discuss (28 Comments)
TechPowerUp today released the latest version of GPU-Z, the graphics subsystem information, diagnostic, and monitoring utility PC enthusiasts swear by. Version 2.3.0 adds support for new GPUs, and comes with several under the hood improvements. To begin with, GPU-Z 2.3.0 adds official support for AMD Radeon RX Vega 64 and RX Vega 56; Radeon Pro WX 7100 and WX 3100; NVIDIA GeForce GTX 1080 Mobile, GeForce MX150, and Quadro M2200. We've added a new VRM efficiency monitoring feature, and VDDC/VDDCI power readings for AMD "Polaris" based graphics cards. Also addressed are bugs with GPU and memory activity monitoring on Radeon RX 500 series; missing or incorrect information on AMD graphics cards running on 17.7.2 drivers; and a rare crash on machines with AMD CrossFire configurations.
DOWNLOAD: TechPowerUp GPU-Z v2.3.0

The change-log follows.

  • Added support for AMD Radeon RX Vega Series
  • Fixed incorrect/missing information AMD Catalyst 17.2.2 and newer
  • Fixed GPU & memory activity monitoring on AMD Radeon RX 500 Series
  • Fixed crash on startup in rare CrossFire configurations
  • Fixed CrossFire detection for slave cards
  • Addded VRM efficiency & VDDC/VDDCI power readings for Polaris
  • Added support for AMD Radeon WX 7100, WX 3100
  • Addded support for NVIDIA Quadro M2200, GTX 1080 Mobile, GeForce MX150

Related News

Add your own comment

28 Comments on TechPowerUp GPU-Z v2.3.0 Released

#2
W1zzard
LightofhonorChanged from 2.2.1 to 2.3 mid article :)
Fixed
Posted on Reply
#6
WhyCry
How is GPUZ detecting SPs? I have 64 flashed with 56 BIOS and it reads 4096 cores, while it's 3584. Even the built-in OpenCL says 56 CUs.

Posted on Reply
#7
W1zzard
WhyCryHow is GPUZ detecting SPs? I have 64 flashed with 56 BIOS and it reads 4096 cores, while it's 3584. Even the built-in OpenCL says 56 CUs.

Interesting, it should read them from hardware, maybe I'm poking the wrong registers
Posted on Reply
#8
WhyCry
W1zzardInteresting, it should read them from hardware, maybe I'm poking the wrong registers
Not sure if this matters, but the previous version is showing 3584.
Posted on Reply
#12
TheoneandonlyMrK
W1zzardDon't forget to upload your BIOS :)
I have frequently been advised that gpuz does not get the whole bios, ie Gop tables have you any mind to do this and does it matter anyway.
Im liking the update btw , is there any chance of adding memory wattage used to the monitored values for vega too.
Posted on Reply
#13
W1zzard
theoneandonlymrkI have frequently been advised that gpuz does not get the whole bios, ie Gop tables have you any mind to do this and does it matter anyway.
Im liking the update btw , is there any chance of adding memory wattage used to the monitored values for vega too.
There was a bug a few years back that didn't save the whole bios on some amd cards. Earlier versions won't save the fullvega bios because no Vega support. This one supports Vega and thus works fine, do a byte to byte comparison :) no bios saving issues on Nvidia, ever, at least as far as I know.
Posted on Reply
#14
chief-gunney
latest version is showing Samsung memory for my Vega 56, I hope that's correct but I should be able to verify next week when my waterblock arrives.
Posted on Reply
#15
BadIronTree
W1zzardThere was a bug a few years back that didn't save the whole bios on some amd cards. Earlier versions won't save the fullvega bios because no Vega support. This one supports Vega and thus works fine, do a byte to byte comparison :) no bios saving issues on Nvidia, ever, at least as far as I know.
I do not think my MAX is correct lol

948c would boil the water to steam :D
Posted on Reply
#16
Xzibit
BadIronTreeI do not think my MAX is correct lol

948c would boil the water to steam :D
Steel factories will buy these up to treat & melt steel.
Posted on Reply
#17
W1zzard
BadIronTreeI do not think my MAX is correct lol

948c would boil the water to steam :D
did you run any other monitoring tools at the same time? any idea how to reproduce?
Posted on Reply
#18
JB_Gamer
There's a security warning on the downloaded ROG version!?
Posted on Reply
#19
W1zzard
JB_GamerThere's a security warning on the downloaded ROG version!?
Whats the warning? Screenshot?

Edit: Please check now. For some reason the file didn't get the TPU digital signature. I've signed and reuploaded
Posted on Reply
#20
BadIronTree
W1zzarddid you run any other monitoring tools at the same time? any idea how to reproduce?
Only the MSI afterburner 4.4 beta 12 with the overlay riva 7 beta 26 (last beta ver. in both apps) (windows 10 only work with beta now)
Posted on Reply
#21
JB_Gamer
W1zzardWhats the warning? Screenshot?

Edit: Please check now. For some reason the file didn't get the TPU digital signature. I've signed and reuploaded
Sorry, did not make any. But anyway, that was yesterday, now - today it's ok - no warning.
Posted on Reply
#22
W1zzard
BadIronTreeOnly the MSI afterburner 4.4 beta 12 with the overlay riva 7 beta 26 (last beta ver. in both apps) (windows 10 only work with beta now)
I guess that's the reason then. Multiple programs trying to read the same registers at the same time. Can you try without AB?
Posted on Reply
#23
BadIronTree
W1zzardI guess that's the reason then. Multiple programs trying to read the same registers at the same time. Can you try without AB?
I will try in few hours
Posted on Reply
#24
JB_Gamer
A sugg-/question: Would it be possible to add a summary to the log? It's often only most interesting to now MIN/MAX for; temperature, voltage, wattage, load, frequency..., it's not fun (tedious) to look for these result manually.
Posted on Reply
#25
natr0n
"PC enthusiasts swear by"

If you say soo_O
Posted on Reply
Add your own comment
Dec 19th, 2024 04:08 EST change timezone

Latest GPU Drivers

New Forum Posts

Popular Reviews

Controversial News Posts