Skip to content

System insight

Read your CPU, board, and memory like a technician

CPU-Z delivers accurate, real-time hardware information in a compact interface—trusted by PC enthusiasts and support technicians for over two decades.

Windows 11Real-time clocksValidatorPortable ZIPARM64 & Android
Go to downloads Explore tabs

Why people still open CPU-Z first

Forums, game support, and motherboard Q&A often ask for a CPU-Z screenshot or validation link—it answers stepping, BIOS string, and SPD profile in one place.

CPU-Z SDK icon

SDK option

Developers can license CPU-Z detection via the System Information Kit.

HWMonitor icon

Pair with HWMonitor

For voltages and sensors, HWMonitor complements CPU-Z’s static hardware ID view.

v2.19 Windows x86 / x64

Download CPU-Z

The current classic build is version 2.19 for Windows x86/x64, with setup and ZIP packages. Custom branded builds exist for ASUS ROG, Gigabyte, MSI, ASRock, Cooler Master, and others—pick the plain English build unless you intentionally want a partner skin.

Windows — English

Setup (32/64-bit, English) ZIP portable (English)

Use your preferred software repository or search for the latest CPU-Z Windows build if you need a different version.

Independent information page.

Gamers & overclockers

CPU-Z is a staple in gaming communities. Before asking "why is my FPS low?", users are told to post a CPU-Z validation. Overclockers use it to confirm stable clocks, stepping, and memory profiles after tuning. Benchmark leaderboards often require a validation link as proof.

Buying used hardware

When buying a used CPU or motherboard, a fresh CPU-Z validation reduces fraud risk. Compare the validation’s stepping, cache, and board model with the seller’s photos. Scammers often reuse old validations—always ask for one taken the same day.

IT support & diagnostics

Support teams use CPU-Z to verify hardware before BIOS updates, RMA claims, or driver installations. The CPU tab shows microcode; the Mainboard tab shows BIOS version. Quick identification without opening the case.

What CPU-Z reports (at a glance)

CPU tab: Name, codename, package, process node, cores/threads, caches (L1–L3), instruction sets, core voltage, bus speed, multiplier, real-time clocks.
Mainboard: Manufacturer, model, chipset, southbridge, BIOS brand/version/date, graphic interface (PCIe link width/speed).
Memory: Type (DDR4/DDR5, etc.), size, channel mode (single/dual/quad), NB frequency, DRAM frequency, timings (CAS, tRCD, tRP, tRAS, tRFC, Command Rate).
SPD: Per-slot module info— manufacturer, part number, serial, JEDEC profiles, XMP/EXPO profiles, voltage, timings.

System requirements

  • OS: Windows 95 to Windows 11 (32-bit and 64-bit). ARM64 and Android builds available.
  • RAM: Minimal—program uses under 50 MB.
  • Storage: ~2 MB for the portable ZIP.
  • Permissions: Admin rights recommended for full sensor and DMI access; runs limited without.

Quick tips for beginners

  • Press F5 to save screenshots (CPU, Cache, Mainboard, Memory).
  • Press F6 to copy the current tab to clipboard.
  • Use F7 to save a validation file for upload to valid.x86.fr.
  • Right-click the CPU tab to switch which core’s clock is displayed.

CPU-Z vs other system tools

CPU-Z focuses on static hardware identification: what CPU, board, and RAM you have. It is not a benchmark, stress tester, or temperature monitor. For those tasks, pair it with tools like Cinebench, Prime95, or HWMonitor. CPU-Z’s built-in bench is useful for quick relative comparisons, but dedicated benchmark suites give more repeatable results.

CPU-Z: Identity, specs, validation, light bench.
HWMonitor: Voltages, temps, fan speeds.
MemTest86: RAM stress and error detection.

RAM compatibility checks

Before adding or replacing RAM, check the SPD tab for supported JEDEC and XMP profiles. Compare with your motherboard’s QVL (Qualified Vendor List). If the module is not listed, it may still work, but the QVL indicates tested combinations. CPU-Z’s Memory tab shows what is actually running—if it says DDR4-2133 but your kit is DDR4-3600, enable XMP in BIOS.

Validator: why it matters

A CPU-Z validation is a cryptographically signed snapshot of your hardware. It proves you own the parts and that they were detected correctly. Overclocking forums, contests, and marketplace sellers use validations to build trust. The validation URL is short (e.g. valid.x86.fr/abc123) and easy to share.

Common questions answered

Why does CPU-Z show low clock speed?
Power-saving (SpeedStep, Cool’n’Quiet) idles the CPU. Load it with a game or benchmark to see turbo.
SPD shows different speed than the box?
Enable XMP/EXPO in BIOS. JEDEC is the default; advertised speeds use extended profiles.
Can I run it without installing?
Yes. Use the ZIP version and run cpuz.exe from any folder—ideal for USB toolkits.
Is it safe? Any telemetry?
CPU-Z is widely trusted. It reads local hardware only; validation upload is optional and explicit.

20+

Years in development

Free

No paid tiers

Windows 11

Fully supported

Portable

ZIP, no install

Understanding the CPU tab

The Name field shows the marketing name; Codename is the internal project name (e.g. Raptor Lake, Zen 4). Technology reports the process node when available. Specification is the full Intel/AMD string. Stepping and Revision matter for microcode and compatibility. The Core Speed updates in real time—expect fluctuations at idle.

Dual vs quad channel

The Memory tab shows Channel # (Single, Dual, or Quad). Dual channel doubles memory bandwidth compared to single; quad again doubles that. To run dual channel, install sticks in the correct slots per your motherboard manual—usually A2+B2 for two sticks. Mismatched slots often result in single-channel operation.

BIOS update checklist

Before flashing BIOS: note the Mainboard tab’s BIOS Brand, Version, and Date. Confirm the new BIOS supports your CPU (check release notes). Some boards require sequential updates. CPU-Z helps you verify the current state before and after the flash.

Cache hierarchy explained

CPUs have multiple cache levels. L1 is per-core, smallest and fastest. L2 is typically per-core or shared between a small cluster. L3 (or LLC) is shared across all cores. CPU-Z reports sizes and, with the optional latency tool, measured latencies. Larger caches help with gaming and multi-threaded workloads; the CPU tab shows exactly what your chip has.

L1 Data
Per-core, ~32–64 KB
L1 Inst
Per-core, ~32 KB
L2
Per-core or cluster, 256 KB–1 MB
L3
Shared, 8–128+ MB

Command-line and silent mode

Run cpuz.exe -txt=C:\reports\mypc to generate a text report without opening the GUI. Use -html= for HTML output. Useful for scripted inventories or remote support. The report includes CPU, mainboard, and memory data in a single file.

Use -core=0 through -core=N-1 to display a specific core’s clock. Run multiple instances with different -core values to monitor each core separately.

PCIe link width and speed

The Mainboard tab’s Graphic Interface section shows the PCIe link between CPU and GPU: e.g. "x16 4.0" means 16 lanes at PCIe 4.0. If you see "x8" instead of "x16", the slot or CPU might only provide 8 lanes, or the card is in a secondary slot. PCIe 4.0 x8 is still ample for most GPUs; x16 is preferable for high-end cards.

Custom branded builds

Partner versions of CPU-Z exist with custom branding: ASUS ROG, Gigabyte AORUS, MSI Gaming, ASRock Phantom/Taichi, Cooler Master. Functionality is identical; only the skin and branding differ. If you prefer a neutral look, use the standard build. Custom builds are useful if you want your validation to match your board’s aesthetic for screenshots.

ASUS ROG Gigabyte AORUS MSI Gaming ASRock Phantom Cooler Master

Laptop vs desktop

Laptops often use mobile variants (e.g. Intel U/H/P series, AMD Ryzen U/HS/HX). CPU-Z correctly identifies these. Mobile chips may show lower base clocks and different TDP; turbo behavior depends on thermal headroom. The Mainboard tab will show the laptop model. Memory is typically soldered or in SO-DIMM slots—check SPD for what is installed.

OEM vs retail CPU

OEM (tray) CPUs are functionally identical to retail boxed units. CPU-Z does not distinguish them—both show the same name and stepping. The main difference is warranty: retail comes with a longer warranty. For identification and validation purposes, CPU-Z treats them the same.

Instruction sets: AVX, SSE, AVX-512

The CPU tab lists supported instruction sets: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, and sometimes AVX-512. These affect compatibility with certain software. AVX-512 is found on some Intel server and enthusiast chips; newer consumer Intel and AMD may use different subsets. Software that requires AVX will not run on CPUs without it—CPU-Z helps you verify.

Virtual machines

CPU-Z inside a VM reports the virtual CPU presented by the hypervisor. You will see the host’s architecture and often modified brand strings. Useful for confirming VM config; not suitable for validating physical hardware.

Multi-socket systems

Workstation and server boards with two or more CPUs: CPU-Z shows the first processor by default. Use the drop-down or right-click to switch between sockets. Each socket has its own memory controllers and PCIe lanes.

ARM64 and Android

ARM64 Windows builds exist for Snapdragon X Elite and similar. Android CPU-Z reports SoC, GPU, sensors, and battery. Feature sets differ from the Windows x86 version but serve the same identification purpose on mobile.

Validation submission steps

  1. Run CPU-Z and ensure all tabs load correctly.
  2. Press F7 or click the "Validate" button in the CPU tab.
  3. A validation file (e.g. cvf) is saved. Upload it to valid.x86.fr.
  4. You receive a short URL. Share that link in forums or marketplaces.
  5. Validations are permanent; the URL will always show the same snapshot.

Screenshot best practices

When posting for support: include the full CPU tab (do not crop). Show Mainboard if the issue involves BIOS or drivers. For RAM issues, include both Memory and SPD tabs. Use F5 to save BMPs or F6 to copy—paste into an image editor if you need to annotate. Avoid sharing only a partial crop; context helps diagnose.

Built-in benchmark

CPU-Z includes a simple benchmark (Bench tab): single-thread and multi-thread. Scores are relative to a reference CPU. Useful for quick before/after comparisons (e.g. before and after overclock). For serious benchmarking, use Cinebench, Geekbench, or 3DMark. The CPU-Z bench is convenient for a rough sanity check.

Glossary of terms

Stepping
Revision of the CPU die; affects microcode and compatibility.
Codename
Internal project name (e.g. Raptor Lake, Zen 4).
QVL
Qualified Vendor List—RAM modules tested by the motherboard maker.
XMP/EXPO
Extended memory profiles for beyond-JEDEC speeds.
SPD
Serial Presence Detect—data stored on the RAM module.
DMI
Desktop Management Interface—BIOS and mainboard info.
tCL / CAS
Column Address Strobe latency—first number in RAM timings.
tRCD
RAS to CAS delay—second timing value.
tRP
Row Precharge time—third timing value.
tRAS
Row Active time—fourth primary timing.
tRFC
Refresh cycle time—critical for stability at high speeds.
Microcode
CPU firmware patch; BIOS updates often include newer microcode.

Intel vs AMD: what CPU-Z shows differently

Both vendors report core counts, threads, caches, and clocks. Intel CPUs show Technology (process node, e.g. Intel 7), Bus Speed (typically 100 MHz base), and Multiplier. AMD shows Specification with the full OPN string, Core VID (voltage), and NB Frequency (Infinity Fabric). AMD codenames (Vermeer, Raphael, Phoenix) differ from Intel (Raptor Lake, Alder Lake). The Cache tab layout also varies—Intel lists L1D/L1I, L2, L3; AMD may show L1/L2/L3 plus CCX structure for Ryzen.

Intel: Bus speed × multiplier, SpeedStep, Hyper-Threading, E-cores vs P-cores on hybrid chips.
AMD: Precision Boost, SMT, CCD/CCX layout, Infinity Fabric ratio on some Zen parts.

Understanding core speed fluctuations

At idle, you may see 800 MHz, 1.2 GHz, or similar. This is normal—C-states and power management reduce clocks to save energy. Under load, clocks should rise to base or turbo. If clocks stay low under a sustained load, check thermal throttling (use HWMonitor), power limits, or Windows power plan (High Performance vs Balanced).

Memory rank: single vs dual

SPD may show "Single" or "Dual" rank. Dual-rank modules have chips on both sides (or double-density); they often clock slightly lower but can offer better performance in some workloads. Two single-rank sticks can run in dual-channel; four single-rank sticks can run dual-channel with two ranks per channel. CPU-Z SPD tab shows this per slot.

Southbridge and chipset

Older boards had a separate southbridge; modern chipsets often integrate I/O. The Mainboard tab lists both when present. Chipset determines PCIe lane count, USB ports, SATA, and M.2 support. Useful when upgrading or troubleshooting expansion cards.

Memory timings: a deeper look

The Memory tab shows primary timings (tCL, tRCD, tRP, tRAS) and often tRFC, Command Rate (1T/2T), and tREFI. Lower numbers generally mean faster response but require more voltage and better silicon. XMP/EXPO profiles define these in the SPD; the motherboard applies them when the profile is enabled. If you manually overclock RAM, CPU-Z confirms what is actually running—compare with your target profile. tRFC is especially sensitive; too low can cause random crashes. tREFI (refresh interval) is rarely shown but matters for high-frequency DDR5.

DDR4-3200
Common: 16-18-18-36 or similar
DDR5-5600
Typical: 36-36-36-76 or looser
JEDEC default
DDR4-2133, DDR5-4800 baseline
1T vs 2T
Command Rate; 1T is faster, 2T more stable

Overclocking verification workflow

  1. Before OC: run CPU-Z, save validation, note base clocks and RAM profile.
  2. Apply OC in BIOS (multiplier, voltage, XMP/EXPO).
  3. Boot, run CPU-Z—confirm Core Speed matches target, Memory shows correct frequency.
  4. Stress test with Prime95, Cinebench, or memtest.
  5. If stable: save a new validation. Keep both "before" and "after" links.
  6. For RAM OC: compare SPD profiles with active Memory tab; tighten timings gradually.

Diagnostic workflow for "something is wrong"

  1. Run CPU-Z—do all tabs load? If one hangs, note which (DMI, Sensor, SMBus can cause issues).
  2. CPU tab: does the name match what you bought? Check stepping and revision.
  3. Mainboard: BIOS version—is it ancient? Check vendor site for updates.
  4. Memory: is it single channel when you expected dual? Reseat sticks per manual.
  5. SPD: do all slots show modules if you installed them? Blank = bad slot or stick.
  6. Save validation and screenshots—share in support forums with the validation link.

Extended FAQ (20+ questions)

Why does CPU-Z show different core speeds per core?
Intel hybrid (P+E cores) and per-core turbo mean each core can run at different clocks. Right-click the CPU tab to pick which core’s speed is displayed.
SPD is empty for one slot—is the RAM dead?
Not necessarily. Try reseating the module, testing in another slot, or using one stick at a time to isolate. A dead stick often shows nothing in SPD; a bad slot may show nothing for that slot only.
What is "Uncore" or "NB Frequency"?
On Intel, Uncore includes the ring/cache clock. On AMD, NB (North Bridge) is often the Infinity Fabric. It links the memory controller to the cores and affects RAM performance.
Can I use CPU-Z on a Mac?
No native Mac version. Mac users typically use System Information or third-party tools. CPU-Z runs on Windows (x86, ARM64) and Android.
Why does my validation link show old hardware?
Validations are immutable. If you changed hardware, create a new validation. Old links always show the old snapshot.
DRAM frequency vs NB frequency—which matters?
DRAM is the actual RAM clock. NB (or UCLK on AMD) is the memory controller clock. They can be 1:1 or async depending on platform and BIOS settings.
What if CPU-Z crashes on startup?
Edit cpuz.ini and disable options like DMI, Sensor, SMBus, or UseDisplayAPI one at a time. Some hardware/firmware combinations trigger bugs.
How do I know if XMP is applied?
Memory tab shows the active frequency and timings. If it says DDR4-2133 but your kit is DDR4-3600, XMP is not applied—enable it in BIOS.
Package vs TDP vs power draw?
CPU-Z does not report power draw. TDP is a thermal design point from the vendor. Use HWMonitor or similar for real-time wattage.
Can I run CPU-Z from a USB stick?
Yes. Use the ZIP version, extract to the USB drive, run cpuz.exe. Some write-protected USBs may prevent the INI from being updated.
Why does Memory show half the DRAM frequency?
DDR = Double Data Rate. The effective frequency is 2× the base clock. CPU-Z often shows the base (e.g. 1800 MHz for DDR4-3600). Multiply by 2 for effective.
My laptop CPU shows lower clocks than spec—is it throttling?
Laptops have strict power and thermal limits. Short turbo bursts may hit spec; sustained load often drops. Check HWMonitor for power limits (PL1/PL2) and temps.
What is "Max TDP" in the CPU tab?
Thermal Design Power—the heat the cooler must dissipate at base load. Actual power can exceed TDP during turbo. "Max TDP" or "TDP Down" variants indicate configurable TDP parts.
Can CPU-Z detect a fake or relabeled CPU?
It reads CPUID. A relabeled chip would show the actual CPUID, not the label. Compare name, cores, cache, and stepping with official specs. Mismatches suggest tampering.
What does "ES" or "QS" mean in the processor name?
Engineering Sample or Qualified Sample—pre-release chips. They may have different stepping, bugs, or lack warranty. Common in grey-market builds.
Why does Graphics show "Intel UHD" but I have a discrete GPU?
CPU-Z shows integrated graphics in the CPU. Discrete GPUs appear in the Graphics tab if drivers are installed, or use GPU-Z for dedicated GPU details.

Security and privacy

CPU-Z reads hardware IDs locally. No telemetry or automatic uploads. Validation is opt-in—you explicitly choose to submit. The validation file contains hardware details; only upload if you are comfortable sharing that. Valid.x86.fr stores validations publicly; the link is permanent.

When to update CPU-Z

New CPUs often need a newer CPU-Z build for correct detection. If you have a brand-new chip and CPU-Z shows "Unknown" or wrong specs, check for the latest version. Release notes list detection fixes. For older hardware, an older build is usually fine.

Export formats: TXT and HTML

Use -txt=path or -html=path to generate reports. Useful for asset inventories, remote support, or comparing two PCs. The report includes CPU, mainboard, memory, and SPD data in a single file. Run from a script or batch file for automation.

Tool comparison: when to use what

ToolBest forCPU-Z complements
HWMonitorVoltages, temps, fan speedsCPU-Z = identity; HWMonitor = live sensors
HWiNFO64Deep sensor and hardware dataCPU-Z is lighter; HWiNFO for power users
MemTest86RAM stress testingCPU-Z shows config; MemTest86 finds errors
Thaiphoon BurnerReading/editing SPDCPU-Z reads SPD; Thaiphoon for advanced SPD
CinebenchCPU performance benchmarkCPU-Z validates hardware; Cinebench measures speed
AIDA64System info + stress + benchmarkCPU-Z is free and focused; AIDA64 is paid suite

Upgrade path: before you buy

Use CPU-Z before upgrading. CPU tab: note socket and chipset—a new CPU must match. Mainboard: check BIOS version; some boards need a BIOS update to support newer CPUs. Memory: if adding RAM, SPD shows existing modules; match type (DDR4/DDR5), speed, and ideally same vendor/part for best compatibility. SPD: see how many slots are used and what profiles exist. A validation link proves your current setup when asking for upgrade advice.

Forum and marketplace etiquette

When selling: provide a fresh validation link (same day). Buyers can verify stepping, cache, and board. When asking for support: post the full CPU tab, and Mainboard/Memory/SPD if relevant. A validation link is better than a screenshot—it cannot be faked. When overclocking: share before/after validations so others can see your settings and results.

Benchmark interpretation

The Bench tab scores are relative to a reference CPU (often an old Intel). Higher is better. Single-thread reflects per-core performance; multi-thread scales with core count. Use it for quick comparisons—e.g. before and after an overclock, or to confirm a new build performs in the right ballpark. For publication-quality benchmarks, use Cinebench R23, Geekbench, or 3DMark. CPU-Z bench is a sanity check, not a substitute.

Single-thread
Gaming, responsiveness
Multi-thread
Rendering, encoding, workloads
Reference
Scores are relative, not absolute

Platform-specific notes: laptop vs desktop vs OEM

Laptops: OEMs often lock down BIOS—no XMP, limited voltage control. CPU-Z will show JEDEC speeds even with faster RAM. Some laptops report correct specs; others cap at base clocks. Thunderbolt and discrete GPU may not appear depending on drivers. Battery vs AC can affect reported clocks.

Desktops: Full visibility. XMP/EXPO, overclocking, and all tabs typically work. DMI may be slower to load on some boards. Custom builds: ensure chipset drivers and BIOS are up to date for accurate detection.

OEM (Dell, HP, Lenovo): Prebuilts may use proprietary mainboards. CPU-Z still reads CPU and RAM correctly. BIOS version strings may be long and vendor-specific. Some OEMs hide RAM profiles—SPD may show XMP but BIOS has no option to enable it.

Common errors and quick fixes

  • "Unknown processor" — Update CPU-Z; new chips need newer builds.
  • DMI hangs or freezes — Disable DMI in cpuz.ini or run as admin.
  • Sensor tab missing — Some boards lack compatible sensors; not all builds have the tab.
  • Validation fails to upload — Check firewall, try again; server can be busy.
  • Wrong RAM capacity — Reseat sticks, check slot population per manual.
  • Clocks show 0 MHz — Rare; try different CPU-Z version or check for virtualization/VM.

Advanced SPD interpretation

Each SPD profile (JEDEC, XMP, EXPO) lists frequency, timings, and voltage. Compare "Max bandwidth" with "DRAM frequency" in the Memory tab to confirm which profile is active. "Manufacturer" and "Part number" help identify exact modules when adding RAM. "Week/year" indicates production date—useful for matching pairs. "XMP 2.0" vs "XMP 3.0" (DDR5) — newer has more profile slots and metadata.

BIOS settings that affect CPU-Z readings

Several BIOS options directly change what CPU-Z reports. XMP/EXPO/DOCP — enables memory profiles; without it, JEDEC defaults apply. Multi-Core Enhancement (MCE) — can unlock higher turbo on Intel; CPU-Z will show higher sustained clocks. C-States — disabling keeps clocks higher at idle; enabling allows deep sleep and lower idle clocks. Virtualization (VT-x/AMD-V) — does not affect CPU-Z output but required for VMs. Resizable BAR — GPU-related; not shown in CPU-Z. Power limits (PL1/PL2) — affect sustained clocks; CPU-Z shows current speed, not the limit.

Server and workstation

Xeon, EPYC, and Threadripper PRO show up in CPU-Z with full core/cache/thread counts. Multi-socket systems: each CPU appears; the app may show one at a time. ECC RAM is detected; the Memory tab may note ECC. NUMA topology is not displayed—use OS tools. Validation works the same; useful for fleet inventory.

VM and virtualization

Inside a VM, CPU-Z sees the virtual CPU presented by the hypervisor—often a generic or passthrough identifier. Core count may match the host or be limited. Do not use VM results for hardware validation; run on bare metal. Useful for checking what the guest OS sees.

ARM64 (Windows on ARM)

CPU-Z has an ARM64 build for Snapdragon and other ARM Windows devices. It reports core count, architecture, and similar info adapted for ARM. Feature set may differ from x86. Available from the main download page.

Instruction sets and extensions

The Instructions section in the CPU tab lists supported extensions: SSE, AVX, AVX2, AVX-512, AES-NI, etc. Developers use this to check if the CPU supports optimizations for their code. Gamers rarely need it. AVX-512 appears on some Intel (Ice Lake, Sapphire Rapids) and newer AMD (Zen 4); absent on others. When reporting compatibility issues, including this list can help. Benchmark and validation tools may require specific extensions.

Validation use cases in depth

  • Proof of build: Share a link after a new build so others can verify specs. No screenshots to edit.
  • Overclocking records: Submit before and after validations; the database stores them permanently. Compare with similar setups.
  • Buying used: Ask the seller for a fresh validation. Confirm stepping, cache size, and that the mainboard matches the listing.
  • Support tickets: Attach the validation link instead of typing specs. Reduces errors and speeds up troubleshooting.
  • Fleet and asset tracking: Run CPU-Z with -txt or -html and collect validations into a central DB. Automate with scripts.

Screenshot and report best practices

  • Include the tab name: Screenshot the whole window so the active tab (CPU, Memory, SPD, etc.) is visible.
  • Full resolution: Don't crop critical fields. Scaling can hide details.
  • SPD: If reporting RAM issues, capture all populated slots. Switch the slot dropdown and screenshot each.
  • Validation over screenshot: A validation link is tamper-proof and includes more data. Prefer it when possible.
  • TXT/HTML export: For long reports, use -txt=report.txt — includes all tabs in one file.

Use-case expansion: more scenarios

Content creators
Check core count and cache before video encoding; validate export/import workflows.
IT support
Quick hardware audit; compare with asset lists; verify upgrades were applied.
System integrators
Pre-ship verification; generate validation links for each build.
Second-hand buyers
Confirm CPU stepping and RAM config before purchase; avoid bait-and-switch.
Benchmarkers
Document hardware for fair comparisons; rule out misconfigured systems.
Developers
Check instruction sets for SIMD optimizations; verify target platform support.
Educators
Teach CPU architecture; show real hardware specs in class.
Warranty claims
Provide validation as proof of hardware; some vendors accept it.

Quick reference: what each tab tells you

TabKey info
CPUName, cores, threads, clocks, cache, stepping, codename, instructions
CachesL1D, L1I, L2, L3 sizes and structure per core/CCX
MainboardVendor, model, chipset, BIOS version, DMI strings
MemorySize, type, channel mode, frequency, timings, CR
SPDPer-slot: manufacturer, part number, profiles, voltage, density
GraphicsiGPU or discrete GPU name, driver (if detected)
BenchSingle/multi-thread scores vs reference CPU
AboutVersion, validation, tools, links

~2 MB

ZIP size

<50 MB

RAM usage

4+

Main tabs

F5–F9

Useful hotkeys

CPU-Z tabs explained

Each tab maps to a layer of your PC. Use this when someone asks for a specific screenshot or when you are comparing two machines.

CPU Processor

Package, code name, technology node (when reported), core/thread count, caches, and instruction sets. Clocks can idle low on modern CPUs—this is normal under power-saving; load the CPU to see nominal turbo behaviour.

MB Mainboard

Manufacturer, model, chipset, BIOS version. Essential when flashing BIOS, RMA-ing a board, or confirming whether a retail board matches the review unit you read about.

RAM Memory

Current DRAM type, size, channel mode, frequency, and timings as seen at runtime. This reflects what the system is running now—not always the XMP/EXPO label on the box if the profile is disabled.

SPD Module SPD

Per-slot module vendor, part number, nominal JEDEC and extended profiles (XMP/EXPO where present). If something looks “wrong”, compare SPD tables with the label on the stick and the motherboard QVL.

Shortcuts & command-line

CPU-Z supports parameters such as -txt=report and -html=report for silent reports, and keys like F5 (save BMP screenshots), F6 (copy tab), F7 (save validation file). Full parameter documentation is available in the program.

CPU-Z Validator & hardware proof

The CPU-Z Validator lets you submit a validation file and receive a short public URL (examples: valid.x86.fr/…). Overclockers, community contests, and buyers checking used hardware use these links because they are harder to fake than a cropped screenshot.

Before you buy used

Ask for a fresh validation link and compare CPU stepping, default RAM profile, and mainboard model with the listing photos.

Stability threads

Pair validation with stress tools; CPU-Z confirms identity, not long-term stability. Combine with mem testing when RAM is in question.

Sample links

Explore public examples: eqvml3, h416bm, qhsx1u, r23eul — same host, different rigs.

Real-world scenarios (what people actually use CPU-Z for)

The stories below are composite scenarios based on common support patterns—they illustrate how CPU-Z fits into troubleshooting and buying decisions, not individual testimonials.

Scenario

“My CPU is underclocked!”

A user sees 800–1200 MHz on the CPU tab and assumes the chip is defective. In most cases SpeedStep / Cool’n’Quiet is simply idling the cores. Loading a short benchmark or game session usually shows turbo clocks. CPU-Z is the right tool to confirm; teaching moment: always observe under load.

Scenario

RAM runs at JEDEC, not the box speed

Memory tab shows DDR4-2133 but the kit advertises 3600. Check BIOS: enable the correct XMP / EXPO / DOCP profile. CPU-Z’s SPD tab shows which profiles exist on the module; the Memory tab shows what the board actually applied. Mismatch here is one of the most frequent “easy wins” in PC tuning.

Scenario

Blue screen after opening CPU-Z

Rare, but reported when low-level buses or sensors misbehave. Edit cpuz.ini and disable DMI, Sensor, SMBus, Display, or UseDisplayAPI one by one to find the trigger.

Scenario

Wrong CPU name after BIOS update

Microcode and AGESA updates sometimes change how a CPU is reported. Compare stepping and cache sizes—not only the marketing string—with a known-good validation database entry. When in doubt, update CPU-Z to the latest build; release notes list detection fixes.

Troubleshooting & FAQ-style answers

Common issues and solutions.

CPU-Z shows a lower Vcore than I expect
Voltage readout quirks are common across boards. Use a monitoring tool to capture data when something looks inconsistent.
SPD shows a slower speed than the sticker promises
JEDEC is the safe default profile; marketing speeds often live in extended profiles requiring higher voltage. If the programmed SPD is conservative, CPU-Z will reflect that.
Installer vs portable ZIP
Since 1.51, the installer adds Start menu entries and drops the correct 32- or 64-bit binary. Portable ZIP stays handy for USB toolkits and quick support calls.
Android and ARM64 Windows
CPU-Z is available for Android and Windows ARM64, including support for Snapdragon X series laptops.

Reference index (for crawlers & readers)

Curated external destinations mentioned on this page.

Download