Updated October 18, 2026: Reorganized the guide around identification, live monitoring and useful troubleshooting evidence.
GPU-Z is a graphics-card information and monitoring utility. Use it to check which GPU the computer is using, inspect its firmware and driver information, and record sensor readings while reproducing a problem. It does not turn specification numbers into a reliable gaming benchmark.
Confirm which GPU you selected
Obtain GPU-Z from TechPowerUp’s official site. If your computer has integrated and dedicated graphics, select the relevant device in the selector before reading the tabs. On older systems, confirm whether you are examining an iGPU such as Intel Iris Plus 655 or a separate graphics card. Save a screenshot of the identification screen when asking a manufacturer for help.
| Information | How it helps |
|---|---|
| Name, GPU, Device ID and subvendor | Identify the chip and board partner. Compare the details with the exact product you bought. |
| BIOS and driver version | Record the software/firmware environment before troubleshooting. |
| Memory size, type and bus width | Describe the memory configuration; these numbers alone do not rank gaming speed. |
| Bus interface | Check the reported PCIe connection, remembering that power saving can reduce the active link at idle. |
Use Sensors to investigate a symptom
Look at GPU load, clock speeds, temperatures and any power or fan readings exposed by your device. Sensor availability varies, so an absent reading is not automatically a fault. On a supported Radeon system, the AMD GPU stress test can provide a controlled workload for comparison. Compare the same workload before and after a change, rather than comparing an idle screenshot with someone else’s gaming result.
A brief temperature spike, a low idle clock or a fan that stops at idle is not enough to diagnose a broken card. Check the model’s documented behavior and look for a repeatable relationship between the symptom and the readings.
Record a log
- Open Sensors and enable Log to file.
- Choose a location you can find again, and allow background refreshing if needed.
- Note the time, then reproduce the problem with your normal application or game.
- Stop logging and keep the log together with the driver version and a description of what happened.
NVIDIA documents GPU-Z logging as a way to collect troubleshooting evidence. A log helps support correlate events; it is not, by itself, proof that the GPU is the failed component.
Saving the video BIOS is a separate action
The save control beside BIOS Version can export a supported card’s ROM for a support request. Saving a ROM does not modify the card, and is not a reason to flash a different one. Check firmware compatibility before using NVFlash. If the export is unavailable, record the limitation instead of trying to defeat it.
For performance comparisons, use the same application, settings, resolution and test conditions. Keep frame-rate results separate from GPU-Z’s theoretical specifications.
Images from the original article
These original illustrations are retained for reference. Product examples and software screens may show older versions; use the model-specific instructions above.
