• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

TechPowerUp GPU-Z 0.6.8 Released

btarunr

Editor & Senior Moderator
Staff member
Joined
Oct 9, 2007
Messages
47,690 (7.42/day)
Location
Dublin, Ireland
System Name RBMK-1000
Processor AMD Ryzen 7 5700G
Motherboard Gigabyte B550 AORUS Elite V2
Cooling DeepCool Gammax L240 V2
Memory 2x 16GB DDR4-3200
Video Card(s) Galax RTX 4070 Ti EX
Storage Samsung 990 1TB
Display(s) BenQ 1440p 60 Hz 27-inch
Case Corsair Carbide 100R
Audio Device(s) ASUS SupremeFX S1220A
Power Supply Cooler Master MWE Gold 650W
Mouse ASUS ROG Strix Impact
Keyboard Gamdias Hermes E2
Software Windows 11 Pro
TechPowerUp announced version 0.6.8 of GPU-Z, the popular graphics subsystem information, monitoring, and diagnostic utility, which gives you detailed information about the installed graphics hardware, and lets you monitor key specifications in real-time, such as clock speeds, temperatures, voltages, and video memory usage. Version 0.6.8 introduces support for new GPUs, namely NVIDIA's GeForce GTX Titan, GeForce 505 (GT216), GT 640M, GTX 675MX, Quadro K2000, and K3000; AMD's Radeon HD 7480D, FirePro W8000, V8700, fake HD 6850 (based on HD 6450). GPU load monitoring method on AMD GPUs is improved, and should be more accurate. Several minor bugs were patched.



DOWNLOAD: TechPowerUp GPU-Z 0.6.8, TechPowerUp GPU-Z 0.6.8 ASUS ROG Themed

The change-log follows.
  • Added support for GeForce GTX Titan, GeForce 505 (GT216), GT 640M, GTX 675MX, Quadro K2000, K3000
  • Fixed GT 620 GPU name
  • Added support for AMD Radeon HD 7480D, FirePro W8000, V8700, fake HD 6850 (based on HD 6450)
  • Fixed release date for Trinity HD 7000G
  • Added detection for Intel GMA
  • Improved GPU load monitoring on AMD cards
  • Fixed two application crashes related to Intel IGPUs

View at TechPowerUp Main Site
 
fake HD 6850 (based on HD 6450)

- Chinese company buys HD 6450
- modifies BIOS so that the device ID is one that is currently unused and not supported by the official driver
- bundles special driver that shows the card as HD 6850
- Profit!
 
- Chinese company buys HD 6450
- modifies BIOS so that the device ID is one that is currently unused and not supported by the official driver
- bundles special driver that shows the card as HD 6850
- Profit!

I must express my sincere admiration for your dedication to GPU-Z by even including cards like these! :)

Edit:
By the way, will the memory usage readout ever be changed for Windows 8 in any future version of GPU-Z? The dedicated memory useage never goes above 0 as far as I know, so I guess it has become a bit redundant?
 
Last edited:
I must express my admiration for your dedication to GPU-Z by even including cards like these :laugh:

The idea is that the unlucky buyer can use GPU-Z to get real info on the card and possibly get his $$ back
 
very nice works cheers :)
 
by chance do you have a Gpu-Z screenshot of this "fake 6850" ?
 
The idea is that the unlucky buyer can use GPU-Z to get real info on the card and possibly get his $$ back

Yep, I can certainly understand that.

However, I would imagine that of all the people using GPU-Z, only a very small fraction would ever need it for that exact purpose, so I found it admirable that you still choose included it your piece of software. :)
 
Can we have some more info regarding those fake 6850 please???
 
Can we have some more info regarding those fake 6850 please???

I got no further info for you. I saw a submission that had an unknown GPU (because GPU-Z didn't know about the device Id), took a look at the data, determined it's fake. Added device id. Gotta wait for a submisison using working GPU-Z
 
W1zzard, Thank You for all you do.

You and your labours are appreciated.
 
I can confirm that the GPU load measurement problem on Tahiti boards has been fixed. Thanks W1zzard! :lovetpu:
 
Not exactly a 0.6.8 observation (but a 0.6.7 one)... but why did it take so long to implement a Texture Mapping Unit readout?
 
Not exactly a 0.6.8 observation (but a 0.6.7 one)... but why did it take so long to implement a Texture Mapping Unit readout?

We didn't have enough data. TMU count isn't something the driver will report.
 
Back
Top