A crash occurs when a program, driver or operating system hits a condition it cannot handle and terminates abnormally. An application crash closes only that program, while a system crash halts the whole computer, producing a blue screen on Windows or a kernel panic on macOS and Linux.
Why it matters
Crashes lose unsaved work and can signal deeper problems such as bugs, faulty memory, overheating, bad drivers or corrupted files. Knowing the type helps you diagnose it: a single app crashing repeatedly points to that software, while random system-wide crashes suggest hardware or driver trouble.
Example
A program accessing memory it does not own triggers a segmentation fault:
Segmentation fault (core dumped)Developers analyse the core dump or crash log to find the faulty line. On Windows, Event Viewer, Windows Logs, Application records an application error with the faulting module name.
Common mistakes
- Reinstalling everything before reading the crash log or error code.
- Confusing a crash with a freeze: a frozen app is still running, just not responding.
- Ignoring repeated crashes after a new driver or update, which are a strong clue.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.