A kernel panic is macOS's equivalent of the Blue Screen of Death — a grey or black screen telling you the computer needed to restart, sometimes accompanied by a message in multiple languages. It's macOS's way of shutting down immediately when the core of the operating system hits an error it can't safely recover from. This guide explains what causes kernel panics on both Intel and Apple Silicon Macs, and takes you through a structured process for finding and fixing the cause.

What exactly is a kernel panic?

The kernel is the core part of macOS that manages memory, hardware communication, and process scheduling. When it encounters an error serious enough that continuing could corrupt data or damage hardware, it "panics" — stopping everything immediately and restarting, rather than trying to carry on in an unstable state. Unlike a simple app crash, a kernel panic affects the entire system, not just one program.

Reading the panic report

macOS automatically saves a detailed report each time a kernel panic occurs, and reading it is the fastest way to identify a specific cause.

  1. Open System Settings > General > About > System Report (or search "System Information").
  2. In the sidebar, under Software, click Logs, or alternatively open Console (found via Spotlight search) and look in the sidebar under Crash Reports for entries prefixed "Kernel".
  3. Look near the top of the report for a line beginning "panic(cpu" followed by details of what the kernel was doing.
  4. Scroll to the section listing loaded kernel extensions (kexts), particularly any third-party ones (not prefixed com.apple). A third-party kext named close to the top of the crashed process list is a strong lead, as third-party drivers and system extensions are a common cause of panics.
  5. Note the exact date and time, and cross-reference against anything you'd just done — plugged in a new peripheral, woken the Mac from sleep, or opened a specific application.

Common causes of kernel panics

  • Third-party kernel extensions or system extensions, especially from older security software, virtualisation tools, or hardware utilities not yet updated for your macOS version
  • Faulty or incompatible RAM, on older Intel Macs with user-upgradeable memory
  • Peripheral or driver conflicts, particularly external displays, docks, or audio interfaces with outdated drivers
  • Overheating, especially on older MacBook models with worn thermal paste or dust-clogged fans
  • Failing storage, where read/write errors on the drive corrupt data the kernel depends on
  • A corrupted macOS installation, following an interrupted update or a disk error
  • Faulty external hardware, such as a failing USB-C hub, dock, or external drive drawing unstable power

Step-by-step troubleshooting

1. Update macOS and all software

  1. Open System Settings > General > Software Update and install any pending updates, as many kernel panic causes are fixed in point releases.
  2. Update any third-party software you suspect might be involved, particularly security tools, VPN clients, and virtualisation software (Parallels, VMware Fusion, Docker) — these commonly install low-level system extensions.
  3. Check System Settings > Privacy & Security > Login Items & Extensions for outdated system extensions, particularly ones tied to software you no longer actively use, and remove them if unnecessary.

2. Boot into Safe Mode to isolate the cause

  1. Apple Silicon Macs: shut down completely, then press and hold the power button until "Loading startup options" appears, select your startup disk, then hold Shift and click Continue in Safe Mode.
  2. Intel Macs: restart and immediately hold Shift until the Apple logo appears.
  3. Safe Mode disables non-essential kernel extensions and login items, and also runs some disk checks automatically on startup. If kernel panics stop occurring while in Safe Mode, this strongly points to a third-party extension or startup item as the cause, since Safe Mode largely excludes them.
  4. Once confirmed, restart normally and work through System Settings > General > Login Items & Extensions, disabling third-party extensions one at a time and testing between each to isolate the specific culprit.

3. Check Disk Utility for storage errors

  1. Open Disk Utility (via Spotlight search).
  2. Select your startup disk (the physical drive, not just the volume) in the sidebar, and click First Aid.
  3. Let it run fully — this checks and repairs the disk's file system structure.
  4. If First Aid reports errors it cannot fix, or the process fails to complete, this points toward failing storage hardware, particularly on older Macs, and data should be backed up immediately via Time Machine or a manual copy to an external drive.

4. Test RAM (Intel Macs with upgradeable memory)

  1. Shut down completely and disconnect all peripherals except keyboard, mouse, and display.
  2. Restart while holding D to run Apple Diagnostics (or hold Option+D to run it over the internet if the local version doesn't load), which includes a memory test among its checks.
  3. If you've recently added third-party RAM, try removing it and testing with only the original modules to rule out a compatibility issue.

Apple Silicon Macs have RAM integrated into the chip package and cannot be tested or upgraded this way; a RAM-related panic on these models is rare and would point to a deeper hardware fault requiring professional diagnosis.

5. Disconnect peripherals

  1. Shut down, disconnect every non-essential peripheral (external displays, docks, hubs, external drives, printers), and use the Mac for a period with just the essentials connected.
  2. If panics stop, reconnect peripherals one at a time, testing between each, to identify which device or its cable/driver is causing the conflict.
  3. Try a different cable or USB-C port for any peripheral you reintroduce, as a damaged cable or port can itself cause instability.

6. Check for overheating

  1. Download a free monitoring utility such as Macs Fan Control or iStat Menus to check CPU temperature and fan speed under normal use and load.
  2. Ensure vents (typically along the hinge or underside on MacBooks) are free of dust and the Mac isn't being used on a soft surface that blocks airflow.
  3. On older MacBooks (roughly five years or older), dried thermal paste is a realistic possibility if temperatures climb rapidly under light load — this requires professional reapplication given the tight tolerances of Mac cooling assemblies.

Kernel panics that happen consistently only when the lid is closed and the Mac is in clamshell mode, or only when waking from sleep, point specifically toward a sleep/wake driver conflict — try disabling Power Nap under System Settings > Battery > Options as a targeted test.

Reinstalling macOS

If the panic report consistently names Apple's own kernel rather than a third-party extension, and Safe Mode, Disk Utility, and peripheral checks haven't resolved it, reinstalling macOS is a reasonable next step.

  1. Back up fully via Time Machine first.
  2. Restart into Recovery Mode (hold power button on Apple Silicon until startup options appear, and choose Options; hold Command+R on Intel Macs during startup).
  3. Choose Reinstall macOS from the utilities window, which reinstalls the operating system while typically preserving your files, though a full backup remains essential beforehand.

Still not fixed?

If kernel panics persist after updates, Safe Mode testing, disk checks, RAM testing where applicable, and a clean macOS reinstall, the cause is very likely a genuine hardware fault — most often a failing logic board component or storage module. Apple Diagnostics (hold D at startup) can sometimes flag this directly, and from there, booking a Genius Bar appointment or an authorised Apple service provider is the most reliable route, particularly if the Mac is still covered by AppleCare or Apple's standard warranty.

Was this guide helpful? Explore more Windows & macOS Tweaks guides, or browse all Operating System & Software articles.