Windows has been keeping a diary of your drive's bad days — it just spreads the entries weeks apart so nobody notices. Filtered into one timeline, those occasional warnings are the earliest written evidence of a hidden drive fault.
Most users open Event Viewer once, see a wall of red and yellow, and close it forever. The trick is not reading everything — it is reading one filtered timeline. A single disk warning after a power cut is noise. The same warning appearing twice this week, four times next week, and in a burst at the exact minute your PC froze is a drive writing its own medical history. Hidden faults live in that gap: each incident is small enough to ignore, and Windows recovers from most of them, so the PC 'seems fine' — while the log quietly shows the incidents getting closer together. This page shows you which entries to collect, what the common IDs honestly mean, and how to match them against your freezes.
eventvwr.msc and press EnterYou are looking for a rhythm: how many entries per week, and whether that number is growing. Export or screenshot the list — this timeline is evidence you can hand to any technician, and it survives even if the drive later dies completely.
Exact wording varies a little between Windows versions and controller drivers, but these are the regulars:
File-system sources add their own: Ntfs events such as 55 or 98 report corruption in the file system's structures — the damage has reached the level where Windows' bookkeeping itself is being hurt.
One Event 7 in six months, on the day the power failed, is an anecdote. The hidden-fault signature is acceleration: entries that were monthly become weekly, weekly become daily, and daily start arriving in clusters. Acceleration means the underlying cause — surface damage spreading, a head weakening, a connection loosening — is getting worse on its own schedule, not yours. This is also why a technician who only looks at today's log will miss it: today's log may hold a single mild retry. The diagnosis is in the shape of the month, so always scroll back before concluding anything.
The strongest evidence you can produce is a coincidence of timestamps. Next time the PC freezes for twenty seconds, note the time. Then find that minute in the filtered log. A cluster of 153 retries or a 129 reset at exactly that minute ties the symptom to the storage chain with no guesswork — the freeze was the drive (or its connection) stalling, not a random software hiccup. Two or three such matches close the case. Conversely, freezes with a completely silent disk log point you elsewhere — towards RAM, drivers or software — which is equally valuable to know.
Honesty requires this page too: a clean disk log does not clear the drive. Mechanical problems — the shaking, catching and clicking from the hold-and-listen test — can be well advanced while the controller still completes most operations without logging retries. And some failing drives stall in ways Windows attributes to other sources. Treat the log as one witness. If the physical signs and SMART trends accuse the drive, a quiet Event Viewer is not an acquittal — it just means this particular witness saw nothing. Back up, and keep the physical evidence in charge.
Watch the video for the complete hidden-fault check, including the physical signs the log cannot record.
▶️ Watch Full VideoOne isolated entry — especially after a power cut, a forced shutdown or a crash — is usually noise. Drives log occasional retries across a long life. Worry about the pattern instead: entries repeating weekly, growing more frequent, or arriving in bursts at the same times your PC freezes. That acceleration is the real warning sign, and it deserves a backup and closer checks.
Event 153 means an IO operation was retried — Windows asked the drive again and usually succeeded, which is why the PC often just pauses and recovers. Event 7 means the drive reported a bad block, actual damaged surface. Retries are the earlier, softer signal; bad blocks are confirmed damage. Both belong in your timeline, but a drive producing Event 7 should already have its replacement planned.
A clean disk log removes one suspect, not all of them. Freezes also come from RAM faults, overheating, driver problems and software. And a mechanically failing drive — clicking, shaking, catching — can disturb a PC while logging little. Run the physical hold-and-listen check and read the SMART raw values; if those accuse the drive, trust them over the silent log.