Mac Keeps Crashing? How to Find the Cause and Fix It

“My Mac keeps crashing” describes four different problems with four different causes, and every hour spent on the wrong one is wasted. Start by answering one question: what did the screen do? The answer tells you which of the sections below applies — and macOS has already written a report about it, which almost nobody reads.

Which crash do you have?

A spinning beach ball that clears after a while is not a crash at all — that's an app failing to keep up, which has its own guide.

Read the report macOS already wrote

Every crash on your Mac produces a file, whether or not you sent it to Apple. You don't need to interpret the whole thing — the first fifteen lines usually name the culprit.

1. Open Console (in /Applications/Utilities).
2. In the sidebar, choose Crash Reports for app crashes, or Log Reports for system-level ones.
3. Sort by date and open the entry matching the time it happened.

What to look for near the top:

• Process — which app died. Sometimes it isn't the one you were using.
• Exception Type — EXC_BAD_ACCESS means the app tried to touch memory it didn't own, the classic programming bug. EXC_RESOURCE means it was killed for using too much of something.
• Termination Reason — often names the actual cause in plain text, including when macOS killed the app for running out of memory.
• Binary Images, at the bottom — if a third-party plug-in or extension appears near the top of the crashing thread, that's your suspect.

The same files are on disk at ~/Library/Logs/DiagnosticReports (your apps) and /Library/Logs/DiagnosticReports (system and kernel).

Section 1: one app keeps crashing

If it's always the same app, the Mac is fine and the app isn't. In order:

1. Update it. The most common cause of repeated crashes is an app that hasn't been updated for your version of macOS. Check the App Store's Updates tab and the app's own updater.
2. Update macOS. System Settings → General → Software Update. Point releases fix crash-inducing framework bugs regularly.
3. Disable its plug-ins. Audio units, Photoshop plug-ins, browser extensions and Finder extensions all run inside the host app, so a bad one takes the app down. Start it with plug-ins disabled if it offers that; otherwise remove them and add back one at a time.
4. Reset its preferences. Quit the app, move its file from ~/Library/Preferences to the Desktop, and relaunch. A corrupt preference file causes crash-at-launch surprisingly often. If it doesn't help, move the file back.
5. Reinstall it properly. Dragging to Trash leaves support files behind, so a reinstall lands on the same broken state — clear the leftovers first.

Section 2: lots of apps crash

When crashes span unrelated apps, the cause is underneath them. Work through these in order, because each one rules out a layer:

1. Check free disk space. A nearly full startup disk causes apps to fail on save and quit unexpectedly. System Settings → General → Storage; then what to do when the disk is almost full.
2. Check memory pressure. In red, macOS force quits apps to keep the system alive — which looks exactly like random crashing. How to read it.
3. Disconnect every peripheral. Hubs, docks, external drives and audio interfaces install drivers that run with system privileges. Unplug everything, use the Mac for a day, then reconnect one device at a time.
4. Test in Safe Mode. On Apple silicon: shut down, hold the power button until Loading startup options appears, select your disk, hold Shift, click Continue in Safe Mode. On Intel: restart holding Shift. Safe Mode blocks third-party startup items and extensions — if crashes stop, something you installed is responsible. Full Safe Mode steps for both chip families.
5. Test in a new user account. Create one in System Settings → Users & Groups and work there for a while. Crashes that follow you into a clean account are system-wide; crashes that don't are caused by something in your own library, which narrows it enormously.
6. Run First Aid. Filesystem damage produces crashes that look random. How to run it.
7. Run Apple Diagnostics. Shut down, then on Apple silicon hold the power button until startup options appear and press ⌘ + D; on Intel, restart holding D. It tests memory and other hardware in a few minutes and gives you a reference code.

The usual culprits, in practice

• Software that installs a system extension — VPN clients, antivirus, disk utilities, virtualisation tools, audio drivers. These run deep enough to take the whole system down. Check System Settings → General → Login Items & Extensions and remove anything you no longer use.
• An app left behind by a macOS upgrade. Anything that hasn't been updated in a couple of years is a candidate.
• A failing external drive. Crashes that only happen when a particular drive is attached aren't a coincidence.
• Failing memory, on Intel Macs with replaceable RAM. Apple Diagnostics finds most of it.
• Heat. A Mac that crashes only under sustained load, and runs hot doing it, may be shutting down to protect itself — see overheating.

Before you reinstall macOS

Reinstalling is the sledgehammer, and it's worth doing properly rather than early. Make sure you have a current backup first — System Settings → General → Time Machine, or an rsync copy if you prefer. Then try, in order: a Safe Mode boot, a new user account, and disconnecting everything. Those three tests identify the layer at fault in an afternoon; a reinstall takes longer and, if the cause is a peripheral or a failing drive, changes nothing.

The settings-level fixes above are one-click, reversible toggles in Mainspring — labelled in plain English, with an undo button for every one.

Common questions

What is the difference between a Mac crash and a kernel panic?

An app crash affects one app and leaves the rest of the system running. A kernel panic takes down the whole operating system, so the Mac restarts itself and shows 'Your computer was restarted because of a problem' when it comes back.

Where are crash reports stored on a Mac?

In ~/Library/Logs/DiagnosticReports for your own apps and /Library/Logs/DiagnosticReports for system and kernel reports. The Console app shows both under Crash Reports and Log Reports.

Why do my Mac apps quit unexpectedly?

Most often the app is out of date for your macOS version, or a plug-in or preference file has been corrupted. When many unrelated apps quit, look underneath them instead: low disk space, red memory pressure, a faulty peripheral, or filesystem damage.

Can low disk space cause a Mac to crash?

Yes. When the startup disk is nearly full, macOS runs short of room for swap and temporary files, and apps fail on save or are terminated. Keeping 10 to 15 percent free avoids it.

Will reinstalling macOS fix constant crashing?

Only if the cause is software in the system itself. Test Safe Mode, a new user account, and running with no peripherals attached first: those identify the layer at fault in an afternoon, whereas a reinstall does nothing for a failing drive or a bad dock.