Counts that add up

An accuracy release for how the app reports crashes. When Windows quietly recovers from a stalled component, the app no longer mistakes that for an application crash or invents an app called '193', and a single unexpected shutdown is now counted once instead of twice, even on PCs whose date format writes the day before the month.

• When Windows quietly recovers from a stalled component, like a driver that hangs and heals on its own without a blue screen, the app no longer mistakes those reports for application crashes. It used to show lines like 'A Windows component (193) restarted 15 times' and could even suggest reinstalling an app called '193'. It now says in plain English that Windows recovered from a stalled component, counts each distinct incident once even when Windows re-logs old reports, and suggests checking for display driver updates when the reports point at the graphics stack.
• One unexpected shutdown is no longer counted twice. Windows records the same power loss or hard reset in two places at the next boot, and the app now pairs those records and counts the incident once, while keeping two genuinely separate crashes apart, including on PCs whose date format writes the day before the month.
• Behind the scenes, the health summary the local AI reads now follows the same no-raw-codes rule as the chat window, the scan-history comparison, audio-device classification, and safety pre-checks are now one shared implementation instead of two copies, and internal test counts moved into a single registry. None of this changes what you see.