Mac Kernel Panics: Why Your Mac Keeps Restarting

A kernel panic is macOS deciding that continuing would be worse than stopping. The kernel hits a state it cannot safely recover from, halts everything, and restarts — which is why you lose whatever you were doing and see “Your computer was restarted because of a problem” when you come back. One panic in a year is not worth investigating. Panics that repeat almost always have a specific, findable cause, and macOS writes it down.

Confirm it was a panic

Two things distinguish a kernel panic from other failures: the Mac restarted itself, and it showed the “restarted because of a problem” dialog afterwards. If it powered off and stayed off, that's a shutdown, which points at power or heat. If it stopped responding but never restarted, that's a freeze. Different causes, different fixes.

Read the panic report

The dialog offers to send a report to Apple. Before you dismiss it, click Report… and read it — or find it later:

1. Open Console from /Applications/Utilities.
2. Select Log Reports in the sidebar.
3. Open the newest file named Kernel- with a .panic or .ips extension. On disk they live in /Library/Logs/DiagnosticReports.

You are not trying to understand the whole thing. You're scanning for two specific things:

• A panic string near the top, after panic(. Phrases like watchdog timeout or a named driver are the useful part.
• Any non-Apple name in the backtrace or the loaded extension list. Apple's own components start with com.apple.. A third-party bundle identifier — a VPN client, an audio interface driver, a disk utility, a virtualisation tool — appearing anywhere in that list is your prime suspect, and removing it is the fix.

If every name is an Apple one, that points toward hardware or a peripheral rather than installed software.

The elimination sequence

Run these in order. Each one rules out a layer, and stopping as soon as the panics stop tells you the answer.

1. Unplug everything. Every external drive, hub, dock, display adapter, audio interface and USB device. Peripherals and their drivers are the most common cause of repeat panics, and a marginal hub or dying drive can panic a perfectly healthy Mac. Use it bare for a day, then reconnect one device at a time.
2. Install every update. System Settings → General → Software Update, and update your apps too. Panics traced to third-party drivers are frequently fixed by an update that already exists.
3. Boot into Safe Mode. On Apple silicon: shut down, hold the power button until Loading startup options appears, select your disk, hold Shift, and click Continue in Safe Mode. On Intel: restart holding Shift. Safe Mode runs without third-party extensions. No panics in Safe Mode means installed software is responsible — more on Safe Mode.
4. Remove system extensions you don't need. System Settings → General → Login Items & Extensions lists what's loaded. Anything from software you no longer use should go — use the vendor's uninstaller, since dragging the app to the Trash leaves the extension behind.
5. Run First Aid. Disk Utility's First Aid on the startup volume. Filesystem damage can panic the kernel during ordinary reads.
6. Run Apple Diagnostics. Shut down; on Apple silicon hold the power button until startup options appear, then press ⌘ + D. On Intel, restart holding D. Memory faults are a classic panic cause on Intel Macs with replaceable RAM, and Diagnostics finds most of them.

If it panics in a loop and won't stay up

A Mac that panics again within seconds of starting is unusable through the normal route. Two things to try:

• Safe Mode, as above. It's often stable when a normal boot isn't, which gives you a window to uninstall the offender.
• Recovery. On Apple silicon, hold the power button from shut down until Loading startup options appears and choose Options. On Intel, restart holding ⌘ + R. From there you can run Disk Utility against the startup volume and, if it comes to it, reinstall macOS without erasing your files.

Take a backup before reinstalling if the Mac is stable enough to make one — Time Machine, or an rsync copy to an external drive.

What not to bother with

• Resetting NVRAM or the SMC on Apple silicon. These don't exist as user-resettable things on M-series Macs. The equivalent is a full shut down for thirty seconds.
• Cleaner apps. Nothing in a panic report is a cache or a junk file. They cannot help here.
• Deleting kernel extension files by hand. Use the vendor's uninstaller. Removing pieces of a driver manually tends to produce a Mac that panics differently.
• Turning off crash reporting to stop the dialog. It doesn't stop the panics, and you lose the reports that identify them — though if you've finished diagnosing and just want quiet, here's how.

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 causes a kernel panic on a Mac?

Most repeat panics come from third-party kernel or system extensions, faulty peripherals and hubs, filesystem damage, or failing memory. The panic report names loaded extensions, which is why reading it first saves a lot of guessing.

Is one kernel panic something to worry about?

No. A single panic in months of use is not worth investigating. Panics that repeat, or that cluster around a particular activity or device, do have a findable cause.

How do I read a kernel panic report?

Open Console, select Log Reports, and open the newest Kernel entry. Look at the panic string near the top and scan the loaded extension list for any bundle identifier that does not begin with com.apple — that is usually the culprit.

Can a bad USB hub or dock cause kernel panics?

Yes, and it is one of the most common causes. Disconnect every external device, use the Mac for a day, then reconnect one at a time to identify which one triggers it.

Does resetting NVRAM fix kernel panics?

Occasionally on Intel Macs, where a corrupt setting can affect startup. Apple silicon Macs have no user-resettable NVRAM or SMC, so any guide suggesting it for an M-series Mac is out of date.