Short answer
Run EventAnalyzer and let it scan the logs for the last 7 days. A frequent cause of freezes is disk errors (Windows waiting for a disk that does not answer), followed by crashing drivers and services. The program puts them at the top among the critical findings, translates system names into an actual disk and proposes a fix.
Step by step
-
Run EventAnalyzer as administrator
It also runs without administrator rights, but then skips some disk health data. With freezes, disks are suspect number one.
-
Choose the period when it froze
If you know the PC froze yesterday afternoon, 24 hours or 3 days is enough. Otherwise pick 7 days.
-
Look at the timeline
The error timeline shows whether errors cluster at a particular moment. If that matches the time the PC froze, you have a lead.
-
Find out which disk it is
The Windows logs refer to disks by system names such as
\Device\Harddisk1\DR1. EventAnalyzer translates them into an actual disk: number, model, capacity, type, bus, volume letters and serial number. You know at once whether it is the system SSD or an old data drive. -
Run a fix or check the hardware
The repair plan, such as a disk or system file check, is shown in advance and starts with a restore point. When the errors point to hardware, check it with a disk or memory test in PCHealthLab.
Common causes of freezes
- The disk or its cable. Repeated read errors and timeouts on the disk. Check the disk health.
- The graphics driver. The screen goes black for a moment and comes back; Windows restarts the driver and logs it.
- A crashing service or application. Shown among the functional findings with an occurrence count.
- Memory and overheating. These may not show in the logs at all. When the logs are silent, check the memory and temperatures.
Things to keep in mind
- A disk that has been removed from the machine is labelled in the findings and does not count towards the score.
- Back up your data before running a disk check. With a failing disk, every extra read can do harm.
- For repeated checks from the command line:
EventAnalyzer.exe --report C:\out\pc01.html --days 7returns 0 for a healthy machine and 1 for an unhealthy one.