HT201753: Mac OS X: How to log a kernel panic

Learn about Mac OS X: How to log a kernel panic
alexcgrade

Q: why OSX keeps rebooting itself without warning and in the middle of any type of work?

I'm on a Mac Pro 3.1 - 8 core dated 2008

OSX is starting to behave as if it was a microsoft OS. It keeps rebooting automatically ruining any type of work

I've reinstalled the OSX

I've tried OSX Leopard, Snow Leopard, Mountain Lion, Mavericks, El Capitan wasting hours and hours

I've made cmd+R to verify and repaired permissions already for several times

The system is no longer stable since last July.

keeps rebooting at its own wish

I've done the basic and also the throughout system diagnostic with the original installation OSX cd disk and it says that is no hardware problem in the Mac

A bug must be in OSX or is there something specific that you can please give us all a clue to resolve this.

As it appears that this is happening across several types of different Macs, like mac book pros, mac pros and so on as it can be verified in these apple forums.

 

Your help is appreciated

Mac Pro, OS X Mountain Lion (10.8.5), null

Posted on May 4, 2016 3:28 PM

Close

Q: why OSX keeps rebooting itself without warning and in the middle of any type of work?

  • All replies
  • Helpful answers

  • by lllaass,

    lllaass lllaass May 4, 2016 3:43 PM in response to alexcgrade
    Level 10 (187,764 points)
    Desktops
    May 4, 2016 3:43 PM in response to alexcgrade

    • Note the time of the next unintended reboot. After rebooting open the Console app in Finder>Applications>Utilities and look for log entries at the time of the reboot. Post suspicious ones here.

    Look before the log entry that starts with BOOT_TIME since that is the first line of a bootup

     

    It still could be a hardware problem. Apple harsware test only reports no errors found. That does not mean that there are no hardware problems.

  • by alexcgrade,

    alexcgrade alexcgrade May 4, 2016 3:49 PM in response to lllaass
    Level 1 (4 points)
    Desktops
    May 4, 2016 3:49 PM in response to lllaass

    i have changed the hard drive

    i have changed the ram

    i have cleaned the entire machine

    seems a OSX bug as its happening to many users with many types of macs

    i'll post the log asap

     

    thanks

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder May 4, 2016 7:45 PM in response to alexcgrade
    Level 9 (60,677 points)
    Desktops
    May 4, 2016 7:45 PM in response to alexcgrade

    do you have any kernel panic logs?

     

    If a kernel panic occurs, information is added to a log file in the folder /Library/Logs/DiagnosticReports

  • by alexcgrade,

    alexcgrade alexcgrade May 5, 2016 12:02 PM in response to Grant Bennet-Alder
    Level 1 (4 points)
    Desktops
    May 5, 2016 12:02 PM in response to Grant Bennet-Alder

    ok I have thousands of lines of code readable in the console different logs what exactly I should be looking for?

    By the way this is against the Steve Jobs legacy and Apple policy of user friendly!

    Is there a simpler way? A user should not have to be analysing kernel errors right?

  • by alexcgrade,

    alexcgrade alexcgrade May 5, 2016 12:07 PM in response to lllaass
    Level 1 (4 points)
    Desktops
    May 5, 2016 12:07 PM in response to lllaass

    ok I have thousands of lines of code readable in the console different logs what exactly I should be looking for on the left categories?

    The major noticeable event here is shutdown stall

    no BOOT time seems to appear anywhere, is there an update for the Mac that can help in this kind of malfunctions?

  • by dot.com,

    dot.com dot.com May 5, 2016 12:47 PM in response to alexcgrade
    Level 2 (434 points)
    May 5, 2016 12:47 PM in response to alexcgrade

    You could note the time the next crash and look at the messages right BEFORE then to get a hint at what the real problem might be

     

    Make sure you have "All Messages" selected in the Console app when you are looking and make sure the "Filter" fill-in box at the top right has nothing in it so that you see everything. Once you get things narrowed down to a specific error or app or whatever seems to be the common thread preceding the crashes post those details for further assistance.

     

    You might try to look for "BOOT_TIME" (don't forget the underscore) messages - think this is the first message during a boot-up sequence that appears in the console logs.

     

    Good luck...