Fix a Mac Kernel Panic and Random Restarts
Seeing 'Your computer restarted because of a problem' on your Mac? Learn how to track down kernel panics from software, peripherals, and disk faults.
A kernel panic is the Mac equivalent of a Windows blue screen. The screen goes dark, the Mac restarts on its own, and you are greeted with the message "Your computer restarted because of a problem." A single panic now and then can be a one-off, but repeated panics mean something is consistently wrong, usually faulty software or a kernel extension, an incompatible or failing peripheral, low disk space, or a hardware fault.
The key is to notice what the Mac was doing when it panicked. If it always happens with the same app or device connected, you already have your prime suspect.
Quick answer
Start by reading the panic report that appears after the restart; it names the process or kernel extension involved. Then update macOS and your apps, disconnect every peripheral, and boot into Safe Mode. If the Mac is stable in Safe Mode the cause is software (a kernel extension, login item, or app); if it still panics, suspect hardware and run Apple Diagnostics. Keep at least 20% of your startup disk free, since a full disk alone can trigger panics.
Key takeaways
- Software and kernel extensions are the most common cause, especially after an app or macOS update.
- A faulty or incompatible peripheral can panic the Mac, so disconnect everything and test.
- Low free disk space starves virtual memory and triggers panics; keep at least 20% free.
- Safe Mode and Apple Diagnostics quickly separate software faults from hardware.
- The panic report after restart names the component involved, which speeds up the fix.
Read the panic report
When the Mac reboots, click Report or open the dialog that appears. Look near the top for the named process or extension. A third-party kernel extension or a specific app in that report points straight at the cause.
The report is dense, but a few lines do most of the work. Here is what to look for and what it usually means:
| Field in the report | What it tells you |
|---|---|
| "panicked task" / process name | The app or service running when it crashed |
A .kext name | A third-party kernel extension is implicated |
| "Backtrace" with a vendor name | Points at a driver from that vendor (audio, VPN, GPU) |
| "Kernel slide" / addresses | Low-level detail, usually not actionable for you |
| Repeated identical reports | A consistent, reproducible fault worth chasing hard |
If the same .kext or app name shows up across several panics, you have found your prime suspect and can skip straight to removing or updating it.
Panics also cluster into a few root causes. Matching your situation to the likely culprit saves time:
| What you notice | Likely cause | First move |
|---|---|---|
| Started after an app or macOS update | Software or kext incompatibility | Update everything, remove the suspect app |
| Happens only with a dock or drive plugged in | Faulty or incompatible peripheral | Disconnect everything, reconnect one at a time |
| Disk nearly full, panics under load | Starved virtual memory | Free space to 20%+, repair the disk |
| Random panics even in Safe Mode | Hardware fault | Run Apple Diagnostics |
Update macOS and your apps
Many panics are fixed by a software update that resolves a known incompatibility.
- Open the Apple menu, then System Settings.
- Go to General, then Software Update, and install any macOS update.
- Open the App Store and update all apps.
- Restart and watch for the panic.
Tip
If panics began right after a macOS upgrade that is still settling, give it time and keep it plugged in. If the upgrade itself stalled, our guide to a macOS update stuck installing covers that separately.
Disconnect peripherals and remove startup items
A broken dock, hub, or external drive can panic the Mac by drawing abnormal power or loading a bad driver.
- Shut down the Mac.
- Unplug every peripheral except the keyboard and mouse.
- Start up and use it normally for a while.
- If stable, reconnect devices one at a time to find the culprit.
Also trim login items under System Settings, General, Login Items and Extensions, and remove anything suspicious or unused, especially third-party system extensions.
Boot to Safe Mode
Safe Mode loads only the essentials and runs a quick disk check, which isolates software causes.
- On Apple silicon, shut down, then hold the power button until startup options appear.
- Select your startup disk, hold Shift, and click Continue in Safe Mode.
- On an Intel Mac, hold Shift immediately after powering on.
If the Mac is stable in Safe Mode, the cause is software, a startup item, a kernel extension, or an app. If it still panics, suspect hardware.
Free up disk space and repair the disk
A nearly full startup disk starves virtual memory and triggers panics. Keep at least 20% free by clearing large files and caches. Then repair the disk: boot to Recovery (hold the power button on Apple silicon, or Command + R on Intel), open Disk Utility, select your startup volume, and run First Aid. Disk corruption is a realistic cause that First Aid can fix.
Run Apple Diagnostics for hardware
If panics persist in Safe Mode and after a disk repair, test the hardware. Restart and hold D (Intel) or hold the power button then press D on Apple silicon to launch Apple Diagnostics. It checks memory, the logic board, and wireless components, and reports a reference code if it finds a fault. A failing memory module or logic board is the usual hardware cause, and that points toward a service visit. Note the reference code it gives you (codes beginning PPN, NDC, or VFD point at power, network, and display hardware respectively), since that code speeds up any support conversation.
What to do right now
If your Mac keeps panicking, run this sequence and stop when the panics stop:
- Read the panic report and note any named app or
.kext. - Update macOS and every app through Software Update and the App Store.
- Disconnect all peripherals except keyboard and mouse, then test.
- Trim login items and remove any third-party system extension you do not recognize.
- Boot into Safe Mode to split software causes from hardware.
- Free disk space to 20%+ and run First Aid in Disk Utility from Recovery.
- Run Apple Diagnostics if panics survive all of the above, and note the reference code.
Frequently asked questions
Is one kernel panic something to worry about?
A single isolated panic is often a transient glitch and not worth chasing. What matters is a pattern. If your Mac panics repeatedly, especially with the same app or peripheral involved, that consistency signals a real fault you should track down using the panic report and Safe Mode.
What is a kernel extension and why does it cause panics?
A kernel extension is third-party code that runs at the deepest level of macOS, often installed by drivers, security tools, or virtualization software. Because it runs in the kernel, a bug there can crash the whole system. Removing or updating an outdated extension named in the panic report frequently fixes the problem.
How much free disk space does a Mac need?
Aim for at least 20% of the startup disk free. macOS uses spare disk space for virtual memory and swap, and when it runs out the system can panic under load. Clearing large files, old downloads, and caches to restore headroom resolves panics caused purely by a full disk.
Will reinstalling macOS erase my files?
A standard reinstall from Recovery installs a fresh copy of macOS over your existing system without erasing your files, though backing up first with Time Machine is always wise. Only choosing to erase the disk removes data. Reinstalling is a reasonable late step if software fixes do not stop the panics.
