Mac Keeps Restarting or Crashing? 10 Fixes

Open Finder → Go → Go to Folder → type /Library/Logs/DiagnosticReports/. Look for files named "Kernel_[date].panic" or "Sleep Wake Failure." Open the most recent one in TextEdit. Scan for lines starting with "Backtrace" — these name the process or driver that caused the crash. If you see a third-party app name or a kext (kernel extension) filename, that's your culprit.

System Settings → General → Software Update. Install any pending macOS update first — kernel panics introduced by OS updates are usually patched quickly. Then open the App Store → Updates tab and update all apps. Third-party apps with kernel extensions (security tools, virtualization, audio interfaces) are the most common kernel panic triggers and frequently release compatibility patches after macOS updates.

If crashes started after installing something new, remove it. Applications with kernel extensions are the main offenders: antivirus software, VPNs, virtualization apps (Parallels, VMware), audio drivers, and backup tools. To fully remove kernel extensions, don't just drag the app to Trash — use the app's official uninstaller or a tool like AppCleaner. Check System Settings → Privacy & Security → Extensions for any third-party kernel extensions you don't recognize.

Apple Silicon: hold Power button at startup until "Loading startup options" appears → hold Shift → click "Continue in Safe Mode." Intel: hold Shift immediately after startup chime until login screen. Safe Mode disables all third-party kernel extensions and login items. If your Mac runs stably in Safe Mode for hours, a third-party extension or login item is causing the panic. Identify it from the crash log and remove it.

Restart into Recovery Mode (hold power on Apple Silicon, hold Cmd+R on Intel) → Disk Utility → select Macintosh HD → First Aid → Run. File system corruption on the startup volume is a common kernel panic cause, especially after crashes or unexpected power loss. If First Aid finds errors it can't repair, your SSD may be failing.

Faulty RAM is a classic kernel panic cause on Intel Macs. Run Apple Diagnostics (hold D at startup). Error codes starting with "MEM" indicate RAM issues. You can also run an extended memory test via Apple Hardware Test. If RAM errors are confirmed, the RAM module needs replacement. Note: Apple Silicon Macs have unified memory soldered to the chip — it cannot fail independently of the logic board.

Disconnect all external devices: USB hubs, external drives, monitors (use built-in display only), docks, and dongles. If crashes stop, reconnect devices one at a time to identify the problematic one. A malfunctioning USB-C dock that sends bad voltage, a failing external drive, or a third-party monitor with buggy DisplayPort firmware can all trigger kernel panics. This is especially common with cheaper USB-C hubs.

Intel: restart and hold Option+Cmd+P+R for 20 seconds. Apple Silicon: shut down fully, wait 30 seconds, restart. NVRAM stores hardware configuration including sleep settings that can trigger wake-from-sleep panics. A reset clears corrupted hardware state that survives normal restarts.

Boot into Recovery Mode → Reinstall macOS. This reinstalls the OS without touching your user data, apps, or settings. It replaces all system files including any corrupted kernel components. Takes 30-60 minutes. If panics persist after a clean OS reinstall with all external hardware disconnected, the issue is hardware-level and needs service.

Apple Silicon Macs have a built-in diagnostics suite more powerful than the startup D-key test. In Recovery Mode, some models offer "Mac Resource Inspector" (MRI) under the Utilities menu — run the full suite. For Intel Macs, an Apple Authorized Service Provider can run ASD (Apple Service Diagnostic) which performs deeper hardware tests than user-accessible tools. If the Mac has an active AppleCare+ plan, kernel panics caused by hardware defects are covered.