trio.so
How-Tos

Kernel Panic on Mac: What the Message Means and How to Fix It

Mac restarted because of a problem? Decode the panic message (SEP, watchdogd, iBoot), read the log, and fix it in order for Intel and Apple silicon.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A kernel panic is macOS stopping itself because it hit an error it could not recover from. You see a black or gray screen, or the Mac restarts and shows "Your computer restarted because of a problem" (Apple silicon Macs say "Your Mac restarted because of a problem"). One panic is usually not a worry. Repeated panics mean a cause you can find: read the panic log, match its first line to a cause, then work through the fixes in order.

What is a kernel panic on a Mac?

The kernel is the core of macOS. When it detects a fault it cannot safely continue past, it halts, writes a report to disk, and restarts the Mac. The usual causes are a faulty or incompatible driver or kernel extension, an app that misbehaves at a low level, a failing peripheral, bad memory or storage, and sometimes a macOS bug. Apple says to treat faulty software as the likeliest cause (see Apple's guidance, If your Mac restarts and a message appears).

Mac restarted because of a problem: where to read the panic log

After the restart, the Mac keeps a report. Open it before you change anything.

  1. Open System Settings > Privacy & Security > Analytics & Improvements > Analytics Data and look for files that start with "Kernel" or contain "panic".
  2. Or open Console, then Log Reports in the sidebar (called Crash Reports on some versions).
  3. Or read the files directly in /Library/Logs/DiagnosticReports. Apple silicon Macs write .ips files there. Intel Macs write .panic files.

The line to read is the panicString (Apple silicon) or the first line that starts with "panic" (Intel). It names the cause. Copy the date, the macOS version, and that line.

Decode common panic messages

Treat these as pointers. They narrow down where to look.

SEP panic

The Secure Enclave Processor, the chip part that handles keys and Touch ID, stopped responding. It is rare. It is usually seen after a macOS update or restore that went wrong, or with a hardware fault. Install the latest macOS update first. If it repeats on the same Mac, book hardware service.

watchdogd

A line such as "watchdog timeout: no checkins from watchdogd" means a core system process did not check in within its timeout (the line gives the seconds) and the Mac restarted itself. Look for what changed: a new driver, a security or VPN tool, a display or dock, or a heavy workload. Boot in safe mode to find out if third party software is involved.

iBoot or SoCD

"SoCD report detected: (iBoot panic)" points at the chip or boot firmware. Treat it as hardware or firmware until an update and Apple Diagnostics say otherwise. Update macOS, then check Apple Diagnostics. A repeat means service.

Unexpected S5 entry

This is usually seen when the Mac dropped into its off state without being asked, often with power, battery or thermal faults. Test with a different charger and cable and check the battery health, then run Apple Diagnostics.

"Your computer restarted because of a problem"

That is the message you see on screen ("Your Mac restarted because of a problem" on Apple silicon). The cause is in the log, not in that sentence. Use the log steps above.

How to fix a kernel panic on Mac, in order

  1. Update macOS and your apps. Open System Settings > General > Software Update.
  2. Remove new or third party software. If the log names a driver, extension or app, remove it. Apple advises removing third party plug-ins and enhancement software.
  3. Disconnect everything except the keyboard and mouse. Add devices back one at a time to find the one that causes it. Remove third party memory on Intel Macs that allow it.
  4. Start in safe mode. Apple silicon: shut down, hold the power button until startup options appear, choose the disk, hold Shift and choose Continue in Safe Mode. Intel: restart and hold Shift. If the panics stop in safe mode, third party software is the cause.
  5. Check free disk space. Free up space if the disk is nearly full.
  6. Run Apple Diagnostics. Apple silicon: hold the power button until startup options appear, then press Command + D. Intel: restart and hold D.
  7. Intel only: reset NVRAM and the SMC. Apple silicon Macs do not have these resets. Restarting does the same job.
  8. Reinstall macOS from Recovery. This keeps your files. Back up first.
  9. Book service. If it still panics with a clean install and nothing attached, the cause is hardware.

Intel vs Apple silicon

 Intel MacApple silicon Mac
Log file type.panic.ips
Safe modeHold Shift at restartStartup options, then Shift + Continue in Safe Mode
Apple DiagnosticsHold D at restartHold power, then Command + D
NVRAM and SMC resetYesNot needed

For IT: collect panic logs from several Macs

One Mac panicking is a ticket. The same panic string on five Macs is a pattern, and it usually points at one app, one macOS build or one peripheral. Collect the reports and compare them by panic string, macOS version and model.

ls -lt /Library/Logs/DiagnosticReports | grep -i -E "kernel|panic"

That lists the newest panic reports on a Mac. For extension related panics, read macOS system extensions and system extension blocked.

Managing this across many devices

trio.so can run a script on an enrolled Mac from the console. The ls check above is one script you can send to a Mac. See Apple device management.

The trio.so console running a script on a Mac, with the script text and the Mac it will run on.
Run a script on an enrolled Mac from the trio.so console.

Related reading: Mac evaluation utility and device manager on Mac.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Run commands on a panicking Mac from the console

Open a live terminal on a managed Mac, run commands and collect results without touching it. Start a 14-day free trial.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

Update macOS, remove new third party software, disconnect peripherals, test in safe mode, run Apple Diagnostics, then reinstall macOS. Read the panic log first, since the first line often names the cause.

Open Console > Log Reports, or System Settings > Privacy & Security > Analytics & Improvements > Analytics Data. Find the panicString and match it to the causes above.

Faulty drivers or extensions, incompatible apps, failing peripherals, memory, storage or power faults, and occasional macOS bugs.

Related

From the blog

The related industry news, interviews, technologies, and resources.