Reliability Monitor is a built-in Windows tool that tracks system stability over time, recording app crashes, Windows failures, warnings, and informational events. This guide shows you how to open it and read the history to identify what’s causing blue screens or app freezes—no extra software needed.
What You’ll Need
- A PC running Windows 11 (any edition)
- Administrator rights (to view some system events, though basic viewing usually works without them)
Step-by-Step
- Open the Start menu by pressing the Windows key on your keyboard or clicking the Start button on the taskbar.
- Type “Reliability” in the search box. You’ll see “View reliability history” appear in the search results. Click it.
- Wait for the chart to load. Reliability Monitor opens a window showing a timeline graph, usually covering the last few weeks. The vertical axis is a stability index from 1 to 10; the horizontal axis shows dates.
- Look for red circles and red X marks. Red circles indicate a critical event (like a system crash or unexpected shutdown). Red X marks are app crashes. Yellow triangles are warnings (e.g., a driver failed to load). Blue “i” icons are informational events (like Windows Update).
- Click on a specific day in the chart. The bottom pane updates to list all events recorded for that day, sorted by time. Each entry shows the event type, source, and a short description.
- Double-click any event to open a detailed report. This report includes technical details like the faulting module, exception code, and the exact time of the failure. For app crashes, it often shows the path to the executable and the error code.
- Use the “View all problem reports” link (located at the bottom of the window) to see a complete list of every recorded issue, not just the ones on the visible chart. This is useful for finding patterns over a longer period.
- Check the stability index trend. The line graph at the top shows the overall stability. A steady decline from 10 to 3 over several days suggests a recurring problem, while a single dip followed by a recovery might indicate a one-off event.
Common Mistakes
- Misreading the stability index. A score of 10 does not mean “no problems ever”—it means no system or app failures occurred during that period. Warnings and informational events do not lower the score.
- Ignoring the time column. Two crashes on the same day might look similar, but if they happened hours apart, they could have different causes. Always check the timestamp before investigating.
- Assuming every red X is a serious problem. Some apps crash on exit (e.g., when you close them), which is often harmless. Look at the frequency and whether the app actually misbehaved.
- Only looking at the current day. The chart defaults to the most recent period, but the real value is spotting a pattern over weeks. Use the scroll bar or the “View all problem reports” link to see the full history.
- Not checking the event details. The summary line often says “Windows stopped working” but the detailed report contains the actual faulting module (like a .dll file) that caused the crash. That detail is essential for a fix.
Tips
- Take screenshots of the chart before you fix anything. If the problem returns, you’ll have a baseline to compare.
- Use the “Copy” button in the detailed report window to save the crash data to a text file. You can then search for the faulting module name online (e.g., “nvlddmkm.dll crash”) to find known fixes.
- Pair Reliability Monitor with Event Viewer. For a deep dive, open Event Viewer (search for it in Start), go to Windows Logs > System, and filter by the exact time of a crash. Reliability Monitor gives you the “what,” Event Viewer gives you the “why” in more technical detail.
- Check for driver updates first. Most critical events in Reliability Monitor are caused by outdated or buggy drivers, especially graphics, network, and chipset drivers. Update those before reinstalling Windows or replacing hardware.
- Note the “Source” column. It tells you which component logged the event (e.g., “Windows,” “Application Error,” “Kernel-Power”). Kernel-Power events with code 41 often point to power supply or overheating issues.
Troubleshooting
Reliability Monitor won’t open. If nothing happens when you click “View reliability history,” try running it from the command line. Press Win + R, type perfmon /rel, and press Enter. If that fails, your system may have corrupted performance counter files. Run sfc /scannow in an elevated Command Prompt to repair system files.
The chart is empty. Reliability Monitor only starts collecting data after the system has been running for a while. If you just installed Windows or cleared the history, you’ll see a blank chart. Wait a few days and check again. Also, ensure the “Diagnostic Policy Service” is running: press Win + R, type services.msc, find “Diagnostic Policy Service,” and set its startup type to “Automatic” if it’s disabled.
No red X’s but you’re still getting crashes. Reliability Monitor only records events that Windows knows about. If your PC freezes completely and you have to force a shutdown, that will appear as a “Kernel-Power” critical event. But if the crash is so severe that the system doesn’t write an event, you may need to check the Windows minidump files (C:\Windows\Minidump) for blue screen analysis.
The stability index is stuck at 1. This usually means multiple critical events occurred. Click each red circle to see what happened. If you see a repeating pattern (e.g., the same driver every time), that’s your culprit. If the events are all different, consider checking for overheating or failing RAM with a memory diagnostic tool.
You can’t see events from more than a few weeks ago. Reliability Monitor keeps data for about a year, but it may purge old entries if the log grows too large. If you need long-term history, you should export the current view regularly (there’s a “Save reliability history” button) or rely on Event Viewer’s Windows Logs, which retain more data by default.
Frequently Asked Questions
Q: Does Reliability Monitor show blue screen (BSOD) errors?
A: Yes, but indirectly. A BSOD typically records a critical event labeled “Windows stopped working” or “Kernel-Power” with a bugcheck code. The detailed report often includes the stop code (e.g., 0x0000001A). For the exact blue screen message, check the minidump files with a debugger.
Q: Can I delete the history shown in Reliability Monitor?
A: No, there’s no built-in button to clear it. You can, however, delete the underlying data files in C:\ProgramData\Microsoft\Diagnosis\RAC, but that’s not recommended unless you’re troubleshooting a corrupted log. The history will naturally roll off after about a year.
Q: Why does Reliability Monitor show a warning for a program that works fine?
A: Warnings are logged for any non-critical failure, like a driver failing to load or a program ending unexpectedly. It doesn’t mean the program is broken—just that something didn’t complete cleanly. Check the details before worrying.
Q: Is Reliability Monitor the same as Event Viewer?
A: No. Event Viewer is a raw log of thousands of events, while Reliability Monitor is a curated, visual summary focused on failures and warnings. They use the same underlying data, but Reliability Monitor is designed for easier human reading.
Q: Will fixing the issues shown in Reliability Monitor improve my PC’s performance?
A: Not necessarily. Reliability Monitor tracks stability, not speed. A crashing driver can cause slowdowns, but a clean history doesn’t guarantee a fast PC. Use Task Manager or Performance Monitor for performance issues.
Q: Can I use Reliability Monitor to diagnose hardware problems?
A: It can help. For example, repeated “Kernel-Power” critical events with no preceding warning often indicate power supply, overheating, or RAM issues. But it won’t tell you which component is faulty—you’ll need additional hardware diagnostics.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Gmail Notifications Not Working? Fixes That Work
- Fix Thumbnails Not Showing on Network Drives in Windows 11
- Stop Skype Auto-Start in Windows: 5 Fixes
- SQL Injection Prevention: Step-by-Step Guide
- Fix Windows PowerShell Popping Up
- Print iMessage or Text Conversations on iPhone & iPad