Why Does My Computer Keep Freezing? How to Read the Evidence It Leaves

First: which of these is actually happening?

Be precise about the symptom. It narrows the cause enormously.

If it's only one application, stop here and deal with that application — update it, disable its plugins, test with a different file. Nothing below applies.

Open the log — it names the culprit

Windows: Reliability Monitor

This is the single most useful and least known tool in Windows. Press the Start button, type reliability, and open View reliability history.

You get a timeline chart with one column per day and a red X for each failure. Click any day to see what happened, in plain language: which application stopped responding, which driver failed, which update installed. Critically, it puts everything on one timeline — so you can see that the freezes started the same day a graphics driver updated, which is the kind of connection that's impossible to make from memory.

What to look for: a repeating entry across multiple incidents. One-off application errors are noise. The same driver or the same hardware event appearing every time is your answer.

For more detail, Event Viewer (eventvwr) → Windows Logs → System, filtered to Critical and Error. Two entries are worth knowing:

• Kernel-Power, Event ID 41 — the system restarted without shutting down cleanly. This is what an unexplained reboot or a hard freeze leaves behind. It confirms an unclean stop; it doesn't identify the cause by itself.
• Disk errors, or Ntfs warnings — a strong pointer at the storage drive. Take these seriously.

macOS: Console and crash reports

Open Console (Applications → Utilities). In the sidebar, Crash Reports lists individual application failures, and Log Reports holds system-wide records. A full system freeze that ended in a restart leaves a panic report — look for a file beginning with "Kernel" or "panic" dated to your incident.

You don't need to interpret the whole report. Look at the first few lines for a named extension or driver — anything ending in .kext, or a third-party product name. That name is usually the whole answer.

The pattern tells you the cause

While you're gathering evidence, note when it freezes. This is often more diagnostic than the logs:

• After 10–30 minutes of heavy use, never when idle → heat. See below.
• When opening or saving large files → the drive.
• When many apps are open, resolved by closing some → memory exhaustion.
• Only in games or video editing → graphics driver, or the power supply under load on a desktop.
• At random, including while idle → memory, drive, or power. The hardest pattern, and the one where the tests below matter most.
• Started on a specific date → check Reliability Monitor for what changed that day. An update, a new driver, a newly installed program.
• Only when a specific device is plugged in → that device or its driver. Unplug everything external and see.

Heat

The clearest signature: fine from cold, degrades or freezes under sustained load, fans loud, chassis hot. Modern processors slow themselves down first and shut off as a last resort, so a hard freeze from heat usually means the cooling has degraded significantly.

Install a temperature monitor and watch while you work. Sustained temperatures near the manufacturer's maximum under normal use point at cooling. What to do:

• Clear the vents. Laptops on beds and sofas block their own intakes. Desktops pull in dust through the front filter until it's a mat.
• Clean the heatsink. Compressed air through the vents helps; opening the case and clearing the fins properly helps far more.
• Replace thermal paste on machines more than about five years old. A cheap job at a repair shop, and often transformative.
• Check the fans actually spin. A seized fan is silent, which people mistake for a quiet computer.

A failing drive

This is the most urgent possibility, because unlike the others it takes your data with it. Signature symptoms: soft freezes of 10–60 seconds that recover on their own, freezes when opening large files, file operations that hang, occasional corrupted files, or a machine that takes far longer to boot than it used to.

Then check the drive's own health data:

• Windows: open Command Prompt and run wmic diskdrive get model,status for a crude verdict, then use a S.M.A.R.T. reading utility for the detail that matters — reallocated sectors, pending sectors, media wear. For file-system corruption specifically, run chkdsk C: /f from an administrator Command Prompt and let it schedule at reboot.
• macOS: Disk Utility → select the drive → First Aid. Also check System Information → Storage → S.M.A.R.T. status, which should read Verified.

Any non-zero and rising count of reallocated or pending sectors means replace the drive. Not "monitor it" — replace it. Drives rarely recover.

Bad memory

Faulty RAM produces the most maddening pattern: random freezes and crashes with no relationship to what you were doing, sometimes with corrupted files thrown in. It's also easy to test definitively.

• Windows Memory Diagnostic — type "memory" in the Start menu, choose Restart now and check for problems. It runs before Windows loads.
• MemTest86 — a bootable tool that's far more thorough. Worth the extra effort if the built-in test passes but you still suspect memory. Let it run several full passes; some faults only appear after an hour.
• macOS — hold D at startup for Apple Diagnostics, which includes a memory check.

On a desktop or an older laptop with accessible slots, there's a free physical test too: if you have two or more sticks, run with one at a time and see whether the freezes follow a particular stick or a particular slot. Also simply reseat the modules — memory can work its way loose over years of heating and cooling, and reseating fixes a genuine share of "random freeze" machines at no cost.

Drivers, especially graphics

If Reliability Monitor names a driver, or freezes only happen in games and video work, start here.

• Get the driver from the hardware vendor, not from Windows Update, which frequently offers an older version.
• If the freezes started right after a driver update, roll back. Device Manager → the device → Properties → Driver tab → Roll Back Driver. New graphics drivers do ship with regressions.
• For a clean graphics reinstall, remove the existing driver completely rather than installing over the top. Leftover files from a previous version are a classic source of instability.
• On a Mac, suspect third-party kernel extensions — old VPN clients, virtualisation tools, and audio interfaces are the usual names in panic reports. Update or remove them.

The test that separates hardware from software

If you've done the above and still don't know, this settles it. Boot into a minimal environment and use the machine the way that normally triggers a freeze.

• Windows Safe Mode — Settings → System → Recovery → Restart now under Advanced startup, then Troubleshoot → Advanced options → Startup Settings → Restart → choose Safe Mode. Only Microsoft's own drivers load.
• macOS Safe Mode — on Apple Silicon, shut down, hold the power button until startup options appear, select your disk and hold Shift while clicking Continue in Safe Mode. On Intel Macs, hold Shift during startup.
• Or boot from a Linux USB stick — a live USB runs entirely independently of your installed system. If the machine is rock solid for an hour under Linux, your hardware is fine and the problem is in your installation.

Freezes stop in Safe Mode → software: a driver, a startup program, or a background service. Re-enable startup items in batches to find it. Freezes continue in Safe Mode → hardware, and the memory and drive tests above are where to concentrate.