How to capture the panic log, immediate actions likely to help make a diagnosis, and how to read the panic log.
Using the correct term gets us half way to a diagnosis: kernel panics, freezes, app crashes and unresponsive apps are distinguished here.
What to do when your Mac panics during booting, and enters a boot loop, or when it simply fails to get to the login window.
Why you should keep a copy of the Panic Log. How to check that your Mac isn’t the cause. And above all, don’t panic.
Do you have a suitable Mac you could afford to lose completely for a while? Can you restore your Apple silicon Mac in DFU mode? You could be just the right person.
Big Sur and Monterey allow kernel extensions with limitations, particularly on M1 models. Full details, including how to control them.
How the kernel relies on its extensions to make your Mac work, and has highest privilege for stability and security. How this must change for Apple Silicon.
Apps may crash, but kernels panic. Don’t accept your Mac just panics often. It should never panic at all, and more than one panic a year needs to be properly investigated and reported.
What’s the difference between an app and kernel memory leak? How would you notice one, and how to investigate it, and (sometimes) work around the problem.
Recovering from one regular panic should be straightforward. But what if it’s a boot loop, in which your Mac tries to start up, panics, restarts, in an endless loop? Don’t panic: here are the solutions.