← All Documentation
What is the Event Log?
Windows constantly logs interesting things that happen — services starting, apps crashing, drivers loading, logins succeeding, errors from the kernel. It's an invaluable record, but the built-in Event Viewer is notoriously intimidating: dozens of log categories, cryptic event IDs, and walls of raw XML. TuneBit's Event Log Viewer takes the same data and shows you just the interesting stuff.
Features
- Curated level filter. Show only Critical and Error events by default — the ones that actually indicate trouble.
- Time range. Last hour, last day, last week, last month, or everything.
- Combined view. Application, System, and Security logs all in one list.
- Inline details. Click any entry to read the full event message in the panel below — no drilling into properties.
- Export. Save the filtered list to a file to share with support.
How to use it
- Go to Diagnose → Event Log.
- Pick a filter level. Errors and Critical is almost always the right starting point.
- Pick a time range. Last 24 hours is useful when you've just noticed a problem.
- Scroll the list. Each row shows time, level, source (which Windows component logged it), event ID, and a short description.
- Click a row to see the full message in the details panel.
- Use Export to save what you're looking at to a text file.
Common event sources to pay attention to
- Disk — hardware errors on a drive. Often a sign of a failing hard disk or bad cable.
- Kernel-Power — unexpected shutdowns. Event ID 41 typically means the PC lost power or froze.
- Service Control Manager — services that failed to start.
- Application Error — a program crashed. Paired with the program name and a faulting module.
- DistributedCOM — usually harmless permission warnings; typically safe to ignore.
Noise warning: Even a healthy PC logs dozens of errors per day. Perfectly normal stuff — a printer driver grumbling, a background service retrying — fills the log. Look for patterns (same event, repeating) rather than individual entries.
Security log requires admin rights. If the Security log is empty when you expect data, make sure you're running TuneBit as Administrator. TuneBit usually elevates automatically, but re-launch with Run as administrator if you skipped the prompt.