Marketplace purchases
Sellers promise an “i7” or “RTX laptop,” but the CPU tab shows the exact SKU, stepping, and core layout. Pair it with Memory/SPD when the listing mentions RAM speed or XMP.
Independent
Windows
CPU-Z Know your CPU, board & RAM before you open the case
CPU-Z freeware from the official developer: hardware IDs in clear tabs. This guide covers what each area means, real-world use, fixes when readings look wrong, and safe download links.
Live gallery
cpu-z.exe — preview
CPU-Z screenshot (CPU)
Coverage
CPU, caches, board, DRAM, SPD, graphics
Outputs
TXT/HTML reports, validation snapshots
Context
Idle vs load, AC vs battery, BIOS profiles
Audience
Buyers, builders, tech support, overclockers
Why this home page exists
CPU-Z is often the fastest way to settle arguments about “what chip is this,” whether XMP is active, or which BIOS string a board is really running. Forums still ask for the same screenshots because they compress a lot of identifiers into one place—if you know how to read them.
This guide is written for people who do not want to guess. You will see how each tab maps to real decisions: buying a used PC, planning a RAM upgrade, filing an RMA, tuning an overclock, or explaining why a laptop’s clocks look low on battery.
What you will take away
- •Which fields matter on the CPU tab when proving model, stepping, and live clocks.
- •How Memory differs from SPD when diagnosing “rated speed vs running speed.”
- •Why Mainboard strings are paired with vendor support pages during BIOS updates.
- •When a validation link is better than a lone screenshot for timestamped proof.
- •Practical triage if readings look “wrong” under power limits or mis-read sensors.
- •Safe habits around downloads, signatures, and avoiding repackaged installers.
Scenarios people actually use CPU-Z for
RAM upgrades
SPD reveals ranks, XMP/EXPO tables, and JEDEC bins—critical before you buy a second kit. Memory shows what the firmware actually selected after POST.
Support & RMA
Agents want unambiguous model strings. A TXT report or a tight set of tab screenshots reduces round-trips and avoids blurry photos of silkscreen labels.
Reading flow (quick)
- CPU tab first — confirm the processor identity and whether core speeds respond when you apply light load.
- Mainboard next — capture manufacturer, model, chipset, and BIOS version before you discuss firmware.
- Memory + SPD — separate “running now” from “what the modules advertise,” especially with mixed kits.
- Graphics if needed — useful when iGPU vs discrete naming is confusing on laptops.
- Validator optional — when you need a shareable snapshot others can audit later.
Before you trust a single number
Clocks and voltages move with power policy, background tasks, and firmware limits. A reading taken two seconds after opening the app is not the same as a reading after a short stress test—or on AC vs battery.
- Note laptop power source and Windows power mode.
- Pair CPU-Z with a temperature tool if you are diagnosing throttling.
- Check whether an overclock, undervolt, or eco profile is enabled in BIOS or vendor software.
Reporter, not a stress lab
CPU-Z answers “what is wired in and what is the firmware choosing right now.” It does not replace a full benchmark suite, a memtest pass, or a long thermal log. Treat it as the first layer of evidence—fast, lightweight, and easy to share.
Good for
IDs, clocks at a glance, SPD tables, board strings
Pair with
Temps, stress tests, MemTest86, vendor utilities
Weak alone
Stability proof, gaming FPS, storage health
Myths vs reality
- “If CPU-Z says DDR4-2133, my RAM is fake.”
- Often the board simply has not applied XMP/EXPO, or mixed kits negotiated a safe JEDEC speed. SPD still lists what the module can advertise.
- “Low GHz in CPU-Z means I was scammed.”
- Idle power-saving is normal. Confirm under brief load, on AC for laptops, and with sensible background CPU use.
- “One screenshot is enough for every dispute.”
- Disputes about RAM, BIOS, or thermals usually need context: which tab, when it was captured, and what load state you describe.
Mini glossary (home edition)
- CPUID — instruction families the CPU exposes; CPU-Z maps them into readable fields.
- Stepping / revision — silicon or stepping identifiers used when matching CPU support lists.
- Package — physical socket or package type (AM5, LGA1700, etc.).
- Core speed — live reported frequency; moves with load and power limits.
- Multiplier / bus — how the reported clock relates to reference clocks on many platforms.
- Channels — single vs dual (or wider) memory wiring as seen by the memory controller.
- JEDEC — standard SPD speed tables every module should expose.
- XMP / EXPO — vendor overclocking profiles stored in SPD (board must enable them).
- SPD slot — per-DIMM data; empty slots simply show no module.
- Validation — packaged snapshot you can link to; not a substitute for raw tab exports when debugging.
Tabs at a glance
CPU & Caches
Model, cores, caches, instruction sets, and live clocks—start here for “which CPU is this?”
Mainboard
Vendor strings, model, chipset, BIOS—pair with the board’s download page before flashing.
Memory
What the system runs now: type, size, mode, frequency, timings.
SPD
Per-stick EEPROM tables—useful before buying another kit or arguing about XMP.
Graphics
What the driver exposes for the GPU block—handy on hybrid graphics laptops.
Bench
A simple throughput check on builds that still ship it—not a replacement for real benchmarks.
About
Build version and validation tools entry point—confirm you are on the binary you think you launched.
Listing red flags
When someone refuses CPU-Z screenshots but offers a blurry Task Manager crop, treat it as a signal to slow down. These patterns are common in rushed marketplace deals.
- CPU tab shows a different stepping than the advertised “new sealed” SKU.
- Memory runs at JEDEC while the listing shouts “3600 XMP ready.”
- BIOS string is years behind the CPU launch window without explanation.
- SPD missing for a slot that should be populated—physical check still matters.
Portable reports (command line)
Many builds support dumping a text report for tickets. Exact switches vary by version—verify in the build you run—but the pattern looks like:
cpuz.exe -txt=reportAttach the generated file to support email instead of six separate screenshots when an agent requests “full details.”
Laptops & hybrids
Dynamic power limits and “silent” OEM modes can cap turbo harder than desktops. Capture CPU-Z twice: on battery vs AC, and after switching Windows power modes.
Windows on Arm
Arm64 builds exist for some Snapdragon-class machines; tab coverage can differ from classic x64. Treat missing fields as a platform quirk until you confirm with release notes.
Labs & IT
Standardize a screenshot set per ticket type (CPU+Mainboard for BIOS cases, Memory+SPD for RAM cases) so your team compares apples to apples.
Common reading mistakes
- Base vs turbo: The “Core Speed” field shows live frequency, not a fixed “rated” value. At idle it often sits below base clock; under load it should move toward turbo.
- SPD = capability, Memory = reality: SPD lists what the stick advertises; Memory shows what the controller is running. Mixing these causes “why is XMP not applied?” confusion.
- One snapshot is universal: Clock disputes often need two captures—idle vs load—plus power and BIOS context.
Where CPU-Z gets its data
The app reads from CPUID instructions (CPU, caches, instruction sets), SMBus/SPD (module EEPROMs where allowed), PCI config space (graphics, sometimes board), and DMI tables (mainboard, BIOS). Some probes can fail or be disabled—hence the cpuz.ini toggles for DMI, Sensor, SMBus, Display.
Sensor data (voltages, temps) comes from Super I/O or similar when enabled; routing differs by board, so misreads are possible—use HWMonitor or vendor tools to cross-check.
Screenshot checklist
Before sharing, capture at least:
- CPU tab (Specification, Core Speed, Package)
- Mainboard tab if BIOS/board is relevant
- Memory tab when RAM speed or timings matter
- SPD for the populated slot(s) when diagnosing kits
When to capture
- Clock questions: Idle first, then after a short stress or load spike.
- RAM upgrades: Before and after BIOS changes or kit swaps.
- RMA / support: Fresh boot, clean background; note BIOS version.
Quick answers
- Safe to use? Yes—from official sources; avoid repackaged installers. FAQ
- Replace benchmarks? No—it reports IDs and live values, not sustained scores. FAQ
- Crashes on start? Disable probes in
cpuz.inione by one. Fix issues
Keyboard & UI tips
- F7 — save validation file in the working directory (check the About tab or docs for your build).
- Right-click CPU tab — on supported builds, pick which core to display; useful for per-core boost or undervolt tuning.
- Command line —
-txt=reportdumps a text report;-html=reportfor HTML (exact flags vary by version).
Export formats
- TXT / HTML
- Full dump for tickets or logs; attach to email instead of multiple screenshots.
- Validation (.cvf)
- Upload to valid.x86.fr for a shareable link; good for contests, listings, or timestamped proof.
- Screenshots
- Quick for forums; pair with context (load state, power mode) when clocks or RAM are in question.
Portable vs installer
ZIP portable
Extract and run—no install, no registry. Ideal for USB sticks, lab images, or quick checks on multiple machines without leaving traces.
Installer
Adds shortcuts, may integrate with validation; easier for daily use. Both builds read the same hardware; choose based on workflow.
CPU-Z vs other tools
| Tool | Focus |
|---|---|
| CPU-Z | IDs, clocks, SPD, board strings, validation |
| HWMonitor | Voltages, temps, fan speeds—pair when sensors disagree |
| Task Manager | Quick clock view; no SPD, no board, limited per-core detail |
| MemTest86 | RAM stability; run after CPU-Z confirms SPD and XMP setup |
First-run checklist
- Confirm you launched the correct build (check About tab for version).
- Click through CPU, Caches, Mainboard, Memory, SPD—note any blank or “N/A” fields (some are platform-dependent).
- If on laptop, plug in AC and compare Core Speed at idle vs after opening a few browser tabs or Task Manager.
- Capture CPU + Mainboard at minimum; add Memory and SPD when RAM is relevant.
- Optional: save a TXT report via command line for future reference or tickets.
Pre-purchase (used PC)
- Ask for CPU-Z CPU + Mainboard + Memory tabs before paying.
- Verify CPU Specification matches listing (e.g. “i7” is vague—exact SKU matters).
- Check BIOS string against board support page for CPU compatibility.
- SPD confirms rank config and XMP presence for each stick.
- If seller refuses screenshots, treat as a red flag.
Post-upgrade (RAM / CPU)
- Capture CPU-Z before and after BIOS or hardware changes.
- After RAM swap: Memory tab for running speed, SPD for new stick details.
- After CPU swap: CPU tab for new model, Mainboard for BIOS revision.
- Run MemTest86 or stress test before assuming stability.
Before BIOS flash
- Mainboard tab: exact model and current BIOS version.
- CPU tab: confirm stepping if the update targets a specific stepping.
- Check vendor support page for “supported since” notes.
- Keep a screenshot in case you need to revert or RMA.
Validation workflow
- Capture the tabs you want in the snapshot (CPU, Mainboard, Memory, Bench if used).
- Press F7 or use validation from the interface; save the .cvf file.
- Upload to valid.x86.fr via the in-app flow or site.
- Share the resulting URL for contests, listings, or proof.
Sensor disagreements
When CPU-Z shows different clocks or voltages than HWMonitor, Core Temp, or vendor software: routing differs by board and Super I/O. CPU-Z reads what its probes expose; other tools may use different paths. Cross-check with a second tool and note which one matches BIOS or vendor documentation. For voltage disputes, HWMonitor or vendor utilities are often preferred.
Desktop vs laptop
- Laptops: Power limits, OEM “quiet” modes, and battery policies cap turbo more aggressively. Core Speed often sits lower at idle; compare AC vs battery.
- Desktops: Less constrained; clocks usually respond faster to load. Still check power plan and BIOS settings.
- Both: SPD and Memory tabs work the same; Mainboard strings help with BIOS updates regardless of form factor.
OEM & tray identifiers
CPU-Z shows the chip’s Specification and stepping; it does not label “OEM” vs “retail” directly. Some OEM chips have different stepping or branding; compare against Intel Ark or AMD product pages. Package type and socket are reliable; marketing names can differ between tray and boxed SKUs.
For board RMA, model and revision strings from Mainboard are what vendors expect—OEM vs retail is less relevant there.
Troubleshooting decision tree
- Clocks “too low” → Check power source (AC/battery), Windows power plan, BIOS power limits. Put under load and re-check. See Tips.
- RAM below XMP → Enable XMP/EXPO in BIOS; check board QVL and mixed-kit limits. See Reading specs.
- App freezes / BSOD → Edit
cpuz.ini, disable DMI/Sensor/SMBus/Display one by one. See Fix issues. - Voltage looks wrong → Cross-check with HWMonitor; sensor routing varies. Report via bug form with both tools’ outputs if needed.
Hardware requirements
Minimal: Windows x64, ~50 MB disk. Runs on almost any PC; ARM64 builds exist for supported Windows-on-Arm devices.
Languages
Multi-language builds available; choose the installer or ZIP that matches your locale from the official download page.
Updates
Check the official site for new versions; changelog lists CPU support, DDR5/DIMM updates, and platform fixes.
Still stuck after the basics?
Clock puzzles
See Tips for real-world load patterns, then Fix issues if numbers refuse to move.
RAM mysteries
Jump to Reading specs for Memory vs SPD, then cross-check BIOS screenshots if possible.
Crashes on launch
The Fix issues section walks through disabling probes in cpuz.ini one group at a time.
Explore the rest of this guide
Each section below goes deeper with different examples: tab-by-tab explanations, troubleshooting patterns, FAQs, and companion tools when sensors disagree. Use the gallery above as a visual anchor while you read.
What CPU-Z actually does
CPU-Z does not benchmark your whole PC in the way Cinebench or 3DMark do. It is a hardware reporter: it queries CPUID instructions, SMBus/SPD where allowed, and PCI information to show what is installed and how it is running right now. The current Windows build is widely used on Windows 11 and remains a standard reference when forum users ask “screenshot your CPU-Z CPU and Memory tabs.”
Because readings can be affected by power limits, background load, and BIOS settings, CPU-Z works best alongside a bit of context: note whether you are on battery (laptops), whether Eco/Quiet modes are on, and whether any overclock or XMP/EXPO profile is enabled.
This site is not affiliated with the original developer. Prefer official sources for binaries and release notes.
What you can read in each area
The following matches how CPU-Z presents data on a typical desktop. Exact fields vary by CPU generation and vendor.
Processor
Name, code name, socket, process node, core/thread count, core speeds, bus and multiplier, instruction sets, and cache hierarchy summary—ideal for proving you received the chip you ordered.
Mainboard
Manufacturer, model, chipset, BIOS version, PCIe link info where exposed—useful when a BIOS update is required for a new CPU or memory QVL issues appear.
Memory & SPD
Current DRAM type, size, channel mode, frequency, and timings. The SPD tab lists JEDEC and XMP/EXPO profiles per module—critical when mixing kits or tuning voltage.
Graphics
GPU name, vendor, process, clocks, and memory type where the driver exposes them—handy for iGPU vs discrete confusion on laptops.
Live clocks
Per-core frequency updates help you see whether Turbo is engaging. Compare idle vs load with a quick stress test (and watch thermals with a monitor tool).
Validator
Submit a validation to the online validation database for a shareable link—often used in overclocking contests and marketplace listings.
Reading specs
Use this section when someone asks for “CPU-Z screenshots” and you are not sure which tab matters.
CPU tab
Focus on Specification (marketing name), Code Name (silicon family), and Package (socket). The Core Speed field moves with load—if it looks “too low,” open a second window or use Task Manager sorted by CPU while you run a short stress test. On laptops, plug in AC power; many firmware policies cap turbo on battery.
Right-clicking in the CPU page (on supported versions) can let you pick which core to display—useful when diagnosing uneven core boosting after a bad undervolt or thermal paste application.
Memory vs SPD
Memory shows what the system is running now (channels, frequency, timings). SPD shows what the module claims in its EEPROM—including multiple JEDEC bins and XMP/EXPO profiles.
If the running frequency is below the XMP you expected, check BIOS: profile enabled? Board QVL? Mixed kits often fall back to the safest common JEDEC speed. CPU-Z’s FAQ explains cases where theoretical bandwidth from SPD timing fields can read lower than the label speed—SPD programming and voltage-dependent profiles are common reasons.
Mainboard tab
Pair this with your board’s support page: BIOS string mismatch often means you are one revision behind for a new CPU stepping. When RMA’ing a board, vendors frequently want model and revision strings exactly as reported.
Reading specs: Validator
The validation service valid.x86.fr lets users upload validations to get a permanent page showing CPU, motherboard, RAM, and scores where applicable. That is why you see long lists of example links in enthusiast threads: each URL is a frozen snapshot others can audit.
For search engines, descriptive pages that explain how to read a validation (and what cheating or swapped screenshots look like) tend to earn longer visits—signals that help visibility in Google, Bing, and Yandex when paired with clean structure and unique copy.
Checklist before you share a validation
- Close background CPU hogs so clocks in the screenshot represent a fair idle or load state you describe.
- Capture both Memory and SPD if the question is about RAM speed or timings.
- Note BIOS version from the Mainboard tab when discussing stability after an update.
- If voltage looks wrong, cross-check with HWMonitor and consider filing a structured report via the developer's bug form.
Tips
Real situations where CPU-Z saves time—practical notes from real builders and buyers.
Used PC from a marketplace
Ask the seller for CPU-Z CPU + Mainboard + Memory tabs, or run it live on pickup. Mismatched CPU stepping vs listing, or a BIOS that does not match the board revision, has saved many buyers from “i7 laptop” listings that were actually a renamed low-power SKU.
RAM upgrade planning
SPD shows whether you already have 1Rx8 or 2Rx8 sticks, rated speed bins, and if XMP is present. That reduces “bought 3200 but runs 2133” surprises after you discover the second kit only had JEDEC tables the board picked by default.
Warranty and RMA threads
Support agents often want unambiguous model strings. A TXT report (cpuz.exe -txt=report per official documentation) attaches cleanly to tickets compared to blurry photos of CPU laser marking.
Overclock sanity check
After tuning, validators document the run for peers. Combine with temperature logs from Core Temp or HWMonitor so clock screenshots are not misread as stable if the chip was thermal throttling.
Fix issues
Summarized from the developer's public FAQ (always verify on the official page). These are starting points, not guarantees.
“My CPU is below its rated GHz”
Idle power-saving (EIST/SpeedStep, C-states, AMD Cool’n’Quiet) lowers clocks. Put the machine under load and watch the core speed climb. Laptops: check power mode and AC adapter wattage.
“Vcore looks wrong”
The developer suggests using HWMonitor, saving monitoring data, and sending it through their bug report form—sensor routing differs by board and Super I/O chip.
Freeze, GPF, or blue screen when opening CPU-Z
Edit cpuz.ini: set DMI, Sensor, SMBus, Display, and UseDisplayAPI to 0, then re-enable one at a time to find the trigger. Report which flag causes the crash to the developer.
RAM label says DDR4-3200 but CPU-Z shows lower
Enable the profile in BIOS (XMP/EXPO/D.O.C.P.). If still low, inspect SPD: mixed kits, motherboard limits, or conservative JEDEC tables may explain it. MemTest86 (memtest.org) helps confirm stability after changes.
Frequently asked questions
Is CPU-Z safe?
Download only from the official source or listed mirrors. The installer build is digitally signed when obtained from official sources. Avoid repackaged “bundled” installers from unrelated download portals.
Does CPU-Z replace benchmarking?
No. It may include a simple bench tab on some builds, but serious performance testing still uses dedicated benchmarks and thermal logging under controlled conditions.
Why do forums insist on CPU-Z screenshots?
They compress many identifiers into one view, reducing back-and-forth. Pair screenshots with a validation link when you want a third-party timestamped record.
Where do I report bugs?
Use the official bug report form with the files they request. Check social channels for the developer's support channels.
Alternatives
If CPU-Z answers “what is installed,” these tools help with “how hot,” “how stable,” and “what else to check.”
HWMonitor
Voltages, temperatures, and fan speeds—pairs with CPU-Z when sensors disagree.
HWMonitor Pro
Extended monitoring features for enthusiasts and small labs.
PRO / SDK
Commercial kits for system information and monitoring integration.
SIW & similar auditors
Third-party system inventories—compare readings when something looks off.
DriversCloud
Online hardware reports and driver context—useful after board swaps.
Download CPU-Z (official)
Links below point to the official current English builds. Version numbers change over time—if a link 404s, open the official page and grab the latest EXE or ZIP.
Release highlights (2.19)
- Support and fixes for recent AMD Ryzen AI and related mobile parts; preliminary Intel platform support as listed on the official CPU-Z site.
- CQDIMM (4-ranks CUDIMM) memory support updates.
- Security fix for DLL hijacking (acknowledged contributor on official changelog).
Android and ARM64 Windows builds are available—check the official release notes for the latest builds and news.