CPU-Z

CPU-Z reads the identification data that hardware reports about itself and presents it in a set of compact tabs. The CPU tab names the processor, its codename, package, lithography, cache sizes, instruction sets and current multiplier; the mainboard tab shows the motherboard model, chipset and BIOS version; the memory and SPD tabs describe installed modules, their part numbers, rated timings and XMP profiles. A live readout of core clocks, multiplier and core voltage makes the effect of a BIOS setting or a power plan immediately visible, which is why the tool is standard equipment for anyone tuning or troubleshooting a desktop.

How the workflow fits together

Start the program and the first tab opens on the detected processor. Moving between tabs takes no scan time, and the memory tab reports the currently active timings while the SPD tab reads each slot's programmed profiles. Validation and reporting actions capture the current state so it can be compared or shared, and a small benchmark measures the processor and memory subsystem for a rough cross-machine comparison. For overclockers the usual loop is to change one BIOS setting, boot, and read the clock and voltage readouts to see whether the change actually took effect before moving on to stability testing.

Configuration, limits and trade-offs

There is very little to configure, which is part of the appeal: the tool is a reader, not a tuner. The version bundled with some motherboard vendors shows slightly different branding, and the language can be switched in the settings. Limits are worth keeping in mind. CPU-Z reports what the firmware tells it, so a misreporting BIOS produces a misreporting tool; mobile processors may not expose voltage at all; and inside a virtual machine it shows the virtualised identity rather than the physical part. It also does not stress-test or change any setting, so it can never be a stability test on its own.

When to choose something else

Choose a different program when you need fan speeds, voltages across many rails, temperature sensors or logging to a file, which is what a full hardware monitor such as HWiNFO or Open Hardware Monitor provides. For detailed per-core stress testing and thermal validation, a dedicated stress-test utility is the right tool. On Linux the same information is available from command-line tools such as lscpu and dmidecode, so a desktop download is unnecessary there.