Freezing and crashing are not the same thing
A freeze (sometimes called a hang) means a program stops responding. The window may turn pale, the pointer may spin, and clicks do nothing. The program is usually still running but stuck, perhaps waiting on something slow.
A crash means the program closes suddenly, often with a message, or vanishes without warning.
Both are common, and one occasional freeze is rarely a reason to worry. The useful question is whether the problem lives in one program or in the computer as a whole. Everything else follows from that.
Give a frozen program a little time
Many freezes are temporary. A program may be reading a large file, waiting for a network connection, or working through a long task. Before taking action, wait a minute or two. If the drive light is busy or the fan is loud, the computer may simply be working hard.
If it does not recover, use the system’s built-in way to end a stuck program, usually through a task manager or “force quit” option. Ending the task closes the program, and any unsaved work in it will likely be lost. This is a good reason to save often and to use autosave features where a program offers them.
If the whole computer, including the mouse pointer and clock, stops responding, that is a system-wide freeze and calls for a different approach, described below.
Is it one program or everything?
Ask a few questions and write down the answers.
- Does it happen in only one program? If other software works normally, the fault probably lies with that program, its settings, or the files it opens.
- Does it happen in several unrelated programs? That suggests something shared: the operating system, a device driver, low memory, low disk space, heat, or failing hardware.
- Does it happen with one particular file? The file may be damaged or unusually large.
- Does it start only after a certain action, such as printing, plugging in a device, or joining a video call? That action points toward a specific driver or accessory.
This sorting step is the same approach described in the general guide to troubleshooting steps: separate the problem into a category before trying fixes.
Common causes of a single misbehaving program
If just one program is the trouble, try these in order, changing one thing at a time:
- Restart the program, then the computer. Many glitches clear this way.
- Check for updates to that program. Developers fix crash bugs regularly. Take the update from the official source only.
- Try opening a different file. If the program works with other files, the original one may be damaged.
- Reset its settings or turn off add-ons. Plug-ins and extensions are a frequent source of trouble, especially in web browsers. See the article on browser extensions for ideas on testing them safely.
- Reinstall it. Removing a program and installing it again can replace damaged files. The guide to uninstalling programs explains how to do it cleanly. Save your own files and settings first.
If the program was recently updated and began crashing right after, the update itself may be the cause, and waiting for a fix from the developer may be the practical answer.
Causes that affect many programs
When several programs freeze or close, these are the usual suspects.
- Not enough memory. If too many programs are open, the system may become sluggish and unresponsive. Closing some, or checking your real memory and storage needs, can help.
- A nearly full drive. Programs need working space. If the drive is almost full, freeing up disk space can reduce freezing.
- Heat. Computers may slow down, freeze, or shut down when too hot. Dust, blocked vents, and a laptop sitting on a soft surface are typical causes. See the guide on laptop overheating, and think about case airflow in a desktop.
- Outdated or faulty drivers. A driver is the software that lets the system talk to hardware. Problems with graphics or storage drivers can show up as freezes. Updates should come from the computer or device maker.
- Unwanted software. Malware can slow systems and cause odd behavior, so review the malware warning signs if crashes arrived alongside pop-ups or new toolbars.
- A failing drive or memory module. Hardware faults can look like random software trouble.
What a pattern of repeated crashes can suggest
Patterns carry information, so keep a short log of when crashes happen.
- Always the same program, same action: likely a software bug, a bad file, or a conflicting add-on.
- Different programs, but always after the computer has been on for a while: often heat or memory trouble.
- Mostly during demanding tasks, such as games, video editing, or many tabs open: possible overheating, a graphics driver issue, or power supply strain.
- Along with file errors, very slow file opening, or clicking sounds: possibly a failing drive. Copy your important files to another place promptly. The guide on warning signs of failing drives goes into this.
- Followed by a sudden full-screen error or restart: a deeper system-level fault, covered in the articles on blue screens and random restarts.
None of these is a certain diagnosis, but each tells you where to look first.
Try safe mode to separate software from hardware
If the whole system is unstable, starting in safe mode loads only the basics. If the computer behaves well there, the cause is more likely software or a driver than failed hardware. If it still crashes, hardware moves up the list. How to start safe mode differs between systems, so follow the official instructions for yours.
When to stop and ask for help
Back up your files first, then consider getting help if crashes continue after updates and restarts, if several programs are affected, or if you notice signs of heat, strange noises, or drive trouble. Opening the case to check memory or fans is a job for someone experienced. As a final software step, a clean reinstall of the operating system can clear deep software faults, but it erases data, so it should come only after you have a safe, verified copy of what you need.