Our Verdict
The right fix depends entirely on the symptom. A spinning wheel usually just needs patience or a single restart, while a total crash that keeps repeating points to something worth investigating — whether that's low storage, a misbehaving app, or an operating system issue. Matching the response to the problem saves time and avoids making things worse.
| Best for | Recommended |
|---|---|
| One-time freeze or temporary hang | Wait, then force-quit the offending app |
| Persistent spinning wheel with no recovery | Forced restart after waiting 2–3 minutes |
| Repeated crashes or blue/black screen errors | Check storage, update software, then seek deeper diagnosis |
| Complete unresponsiveness with no display | Power cycle and verify charging/hardware basics first |
Why the Symptom Matters Before You Do Anything
When your device stops responding, the instinct is to immediately hold down the power button and force it off. Sometimes that's exactly right. Other times it can interrupt a process that was quietly finishing in the background — like saving a file or completing an update — and leave things in a worse state than before.
The three most common freeze scenarios — a frozen screen, a spinning wait cursor (sometimes called a spinning wheel or "beachball"), and a total crash — look alarming but have meaningfully different causes. Treating them the same way wastes time and occasionally creates new problems. See our guide to reading error messages for help decoding any alerts that appear alongside these symptoms.
The Three Symptoms Side by Side
Before jumping to fixes, it helps to pin down exactly what you're seeing. Here's how each scenario typically presents itself — and what it usually means under the hood.
| Frozen Screen | Spinning Wheel | Total Crash | |
|---|---|---|---|
| What you see | Display stuck, no input works | Cursor animating, nothing responds | Screen goes black, error, or sudden reboot |
| Device still running? | Yes, but unresponsive | Yes, actively processing | No — exited unexpectedly |
| Most common cause | App using too much memory | Low storage or heavy background task | Overheating, driver error, or OS fault |
| First response | Wait, then force-quit app | Wait 2–3 min, check storage | Restart and check for updates |
| When to worry | Same app freezes repeatedly | Spinning returns right after restart | Crash happens more than once |
| Risk of data loss | Low if force-quit used carefully | Low if given time to finish | Moderate — unsaved work may be lost |
The key distinction is whether your device is still doing something (spinning wheel), has stopped responding entirely (frozen screen), or has exited to an error state (crash). That difference shapes every step that follows.
Responding to a Frozen Screen
A frozen screen — where the display is visible but nothing responds to clicks, taps, or keyboard input — is usually caused by a single application consuming more memory (RAM) than the system can spare. The rest of the device hasn't failed; one program has just crowded everything else out.
What to try first
- Wait 60–90 seconds. Counterintuitive as it feels, some freezes resolve on their own once a background task finishes.
- Force-quit the unresponsive app. On Windows, press Ctrl + Shift + Esc to open Task Manager and end the frozen program. On a Mac, press Command + Option + Esc to bring up the Force Quit window.
- If that doesn't work, restart — don't just shut down. A restart clears temporary memory in a way a simple shutdown sometimes doesn't. See why restarting and shutting down aren't the same thing for the full explanation.
Save Your Work Before Force-Quitting
If other apps on the screen are still responsive, try saving open documents in those programs before you force-quit or restart. Only the frozen application needs to be terminated — everything else can often be closed normally, protecting your work in progress.
If freezes happen regularly with the same app, that app is likely the culprit — check whether an update is available for it, or consider whether it's doing more than your device's hardware can comfortably handle.
Responding to a Spinning Wheel or Wait Cursor
The spinning wheel (or hourglass on older Windows systems) means your device is actively working on something and asking you to wait. It becomes a problem when it never goes away. This usually points to one of three causes: the task genuinely needs more time, the system is nearly out of available memory, or storage space is too low for the device to operate smoothly.
What to try first
- Give it real time — at least two to three minutes. Updates, large file operations, and antivirus scans can legitimately hold up the cursor for a while.
- Check whether storage is critically low. Devices need a meaningful buffer of free space to function. If your drive is nearly full, that alone can cause persistent spinning. Deleting temporary files or unneeded downloads often helps immediately.
- Force restart if there's no progress. Hold the power button until the device turns off, then power it back on normally.
If the spinning wheel returns quickly after a restart, that's a signal to look more broadly at what's running at startup. A full walkthrough of slow-computer causes can help you trace the source.
Responding to a Total Crash
A total crash — where the device abruptly restarts, displays a blue or black error screen, or powers off without warning — is the most startling of the three. It's also the one most worth taking seriously if it happens more than once.
What to try first
- Note any error message before it disappears. Crash screens often flash a code or brief description. Even a partial note helps narrow down the cause.
- Restart and check for pending updates. Operating system updates frequently contain fixes for stability issues that cause crashes.
- Look for a pattern. Does it crash during a specific task — playing video, running a particular program, charging? A consistent trigger points toward a specific culprit.
- Check the device's temperature. Overheating is a common cause of sudden shutdowns. Make sure vents aren't blocked and the device has airflow.
Repeated Crashes Deserve More Than a Reboot
Restarting after a one-time crash is reasonable. But if your device crashes two or more times in a short period, rebooting again without investigation is just delaying the problem. Recurring instability can sometimes precede hardware failure, and unsaved work is at risk every time it happens. Keeping regular backups is one of the simplest protections you can have.
If crashes recur after updates and basic checks, it may be time to run a pre-support checklist before escalating to a technician. Some recurring crashes do point to failing hardware — continuing to ignore them can risk data loss.
The content on this site is for informational purposes only and is not a substitute for professional advice. Always consult a qualified professional for guidance specific to your situation.