How to Run a Hardware Diagnostic on Windows 11: A Step-by-Step Guide

If you’re reading this, chances are your PC is acting up — maybe it crashes, freezes, or behaves sluggishly. Before assuming it’s time to replace hardware, let’s calm down, roll up our sleeves, and run a hardware diagnostic on Windows 11 to isolate the issue. In this comprehensive, beginner-friendly guide, we’ll walk you through every step — from simple built-in tools to advanced diagnostics — with analogies, tips, and best practices. By the end, you’ll know exactly how to check CPU, RAM, storage, GPU, and more, with confidence.

What Is a Hardware Diagnostic and Why Do You Need It?

Imagine your PC as a car. When a light shows up on the dashboard, you don’t replace the engine right away — you run diagnostics. In computing, a hardware diagnostic is like turning on your car’s scanner: you test components (CPU, RAM, disk, GPU, motherboard) to see which part is faulty, stressed, or misbehaving.

Running diagnostics is smart because:

• It lets you pinpoint the failing component rather than guess.

• It can help you prolong component life by catching issues early.

• It saves time, money, and heartbreak — you avoid replacing working parts.

• It helps when you ask for support: you’ll have logs or results to share.

In this article, “hardware diagnostic” refers to the process of testing physical components (not just software errors) — though software and driver issues often interplay. We’ll cover tools built into Windows and 3rd-party utilities to help you diagnose thoroughly.

---

2. Common Hardware Symptoms That Warrant Diagnostics

You don’t need to run diagnostics daily — but when you see signs that your system is unhappy, it’s time. Some red flags:

• Frequent blue screens (BSODs) or system crashes

• Random freezes, lockups, or “Not Responding” states

• Slow performance during normal tasks

• Strange noises from drives (clicking, grinding)

• Artifacts, glitches, or crashes in graphics or GPU workloads

• Memory errors, file corruption, weird file behavior

• Overheating or thermal throttling

• Devices not detected (USB, drives, etc.)

If you see any of these, a diagnostic session can reveal the weak link. Sometimes the problem is simple (e.g. driver issue), but often diagnostics help cut through the guesswork.

---

3. Before You Start: Preparations & Precautions

Before digging into diagnostics, let’s ensure you get reliable results and don’t cause further problems.

• Backup your data. Always. If a drive is failing, diagnostics stress it. Save important files elsewhere first.

• Update system & drivers. Sometimes misbehaving drivers trigger false “failures.” Update Windows and your device drivers.

• Disconnect unnecessary peripherals. Remove USB devices, extra disks, or external components to simplify testing.

• Ensure good cooling. Run tests in a cool environment, and make sure fans are working.

• Monitor power source. Use a stable power supply (avoid battery or unstable external power).

• Record logs & timestamps. When you run diagnostics, note when you ran them and under what conditions (ambient temp, workload).

• Use safe mode if necessary. If the system is unstable, some tests may require minimal running services or safe mode to avoid interference.

With precautions in place, we’ll move on to actual tools.

---

4. How Windows 11 Diagnostics Work: Overview

Windows 11 includes several built-in diagnostic components, plus the ability to run system reports and diagnostics with internal tools. Here’s a quick map:

• Windows Troubleshooters — targeted fixes (network, Bluetooth, updates) Lifewire+1

• Windows Memory Diagnostic — RAM testing Lifewire+2Microsoft Q&A+2

• Performance Monitor / System Diagnostics Report — holistic system health & performance metrics Wccftech+2NinjaOne+2

• Check Disk (CHKDSK) — tests disk file system and sectors

• Device Manager / Driver checks — detect missing or failing devices

• DxDiag (DirectX Diagnostic Tool) — primarily GPU, sound, display diagnostic info Wikipedia

• WinSAT / System Assessment Tool — performance benchmarking and subsystem scoring Wikipedia

Beyond these, OEMs (Dell, HP, etc.) often provide hardware diagnostics you can invoke at boot.

---

5. Using Windows Built-In Diagnostic Tools

Let’s take a walk through each built-in method, with step-by-step instructions. These are the tools you should try first before turning to third-party software.

5.1 Windows Troubleshooters

Windows 11 has built-in troubleshooters for common system issues.

How to run them:

1. Open Settings (Press Windows + I).

2. Go to System → Troubleshoot. geek-way.com+2Microsoft Support+2

3. Click Other troubleshooters.

4. You’ll see a list (e.g. Network, Bluetooth, Keyboard, Windows Update).

5. Click Run next to the relevant item and follow on-screen prompts.

These built-in troubleshooters are convenient and safe. They often detect driver issues or minor misconfigurations and offer fixes. Note: they don’t deeply test physical hardware — for that, you’ll need more powerful tools.

5.2 Windows Memory Diagnostic (RAM Test)

If you suspect memory (RAM) issues — symptoms like crashes, data corruption, or erratic behavior — run this tool.

Step-by-step:

1. Press Windows + R to open the Run dialog.

2. Type mdsched.exe and press Enter. Lifewire+2MakeUseOf+2

3. You’ll see options:

   • “Restart now and check for problems (recommended)”

   • “Check for problems the next time I start my computer”

4. Choose the first one to reboot immediately.

5. The PC restarts and memory testing begins.

6. After the test completes (this may take a few minutes), Windows boots normally.

7. To view results: open Event Viewer → Windows Logs → System. Look for entries marked “MemoryDiagnostics-Results”.

If errors are found, it’s likely your RAM modules or slots are failing. Many users follow this up with MemTest86 (discussed later). Microsoft Q&A+1

5.3 Performance Monitor / System Diagnostics Report

This tool gives you a broad “snapshot” of your system health — kind of like a full checkup.

How to run:

1. Press Windows + R, type perfmon, then press Enter. (Or search “Performance Monitor.”) NinjaOne+2Wccftech+2

2. In the left pane, expand Data Collector Sets → System.

3. Right-click System Diagnostics, then click Start.

4. Wait about 60 to 120 seconds while it gathers data.

5. Then, in Reports → System → System Diagnostics → [Your PC name], open the report.

6. Review sections such as Disk, Memory, Processor, Network, etc.

This report will flag errors or warnings (red, yellow) and give details. Wccftech+2NinjaOne+2

5.4 CHKDSK (Check Disk)

To test storage (HDD or SSD) and file system integrity, use CHKDSK.

Steps:

1. Open an elevated Command Prompt (Press Windows, type cmd, right-click → “Run as administrator”).

2. Type:

   chkdsk C: /f /r /x


   • C: is the drive letter (change if testing another drive).

   • /f fixes errors, /r locates bad sectors and recovers readable info, /x forces dismount if needed.

3. Press Enter.

4. If the drive is in use, it’ll prompt to schedule on next reboot — type Y.

5. Restart your PC; CHKDSK will run before Windows loads.

6. After the scan, Windows boots — check logs in Event Viewer → Application (look for Wininit entries).

CHKDSK is one of the classic hard drive tests. Use it when storage issues or system file corruption are suspected.

5.5 Device Manager & Driver Checks

Sometimes what looks like hardware failure is actually a driver issue (software layer) misbehaving.

How to inspect:

1. Press Windows + X and choose Device Manager.

2. Expand categories, e.g. Disk drives, Display adapters, Network adapters.

3. Look for warning icons (yellow exclamation) — these point to driver problems.

4. Right-click and select Update driver or Uninstall device then reboot and let Windows re-detect it.

Also, you can run:

• msinfo32 (System Information) — view hardware summary plus diagnostics colors. Microsoft Support

• Check Event Viewer → System for device-related errors.

5.6 DirectX Diagnostic Tool (DxDiag)

DxDiag is useful for diagnosing GPU, audio, and DirectX subsystem health.

How to run DxDiag:

1. Press Windows + R, type dxdiag, and press Enter.

2. The DirectX Diagnostic Tool opens.

3. Review tabs:

   • System: general system, OS, memory, etc.

   • Display: GPU info, driver version.

   • Sound: audio hardware.

   • Input: game controllers, etc.

4. You may also click “Save All Information” to generate a text log.

Note: DxDiag is more for gathering system information and driver status than “stress testing.” Wikipedia

5.7 WinSAT / Windows System Assessment Tool

WinSAT is a performance assessment engine. In older Windows, it gave the “Windows Experience Index.” In Windows 11, it remains under the hood.

Use via command line:

1. Open Command Prompt (regular or elevated).

2. Type:

   winsat formal


   to perform the full set of performance tests (CPU, memory, graphics, disk).

3. Let it run — it will display progress and results.

4. Analysis results are stored under %windir%\Performance\WinSAT\DataStore.

You can also run subsets, e.g. winsat cpu, winsat disk etc. Wikipedia

---

6. Using OEM / Manufacturer Diagnostics (Dell, HP, Lenovo, etc.)

Many PC manufacturers include diagnostics tools that run outside of Windows (preboot) and have deeper hardware-level checks.

These tests operate at the firmware level and can catch issues that Windows-level tools sometimes miss (e.g. motherboard faults, power delivery, sensor failures). Always consult your OEM’s support site for specific instructions.

Also, OEM-provided software (Dell SupportAssist, HP PC Hardware Diagnostics) can run within Windows and complement built-in tools.

---

7. Third-Party Diagnostic Tools & Stress Tests

Built-in tools are solid, but sometimes you need deeper, more aggressive, or more specialized tests. Here are go-to third-party diagnostics.

7.1 MemTest86 / MemTest86+

If Windows Memory Diagnostic flags issues (or doesn’t flag anything but you still suspect RAM), MemTest86 is the gold standard.

• Download the ISO or USB installer from its official site.

• Boot your PC from the USB.

• Let it run overnight (a full test suite takes time).

• It will continuously test each memory address and report any errors.

• If errors occur, try testing individual sticks or slots.

Many enthusiasts recommend running tests on one stick at a time to isolate problems. Microsoft Q&A+2MakeUseOf+2

7.2 HWiNFO / HWInfo64

HWiNFO is a powerful utility that gives you in-depth hardware data, real-time monitoring, and logging. HWiNFO

How to use:

1. Download and install HWiNFO.

2. Launch in Sensors-only mode or full mode.

3. Monitor temps, voltages, fan speeds, and hardware status.

4. Use built-in logging to record data under load.

5. Compare readings against manufacturer specs to detect anomalies.

HWiNFO is especially useful for thermal/power diagnostics (overheating, undervoltage, poor cooling).

7.3 Stress Testing Tools (CPU, GPU, Disk, etc.)

To push your components, use dedicated stress tests:

• Prime95: CPU torture test

• FurMark / Unigine Heaven / 3DMark: GPU stress test

• CrystalDiskInfo / CrystalDiskMark: Disk health & performance

• AIDA64: All-in-one benchmarking and stress

• OCCT: power/CPU/GPU test with logs

How to proceed:

1. Run the baseline diagnostic (Performance Monitor, Memory Diagnostic).

2. Run stress tests for 15–30 minutes under monitoring.

3. Watch for crashes, thermal shutoffs, errors, or reboots.

4. Compare with normal idle diagnostic output.

If your system fails under stress, it’s a strong hint the hardware is the weak link (cooling, CPU, GPU, PSU, etc.).

---

8. Interpreting Diagnostic Results: What to Look For

Running diagnostics is one thing — understanding the results is another. Let’s break down what you want to watch for, and what common indicators mean.

Indicators of Hardware Issues

• Red / Critical flags in Performance Monitor or OEM logs

• Frequent errors in Event Viewer (particularly Disk, Memory, or System logs)

• Memory errors from Windows Memory Diagnostic or MemTest86

• Bad sectors / errors in CHKDSK or drive manufacturer tools

• Overheating / thermal throttling from HWiNFO or sensors

• Voltage anomalies / power delivery issues

• Artifacts or display glitches under GPU stress tests

• Sudden reboots, crashes under load

• Driver failure events / device disconnects in Device Manager

Diagnosing by Component

Once you identify the failing component, the next steps are repair, replacement, or further targeted diagnosis (e.g. run testing on another identical part).

---

9. Troubleshooting Based on Findings

Now that your diagnostics have flagged an issue — what next? Here’s a roadmap:

1. Re-run or isolate. If a memory stick shows errors, test individually. If a drive shows bad sectors, back up immediately and run full drive test.

2. Update firmware / drivers. Sometimes firmware-level updates fix latent hardware compatibility issues (e.g. SSD firmware).

3. Check cooling & airflow. Overheating can cause throttling or shutdowns. Clean dust, replace thermal paste, boost airflow.

4. Replace or upgrade faulty component. If diagnostics confirm a failing part (e.g. bad RAM stick, failing SSD), get replacement.

5. Test system again. After replacement or fixes, rerun key diagnostics to verify.

6. Revisit system stability. Use real-world workloads (games, video editing, multitasking) to validate stability.

7. Document and share logs. If getting help from forums or OEM support, share diagnostic logs and results.

Think of it as detective work — use clues, isolate suspects, test, then act.

---

10. Preventing Hardware Issues: Best Practices

Diagnostics is reactive. Let’s be proactive and reduce need for frequent diagnostics.

• Clean internal components periodically (dust kills cooling).

• Monitor component temperatures (use HWiNFO or similar).

• Use quality surge protector / UPS to avoid power spikes.

• Avoid overclocking unless you’re experienced.

• Keep drivers & firmware updated (especially for motherboard, BIOS, SSD).

• Check for SMART warnings for drives often.

• Use good-quality cooling (fans, case airflow).

• Don’t push components at 100% continuously (give rest periods).

• Keep system and chassis well ventilated.

These habits can dramatically reduce hardware failures and extend component lifespans.

---

11. Summary of Key Diagnostic Steps

Here’s a quick checklist you can follow:

1. Backup essential data.

2. Run Windows Troubleshooters for obvious issues.

3. Run Windows Memory Diagnostic for RAM health.

4. Generate a System Diagnostics Report via Performance Monitor.

5. Run CHKDSK to check drive integrity.

6. Check Device Manager / drivers for issues.

7. Use DxDiag for GPU / sound diagnostics.

8. Optionally run WinSAT to benchmark subsystems.

9. Use OEM diagnostics at boot (Dell, HP, etc.).

10. Use third-party tools (MemTest86, HWiNFO, Prime95, etc.) for deeper tests.

11. Interpret results, isolate failing components, and take corrective action.

12. Rerun diagnostics to confirm stability.

---

Conclusion

Running a hardware diagnostic on Windows 11 might sound daunting, but with the right tools and a methodical approach, you can find the real culprit — whether it’s failing RAM, a dying SSD, an overheating GPU, or a flaky motherboard. In this guide, we covered:

• Why diagnostics matter

• How to prep safely

• How to use built-in tools: troubleshooters, Memory Diagnostic, Performance Monitor, CHKDSK, DxDiag, WinSAT

• OEM diagnostics and third-party stress tools

• Interpreting results and acting on them

• Prevention tips

Diagnostics aren’t magic — they’re tools that put data in front of you so you can make informed decisions instead of guessing. Don’t let a bad stick of RAM or a nearly-dead SSD ruin your productivity or data.

Now it’s your turn: run those tests, document results, fix what you find, and you’ll have a healthier, more reliable PC.

---

FAQs

1. Can I run hardware diagnostics without installing anything?
   Yes — Windows’ built-in tools (Memory Diagnostic, Performance Monitor, CHKDSK, DxDiag) require no additional installation.

2. Do diagnostics risk damaging hardware?
   In normal, moderate use, no. However, extreme stress tests (e.g. overclocking under load) can push poorly cooled systems into trouble — always monitor temps.

3. How long do diagnostics take?
   Basic tests (Memory, Performance Monitor) typically take 1–5 minutes. Stress tests or full memory scans (e.g. MemTest86) may take hours or overnight.

4. If a diagnostic shows an error, is it 100% certain the hardware is bad?
   Not always. Sometimes errors stem from driver bugs, firmware issues, or power/thermal problems. Use diagnostics as clues and corroborate with further testing.

5. How often should I run diagnostics?
   As needed — when symptoms arise. For preventive care, once every few months (or after major changes) is reasonable.

---

Summary (Key Takeaways)

• “How to run a hardware diagnostic on Windows 11” starts with using built-in tools like Memory Diagnostic, Performance Monitor, CHKDSK, DxDiag, and WinSAT.

• OEM and third-party diagnostics (MemTest86, HWiNFO, stress tests) add depth and reliability.

• Interpret results carefully, isolating issues component by component.

• Fix, replace, or optimize based on findings; retest afterward.

• Preventive habits (cooling, updates, airflow, power stability) reduce future hardware failures.

If you follow this guide step by step, you’ll gain confidence in diagnosing PC faults, avoid guesswork, and understand your system’s health more clearly. Need help interpreting logs or choosing a tool? Just ask — I’m