When a PC starts crashing, freezing or throwing errors, the hardest part is often working out when it started and what changed. Windows has a built-in tool for exactly that: Reliability Monitor. It shows a timeline of app failures, Windows failures, hardware errors and software installs, so you can line up the first crash with the driver, update or app that arrived the same day. This guide is based on Microsoft's documentation and Dell's support guide. Forge PC hasn't tested it against specific faults; it's a diagnostic tool, not a fix in itself.
How to open Reliability Monitor
There are three quick ways:
Start menu search: type reliability and select View reliability history.
Run box: press Windows + R, type perfmon /rel and press Enter. The same command works in Terminal or Command Prompt.
Control Panel: go to System and Security > Security and Maintenance, expand Maintenance and select View reliability history.
Microsoft's support team has confirmed that these routes, along with opening it from within Performance Monitor, all lead to the same tool.
How to read the stability chart
The top of the window is the System Stability Chart. Microsoft explains that its upper half plots a Stability Index, while the rows underneath mark reliability events by date with an icon on each day they happened. Dell's guide notes that each column is a day or a week, depending on the View by setting, and that events are listed by severity: critical first, then warnings, then information.
Microsoft's documentation for the tool (written when it was introduced, so some labels may differ slightly in Windows 11) describes these kinds of events:
Application failures: an app that stopped working or stopped responding, with its name and version.
Windows failures: operating system crashes and boot failures. For a crash, the details include the stop code, which you can look up in our blue screen guide.
Miscellaneous failures: other events that affect stability, including unexpected shutdowns where the PC wasn't shut down cleanly.
Hardware failures: disk and memory failures.
Software installs and uninstalls: Windows updates, drivers and apps, marked as successful or failed.
Microsoft says Reliability Monitor keeps up to a year of history, so you can scroll back to well before the problems started.
Find out what happened on a bad day
Click the column for a day with a red error icon.
The list underneath shows that day's events, most serious first.
Click an event, or choose View technical details, to see more, such as the name and version of the app that failed and the faulting module.
Dell's guide makes a useful point about those details: if a core Windows file such as KernelBase.dll appears as the faulting module in an app crash, the problem usually lies with the app itself or an add-on it uses, not with Windows.
Use the timeline to spot the cause
The real value is seeing patterns. Microsoft suggests looking at whether significant changes in stability began at the same time as something else, such as a software install or a hardware failure. Some examples of how to act on what you see:
Crashes started the day a graphics driver installed: roll it back with our driver rollback guide, or do a clean install with DDU.
Problems began after a Windows update or new app: uninstall it, or use System Restore to go back to before it arrived.
One app keeps failing: Microsoft's advice is to update the failing application; check the developer's website for a newer version. Dell resolved one old app's crashes using Windows' compatibility troubleshooter.
Lots of unexpected shutdowns: that points away from software. See our guide to a PC that randomly restarts or shuts down.
Crashes in many different apps: Microsoft notes that memory failures appearing alongside widespread app failures can point to faulty RAM. Test it with MemTest86, and check your drive with our SSD health guide.
Our verdict
Open Reliability Monitor with perfmon /rel or by searching for "reliability", click the first day with red error icons, and check what else installed or changed that day. It won't fix anything on its own, but it's often the quickest way to connect a crash to the driver, update or app that caused it. Forge PC hasn't tested it against specific faults; the steps follow Microsoft's and Dell's guides.