CPU
Processor name, code name, package, core/thread count, cache sizes, and instruction sets. Useful to confirm you received the CPU you paid for and to see stepping/revision when two retail boxes look identical.
CPU-Z: see your CPU, motherboard, and RAM without opening the PC
CPU-Z is free Windows software from CPUID that pulls model names, memory timings, and CPU details from the machine. Here we walk through the tabs, spell out what the numbers usually mean, cover typical forum-style problems, and link to direct Windows and Android downloads below.
This site is not affiliated with the original developer. Windows and Android builds are linked below as direct downloads.
Why people still open CPU-Z
Upgrading RAM, chasing a crash, or selling a PC usually starts with one question: what is actually installed? CPU-Z reads identifiers from the hardware—module part numbers, BIOS version, CPU stepping—so you are not guessing from worn stickers or vague retail names.
It shows up constantly for RAM shopping (SPD tells you what is in each slot), board and BIOS checks before a flash, and CPU verification when two boxes say the same model but silicon can differ. Support threads and shops often ask for screenshots because one window covers the basics.
- Portable copy: the ZIP build is easy to keep on a USB stick for a quick look at someone else’s PC.
- Validation links: sites like valid.x86.fr host a frozen CPU-Z report others can open without re-uploading screenshots.
- Same vendor, more sensors: CPUID’s HWMonitor adds temps and voltages if you need that next to a CPU-Z grab.
Tabs and what they are for
Each tab pulls from a different part of the system. Knowing which is which saves confusion in help posts—for example, box-speed marketing versus the clock the CPU is holding at that second.
Mainboard
Manufacturer, model, chipset, BIOS version/date. Critical before flashing BIOS or when a driver site lists ten boards with similar names.
Memory
DRAM type (DDR4/DDR5), total size, current frequency and timings as reported by the memory controller. Helpful to verify XMP/EXPO is actually applied.
SPD
Serial presence detect: per-slot module manufacturer, part number, nominal speed tables, and XMP/AMP profiles. If dual-channel is wrong, SPD is where you notice a stick missing or seated badly.
Graphics
GPU name, process, clocks, memory type/size where available. Handy on laptops with hybrid graphics to see which device is primary in software.
Bench
A simple built-in benchmark on supported versions. Treat it as a coarse health check, not a substitute for dedicated stress tests. Compare results only on similar power profiles and drivers.
Windows on ARM and newer SoCs
There is an ARM64 build for Windows; coverage for new SoCs lands in release notes. On an ARM laptop, grab the ARM build from CPUID rather than assuming the usual 64-bit PC installer is the right one.
Reading CPU-Z without getting lost
A screenshot helps only if the right fields are visible. Use the points below when you post for help or check a machine you might buy.
Clocks and “why is my GHz jumping?”
Modern CPUs scale frequency every millisecond. A single snapshot in CPU-Z may show a low idle clock even though the chip boosts under load. For stability testing, pair identification in CPU-Z with a sustained load tool and a temperature monitor such as Core Temp or HWMonitor.
Memory: effective vs data rate
DDR memory is often discussed in “MT/s” while some labels show half that value as a frequency. When upgrading, match DDR generation, module type (UDIMM/SODIMM), and ideally speed bins. SPD shows what the modules are rated for; the Memory tab shows what the system is running right now.
Motherboard strings vs retail names
The board model in software is what the firmware advertises. If it looks unfamiliar, search the exact string plus “BIOS” to land on the right support page. Keep a note of the BIOS date before you update—if something goes wrong, support will ask for it.
When validation links help
Sites like valid.x86.fr let you publish a CPU-Z validation ID so others can inspect the same structured data without re-uploading images. That reduces arguments about “Photoshopped tabs” in sales threads.
Validation IDs
A validation link is a snapshot others can open: CPU, board, memory, sometimes bench scores. For a used kit or expensive RAM, a recent validation plus matching SPD part numbers in your own photos is stronger than a single cropped tab.
Validators such as valid.x86.fr are third-party sites; use them as references, not guarantees.
Typical uses
These are common reasons people open the app; your setup may differ.
“I want to add RAM—will any DDR5 stick work?”
Open the SPD tab and write down module part numbers, ranks, and XMP profiles. Check whether both channels populate. Then search for your motherboard’s qualified vendor list (QVL). CPU-Z does not replace QVL research, but it stops you from guessing whether you currently run 1×16 GB or 2×8 GB.
“Buyer wants proof before PayPal”
Take CPU-Z screenshots of CPU, Mainboard, Memory, and SPD. Better: add a validation link. Pair with a short video showing the machine booting if the sale is remote—scammers rarely match every string across tabs.
“Blue screens after ‘auto’ overclock”
Capture CPU-Z before and after clearing CMOS. If Memory tab timings change dramatically, your instability may be memory training rather than CPU voltage. Document BIOS version from the Mainboard tab when asking for help—answers depend on AGESA or Intel ME context.
“Is this laptop really the GPU model advertised?”
The Graphics tab lists the active adapter strings. On hybrid systems, power modes can switch GPUs; note whether you were on battery and which driver branch is installed. For persistent doubts, cross-check with the device vendor’s spec sheet.
More situations
Extra cases that come up often—handy as a checklist when you are on the phone with a friend or filing a ticket.
RMA prep: “prove the CPU stepping”
Retailers sometimes want evidence that the installed processor matches the box. Capture the CPU tab with stepping, revision, and cache blocks visible. Add a photo of the retail label and keep BIOS defaults—odd overclocks can invalidate warranty conversations even when the hardware is fine.
Warranty RAM swap without opening the case twice
Before you remove modules, export your mental model: SPD part numbers per slot, ranks, and nominal speed tables. When the replacement kit arrives, re-run CPU-Z and confirm the SPD strings changed—not just the Memory tab frequency, which can look similar across kits.
“My board supports DDR5-6000 but CPU-Z shows less”
Marketing speeds are ceiling claims under specific BIOS versions and CPU memory controllers. CPU-Z reflects what the firmware applied after training. If EXPO/XMP failed silently, you may be on JEDEC defaults. Document Mainboard BIOS date before tuning—older AGESA or Intel microcode can cap memory training.
Hybrid graphics: which GPU am I actually using?
Note OS power mode, whether the laptop is on AC, and whether an external monitor is routed through iGPU or dGPU. Take two screenshots minutes apart if the system switches adapters dynamically. Pair with the vendor’s MUX switch documentation if applicable.
Fresh Windows install: “did the shop swap my CPU?”
Compare CPU name, core count, and cache sizes against your receipt. If the OS was cloned from another image, also check Mainboard strings—unexpected board names can indicate a mainboard swap rather than a CPU swap.
Linux dual-boot confusion
Firmware fast boot and OS-specific drivers can change how aggressively the CPU idles. For apples-to-apples comparisons, boot Windows, set a known power plan, wait two minutes, then capture CPU-Z under a light repeatable load (not a random single screenshot at desktop).
Office fleet audit (no admin drama)
Standardize a portable ZIP workflow, capture CPU + Mainboard + Memory in one pass, and store files by asset tag. IT teams value consistent filenames more than pretty screenshots—use ASSET123_cpu_main_mem.png style naming.
Streamer PC: “VRAM string looks odd after driver update”
Driver branches sometimes rename reporting strings even when silicon is unchanged. Capture CPU-Z before and after the update alongside the driver version from the vendor installer. That prevents false panic when only the label moved.
Mini-PC / NUC thermal throttling checks
CPU-Z alone will not show sustained power limits; pair it with a temperature tool. Still, CPU-Z helps document base configuration before you re-paste or adjust fan curves—especially when the seller claims “like new.”
e-waste donation: sanitize + prove specs
Charities often publish “minimum specs” lists. CPU-Z gives defensible evidence of CPU generation and RAM size after you wipe storage. Avoid sharing serial numbers publicly—crop screenshots if you post them online.
Step-by-step workflows
Copy or adapt these so whoever is helping you gets the same facts in one pass.
A. RAM upgrade decision in 10 minutes
- Open Memory tab: note DDR generation, module size, channel mode.
- Open SPD tab: write part numbers for each populated slot.
- Check whether XMP/EXPO profiles exist and whether they are active in practice.
- Search your motherboard model + “memory QVL” + BIOS version.
- Only then shortlist kits—CPU-Z prevents buying the wrong generation or form factor.
B. “Post my specs” forum package
- CPU tab: full window, no cropping of stepping/revision if visible.
- Mainboard tab: manufacturer, model, BIOS version/date.
- Memory + SPD: show both what you run now and what modules claim.
- Add context: desktop vs laptop, power plan, and whether you tested under load.
- Optional: validation link if the community expects proof-heavy threads.
C. BIOS update safety snapshot
- Record Mainboard strings and current BIOS date.
- Capture Memory timings actually applied (not just the kit box).
- Store screenshots offline—if flash fails, you still have baseline identifiers.
- After update, re-check Mainboard BIOS date and memory training results.
D. Used PC purchase remote inspection
- Ask for live video showing Task Manager + CPU-Z opening from a cold boot.
- Request SPD part numbers, not just total GB.
- Compare CPU name and core count to the listing title.
- If the seller refuses tab screenshots, treat it as a red flag—not proof of scam, but proof of friction.
E. Bench tab: a disciplined run
- Close background updaters and browser heavy tabs.
- Set a repeatable power plan and wait for idle settle.
- Run Bench once, note thermals elsewhere, do not chase scores by killing security software.
- Compare only against similar cooling, drivers, and power limits.
F. Android vs Windows: compare fairly
- Accept that mobile SoCs report through different paths—treat as hints.
- Match scenarios: same app versions where possible, same thermal state.
- Use PC CPU-Z for upgrade planning; use phone readings for quick identification on the go.
Glossary
Short meanings for labels you will see in the app. Exact names vary by board and CPU.
- Stepping / revision
- Silicon iteration markers; two CPUs with the same marketing name can differ subtly.
- Package
- Physical CPU socket family; critical when buying coolers or diagnosing board compatibility.
- TDP (when shown)
- A reference power class, not a literal constant power draw on modern chips.
- Instruction sets
- CPU capabilities such as AVX tiers; relevant for some creative and scientific apps.
- L1 / L2 / L3 cache
- On-chip memory hierarchies; useful when comparing CPUs within the same generation.
- Core voltage (when readable)
- May be reported indirectly; treat as informational unless you know your board’s sensors.
- Northbridge report (legacy context)
- On older systems, memory controller placement differed; modern CPUs often integrate more functions.
- BIOS vs UEFI
- Firmware interface generation; CPU-Z shows a version string your board vendor maintains.
- Chipset
- Platform controller hub identity; helps when searching for drivers or known quirks.
- DRAM frequency vs data rate
- DDR is often discussed in MT/s; half-rates appear in some tools—compare carefully.
- Timings (tCL, tRCD, …)
- Latency parameters; lower is not always automatically faster without stability testing.
- Command rate
- Memory signaling mode; mismatches can appear when mixing unusual configurations.
- Dual channel
- Width mode for memory controllers; single-channel hurts bandwidth-sensitive workloads.
- Rank
- Logical organization inside a module; boards can limit ranks per channel.
- SPD
- Module EEPROM data: manufacturer, part code, JEDEC tables, and profile blobs.
- XMP / EXPO / AMP
- Vendor overclock profiles embedded in SPD; enabling them depends on BIOS support.
- JEDEC
- Standard “safe default” speed tables for memory; what many boards fall back to.
- SODIMM vs UDIMM
- Physical module formats for laptops/small PCs vs typical desktops.
- Integrated graphics
- GPU inside the CPU package; naming in OS and firmware can diverge slightly.
- Discrete GPU
- Separate adapter; CPU-Z may list the active device context you are running under.
- Validation
- A shareable snapshot concept—use community validators when you need third-party hosting.
- SMBus / I2C locks
- Low-level buses SPD tools use; contention can make tabs intermittently empty.
- Hypervisor
- Software layer that can mask or virtualize hardware reporting inside guests.
- ES / QS samples
- Engineering or qualification silicon; names may look odd compared to retail CPUs.
- Power plan
- OS policy that changes idle and boost behavior—always mention it with clock screenshots.
- Thermal throttling
- Protection that lowers clocks; CPU-Z may show a snapshot that is not “under load truth.”
- Driver branch
- GPU driver lineage; string changes can be cosmetic across releases.
- Portable build habit
- ZIP-style usage reduces installer variables when triaging unfamiliar PCs.
Common wrong assumptions
Quick reality checks before you RMA something or fight in a thread.
| Common claim | Why it breaks down | What to do instead |
|---|---|---|
| “If CPU-Z says DDR5-4800, my kit is defective.” | You might be on JEDEC defaults, training failed, or the CPU memory controller limits the ceiling. | Compare SPD profiles vs Memory tab, update BIOS, re-seat modules, then re-test. |
| “Lower GHz in CPU-Z means my PC is slow.” | Idle snapshots mislead; laptops aggressively downclock on battery. | Capture under a known load with a defined power plan and AC power. |
| “GPU name mismatch = fake laptop.” | Driver rebrands, hybrid switching, and external display paths change active strings. | Document power source, display routing, and driver version alongside screenshots. |
| “SPD empty = dead RAM for sure.” | Seating, firmware blocks, and bus contention also produce blanks. | Swap slots, single-stick tests, close other hardware tools, update chipset drivers. |
| “Bench score defines my entire PC worth.” | Cooling, background tasks, and power limits swing short benchmarks. | Use Bench as a coarse signal; validate stability with dedicated stress tools. |
| “VM CPU-Z equals bare metal proof.” | Guests can show synthetic models and partial cache layouts. | Run on host OS for sales, warranty, and hardware dispute evidence. |
IT, repair shops, and teaching
Asset documentation
- Store CPU-Z captures next to service tags—not only in chat apps where search dies.
- When a machine returns from warranty repair, re-capture Mainboard BIOS strings to detect board swaps.
- For loaner laptops, snapshot baseline RAM and GPU strings before handing them out.
Security conversations
- Explain that identification tools read public hardware data; pair policy with your org’s software allow lists.
- Prefer official ZIP packages when auditors ask about installer behavior.
- Teach staff to verify file source and signatures rather than trusting search ads.
Teaching hardware literacy
- Have students compare SPD nominal tables with what the Memory tab shows after enabling profiles.
- Use validation links to discuss integrity of online evidence—what can and cannot be faked easily.
- Pair CPU-Z with a temperature tool before discussing “performance” emotionally.
Repair shop scripts
- “Before we order RAM, send SPD part numbers.”
- “Before BIOS flash, send current BIOS date string from Mainboard tab.”
- “If clocks look wrong, tell us AC vs battery and which power plan.”
Memory upgrades—edge cases
Problems that show up when “total GB” was the only thing anyone checked.
When “matched pairs” actually matters
Symmetric configurations help dual-channel modes and sometimes training stability. If SPD shows mismatched ranks or different XMP blobs, expect the motherboard to pick a safe common denominator. CPU-Z makes those mismatches visible before you spend money.
Laptop SODIMM traps
Some machines ship with soldered RAM plus one slot. CPU-Z cannot unsolder chips—but it prevents ordering a second SODIMM when none exists. Check SPD population maps against the physical bay count you expect.
“I enabled EXPO but nothing changed”
Firmware can fail training and reboot into safe defaults without a loud error. Compare SPD profile targets with the live Memory tab. If they diverge, your next step is BIOS logs and gradual manual tuning—not another purchase.
DDR4 to DDR5 migrations
CPU-Z helps you document the old world before you migrate boards. Save screenshots of the old SPD kit in case you need to re-buy similar latency characteristics for a sensitive workload.
VMs, containers, odd CPU names
CPU-Z inside a guest can still orient you, but do not treat it like proof of physical hardware for a sale or warranty.
Type-2 hypervisors
Guests may show a synthetic model string while still exposing some cache sizes. Treat this as “environment labeling,” not silicon forensic proof.
WSL and hybrid dev setups
Developers often compare Windows-native and Linux-native readings. Note kernel and hypervisor features enabled in firmware—CPU-Z captures the Windows side story.
Cloud gaming rigs
If you rent a remote PC, assume everything is a managed image. CPU-Z helps you learn what you paid for this month, not what metal sits in a specific rack row.
When CPU-Z misbehaves
Usually it is an old build, another tool locking the SPD bus, Windows permissions—or the number is fine and the reading was taken at idle.
| Symptom | Likely cause | What to try |
|---|---|---|
| SPD tab empty for a slot | Stick not detected, bad seat, or firmware block | Reseat RAM, test one stick, update chipset drivers, try the latest CPU-Z from the official developer. |
| CPU name looks generic or wrong | Very new stepping, ES/QS sample, or hypervisor masking | Update to the newest build; check for virtualization layers; compare with OS device manager. |
| Clocks frozen low on laptop | Power saver, thermal limit, or plugged state | Use balanced/high performance plan, AC power, and log under load—not at idle. |
| Antivirus quarantined CPU-Z | Heuristic false positive on low-level reads | Restore from the official ZIP; report through vendor channels; verify hash when possible. |
| Program will not start after OS update | Blocked by policy, corrupted download, or missing runtime dependency | Re-download using a fresh direct link (see below), unblock the ZIP, run as a normal user first, then review Event Viewer if it still fails. |
| SPD flickers between populated and empty | Another utility is polling the same SMBus lane | Close RGB suites, motherboard tuning tools, and laptop OEM “system care” apps; retry on a clean boot if needed. |
| Graphics tab missing on Server SKU | Headless roles, remote session-only GPUs, or minimal display stacks | Attach a local session with a real display path or compare with vendor management tools for out-of-band inventory. |
| CPU name differs from retail box | Regional naming, engineering sample, or reseller sticker errors | Compare stepping, core count, cache sizes, and socket package; escalate with photos if fraud is suspected. |
| Bench tab crashes instantly | Unstable overclock, aggressive undervolt, or broken power profile | Return to BIOS defaults temporarily, update chipset/GPU drivers, and test after thermals are healthy. |
| All tabs look “too old” after clone | Image deployed from different hardware without cleanup | Run on fresh boot, reinstall chipset drivers from the board vendor, and avoid comparing cloned images to new installs. |
| Android reading differs from desktop for same device | Different APIs, thermal states, and OS build channels | Treat both as hints; use desktop CPU-Z when planning Windows-side upgrades and Android readings for quick identification. |
For product defects or crash dumps, the developer maintains bug report and contact pages.
Frequently asked questions
Is CPU-Z safe to download?
Download only from the official developer website or mirrors clearly linked from the official site. Avoid bundled installers from unrelated download portals. On Windows, prefer the ZIP/portable package if you want fewer surprises.
Why does CPU-Z show a different CPU speed than Task Manager?
CPUs change speed constantly. Task Manager may average or round differently. Capture CPU-Z while running a known load if you need comparable numbers, and note power limits in BIOS.
Does CPU-Z stress the CPU or write to hardware?
Normal identification reads are light. The Bench tab runs a short workload when you start it. It is not a replacement for long validation tools like Prime95, OCCT, or memory testers such as MemTest86.
Is there an Android version?
Yes—the developer publishes a dedicated Android page. Mobile SoCs expose different data paths; treat phone results as complementary to PC screenshots when comparing devices.
Where do I read privacy terms?
Refer to the developer’s own legal pages for authoritative wording: privacy policy and terms of service.
Why is my SPD tab blank for one memory slot?
Usually the module is not fully detected, the slot is disabled, or another program is locking the SPD bus. Reseat RAM, test one stick, update chipset drivers, close RGB and tuning utilities, then try the latest build from the official developer.
Does CPU-Z replace reading the motherboard QVL?
No. It tells you what is installed and what SPD says; whether a new kit will train and post still depends on the board, BIOS version, and the vendor’s QVL. Use CPU-Z to collect part numbers and speeds, then check the list.
Can CPU-Z prove a PC is “new”?
It proves what hardware the firmware reports right now. It does not prove shipping history, prior use, or whether parts were swapped yesterday. Combine screenshots with receipts, seals, and—when serious money is involved—professional inspection.
Will CPU-Z slow down games while open?
Normal identification reads are light. Leaving extra monitoring tools running is a different story. Close what you do not need before benchmarking or competitive play.
Why do two identical PCs show different memory timings?
BIOS defaults, AGESA or microcode versions, and training luck all matter. Even small differences in firmware age can pick different safe tables after memory training.
Does CPU-Z write BIOS settings?
It is not a BIOS editor. Changing frequencies or enabling XMP/EXPO still happens in firmware setup. CPU-Z reports the outcome after the system trains and boots.
Is CPU-Z enough for thermal diagnosis?
No. Pair identification with a temperature and power tool. CPU-Z helps you document the hardware baseline; it does not replace sensor graphs under load.
What if my employer blocks portable executables?
Follow internal policy first. Some organizations allow signed packages in a sandbox; others provide corporate inventory agents instead. Do not bypass security controls—ask IT for an approved workflow.
Can I trust screenshots in marketplace listings?
Treat them as hints. Prefer live video, validation links, and consistent tab details across CPU, board, memory, and SPD. Mismatched dates or cropped critical fields should prompt more questions.
Why does my laptop CPU speed look “stuck”?
Battery saver, silent fan modes, VBS-related overhead, and corporate power policies can cap boost behavior. Mention AC vs battery and the active power plan when asking for help.
Does CPU-Z show ECC memory correctly?
Consumer boards and firmware vary in how they expose ECC status. CPU-Z can still show module identity via SPD in many cases, but mission-critical verification should follow vendor documentation for your platform.
What about Windows on ARM laptops?
Use the ARM64 build when applicable. If a tab is sparse, it may be a platform limitation or an immature firmware path—not necessarily user error. Read release notes from the official developer when a new SoC launches.
Should I run CPU-Z as Administrator?
Try a normal launch first. If SPD or certain reads fail consistently under a locked-down profile, elevation can change outcomes—but only when your policy allows it.
How often should I update CPU-Z?
After major platform launches, BIOS updates, or when tabs suddenly look wrong compared to reviews. You do not need daily updates unless you are chasing new CPU support.
Can CPU-Z detect fake GPUs?
It helps compare reported strings to expectations, but determined fraud can still involve deep software tricks. Cross-check device manager, driver INF details, and physical inspection when a deal is too good.
Is a validation ID forever?
It is a snapshot hosted by a third-party service. Links can break, services can change, and hardware can be upgraded later. Download a local screenshot archive for your own records.
Other tools that pair well
CPU-Z is narrow on purpose. For sensors, long reports, or drivers, use something built for that.
HWMonitor
Voltages, temperatures, fan speeds—pairs naturally with CPU-Z snapshots.
HWMonitor Pro
Remote monitoring features for IT-style workflows.
SIW / Gtopala tools
Broader inventory-style reports for auditors who want everything in one export.
DriversCloud
Hardware detection with a driver/update angle—useful after board swaps.
Developer kits
The developer offers professional kits for OEMs and tool builders—see the developer pro portal for system information and monitoring products.
HWMonitor SDK
For integrators embedding sensor logic—distinct from the free consumer app.
Quick topic map
Short reminders; the longer explanations are in the sections above.
Buying & selling
- Proof bundles: combine CPU, Mainboard, Memory, and SPD tabs; add validation when money is serious.
- Partial truths: a single “16 GB” screenshot does not prove dual-channel or module quality.
- GPU hybrid laptops: always record AC vs battery and whether an external display is in the path.
- Refurb desktops: BIOS dates from Mainboard tab help you guess firmware neglect before you flash.
Upgrades
- DDR generation locks: CPU-Z shows the generation you cannot negotiate with adapters.
- Profile failures: SPD may advertise an XMP table that the board refuses to train—compare to Memory tab reality.
- Cooling ceilings: memory stability can be thermal; CPU-Z shows timings, not DIMM temperature.
Debugging culture
- Repro language: say “at idle on battery” vs “Cinebench run on AC”—precision reduces noise.
- Single screenshots lie: attach context or take two captures minutes apart on hybrid GPUs.
- Ticket hygiene: filenames and dates matter more than RGB aesthetics in enterprise queues.
Platform quirks
- Multi-boot: compare readings using the same OS session when arguing about “what the machine is.”
- VMs: good for learning, weak for hardware receipts.
- ARM transition: expect rapid changes to SoC support—read notes when laptops are new.
Direct download
Direct links for Windows (including ARM64 builds where applicable) and Android. Prefer ZIP/portable if you want fewer installer prompts. Re-check the build after major Windows or BIOS updates.
- Prefer ZIP/portable if you want minimal installer behavior.
- Re-check version after major Windows updates or BIOS changes.
- Follow developer news for SoC and platform additions.