ComputerManagement.us
Menu

[preview]Notebook Pass $1.95 a month or $19.50 a year // Free during preview. Billing is off, so nothing is charged and every Pass feature is open. Compare free and Pass

Windows stability report

Why did it crash? Ask the computer.

Windows writes down every blue screen, sudden restart, failing disk and driver reset. Hand us that log and get it back in plain English: what happened, how often, what it usually points to and what to try first.

Free report · nothing to install · the log is read once, then deleted

Sample report14 days · Windows 11 laptop
Watch

1 blue screen: DRIVER_POWER_STATE_FAILURE, a driver did not finish a sleep or wake in time. 3 graphics resets. Next: newest drivers from the maker.

Three steps, about two minutes

Take the log off the computer, read it here.

  1. 1

    Open PowerShell

    Press the Windows key, type PowerShell, press Enter. No administrator rights needed.

  2. 2

    Paste this one line

    It only reads the event log and saves the events this report uses to crash-log.csv on your Desktop. It changes nothing.

  3. 3

    Upload the file

    Choose crash-log.csv on the Crash Reader. The report appears at once.

What the report reads

Eleven things Windows records when something goes wrong.

Each one is matched by the program that wrote it and its event number, the way Windows itself files them, so an unrelated event with the same number is never counted.

How each one is read
FindingWindows event
Blue screens (stop errors)BugCheck 1001
Unexpected restartsKernel-Power 41 / EventLog 6008
Disk warningsdisk 7, 51, 153
File system damageNtfs 55
Fatal hardware reportsWHEA-Logger 18
Corrected hardware reportsWHEA-Logger 17, 19, 47
Graphics driver resetsDisplay 4101
Failed updatesWindowsUpdateClient 20
Service crashesService Control Manager 7031, 7034
Program crashesApplication Error 1000
Program hangsApplication Hang 1002

One verdict, by published rules

No mystery score. Three flags, and the reason each was raised.

Act now

A fatal hardware report, a bad block or paging error on a disk, file-system damage, or two or more blue screens. Back up first.

Watch

One blue screen, a retried disk read or write, three or more unexpected restarts or graphics resets, a stream of corrected hardware errors, or repeated failed updates.

Steady

Nothing above. Program crashes and service restarts are still listed, by name, so you can see which one misbehaves.

Stability Notebook

Fixed it? Prove it.

Save a reading, note what you changed ("new memory fitted"), read the log again in a few weeks and see the before and after side by side: restarts per week, blue screens, disk warnings. Hand the printed sheet to a repair shop instead of describing it from memory.

Only the summary is saved: counts by day, stop codes and program names. Never the log itself; only the name you give each computer, never its network name. Opened by a private link; no account, no email.

Free

$0

  • Crash Reader: every report, up to 120 reads a day from one address
  • Stop code lookup, all 379 codes
  • Notebook: 1 computer, 3 saved readings
  • Repair-shop sheet for that computer
Read a log

Notebook Pass

$1.95 a month

or $19.50 a year (two months free)

  • 10 computers, 60 readings each
  • Before / after comparison around a change you made
  • One sheet for every computer, ready to print
  • CSV download of every reading

Preview Free during preview. Checkout opens when payments are connected; nothing is charged before then.

Questions people ask first

Is it safe to run the PowerShell line?

It uses two standard Microsoft commands: Get-WinEvent reads events, Export-Csv writes them to a file on your Desktop. It changes no setting, sends nothing anywhere and needs no administrator rights. Read it before you paste it; that is good practice for any command.

What does the file contain?

Date and time, event number, the Windows component that wrote it, which log, and the event's message. Messages can include program names and file paths. The reader keeps only the stop code, update number, service or program name. An uploaded file is deleted as soon as it has been read; it is never stored here.

Can it fix the crash?

No. It tells you what Windows recorded and what that usually points to, with Microsoft's own page for each stop code. The fixing is done by you, or by a repair shop you hand the sheet to.

Mac or Linux?

Not yet: this reader is for Windows 10 and Windows 11.