Wednesday, February 27th 2019

TechPowerUp Releases GPU-Z v2.17.0

TechPowerUp today released the latest version of TechPowerUp GPU-Z, the graphics subsystem information, monitoring, and diagnostic utility no enthusiast can leave home without. Version 2.17.0 adds support for new GPUs, and fixes a number of issues. To begin with, GPU-Z adds support for AMD Radeon VII, NVIDIA TITAN RTX, GeForce GTX 1660 Ti, GeForce RTX 20-series Mobile, Quadro RTX 4000, Intel "Amber Lake" GT2 graphics, among several other rare GPU models detailed in the change-log. Support is also added for AMD Radeon Software Adrenalin 2019 Edition drivers.

Among the several issues fixed are improved monitoring on Radeon RX 580 2048-SP, default boost frequency reporting on GTX 1660 Ti and certain "Pascal" GPUs, missing fan sensors on RTX 20-series cards with no display connected, a start-up crash and DXVA 2.0 report crash noticed on Windows XP machines; power-limit reporting and BIOS extraction crashes on certain older NVIDIA GPUs, various general crashes caused by physical memory access, and video memory reporting on "Vega" based graphics cards with 16 GB memory. There are numerous user-experience improvements, including simplified sensor labels, improved memory usage readouts, a more functional crash-reporter that lets you describe the problem along with an e-mail address input so we could directly get back to you; memory timings readouts only appearing in compatible environments, etc. Grab GPU-Z from the link below.
DOWNLOAD: TechPowerUp GPU-Z v2.17.0

The complete change-log follows.

  • Added support for NVIDIA GTX 1660 Ti, Titan RTX, RTX 2080 Mobile, RTX 2070 Mobile, RTX 2060 Mobile, Quadro RTX 4000, GTX 650 (GK106), Quadro P5200
  • Added support for AMD Radeon VII, Radeon HD 8400E
  • Added support for Intel Amber Lake GT2 (Core i7-8500Y)
  • Added support for detection of Radeon Adrenalin 2019 version
  • Simplified some sensor titles: "GPU Clock", "Memory Clock", "Shader Clock"
  • Unified "Memory Used" / "Memory Usage" sensor titles to "Memory Used"
  • Improved crash reporter to ask for problem description and optional email, so we can follow up
  • Advanced Panel dropdown will show "Memory Timings" option only when memory timing details are available
  • OpenCL "Max Packet Size" is now formatted as unsigned value
  • Instead of empty value show "None" when no OpenCL Built-in Kernels supported
  • Added support for "None" in OpenCL DP, SP, Half FP Capability
  • Fixed "File creation failed" message during GPU-Z startup
  • Fixed GPU and memory load monitoring on RX 580 2048 SP
  • Fixed missing default boost clock on GTX 1660 Ti and some Pascal cards
  • Fixed missing fan sensors on RTX cards with no monitor connected
  • Fixed crash on startup (Windows XP)
  • Fixed crash when opening DXVA 2.0 report (Windows XP)
  • Fixed power limit reporting on older NVIDIA cards
  • Fixed crash during BIOS save on older NVIDIA cards
  • Fixed incorrect VRAM reporting on 16 GB Vega
  • Fixed various crashes caused by physical memory access
Add your own comment

15 Comments on TechPowerUp Releases GPU-Z v2.17.0

#1
lexluthermiester
btarunr
  • Fixed crash on startup (Windows XP)
  • Fixed crash when opening DXVA 2.0 report (Windows XP)
I find it very cool W1zzard still supporting XP for those people who still do classic gaming. Very cool indeed.
Posted on Reply
#2
EarthDog
Finally! :)

Thank you for your hard work!!!
Posted on Reply
#3
MrGenius
lexluthermiesterI find it very cool W1zzard still supporting XP for those people who still do classic gaming. Very cool indeed.
XP is still a very important OS for the competitive overclocking community too. And likely always will be. As certain benchmarks run better on XP than any other OS(and/or aren't susceptible to the timer cheats that plague Windows 8 & later OSes). Screenshots with GPU-Z open, and the Graphics Card tab visible, are also required for points on HWBOT(for any benchmarks that use a GPU anyway). And it's actually still being supported with security updates in its Embedded POSReady form(until April 9th 2019). Many people aren't aware of this however. Nor how it's possible, through a very simple registry hack, to convert any XP install(except XP Pro x64) to be recognized as the Embedded POSReady version(capable of receiving said updates). Making it completely viable for general purpose use...for a little while longer at least.

POS = Point Of Service...if you're curious. Not that other POS acronym.
Posted on Reply
#5
Fouquin
lexluthermiesterI find it very cool W1zzard still supporting XP for those people who still do classic gaming. Very cool indeed.
And benchmarking retro hardware! This is actually a really awesome touch for a lot of the retro hardware geeks since we can still use GPU-Z for validation images and such. Being able to validate and rip the older ROMs from these cards that don't really have a lot of support past XP is a pretty nice thing too.
Posted on Reply
#7
R-T-B
MrGeniusAnd it's actually still being supported with security updates in its Embedded POSReady form(until April 9th 2019).
Yep, which is really close, meaning anyone considering a new install right now for general, longer term usage should reconsider.
Posted on Reply
#9
lexluthermiester
R-T-BYep, which is really close, meaning anyone considering a new install right now for general, longer term usage should reconsider.
That presumes of course that they want to use it as a daily driver and get on the internet for extended amounts of time. I think at this point most people know better.
Posted on Reply
#10
GamerGuy
I'm putting this here since I dunno where else to put it, but secondary card sensors tab isn't working it seems. Below is a screenshot, compare the middle and right GPUZ screenshots which are the new 2.17.0 (middle) and 2.16.0 (right) of the same secondary card, note that the older version display the full suite of info. You can ignore the one on the left as that's of the primary card...
Posted on Reply
#11
Loosenut
MrGenius...snip

POS = Point Of Service...if you're curious. Not that other POS acronym.
I was thinking of Point Of Sale but I now stand corrected. Thank you :laugh:
Posted on Reply
#12
R-T-B
lexluthermiesterI think at this point most people know better.
Yeah, you would think. But you know what I've learned? That thing called "common sense" is not always really common. :laugh:
Posted on Reply
#13
W1zzard
GamerGuyI'm putting this here since I dunno where else to put it, but secondary card sensors tab isn't working it seems. Below is a screenshot, compare the middle and right GPUZ screenshots which are the new 2.17.0 (middle) and 2.16.0 (right) of the same secondary card, note that the older version display the full suite of info. You can ignore the one on the left as that's of the primary card...
When you put load on the cards (playing a game with CF support), all the readings are there?
Posted on Reply
#14
GamerGuy
W1zzardWhen you put load on the cards (playing a game with CF support), all the readings are there?
I'll get back to you on this, not at home for a day or two.
Posted on Reply
#15
GamerGuy
I'm back with bad news, my dual Gigabyte VEGA64 rig crashed on me.....and crashed hard! I'm in the process of troubleshooting it, but am getting my butt handed to me because I can resolve the issue.
Posted on Reply
Add your own comment
Dec 22nd, 2024 03:47 EST change timezone

New Forum Posts

Popular Reviews

Controversial News Posts