Fix a Kernel Panic on Mac: Step-by-Step Guide

A kernel panic is your Mac’s way of saying the core system software hit an unrecoverable error, forcing a restart to protect your hardware. This guide walks you through the most common causes and the fixes you can try at home, from simple restarts to resetting NVRAM and safe-mode diagnostics. You’ll need a few minutes, your Mac, and possibly a second device to look up Apple support pages if needed.

What You’ll Need

Your Mac (any model running macOS)
Time (10–30 minutes depending on the fix)
An internet connection for downloading updates or checking Apple support
A backup (Time Machine or other) – always good before major changes

Step-by-Step

Force restart your Mac. Hold the power button for about 10 seconds until it shuts off, then press it again to turn it back on. This clears the immediate panic and often lets the system boot normally.
Check for a recurring pattern. If the panic happens again right away or within a few minutes, note what you were doing (opening an app, connecting a device, waking from sleep). This clue helps narrow the cause.
Boot into Safe Mode. On Apple silicon (M1/M2/M3) Macs: shut down, then press and hold the power button until you see “Loading startup options,” select your disk, hold Shift, and click “Continue in Safe Mode.” On Intel Macs: restart and immediately hold the Shift key until the login window appears. Safe Mode loads only essential extensions and runs a disk check. If the Mac boots fine in Safe Mode, the issue is likely a third-party extension or login item.
Quit or uninstall recently added software. If the panic started after installing a new app, driver, or kernel extension (kext), uninstall it. Check the app’s own uninstaller or drag it to Trash. Also remove any recently added login items: System Settings > General > Login Items (macOS Ventura and later) or System Preferences > Users & Groups > Login Items (earlier versions).
Reset NVRAM (Intel Macs only). Shut down, then turn on and immediately press and hold Option+Command+P+R for about 20 seconds. You’ll hear the startup chime twice. Release and let it boot. This resets non-volatile memory that stores boot settings and can fix boot-related panics. On Apple silicon, NVRAM resets are not needed – restarting is sufficient.
Check disk and repair if needed. Restart and hold Command+R to enter Recovery Mode. Choose Disk Utility, select your startup disk (usually “Macintosh HD”), and click First Aid. Run it – this checks and repairs the file system. If it reports errors, run it again until it says “Operation successful.”
Update macOS. Go to System Settings > General > Software Update (or System Preferences > Software Update) and install any available updates. Apple regularly fixes kernel bugs in updates.
Reinstall macOS (last resort). If nothing else works, back up your data, then restart into Recovery Mode (Command+R) and choose “Reinstall macOS.” This keeps your files and settings but replaces the system files. If the panic persists even after reinstall, it’s likely a hardware issue.

Common Mistakes

Skipping Safe Mode. Jumping straight to reinstalling macOS without testing Safe Mode can waste hours – Safe Mode quickly tells you whether it’s a software extension or something deeper.
Ignoring the panic log. The panic report (shown on screen or in Console after reboot) contains the exact cause. Many people skip it, but it’s the fastest way to identify the culprit (e.g., a specific kext file).
Not backing up before major steps. Resetting NVRAM or reinstalling macOS rarely deletes data, but a backup is essential before any system-level change.
Using a third-party “kernel panic fixer” app. These are usually scams or bloatware; they don’t address the root cause and can make things worse.
Assuming it’s always hardware. Many panics are caused by software, so try all software fixes before assuming a hardware fault.

Tips

Read the panic log. After a reboot, open Console app (in Utilities), search for “panic,” and look for the line that says “Kernel Extensions in backtrace” or similar. That often names the problematic file (e.g., com.company.driver).
Keep macOS updated. Panic bugs are frequently patched in point releases.
Check RAM and peripherals. If you recently added RAM or a USB device, remove it and see if the panic stops. Faulty hardware is a common cause.
Use Apple Diagnostics. Restart and hold D (or Option+D on older Intel) to run hardware diagnostics. This tests RAM, logic board, and other components.
Create a separate test user account. If the panic only happens in your user account, it’s likely a login item or preference file – test by creating a new user in System Settings > Users & Groups.

Troubleshooting

If the Mac still panics after all steps:

Try a different startup disk. If you have an external drive with macOS, boot from it (hold Option at startup). If no panic occurs, the issue is with your internal drive or its cables.
Check for overheating. If the Mac feels hot or fans run loudly, let it cool down and try again. Overheating can cause kernel panics.
Disconnect all non-essential peripherals. USB hubs, external drives, and even some monitors can trigger panics. Boot with only the power cable connected.
If the panic happens during sleep/wake, try disabling Power Nap and automatic graphics switching (System Settings > Battery > Options).
If you suspect a specific kext but can’t identify it, boot into Safe Mode and check if the panic stops – if it does, the kext is likely third-party. You can also use the command kextstat in Terminal to list loaded kexts, but be careful not to remove system ones.
If all else fails, contact Apple Support or visit an Apple Store. They can run advanced diagnostics. If your Mac is under warranty, hardware repairs may be covered.

Frequently Asked Questions

Will I lose my data when fixing a kernel panic?

Most fixes, including Safe Mode, NVRAM reset, and macOS reinstall (as long as you choose “Reinstall” and not “Erase”), preserve your files. However, always back up before attempting any major fix.

What causes a kernel panic on Mac?

Common causes include incompatible third-party software or drivers, corrupted system files, faulty RAM or other hardware, overheating, and bugs in macOS itself. Rarely, a failing hard drive or SSD can cause it.

How do I read the kernel panic log?

After the Mac restarts, open Console (in /Applications/Utilities), click on “Diagnostic Reports” in the sidebar, and find the most recent report with a name like “Kernel-2024-05-01-123456.ips”. Look for the “panic(cpu …)” line and the list of kexts to identify the culprit.

Is a kernel panic a sign of a virus?

It’s unlikely. Kernel panics are usually caused by software bugs or hardware issues, not malware. If you’re concerned, run a reputable antivirus scan, but don’t assume a virus is the cause.

Can I fix a kernel panic by resetting SMC?

Yes, on Intel Macs, resetting the System Management Controller (SMC) can help if the panic is related to power or thermal management. Shut down, then on a laptop with a removable battery, remove it, hold the power button for 5 seconds, then reinsert the battery. For non-removable batteries and desktops, the method varies – check Apple’s support site for your specific model.

How often do kernel panics happen?

Occasionally, a one-time panic is not a concern. If it happens repeatedly (more than once a week), there’s likely an underlying issue that needs addressing.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →