PDF download Download Article PDF download Download Article

This wikiHow will teach you how to force a kernel panic on a Mac. Be aware that forcing a kernel panic will cause you to lose all unsaved data and result in a system crash.

  1. 1
    Disable System Integrity Protection. For newer Macs, system integrity protection is used to stop the user from harming their system. You can disable this by turning your computer off, then, while holding the power button holding down Command+R at the same time. Click "Utilities and Terminal". Then type csrutil disable and press Enter. Restart your computer by clicking the Apple Symbol and pressing restart.
  2. You can open it from the Utilities folder in Finder under the Applications tab, or search for it using Spotlight.
    Advertisement
  3. Type client$ sudo dtrace -w -n "BEGIN{ panic();}" into Terminal and hit Enter.
    • client$ will be replaced by your account name (e.g., wikihow$ sudo dtrace -w -n "BEGIN{ panic();}").
  4. This will allow the kernel panic to commence.
  5. Once the system has rebooted, you should be able to access the crash logs, either directly from the window that opens up or from the computer's diagnostic reports.
  6. Advertisement

Expert Q&A

Ask a Question
200 characters left
Include your email address to get a message when this question is answered.
Submit
Advertisement

Tips

  • This can be useful if you're attempting to debug something.
  • The kernel panic screen will vary depending on which version of Mac OS X or macOS you're using.
    • Mac OS X 7 (Lion) and higher will display a message that starts with, "Your computer shut down because of a problem."
    • Mac OS X 6 (Snow Leopard) and earlier will display a message that starts with, "You need to restart your computer."
Submit a Tip
All tip submissions are carefully reviewed before being published
Name
Please provide your name and last initial
Thanks for submitting a tip for review!
Advertisement

Warnings

  • Do not regularly force kernel panics. Kernel panics are serious errors that occur when something at the hardware level goes wrong, so it's not a good idea to regularly force them.
Advertisement

You Might Also Like

Advertisement

About This Article

Stan Kats
Reviewed by:
Professional Technologist
This article was reviewed by Stan Kats. Stan Kats is a Professional Technologist and the COO and Chief Technologist for The STG IT Consulting Group in West Hollywood, California. Stan provides comprehensive technology solutions to businesses through managed IT services, and for individuals through his consumer service business, Stan's Tech Garage. Stan holds a BA in International Relations from The University of Southern California. He began his career working in the Fortune 500 IT world. Stan founded his companies to offer an enterprise-level of expertise for small businesses and individuals. This article has been viewed 34,976 times.
How helpful is this?
Co-authors: 7
Updated: November 21, 2022
Views: 34,976
Categories: Mac OS X
Thanks to all authors for creating a page that has been read 34,976 times.

Is this article up to date?

Advertisement