My Mac book pro retina has started mis behaving. I am unsing Mountain Loin with atest updates.
When I startup and login I get a blue screen immediately after login. However if I reboot and try again it seems to start ok? Any idea what is going on. This has just started in the last few weeks, and I have checked my startup items and there is nothing new in there.
Many thanks
AK
MacBook Pro (Retina, Mid 2012), OS X Mountain Lion (10.8.2)
It's not really clear what you mean. Every other time you boot you get a blue screen? Or only once in a while?
Hard to say how often this is happening. It was not consistent. It happened twice today, but then has not happened since despite forcing a few restarts.
I am trying to see if I can isolate the probelm by getting it to happen repeatably. If it happens again I will try and see what was in the logs.
Any ideas welcome.
If you have more than one user account, these instructions must be carried out as an 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. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged before the boot, while the system was unresponsive or was failing to shut down. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V). Please include the BOOT_TIME message at the end of the log extract.
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.
Getting concerned now - had number of crashes. But have log of when it happened (Many pages long). Portion included below - this is just before the crash and I had to force a restart.
I have reinstalled OSX, but still got blue screen after install. Also noted there was an OSX update today - so installed that too. I have removed all startup items for the moment. (Was using ClamXav Sentry)
Still not convinced all is well.
02/03/2013 21:13:52.763 Finder[254]: *** WARNING: Method userSpaceScaleFactor in class NSWindow is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
02/03/2013 21:13:52.772 ReportCrash[217]: Saved crash report for Finder[164] version 10.8.1 (10.8.1) to /Users/xxxxxxxxxxx/Library/Logs/DiagnosticReports/Finder_2013-03-02-211352_XXXX XXXXX-MacBook.crash
02/03/2013 21:13:52.778 Finder[254]: *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
02/03/2013 21:13:52.849 WindowServer[105]: CGXGetConnectionProperty: Invalid connection 50435
02/03/2013 21:13:52.849 WindowServer[105]: CGXGetConnectionProperty: Invalid connection 50435
02/03/2013 21:13:52.849 WindowServer[105]: CGXGetConnectionProperty: Invalid connection 50435
02/03/2013 21:13:52.849 WindowServer[105]: CGXGetConnectionProperty: Invalid connection 50435
02/03/2013 21:13:52.850 WindowServer[105]: CGXGetConnectionProperty: Invalid connection 50435
02/03/2013 21:13:54.702 GoogleSoftwareUpdateDaemon[210]: -[KeystoneDaemon logServiceState] GoogleSoftwareUpdate daemon (1.1.0.3659) vending:
com.google.Keystone.Daemon.UpdateEngine: 1 connection(s)
com.google.Keystone.Daemon.Administration: 0 connection(s)
02/03/2013 21:13:55.640 warmd[60]: [___bootcachectl_filter_out_sharedio_from_history_block_invoke_0:2321] Unable to open i386 shared cache: 2 No such file or directory
02/03/2013 21:13:55.994 ClamXavSentry[204]: clamd launched successfully. Continuing...
02/03/2013 21:13:56.007 ClamXavSentry[204]: scan email files
02/03/2013 21:13:56.008 ClamXavSentry[204]: I will quarantine infected files
02/03/2013 21:13:56.009 ClamXavSentry[204]: clamdconfEncoding: 4
02/03/2013 21:13:56.300 sudo[277]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/local/clamXav/bin/freshclam --log=/usr/local/clamXav/share/clamav/freshclam.log --on-update-execute=EXIT_1
02/03/2013 21:14:34.000 bootlog[0]: BOOT_TIME 1362258874 0
The crash report is long - many lines. Happy to add if you think it will help.
Also, curiously, when I try to view some of the crash reports in Console the console app itself crashes.....and generates a send to Apple report.
Any thoughts appreciated.
Are you unable to post a crash report, as requested?
If you haven't already tried Safe Mode as mentioned by dominic23 then do so, and also try repairing permissions on the boot drive which can be done by restarting and holding Command-S at startup, followed by running the following two commands at the command prompt when you are dropped to it (everything will be white text on a black background--this is normal):
/sbin/mount -uw /diskutil repairPermissions /When the second command is done, type "reboot" to restart the system normally.
In addition, try resetting permissions on your user account by restarting the system and holding Command-R to boot to the OS X Recovery HD partition. When you see the OS X Tools window appear, go to the Utilities menu and choose Terminal from there. In the Terminal enter the command "resetpassword" (all one word), after which you will see a small utility show up.
In this utility, select the hard drive, and then select your user account from the drop-down menu, followed by clicking the Reset button in the "Reset Home Directory Permissions and ACLs" section. When finished, choose "Restart" from the Apple menu.
My crash reports in console seem to have been cleared - there must be a regular purge. I will have to wait and see if the problem happens again unless the reports are still on my system somewhere.
ak1956 wrote:
My crash reports in console seem to have been cleared - there must be a regular purge.
Not that I'm aware of. Certainly not with my setup where some are almost two years old. Are you sure you were looking in the correct location?
Blue screen after log in
