How to understand why Beautiful Screen of Death1 appeared?

enter image description here

When I tried to find what happened using "Console" I couldn't find anything useful in logs? There's no 'panic' or 'SIG*' in logs, so what should I look for?

Where does OSX writes the cause of it's death?

1 I'm not sure that it's called BSoD on OSX, but it doesn't look like kernel panic screen (black screen in text mode) either.

  • 1
    The term "BSOD" is generally used to refer only to the well-known "Blue Screen of Death" in Microsoft operating systems. Your use of that term applied to Mac OS X is quite original, and amusing. goo.gl/z4lxW
    – user9290
    Commented Mar 23, 2012 at 15:51

4 Answers 4


The kernel panic text is added to the log after you restart the computer, assuming that you did not reset PRAM (the kernel panic text is stored in PRAM until you restart). In Mac OS X v10.6, the logs are located in in /Library/Logs/DiagnosticReports. In Mac OS X v10.5, the logs are located in /Library/Logs/PanicReporter (source)

If you cannot find these files, or they contain no information on the kernel panic, then there is likely something wrong with the hardware of the computer. Running a system diagnostic or visiting the genius bar is probably your next step.

If you are really interested in attempting to resolve the issue yourself, you might find this guide to resolving OS X kernel panics helpful.


All panic and sleep failure logs are stored in /Library/Logs/DiagnosticReports since Mojave, in Kernel-%DATE%-.panic files.


It is indeed a kernel panic, the default behaviour is to display this screen rather than printing anything useful unfortunately.

If there's nothing in the system logs in console, then you can try booting your Mac in verbose mode. Hold Cmd + V while powering it on, you'll know when you get it right when loads of text gets written to screen instead of the normal spinning indicator.

Verbose mode causes kernel panics to log information to the screen rather than just showing the "you need to restart your computer" instruction. If you get another panic this should at least give you more specific details about the problem.

Apple's official troubleshooting guidelines recommend a safe boot and then a reboot. That support page also includes advanced troubleshooting information such as the location of the panic logs.

  • In my case it's not a boot problem, it appears when I run some script after OS is already running. Will verbose mode allow me to se console with some information in this case (not at boot time)? Commented Mar 23, 2012 at 15:26
  • 2
    Verbose mode persists as long as the kernel's up, rather than just at boot. It seems Macs now store kernel panics in PRAM and write them out to /Library/Logs/DiagnosticReports. You could check that directory to see if anything was written there when you rebooted after the panic. Commented Mar 23, 2012 at 15:33

The cause of a kernel panic can be found in the appreciate report logs and core dumps.

The location of kernel panic log can be found at /Library/Logs/panic.log on your startup disk.

Source: Retrieve Kernel Panic Log.

Cores dump (if enabled), can be located at /cores.

See: Where are core dumps written on Mac?

See also: Technical Note TN2118 about Kernel Core Dumps.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .