Thursday, July 30th 2015

TechPowerUp GPU-Z v0.8.5 Released

by
btarunr
 Discuss (18 Comments)
TechPowerUp released GPU-Z v0.8.5, the latest version of the popular video subsystem information and diagnostic utility. It now gets support for Windows 10, including CUDA detection support for Windows 10. GPU voltage monitoring has been added for AMD "Fiji" silicon. Memory controller load monitoring support has been added for AMD "Sea Islands," "Pirate Islands," and "Volcanic Islands" GPUs. GPU-Z can now tell Radeon R9 300 series GPUs, from previous-gen 200 series SKUs.
DOWNLOAD: TechPowerUp GPU-Z 0.8.5 | GPU-Z 0.8.5 ASUS ROG Themed

The change-log follows.

  • Fixed Windows 10 detection
  • Fixed CUDA detection in Windows 10
  • Added GPU voltage monitoring for AMD Fiji
  • Added memory controller load monitoring for AMD Sea Islands, Volcanic Islands, Pirate Islands
  • Board Id moved into BIOS version tooltip
  • Validation Id now displayed in GPU-Z window title
  • Revision Id of recent AMD GPUs will now be displayed
  • Added support for NVIDIA GeForce GTX 970M & 980M (GM204-B), GeForce 940M, 930M
  • Added support for Intel Atom x7-Z8700, Celeron N3150
  • Added support for AMD R9 370, R9 370X, R9 380, R9 390, R9 390X, R9 Fury, A8-7100

Related News

Add your own comment

18 Comments on TechPowerUp GPU-Z v0.8.5 Released

#1
Caring1
Updated and installed already.
Posted on Reply
#2
lemonadesoda
Windows 10 support would be a good time to get TPU GPUz out of beta and start calling it v1.xx

****************


I hav'nt updated TPU for a long time, but just did, and noticed the nice link of the detected GPU to the TPU-GPU database: www.techpowerup.com/gpudb/1839/quadro-k600.html
Posted on Reply
#3
btarunr
Editor & Senior Moderator
lemonadesodaWindows 10 support would be a good time to get TPU GPUz out of beta and start calling it v1.xx
The builds we release to the masses are not betas. You'll find betas in the GPU-Z forum. It's just that we count from 0, and are following a sequence numbering. 0 does not represent alpha.

In either case, we don't offer any warranties for using our software, "stable" or betas.

Personally, I don't know how we'll handle versioning after 0.9.9, because 1.0.0 would create confusion, and somehow tell people that it's the "very first version" or that people will somehow expect it to be far "more stable." That's a bridge we'll cross over 15 versions from now.
Posted on Reply
#4
Cybrnook2002
btarunrThe builds we release to the masses are not betas. You'll find betas in the GPU-Z forum. It's just that we count from 0, and are following a sequence numbering. 0 does not represent alpha.

In either case, we don't offer any warranties for using our software, "stable" or betas.

Personally, I don't know how we'll handle versioning after 0.9.9, because 1.0.0 would create confusion, and somehow tell people that it's the "very first version" or that people will somehow expect it to be far "more stable." That's a bridge we'll cross over 15 versions from now.
Just add a Ti to the end ;-) 0.9.9Ti Or 0.9.9Fury

If that's the worst of it, rolling into a 1.0.0, I think the world will survive. (Y2K all over again)
Posted on Reply
#5
Caring1
Just tag another digit on the end 0.9.9.0
Posted on Reply
#6
Cybrnook2002
Caring1Just tag another digit on the end 0.9.9.0
Posted on Reply
#7
jabbadap
Caring1Just tag another digit on the end 0.9.9.0
Nah that sound just kind of wierd. Why not 0.year.month i.e. 0.15.7 or somewhat similar, that you see in version number which year and month your app is made(4th number if needed for updates from same month).
Posted on Reply
#8
lemonadesoda
jabbadapWhy not 0.year.month i.e. 0.15.7 or somewhat similar, that you see in version number which year and month your app is made(4th number if needed for updates from same month).
+1, yeah to that idea, and the version number will never >1.0 lulz
Posted on Reply
#9
Mathragh
Regarding memory controller load:
Does the inclusion of these specific architectures but not sourthern islands mean that "GCN 1.0" lacks the ability to report/output this metric to the system while later architectures like the one in Bonaire do? Or can we expect support for cards like the 7970 at a later date aswell?

Thanks for the update! I was half expecting this version to have some rudimentary voltage control built in after your breakthrough with fury, but i suppose that kind of thing is out of the scope of GPU-Z:p
Posted on Reply
#10
qubit
Overclocked quantum bit
btarunrPersonally, I don't know how we'll handle versioning after 0.9.9, because 1.0.0 would create confusion, and somehow tell people that it's the "very first version" or that people will somehow expect it to be far "more stable." That's a bridge we'll cross over 15 versions from now.
I say use 1.0.0 as it's a logical progression of the numbering scheme and don't worry people who don't understand simple version numbers. They probably shouldn't be using a computer anyway.

Regardless, I'm glad to see this latest revision of this awesome free app. Keep 'em coming. :)
Posted on Reply
#11
Mathragh
qubitI say use 1.0.0 as it's a logical progression of the numbering scheme and don't worry people who don't understand simple version numbers. They probably shouldn't be using a computer anyway.

Regardless, I'm glad to see this latest revision of this awesome free app. Keep 'em coming. :)
Or might i suggest,... 0.10.0?
Posted on Reply
#12
Zeki
btarunrThe builds we release to the masses are not betas. You'll find betas in the GPU-Z forum. It's just that we count from 0, and are following a sequence numbering. 0 does not represent alpha.

In either case, we don't offer any warranties for using our software, "stable" or betas.

Personally, I don't know how we'll handle versioning after 0.9.9, because 1.0.0 would create confusion, and somehow tell people that it's the "very first version" or that people will somehow expect it to be far "more stable." That's a bridge we'll cross over 15 versions from now.
2.0 would create less confusion or 2.0.1 which sounds less stable than 2.0
after 9800gtx came gtx280
Posted on Reply
#13
rooivalk
Give back the 'Giveaway' tab
Posted on Reply
#14
nunyabuisness
just letting you know. I got a crash
I sent an error report to you.
it experienced an unrecoverable read error in windows 10. latest catalyst drivers. R9 380
Posted on Reply
#15
Divide Overflow
I'm running the latest Catalyst 15.7.1 for my 290x on Windows 10 64, but GPU-Z 0.8.5 indicates only 11.2 DirectX support. Dxdiag claims that it is 12.
Posted on Reply
#16
calkapokole
PCI-Express Render Test is not working for me in Windows 10, it just shows white window. I am using Lenovo Y580 laptop with GTX 660M.
Posted on Reply
#17
btarunr
Editor & Senior Moderator
Zeki2.0 would create less confusion or 2.0.1 which sounds less stable than 2.0
after 9800gtx came gtx280
That is a good suggestion. Thanks.
Posted on Reply
#18
Prima.Vera
I would suggest a numbering scheme something like ver.year.month.date

Ex: 1.150821
Posted on Reply
Add your own comment
Nov 26th, 2024 16:32 EST change timezone

Latest GPU Drivers

New Forum Posts

Popular Reviews

Controversial News Posts