EventAnalyzer

You sit down at a machine that "freezes now and then". Event Viewer holds twenty thousand records, a thousand of them red, and nine hundred of those are the same line over and over. Digging out what matters eats half an hour.

EventAnalyzer scans in a few seconds and hands back a list of findings ordered by what actually threatens the machine. Every finding comes with an explanation, how many times it happened, when it last occurred and what can be done about it.

Everything sits in one EventAnalyzer.exe, with no installer. Reading the logs does not need administrator rights — it asks for them only when they are genuinely required.

Every common error has a rule that turns it into a sentence that makes sense — and where no rule exists, it is at least read generically by severity. Nothing is thrown away.

Status and stop codes are decoded, so instead of 0x80073712 you see what went wrong.

Findings are grouped by impact, not merely by severity:

• Critical — the system is unstable: crashes, power loss, disk errors, hardware faults.
• Functional — one specific thing is broken: a service keeps dying, an update will not install, the printer stays silent.
• Noise — errors Windows logs constantly that mean nothing. They do not disappear, but they stop dominating the summary and only count towards the score once they become excessive.

It all adds up to a health score of 0–100 %. Repetitions are scaled logarithmically and the period is normalised, so a month of history does not look more dramatic than a single day.

For each finding the program picks fixes from a catalogue of around thirty procedures — from system file and disk checks through service recovery, Windows Update and network stack resets, to memory testing and dump configuration. Every fix states its purpose, the exact script, the level of risk, whether a restart is needed, an estimate of the time and how to verify the result.

• You see the plan before anything happens — the steps, the reasons and the full script, which you can edit.
• A restore point is the first step of every plan. You can untick it, but you can see that it is missing.
• Running it from the app is not required. The plan exports as .ps1 or .bat, or goes to the clipboard to be run elsewhere.
• After a fix the scan repeats and is compared with the previous one: how many findings are gone and how the score moved.
• Scripts and their output are kept, so there is a record of what was done to the machine.

Save report… writes a self-contained HTML file: the verdict, summary tiles, a timeline of error occurrences, the individual findings with their commands, memory dumps, the chain of events before a crash, a recommended order of work, a machine inventory and the history of fixes applied. It opens offline and travels as a single attachment. A plain-text variant is there for the helpdesk.

Without opening the window:

EventAnalyzer.exe --report C:\out\pc01.html --days 7

The exit code is 0 for a healthy machine and 1 for an unhealthy one, which makes it straightforward to run from a logon script or a monitoring system (RMM) and collect results from every machine at once.