Pulse v1.6.0 — Crash history

What crashed on this PC lately, how often, and why? The new Crashes page answers that from the Windows Event Log, in plain language.

New

• Crashes page (sidebar, under Timeline; Ctrl+2). Blue screens, app crashes, apps that stopped responding, unexpected restarts, graphics driver resets, service crashes and hardware errors of the last 7, 30 or 90 days. A one-sentence overview, a counter per category that filters the list, and a bar for each day.
• Grouped by cause. The same crash is listed once with how often it happened: an app crashing in the same file with the same error, a blue screen with the same stop code, a service, a graphics driver. A blue screen that Windows records twice (Kernel-Power 41 and the bug check report) counts once.
• Why it crashed. Each group says what happened in plain language and what to try next. For app crashes Pulse names the file the crash happened in and whether it is the app's own, part of Windows, part of a device driver or another program loaded into the app, with the publisher from the file's version information. Error codes come from Windows' own definitions; an unknown code is shown as it is, never guessed.
• Versions and events. A group lists the app versions it happened on and its latest events; each opens in the Timeline's Explained, Technical and Raw XML views.
• Crash history report as JSON, CSV, HTML or PDF. Like every report, it masks user and computer names and profile paths by default.
• Assistant: a read-only crash history tool, so the local Assistant can answer "what crashed this month?". It gets no file paths.

Changes

• App crashes in the Timeline name the app. "Discord Crashed: Discord closed unexpectedly after a memory access error. The error happened in nvwgf2umx.dll, part of a device driver." instead of "Application Crashed". Apps that stop responding and crashed services are named too.
• Keyboard shortcuts follow the sidebar. Ctrl+1 Timeline, Ctrl+2 Crashes, Ctrl+3 System Health, Ctrl+4 Inventory, Ctrl+5 Reports, Ctrl+6 Diagnostics, Ctrl+7 Settings.

Fixes

• Blue screens, sudden restarts and wake-ups that were already in the Timeline when Pulse started showed the generic wording; only later events got the detailed explanation.

How it works

PulseService reads crash events from the System and Application logs only when you open the Crashes page (at most every two minutes), press Refresh or export a report, or when the Assistant asks. Nothing runs in the background, nothing leaves the PC, and Windows is never changed. Details: 43 — Crash history.

Not yet

• Minidump analysis. Reading C:\Windows\Minidump needs administrator rights and the Windows debugger engine. It is planned as a separate step you start yourself.
• Windows keeps a limited amount of log history, so on a busy PC older crashes may already be gone.

Upgrade notes

• Confirm Diagnose → Service shows 1.6.0 after installing. An older PulseService cannot answer the Crashes page; it then asks to update.
• Event types hidden in the Timeline stay hidden there; the Crashes page lists every crash.

Downloads

Windows x64 Installer

Pulse-Setup-1.6.0-windows-x64.exe

Payload ZIP

Pulse-1.6.0-windows-x64.zip (PulseService is still required; see portable vs service)

Checksums

SHA256SUMS.txt

Pulse remains read-only and local-first: no telemetry, no cloud, no account.