Short answer
Download EventAnalyzer, run it and let it scan the logs for, say, the last 7 days. It reads the memory dumps (minidumps) Windows saves after a blue screen, extracts the stop code and turns it into a plain sentence. For each crash it also shows what happened in the ten minutes before and proposes a concrete fix.
Step by step
-
Download and run EventAnalyzer
A single
EventAnalyzer.exe, nothing gets installed. Reading the logs needs no administrator rights, but Windows does not open the crash dump folder without them: to see the stop codes from minidumps too, right-click the program and run it as administrator. -
Choose the period
The options are 6 hours, 24 hours, 3, 7 or 30 days, or since the last boot. For blue screens that come once every few days, pick 7 or 30 days.
-
Go through the critical findings
Findings are ordered by impact. Crashes and blue screens are critical, so they sit at the top. Each one shows the number of occurrences, the time of the last one and an explanation. The stop code and its parameters are read straight from the minidump.
-
See what led up to the crash
For crashes, unexpected restarts and blue screens, EventAnalyzer collects every event from the ten minutes before. That is usually where the real cause shows: a disk error five seconds before the crash, a failing graphics driver, or a power loss.
-
Run or export a fix
For each finding the program picks fixes from a catalogue of around thirty procedures, such as a system file and disk check or a memory test. You see the whole plan in advance, and its first step is a restore point. Run it directly, or save it as
.ps1or.bat.
What usually causes a blue screen
- A driver. The most common cause, typically graphics, network card or antivirus. Updating or rolling back the driver helps.
- The disk. Read errors in the log right before the crash point to a failing disk or a bad cable. Check it with a disk health test.
- Memory. Random crashes with a different stop code each time are typical of a faulty RAM module. See how to test memory.
- Damaged system files. An SFC and DISM repair helps; EventAnalyzer offers it in the plan.
- Heat and power. A crash under load, in a game for instance, may be temperature or a weak power supply. PCHealthLab measures temperatures under load.
Things to keep in mind
- Without administrator rights the program cannot read the crash dump folder, and the tile says so. The other findings still show.
- Fixes change the system. Read the plan, and on someone else's computer leave the restore point enabled. The program never runs anything on its own.
- After a fix the scan repeats and is compared with the previous one, so you see how many findings are gone.
- The interface is in English; the event texts come in the language of Windows.