Running a thorough computer performance test on a Windows PC is the fastest way to find what’s slowing you down — whether it’s CPU throttling, flaky RAM, a slow SSD, or background services hogging resources — and this guide walks through the built‑in tools and trusted third‑party benchmarks to test, interpret, and act on the results.
Background / Overview
Modern Windows includes several built‑in diagnostics that are powerful, free, and sufficient for most troubleshooting tasks. From the long‑running Windows Performance Monitor (perfmon) and the Windows Memory Diagnostic (mdsched) to simple live checks in Task Manager, these utilities help you collect data and form a remediation plan. For reproducible, comparable scores you’ll want third‑party benchmarks such as PCMark, 3DMark, Cinebench, or disk tools like CrystalDiskMark — each targets a different subsystem (CPU, GPU, storage), producing numeric scores you can compare over time or against similar systems.
Why run a performance test now? Common reasons:
- Your PC feels slow, freezes, or has stuttering during gaming or editing.
- You want to verify hardware after a repair, BIOS update, or driver change.
- You’re comparing before/after results for upgrades (SSD, RAM, GPU).
- You need data to support an RMA or warranty claim.
This article explains step‑by‑step how to run each test, what results mean, how to interpret scores, practical follow‑ups, and safety cautions.
Using Performance Monitor (perfmon) — deep, built‑in diagnostics
What it does and when to use it
Performance Monitor is Windows’ built‑in power tool for capturing a holistic snapshot of system activity under load. Use it when you need detailed, time‑based metrics (CPU queues, disk latency, context switches, kernel counters) rather than a single score. The generated reports are invaluable for diagnosing intermittent slowdowns and for sharing structured evidence with support teams.
How to run a System Performance report
- Press Windows + R, type perfmon, and press Enter.
- In the left pane, expand Data Collector Sets > System > System Performance.
- Right‑click System Performance and choose Start. Let it run for about 60 seconds while you reproduce the slow behavior.
- Open Reports > System > System Performance to view the detailed results.
What to look for in the report
- CPU: sustained 100% usage or frequent context switches can point to a runaway process or driver.
- Memory: high commit values, frequent hard faults (paging), or low available memory indicate that RAM or memory management is limiting performance.
- Disk: long average disk response/queue lengths are classic bottlenecks for slow app launches or choppy behavior.
- Network: saturation or retransmissions can cause perceived system lag for cloud apps.
Perfmon reports are technical; capture screenshots and the XML export when contacting support or marketplaces for comparison.
Testing RAM with Windows Memory Diagnostic (mdsched) — quick hardware triage
When to run the RAM test
Run the Windows Memory Diagnostic if your system randomly freezes, blue‑screens, or exhibits unexplained application crashes. Memory faults commonly masquerade as other issues, so this is a prime first step in hardware troubleshooting.
How to run the test
- Press Windows + R, type mdsched.exe, and press Enter.
- Choose Restart now and check for problems. The machine will reboot into the diagnostic environment and run the default scan.
- Optionally press F1 in the diagnostic UI to select Basic/Standard/Extended tests or to change cache settings. For stubborn issues, run Extended and allow multiple passes.
Reading results
After the test completes and Windows reboots, open Event Viewer > Windows Logs > System and search for
MemoryDiagnostics‑Results to see the result entry. If errors are reported, reseat modules, test individual DIMMs, update BIOS/chipset drivers, and pursue vendor RMA as appropriate.
Quick live checks with Task Manager — fast, practical triage
Why Task Manager first
Before launching extended diagnostics, a quick look at
Task Manager often reveals the obvious: a process consuming CPU or disk, scheduled scans, or runaway background updates. Task Manager is instant, non‑destructive, and requires no setup.
How to use it effectively
- Press Ctrl + Shift + Esc to open Task Manager.
- Select the Performance tab to observe CPU, Memory, Disk, and GPU usage in real time.
- Sort the Processes tab by CPU, Disk, or Memory to identify resource hogs.
- Use the Startup tab to disable unnecessary programs that run on boot.
Task Manager does
not replace perfmon or benchmarks, but it points you to what to test next.
Run benchmark software for comparable numeric scores
Why use third‑party benchmarks
Benchmarks give you reproducible numbers so you can compare results across systems or after upgrades. They stress specific subsystems to reveal performance ceilings and stability under load. Popular tools:
- PCMark 10 — overall system and productivity workloads.
- 3DMark — GPU and gaming performance across DirectX versions.
- Cinebench — CPU single and multi‑core rendering scores.
- CrystalDiskMark — detailed storage sequential/random read/write figures.
How to run benchmarks responsibly
- Close nonessential programs and disable background scans.
- Ensure the machine is on AC power and not thermally throttled (fans unobstructed).
- Run the benchmark and allow it to complete; repeat the run 2–3 times and average results.
- Compare against reference scores for similar hardware to detect underperformance.
Benchmarks are generally safe, but they intentionally stress components — ensure adequate cooling and monitor temperatures while tests run.
Test disk speed with winsat and disk benchmarks
Using winsat (built into Windows)
Windows ships with the Windows System Assessment Tool (winsat), a command‑line utility that can measure disk performance quickly without extra downloads. Common commands:
- winsat disk -seq -read -drive C
- winsat disk -seq -write -drive C
- winsat disk -ran -read/-write -drive <letter>
Run Command Prompt as Administrator to execute winsat and note MB/s read/write results. Winsat is convenient but comparatively basic.
When to use CrystalDiskMark or MiniTool Partition Wizard
For more detailed disk profiling (sequential vs random, multiple queue depths, configurable file sizes), use CrystalDiskMark or MiniTool Partition Wizard’s Disk Benchmark feature. These tools show both sequential and random throughput and are the industry standard for SSD testing.
What counts as “good” disk performance
- SATA SSDs: around ~500 MB/s sequential reads/writes in typical consumer drives.
- NVMe SSDs: can range from ~1,500 MB/s up to 7,000 MB/s depending on generation and model. These figures vary considerably by model and workload, so always compare to the drive’s published specifications.
Manufacturer diagnostic utilities — use vendor tools for firmware and health checks
PC and component makers provide diagnostics tailored to their hardware (Dell, HP, Lenovo, ASUS, Samsung, Crucial, etc.. These apps can run firmware checks, SMART analysis, and guided hardware tests that sometimes catch vendor‑specific failure modes. When a hardware vendor asks for logs, use their official tool and follow instructions for full system scans.
Interpreting results — a practical playbook
CPU results
- High average utilization with one busy thread: look at the specific process and thread.
- High single‑thread latency but low multi‑thread score: system may be balanced for single‑thread workloads or CPU downclocked by power policy.
Memory results
- Repeated memory test errors: failing DIMM(s) — replace or RMA.
- Low available memory with heavy paging: add RAM or reduce memory pressure from background apps.
Disk results
- Low sequential performance on NVMe compared to spec: check for proper NVMe driver, PCIe slot configuration in BIOS, or thermal throttling.
- High disk latency but good MB/s: look at IOPS/latency sensitive workloads — small random read/write performance matters more for apps than raw sequential throughput.
GPU and gaming
- 3DMark/Cinebench lower than expected: update GPU drivers, ensure power plan is not throttling, confirm GPU sits in correct PCIe slot and power connectors are attached.
Troubleshooting checklist — step by step
- Open Task Manager and stop obvious resource hogs.
- Generate a perfmon System Performance report (perfmon) for deep diagnostics.
- Run winsat disk or CrystalDiskMark for storage checks.
- Run Windows Memory Diagnostic (mdsched) if crashes or freezes occur.
- Update drivers (GPU, chipset, storage controllers), BIOS/UEFI, and firmware.
- For persistent instability, run stress tests (CPU: Cinebench, Prime95; GPU: 3DMark, FurMark) and monitor temps.
- If hardware fails diagnostics, contact vendor support and collect logs/screenshots for RMA.
Safety, risks, and caveats
- Benchmarks stress hardware intentionally; ensure good cooling and monitor temperatures during runs. Overheating can cause thermal throttling or crashes — not permanent damage if cooling is adequate, but avoid unattended long burn‑ins on systems with unknown cooling. Exercise caution with stress tools.
- The Windows Memory Diagnostic is non‑destructive but can be slow in Extended mode; plan for downtime.
- Command‑line tools like winsat require administrator privileges and correct syntax; mistyped parameters can cause confusing output. Winsat is useful for quick checks but is not a replacement for full benchmarks.
- Some Windows Insider features (for example, taskbar internet speed test shortcuts) launch web tools rather than native diagnostics; they are useful for quick checks but not for forensic testing. These are often rolling out in preview builds and have limited diagnostic depth. Do not rely on them for enterprise audits.
Advanced tips and best practices
- Always run tests on a steady power source (laptop on AC with high‑performance power plan) to avoid CPU/GPU power‑saving biasing results.
- When testing NVMe drives, use the specifications of the model as the baseline; thermal throttling and PCIe lane allocation (x4 vs x2) matter.
- For repeatable results, reboot before benchmark runs, close antivirus background scans, and perform multiple runs at different times of day.
- Keep a log: record system configuration (CPU, RAM, drives, BIOS version), driver versions, and timestamps for each benchmark run — this helps compare before/after changes.
- If a quick memory scan is triggered by a crash in Insider builds, treat it as triage; run extended tests if quick scans are inconclusive. Insider prompts are experimental and may be noisy for the time being.
When to escalate — hardware replacement vs software fixes
- Replace RAM when Windows Memory Diagnostic or MemTest86 consistently reports errors on the same DIMM or across slots.
- Replace or RMA storage if SMART values indicate reallocated sectors, high wear level, or if disk benchmarks are far below published specifications even after driver and firmware updates.
- Consider motherboard/chipset issues if multiple components show intermittent errors (memory and storage together), or if tests pass for modules in one slot but fail in another after reseating.
Practical examples — short workflows
Quick triage (5–10 minutes)
- Open Task Manager and sort by Disk/CPU/Memory. Identify the top 3 consumers.
- Run perfmon /report (or System Performance) for a one‑minute snapshot to capture counters.
- Run winsat disk -seq -read -drive C for a quick storage sanity check.
Deep diagnostic (30–90 minutes)
- Run a perfmon capture while reproducing the issue. Export the report for analysis.
- Run Windows Memory Diagnostic (Extended) overnight for thorough RAM tests.
- Run CrystalDiskMark and a 3DMark/Cinebench run to quantify storage, GPU, and CPU performance. Compare results to published specs.
FAQs (concise answers)
- Can I use my PC during the test? No — close other programs for accurate, uncontaminated results. Task Manager checks can be left running for observation.
- Are benchmarks safe? Yes when used responsibly; they stress hardware but do not inherently damage components if cooling is adequate. Monitor temps and stop tests if temperatures spike unusually.
- How often to test? Every few months or after driver/firmware updates, major Windows updates, or hardware changes.
- What if scores are low? Update drivers, check power profiles, verify BIOS settings, and retest. If low performance persists, investigate hardware (RAM, storage) and vendor diagnostics.
Conclusion
Running a complete computer performance test on Windows combines quick live checks, targeted subsystem diagnostics, and reproducible benchmarks. Start with Task Manager for immediate clues, use perfmon to capture comprehensive system data, run Windows Memory Diagnostic for RAM stability, and use winsat or CrystalDiskMark to evaluate storage. For comparative, reproducible scores use PCMark, 3DMark, and Cinebench. Always monitor temperatures, run tests on AC power, and repeat runs to average out anomalies. When evidence points to failing hardware, gather logs and vendor diagnostics for RMA or repair.
A methodical approach — observe, measure, interpret, remedy — turns vague “it’s slow” complaints into actionable steps and reliable fixes. Use the tools described here to produce the hard data needed to restore performance, justify upgrades, or document faults for support.
Source: Windows Report
How to Run a Computer Performance Test on Windows