Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Problem with Macbook Pro since last update of OS X Yosemite

Hello all,


My problem is quite strange.


Ever since my Macbook updated to the latest version of Yosemite it has behaving quite strange on startup:


When I start the Macbook from cold, I reach the log-in screen and type in my password, OS X begins to load normally and then reboots suddenly, I then have to retype my password after which everything works fine. It does this now every time I startup the machine. I performed the routine maintenance techniques and used the Recovery tools utility to repair the permissions and the hard disk. The hard disk drive had one error that I cannot remember which was fixed. After performing these steps, startup was normal on the first reboot but the problem returned afterwards.


I've looked at the console report, but I'm not sure up to what entry it is relevant to post it here, hopefully you guys will help with that.


Thanks !

MacBook Pro (13-inch Mid 2012), OS X Yosemite (10.10.5)

Posted on Sep 1, 2015 8:50 AM

Reply
6 replies

Sep 5, 2015 9:20 AM in response to jackborthwick

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter "BOOT_TIME" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Sep 5, 2015 8:16 AM in response to jackborthwick

I put Firevault back on, and although things were working fine up to now, my computed just crashed for no reason (that I understand),
Here are the contents of the latest Kernel report, unfortunately I could not get anything useful out of the CONSOLE as it is also playing up (it keeps insisting on showing entries recorded at 13:00 and not those that were just recorded, the search also found no BOOT_TIME entry even though the machine just rebooted by itself). I also had trouble posting the report directly in the body of the message, the editor complained about invalid characters.

Problem with Macbook Pro since last update of OS X Yosemite

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.