The best approach is to choose the tool that matches your symptom, then investigate before making changes. Diagnostics should reduce guesswork, not give it a more impressive dashboard.
1. Reliability Monitor: Find when trouble started
For recurring application crashes or unexplained Windows failures, Reliability Monitor is a sensible first stop. It presents recorded failures and other reliability events in a dated history, making patterns easier to spot than they would be in a sprawling collection of logs. Dell’s support documentation describes both its timeline and ways to open it.
On Windows 11 or Windows 10:
- Press Windows + R.
- Enter
perfmon /reland press Enter. - Select a date associated with the problem.
- Inspect the relevant event and its available technical details.
Microsoft formally documents /rel as the switch that opens Reliability Monitor; Dell documents the Run-dialog procedure and event inspection. No third-party download is required.
Look for repeated failures involving the same application, or a change that coincides with the start of instability. Treat that timing as a lead—not proof that the most recent update caused everything.
Its boundary: This is a history of recorded events, not a retrospective recording of CPU temperatures or fan speeds. For live hardware readings, HWiNFO serves a different purpose.
2. Windows Repair Toolbox: Organize an investigation
Windows Repair Toolbox is primarily a portable launcher and organizer for other utilities, rather than one diagnostic engine. Its developer says it categorizes tools, downloads suitable versions and helps keep them updated. It can also download tools beforehand for use on an offline computer. The listed compatibility range is Windows 7 through Windows 11.
That makes it particularly useful for technicians who repeatedly troubleshoot different machines. The toolbox includes access to common Windows commands such as chkdsk, sfc and DISM, alongside RAM information and a graphical interface for the Sysinternals Suite.
A cautious workflow is to:
- Identify the symptom before selecting a utility.
- Start with information gathering.
- Review what a repair operation changes before running it.
- Preserve diagnostic results so you can assess whether a change helped.
The developer warns that some tools can trigger antivirus false positives and that third-party utilities retain their own licensing requirements. That warning is not permission to dismiss every detection or switch off protection. Investigate unexpected alerts rather than treating a toolbox as a blanket guarantee of safety.
Its boundary: Convenience does not replace diagnosis. Having a drawer full of spanners does not tell you which bolt is loose.
3. HWiNFO: Observe hardware while the problem happens
HWiNFO focuses on hardware identification, real-time monitoring and reporting. Its publisher describes detailed component information, status logging and integration with other tools or add-ons. This makes it complementary to Reliability Monitor: one helps examine recorded failures; the other helps observe hardware behavior.
For an intermittent performance problem, a useful investigation is to:
- Identify the installed components.
- Observe the available readings during normal use.
- Compare them while performing the task associated with the slowdown.
- Save a log if you need to examine changes over time.
HWiNFO’s official feature description supports both live monitoring and status logging, although the readings available depend on the system.
The analytical caution is straightforward: a number is not a diagnosis. A reading that looks unusual needs context from the component, workload and surrounding symptoms. Avoid replacing hardware merely because one value catches your eye.
Its boundary: HWiNFO provides evidence to interpret, not an automatic verdict. For workplace deployment, review its licensing rather than assuming that a free download authorizes every use.
4. MemTest86+: Test memory outside Windows
MemTest86+ is a free, open-source, stand-alone memory tester. It runs independently of Windows, making it useful when investigating crashes, freezes and instability that might involve memory. It is distinct from PassMark’s similarly named MemTest86.
The project’s Windows USB procedure is:
- Prepare a FAT32-formatted USB drive.
- Run the Windows USB Installer and follow its prompts.
- Restart and select the USB drive in the PC’s boot menu.
- Let testing proceed and record any errors.
Back up the USB drive’s contents before preparing installation media. The project explains that testing loops continuously: a completed pass without errors is encouraging, while additional testing can increase confidence.
Secure Boot can prevent startup. The project documents certificate enrollment or temporarily disabling Secure Boot as alternatives; neither should be treated as a casual click-through. Restore any temporarily disabled protection after testing.
Before changing firmware settings on an encrypted PC, ensure you have access to the BitLocker recovery key. Microsoft documents that certain UEFI configuration and Secure Boot database changes require BitLocker precautions and can otherwise trigger recovery. On a managed machine, involve IT.
Its boundary: Errors warrant investigation, but do not necessarily identify one defective module. The project recommends retesting overclocked systems at defaults, then isolating modules where appropriate.
5. TreeSize: Explain where storage went
TreeSize answers a narrower question: which files and folders are consuming storage? JAM Software describes folder-level breakdowns and visualizations, including treemaps, that help reveal large consumers. That is capacity analysis—not proof that an SSD or hard drive is healthy.
For a straightforward investigation, scan the relevant drive or folder, expand the largest branches and examine their contents before deciding what to remove. The useful result is an identifiable source of storage consumption, not simply a collection of large rectangles.
Edition boundaries matter:
- TreeSize Free is listed for private, non-commercial desktop use.
- Its advertised features include file-level visualization, a treemap and PDF reports.
- Duplicate searches, dedicated largest-file filtering and comparisons over time are listed with paid editions.
- JAM Software says TreeSize Free is not usable on Windows Server.
Its boundary: Size is not permission to delete. Review a file’s purpose, ownership and location first—especially for Windows folders, application data and shared business files. Prefer an application’s own cleanup or uninstall controls when appropriate.
Diagnose first, repair second
These five tools are useful precisely because they are not interchangeable. Start with a question: What failed? What changed? What happens under load? Is memory producing errors? Where did the space go?
Then collect evidence, make one justified change at a time and repeat the original task to assess the result. A quieter error log or a cleaner-looking chart is welcome; a reproducibly working PC is the real finish line.
References
- 5 Powerful PC Tools That Can Help Diagnose Problems - BGR BGR · 2026-11-16T02:47:00+00:00
- How to Use Windows Reliability Monitor to Identify Software Issues | Dell US dell.com
- BitLocker FAQ | Microsoft Learn learn.microsoft.com