Event Viewer is powerful but overwhelming. Windows Reliability Monitor is the friendlier tool most gamers never open: a timeline that plots every crash, freeze, failed update, and driver problem against dates, so you can see at a glance what changed right before your games started crashing. It is built into every Windows install and takes seconds to open.
Opening Reliability Monitor
Press Start, type reliability, and choose “View reliability history.” You will see a graph scored from 1 to 10 with columns for each day. Red circles are critical events (crashes), yellow triangles are warnings, and blue “i” icons are informational, like successful software installs. A dropping stability line that coincides with a new driver or app is your smoking gun.
What the icons tell you
| Marker | Meaning | Why it matters for gaming |
|---|---|---|
| Red circle | Application or Windows crash | Names the .exe that failed |
| Yellow triangle | Warning / failed install | Driver or update that did not apply |
| Blue info | Successful install/update | Correlate changes with new crashes |
Reading a crash entry
Click a red event and choose “View technical details.” You get the faulting application name, the faulting module, and an exception code. If your game’s .exe crashes with a faulting module of nvwgf2umx.dll that points to the graphics driver; ntdll.dll is generic and usually means you need the deeper Event Viewer log or a memory test. The value is the timeline: if crashes all started the day you installed an overlay or a driver, you know exactly what to revert.
Turning patterns into fixes
Look for correlation, not a single event. Three crashes clustered right after a GPU driver update strongly suggests a clean DDU reinstall or a rollback. A crash every time Windows Update ran points at a bad optional driver. Frequent crashes with different faulting modules often mean unstable RAM (test with MemTest86) or an over-aggressive overclock.
When to escalate to Event Viewer
Reliability Monitor is the overview; Event Viewer is the microscope. Once Reliability Monitor tells you which app and roughly when, open Event Viewer’s Windows Logs to read the full error, stack, and any bugcheck code for blue screens. Using the two together is far faster than scrolling Event Viewer blind.
Turn history into a maintenance habit
Reliability Monitor is most useful when you glance at it regularly, not only after disaster strikes. A quick weekly look reveals slow-building problems — a driver that fails to install every update cycle, an app that crashes a little more often each week, or storage warnings that precede a failing drive. Catching these early is far cheaper than reacting to a total failure mid-tournament.
Export and correlate
You can save the reliability history to an XML report to compare over time or share when asking for help on a forum. Pair the timeline with your own change log: note the date whenever you update a GPU driver, change an overclock, or install a new overlay. When crashes appear, lining them up against your notes usually points straight at the culprit without any deep log diving.
Remember that a single isolated red event is rarely worth chasing — software crashes occasionally for benign reasons. It is the pattern, a cluster of failures tied to one app or one date, that tells you where to spend your troubleshooting time.
FAQ
Reliability Monitor is empty — why?
It relies on a scheduled task that can be disabled by “optimizer” tools. Re-enable the RACAgent scheduled task under Microsoft > Windows > RAC, and data will begin accumulating again from that point on.
Can it show crashes from before today?
Yes. It keeps weeks of history by default. Switch the view from Days to Weeks to spot longer-term patterns, such as a driver that crashes only after certain updates.
Bottom line: Reliability Monitor is the fastest way to correlate game crashes with what changed on your PC. Read the timeline, click red events for the faulting module, and use the pattern to decide whether to roll back a driver, test RAM, or dial back an overclock — then confirm details in Event Viewer.
