How to run full diagnostics on PC?

How to Run Full Diagnostics on PC: Top Methods

Knowing how to run full diagnostics on PC helps detect underlying hardware issues before system failure occurs. Regular performance checks ensure hardware components operate within optimal ranges, protecting data and preventing unexpected crashes. Understanding these built-in system tools allows users to maintain machine health and troubleshoot technical problems efficiently.

Getting Ready: A Few Things Before You Start

Its tempting to jump right into scanning. But running a diagnostic when somethings wrong can sometimes make things worse. First, ensure youre logged in with an administrator account, as many tools need this access. Its also wise to back up your important files before running deep disk scans.

Close all unnecessary applications and services to free up system resources, and make sure your PC is plugged into a stable power source. Diagnostics can take time, and you dont want the system to shut down halfway through.(reference:0)

The First 60 Seconds: Your Best Quick Health Check

Before you reach for any third-party tools, Windows has a built-in 60-second assessment thats surprisingly thorough. This is the first step to understanding your PCs health.

Press the Windows key + R, type system health report perfmon command, and hit Enter. Windows will take about 60 seconds to collect data on your CPU, memory, disk, network, and software configuration.(reference:1) It then generates a detailed HTML report saved locally on your machine.(reference:2) This report is color-coded, making it easy to spot warnings and potential issues. Its a complete health snapshot that requires no installation and sends no data to third parties.(reference:3)

Essential Built-in Windows Diagnostic Tools

The perfmon report is a great starting point, but Windows has several other powerful tools for more targeted troubleshooting. They are designed to test different parts of your system: hardware, system files, drivers, and overall performance.(reference:4)

Reliability Monitor: Your PC's History Graph

The perfmon report tells you whats happening now. Reliability Monitor tells you whats been going wrong. Access it by searching for Reliability History or typing perfmon /rel in the Run dialog.(reference:5) This tool presents a timeline of events like app crashes, Windows failures, and hardware errors.(reference:6) It uses a stability index from 1 (most stable) to 10 (least stable). A declining trend on the graph is a clear signal that something is wrong.(reference:7) Click on any day to see exactly which app or driver failed. Its the best tool for spotting patterns.

CHKDSK, SFC, and DISM: The Command Line Trio

When you suspect deeper issues, youll need to open Command Prompt as an administrator. Heres what each command does and when to use them:

First, run dism /online /cleanup-image /restorehealth. This scans and repairs the Windows system image, fixing the component store that SFC relies on.(reference:8) The DISM command usually takes a few minutes to complete.(reference:9)

Next, run sfc /scannow. This scans all protected system files and replaces corrupted versions. Based on experience, it detects errors about 15% of the time on hundreds of systems, making it a valuable tool to run periodically.(reference:10)

Finally, run check hard drive for errors command prompt using chkdsk /f. This command may require a reboot to repair the disk offline. The chkdsk command takes about 3.5 minutes on an SSD when there are no errors, but longer on older hard drives.(reference:11)

Windows Memory Diagnostic: Is Your RAM Failing?

Faulty RAM can cause random crashes, blue screens, and file corruption. To test it, type Windows Memory Diagnostic tool guide in the search bar and select the app.(reference:12) Youll be prompted to restart your PC immediately or schedule a test for the next startup. The tool will run a series of tests on your memory and report any errors. Its a crucial check for systems plagued by unexplained instability.

Hardware-Specific Diagnostics: Dell, HP, and Others

Sometimes a problem persists even after Windows loads. Thats when you need to run diagnostics before the operating system starts. Most major PC manufacturers include pre-boot diagnostic tools. These are the best way to confirm if a hardware component is failing.

To access Dell Diagnostics, restart your computer and press F12 repeatedly at the Dell Splash Screen. In the boot menu, select the Diagnostics option. Youll then have a choice: Express Test (quick test, typically 10-20 minutes), Extended Test (thorough check, an hour or more), or Custom Test (target a specific device).(reference:13) For HP computers, turn off the device, power it on, and immediately press the Esc key repeatedly. Then press F2 for diagnostics.(reference:14)

Third-Party Diagnostic Tools: When Built-in Isn't Enough

Built-in Windows tools are great, but they dont cover everything. For real-time temperature monitoring or in-depth hardware analysis, youll need a third-party application. Many of the best ones are completely free.

For hardware monitoring, HWiNFO is a popular free tool that shows everything from exact CPU and GPU temperatures to fan speeds and voltages.(reference:15) CrystalDiskInfo is a must-have for checking your hard drive or SSDs health, including S.M.A.R.T. data.(reference:16) If you want a more user-friendly historical view of your system, tools like AppControl record second-by-second usage data, letting you see exactly which app spiked your CPU a minute ago.(reference:17)

Interpreting Your Results: What to Do Next

A diagnostic report is only useful if you can understand it. Most tools give you a pass/fail result, but many also provide error codes. For Windows, a blue screen stop code can tell you exactly which driver or hardware component is failing.(reference:18) There are over 250 common stop codes, each offering a clue.(reference:19) The Reliability Monitors timeline is invaluable for seeing when problems started, helping you pinpoint if a recent driver or software update is the culprit.(reference:20)

If a diagnostic test identifies a hardware failure, note the error code and contact the manufacturers support. For example, Dell often provides codes in a format like 2000-0142.(reference:21) A clean report doesnt mean your PC is perfect—it just means no critical faults were found in that specific test.(reference:22) If problems persist after running the main checks, you may need to run more in-depth tests or consult a professional.

Key Takeaways

Built-in Windows Diagnostic Tools at a Glance

Each tool serves a specific purpose. Here's a quick guide to which one you should use for different problems.

Performance Monitor (perfmon /report)

A detailed, color-coded HTML report saved locally.

A comprehensive, 60-second overview of overall system health.

CPU, memory, disk, network, and software configuration.

Reliability Monitor (perfmon /rel)

A graphical timeline with a stability index (1-10) and event details.

Identifying the timeline of crashes, app failures, and hardware errors.

Historical system stability events and patterns.

System File Checker (sfc /scannow)

A report indicating if corrupted files were found and repaired.

Fixing Windows stability issues caused by corrupted system files.

Integrity of all protected Windows system files.

Windows Memory Diagnostic (mdsched.exe)

A report on memory errors after your PC restarts.

Diagnosing random crashes, freezes, and blue screens from faulty RAM.

Your computer's RAM (Random Access Memory) for errors.

Lan's Journey: From Random Crashes to a Stable PC

Lan, a freelance graphic designer in Ho Chi Minh City, had a frustrating problem. Her PC would crash at random times, sometimes three times a day, and she'd lose hours of work. She feared it was a serious hardware issue and thought she might need a new computer. It was costing her money and sanity.

Her first attempt was to reinstall Windows, a time-consuming process that did nothing to solve the crashes. She was about to give up. Then, she tried the Reliability Monitor.

The timeline showed a clear pattern: a critical error every time her PC froze. Clicking on the error revealed it was related to an outdated network driver, not a failing hard drive or motherboard as she had feared.

Lan updated the driver from the manufacturer's website, and the random crashes stopped completely. A 5-minute diagnostic tool saved her from a $1000+ unnecessary computer upgrade and countless hours of lost work.