Short answer
A red line in Event Viewer does not mean there is a problem. Instead of going through them one by one, run EventAnalyzer: it scans the logs for the chosen period, merges identical errors into one finding with an occurrence count, sorts them into critical, functional and noise, and explains each in a plain sentence. The critical findings are the ones that deserve attention.
Step by step
-
Run EventAnalyzer
A single file, nothing gets installed. It reads the System, Application, Security and Setup logs and dozens of other channels, from the file system through disks and drivers to Windows Update. An optional deep scan walks every enabled channel.
-
Choose the period
6 hours, 24 hours, 3, 7 or 30 days, or since the last boot. The score is normalised for the length of the period, so a month of history does not look more dramatic than a single day.
-
Look at the score and the tiles
At the top is a health score of 0–100 % and the finding counts, with the error timeline below. It shows whether errors piled up on a particular day, after an update or a driver install for instance.
-
Open a finding and read the explanation
Every common error has a rule that turns it into a sentence. Status and stop codes are decoded, so instead of
0x80073712you see what went wrong. System device names are translated into an actual disk with its model and volume letter. -
Save a report
Save report… writes a self-contained HTML file with the verdict, the timeline, the findings with their commands and a recommended order of work. There is also a text version for helpdesk use.
Which errors matter
| Group | What belongs there | What to do |
|---|---|---|
| Critical | Crashes, power loss, disk errors, hardware faults. | Deal with it now. |
| Functional | One specific thing is broken: a service keeps dying, an update will not install, the printer stays silent. | Fix it if that thing bothers you. |
| Noise | Errors Windows logs constantly that mean nothing. | Ignore, unless they become excessive. |
Noise does not disappear from the overview; it just stops dominating the summary and only counts towards the score once there is an unusual amount of it.
Things to keep in mind
- Without administrator rights the Security log and some disk health data are skipped. The program says so and carries on.
- The interface is in English; event texts come in the language of Windows. Merging and rules work on identifiers, so the system language does not matter.
- A disk that is no longer in the machine is labelled as such and does not count towards the score.