Short answer
A true freeze is when the whole system stops responding: the pointer won't move, Ctrl+Alt+Delete does nothing, and only holding the power button ends it. That behaviour narrows the field considerably, because it rules out several things a blue screen or a reboot would point at.
Define exactly what happens
People use 'freeze' for four quite different behaviours, and they lead to different causes. Be precise about which one you have — it is the single most useful piece of information you can give a technician.
| Behaviour | What it suggests |
|---|---|
| One program stops responding, rest of Windows fine | Application fault — Task Manager can close it. Not a system-level problem. |
| Everything locks, pointer frozen, no keyboard response | A hard freeze. Kernel-level: memory, storage, drivers, GPU or heat. |
| Blue screen with a stop code | Windows caught the fault and recorded it. Covered in our blue screen guide. |
| Machine reboots or powers off with no warning | Power or thermal protection, not a freeze. See the restarting and shutdown guides. |
Look for the pattern before you change anything
Random is rarely truly random. Keep a note for a few days of when it happens — the pattern usually points straight at the cause.
- Freezes minutes after a cold start, then settles — often memory or a driver loading.
- Freezes only after long uptime or under sustained load — heat, or a component that becomes unstable when warm.
- Freezes when opening files, copying data or launching programs — storage is the first suspect.
- Freezes only in games or video work — graphics driver, GPU, or power delivery.
- Freezes at a consistent time of day — a scheduled task, backup or antivirus scan.
- Started right after an update, a new program or new hardware — start there, not with a full hardware hunt.
Protect your files first
Checks that are safe to run
- 1
Check Reliability Monitor
Search 'reliability' in the Start menu. It gives a plain-English timeline of crashes, failed updates and driver problems, and often shows exactly what changed the day the freezes started.
- 2
Check Event Viewer around the freeze time
Windows Logs, then System. Critical and Error entries logged just before the lock-up are the best clue Windows can give you about a freeze it never recovered from.
- 3
Check drive health
Look at the drive's SMART data with a free health utility. Reallocated sectors, pending sectors or a health percentage below 100 on an SSD all matter. A failing drive freezes a machine while Windows waits on a read that never returns.
- 4
Run the built-in memory test
Search 'Windows Memory Diagnostic' and let it run on restart. It is not exhaustive, but a failure result is meaningful. Bad memory is a classic cause of freezes with no error at all.
- 5
Update or roll back graphics drivers
If the freezes began after a driver update, roll back. If the driver is very old, update it cleanly. Graphics drivers are the most common driver cause of full system hangs.
- 6
Watch temperatures
Run monitoring in the background. A freeze that arrives once the CPU or GPU reaches its limit is a cooling problem, not a Windows problem.
- 7
Test in Safe Mode
Safe Mode loads a minimal set of drivers and no startup software. If the machine is rock solid for a day in Safe Mode, the cause is very likely software or a driver rather than failing hardware.
- 8
Try a clean boot
Disable non-Microsoft startup services and startup apps, then reintroduce them in groups. Slow, but it reliably finds a conflicting background program.
The less convenient possibilities
- Failing storage — an ageing SSD or a mechanical drive with bad sectors produces long hangs and eventually total locks.
- Failing memory — intermittent, load-dependent, and often clean on a short test but obvious on a long one.
- Motherboard faults — ageing capacitors or a chipset problem, usually alongside other odd behaviour.
- Power supply weakness — an ageing unit can hang a machine under load rather than shutting it down cleanly.
- Windows corruption — system file damage after a bad update or an unclean shutdown.
- Thermal throttling gone too far — the machine locking instead of throttling smoothly.
The awkward part is that several of these look identical from the outside. Distinguishing them means swapping known-good parts in and out, which is where home troubleshooting normally stops.
When to bring it in
If drive health looks poor, if a memory test fails, or if you have been through drivers and software and it still locks, that is the point to stop guessing. We test memory properly, check drive health, look at logs and run the machine under load on the bench in Bellevue. Consultations at the counter are free — bring it in and describe the pattern you noticed, because that shortens the job considerably.
Common questions
- What's the difference between a freeze and a blue screen?
- A blue screen means Windows detected a fatal error and stopped deliberately, leaving a stop code behind. A freeze means the system stopped responding without being able to report anything, which usually means the fault took out something more fundamental.
- Can bad RAM cause freezes without a blue screen?
- Yes. Memory faults produce a wide range of symptoms including silent hard locks, corrupted files and failed updates, sometimes without a single stop code.
- Will reinstalling Windows fix random freezes?
- It will fix them if the cause is software or system corruption, and it will do nothing at all if the cause is failing memory, a dying drive or a heat problem. It is worth ruling out hardware first, and backing up before either way.
- Is it safe to keep using a computer that freezes?
- For light use it's usually not dangerous, but every forced restart risks the data being written at the time. Make sure you have a current backup while you sort out the cause.
The service that covers this
Computer Diagnostics & Repair
Won't start, throwing errors, or acting strange? We find out what's actually wrong before anything gets replaced.
Computer Diagnostics & Repair in Bellevue →Related guides
- Windows Blue Screen Keeps Happening: Reading the Stop CodeRepeated blue screens point at drivers, memory, storage, firmware or overheating. Learn what stop codes do and don't tell you, and which fixes to avoid early.
- Computer Keeps Restarting RandomlyRandom reboots with no blue screen usually mean power, heat or a fault Windows never got to log. Here is how to tell an automatic restart from a hardware cut.
- SSD Failing: The Warning Signs Worth Taking SeriouslySolid-state drives rarely warn you with noise. Disappearing drives, read-only behaviour, file corruption, freezes and SMART health warnings are the signals that matter.
- Slow Computer: Is It the SSD, the RAM, or an Actual Fault?Before spending money on an SSD or more memory, work out whether you have a bottleneck or a fault. Failing storage, heat and malware also look like a slow computer.