Software errors can cause a program to crash, freeze, or display an error code, but reinstalling is rarely the best first step. It usually needs one of a handful of specific things checked, in a specific order — and most of that order has nothing to do with how serious the error message sounds.
This covers software that misbehaves on an otherwise working computer: a program that crashes on launch, freezes mid-task, or throws an error code. If your whole computer is sluggish rather than one program failing, or you suspect malware rather than a buggy program, those have their own guides linked further down.
Force-quit the frozen program first, then read the actual error message or code before doing anything else. From there: check for an update, use Windows’ built-in Repair option before a full reinstall, and if the problem is system-wide rather than one app, run sfc /scannow. Reinstalling should be a later step, not the first one — it fixes fewer causes than people assume.
Force-quit a frozen or unresponsive program
On Windows, open Task Manager with Ctrl + Shift + Esc, select the unresponsive program, and choose End task. On a Mac, press Command + Option + Escape to open Force Quit, select the app, and choose Force Quit.
If the whole system is frozen and neither shortcut responds, wait at least 30–60 seconds before assuming it needs a hard restart — a program can look frozen while it is still writing a large file or recovering from a spike in memory use.
Read the error message before you search for it
The exact wording and any error code matter more than how the error looks. A vague dialog box is not the full story: Windows and macOS both keep a more detailed record of what actually happened.
On Windows: Event Viewer
Open Event Viewer, then check Windows Logs > Application for the crash, filtered to Error level and matched by timestamp to when the program failed. The Source and Event ID fields are what you search for, not the generic dialog text.
On Mac: Console and crash reports
Open Console and look under Crash Reports, or check ~/Library/Logs/DiagnosticReports directly. Each crash produces a report naming the specific process and the point in the code where it failed, which is far more searchable than “the app quit unexpectedly.”
Paste the precise error code or the specific line from the log into a search engine, in quotation marks. A paraphrase like “program keeps crashing” returns generic advice; the exact string is far more likely to lead you to someone who hit the identical bug.
Try Repair before you reinstall
Reinstalling feels thorough, but it does not fix everything, and it means downloading the whole program again when a smaller step would have worked. Windows has a built-in option for exactly this.
Go to Settings > Apps > Installed apps, select the program’s More menu, then Advanced options. Microsoft’s own guidance is to try Repair first if it is offered, and use Reset only if Repair is not available or does not fix the problem.
Repair fixes the program’s files without touching your data or preferences. Reset clears the app back to a fresh install, including its settings and, for some apps, saved data — treat it as a step below reinstalling, not a synonym for it.
Not every program offers Repair or Reset; it depends on how the installer registered itself with Windows. If neither option appears, a normal uninstall and reinstall is the fallback — just do it after you have already ruled out the causes below, not before.
When the problem is system-wide, not one program
If more than one unrelated program is crashing, or the same error follows you across different software, the cause is more likely a damaged system file than a problem with any one app.
Open an administrator Command Prompt and run sfc /scannow. Microsoft’s System File Checker scans and repairs protected system files, and it will tell you plainly whether it found and fixed anything, found something it could not fix, or found nothing wrong.
If System File Checker reports it cannot fix what it found, run DISM /Online /Cleanup-Image /RestoreHealth first, then run sfc /scannow again — DISM repairs the underlying Windows image that System File Checker draws its replacement files from, so the order matters.
Three specific causes worth checking directly
A corrupted user profile or config file
Many programs store their own settings separately from Windows or macOS. If a program crashes only for one user account, or only since you changed a setting, try renaming or resetting that program’s configuration folder rather than assuming the whole install is at fault.
A driver conflict, especially graphics drivers
Crashes that happen specifically during video playback, gaming, or anything graphically heavy point at the graphics driver first. Update it from the GPU maker’s own site rather than relying solely on Windows Update, which can lag behind.
Low disk space
Plenty of programs fail in confusing ways — not with a clear “disk full” message — when the drive they are installed on is nearly out of space, because they cannot write temporary files or update logs. Check available space before ruling out anything else.
Not enough RAM for what you actually have open
A single program crashing while a dozen browser tabs, several other apps, and background sync tools are all running at once is sometimes just memory pressure, not a bug in that program specifically. Close what you are not using and see whether the crash still happens before treating it as a software fault.
When it is malware, not the software
A program that was fine last week and is suddenly crashing, throwing unfamiliar errors, or behaving strangely across multiple apps at once can be a sign of malware rather than a software bug — especially alongside new toolbars, pop-ups, or a browser homepage you did not set.
Repairing or reinstalling a program will not fix an infection sitting underneath it, and re-downloading software while infected risks reinfecting the fresh install. Run a full malware scan first if anything about the pattern looks off.
How to choose antivirus software if you don’t already have a reliable one installed.
When it is not the software, it is the computer
If everything runs slowly rather than one specific program crashing or erroring out, the fix is different from anything above — that is a performance problem, not a software fault, and piling on reinstalls will not touch it.
What to check when the whole computer is slow, not just one program.
When these steps do not fix it
Before assuming a program is unfixable, check whether anyone else is hitting the same thing. Most established software vendors run a public status page or a known-issues list for exactly this, separate from general support forums, and it will tell you quickly whether you have found a real bug that is already being worked on rather than something local to your machine.
If the program is older and was not built for your current operating system version, try running it in Compatibility mode (right-click the shortcut, Properties, Compatibility tab on Windows) before giving up on it. And if a program offers to send a crash report when it fails, send it — it costs a few seconds and is one of the more direct ways an issue reaches the people who can actually fix it.
Preventing the next crash
- Keep automatic updates on for both your operating system and the programs you use daily — most fixes for known crashes ship as ordinary updates, not special patches you have to seek out.
- Restart occasionally, not just when something breaks. Background processes and memory leaks in long-running programs accumulate over days, and a normal restart clears them before they cause a crash.
- Keep meaningful free disk space rather than running a drive close to full, since several of the causes above trace back to that.
- Uninstall software cleanly through Settings rather than just deleting its folder, so it does not leave behind configuration files that confuse a future install.
Common mistakes when troubleshooting software errors
- Reinstalling before reading the actual error. It skips the one piece of information most likely to point at the real cause.
- Assuming every crash is the same crash. A program that fails only during one specific action has a narrower, easier-to-find cause than one that fails randomly.
- Running DISM and SFC in the wrong order. If SFC alone cannot fix a problem, DISM needs to run first, then SFC again — not the other way round.
- Ignoring driver updates because “the software is the problem.” A driver conflict often looks exactly like a buggy app.
- Deleting a program’s folder instead of uninstalling it properly. Leftover configuration files are a common reason a fresh reinstall inherits the same error.
Software Errors: Frequently Asked Questions
What should I do first when a program crashes?
Force-quit it if it is frozen, then read the actual error message or check Event Viewer (Windows) or Console (Mac) for the specific error rather than acting on the dialog text alone. That detail usually points straight at the cause.
Should I repair or reinstall a program that keeps crashing?
Try Repair first, through Settings > Apps > Installed apps > Advanced options on Windows. It fixes damaged program files without erasing your settings, whereas Reset and reinstalling both start over. Move to those only if Repair is unavailable or does not help.
What is the difference between sfc /scannow and DISM?
System File Checker (sfc /scannow) repairs damaged Windows system files using a local cache of good copies. DISM repairs the underlying Windows image that cache draws from. If SFC reports it cannot fix something, run DISM first, then SFC again.
How do I know if a crash is caused by malware instead of a software bug?
Suspect malware if the crashes started suddenly, affect several unrelated programs at once, or come with new toolbars, pop-ups, or browser changes you did not make. A software bug is usually consistent and tied to one program or one specific action.
Why does a program crash on one computer but not another?
Usually a difference in drivers (especially graphics drivers), available disk space, or a corrupted configuration file specific to that installation, rather than the program itself being different.
The short version
Force-quit before you panic, read the actual error before you search for it, and reach for Repair before Reset and Reset before a full reinstall. If the problem follows you across multiple programs, run sfc /scannow (and DISM first, if needed). If it looks like malware or the whole machine is slow rather than one program failing, that is a different guide, not a harder version of this one.
