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

MacBook Pro (mid-2010) keeps crashing and restarting.

My mid-2010 MacBook Pro (running Yosemite) frequently crashes -- screen turns black and then restarts. I have a brand new SSD drive so that is not the problem. Has the motherboard gone bad? Can't seem to run Diagnostics either. Thanks for any help.

MacBook Pro, Mac OS X (10.7)

Posted on May 3, 2015 2:41 PM

Reply
10 replies

May 3, 2015 2:45 PM in response to jakeworld

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. Initially the words "String Matching" are shown in that box. 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.

May 3, 2015 2:57 PM in response to jakeworld

5/3/15 2:34:22.730 PM com.apple.xpc.launchd[1]: (com.citrix.ServiceRecords[345]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.citrix.Beacons

5/3/15 2:34:22.730 PM com.apple.xpc.launchd[1]: (com.citrix.ServiceRecords[345]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.citrix.ServiceRecords

5/3/15 2:34:27.402 PM mds[63]: (Volume.Normal:2464) volume:0x7ff42d020a00 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/MobileBackups

5/3/15 2:36:56.651 PM warmd[61]: [_bootcachectl_playlist_for_file:3202] Unable to generate playlist for file: 2 No such file or directory

5/3/15 2:38:30.000 PM bootlog[0]: BOOT_TIME 1430689110 0

May 3, 2015 3:17 PM in response to Linc Davis

No. The crashing did not start until about two months after adding the new SSD. The tech who did the work thinks the logic board may have gone bad. He suggested that I have the Genius Bar swipe and reinstall the OS (after I back it up which I am doing now). It does not crash constantly and (for example) has been on without any problem for the last one hour. For some reason, I cannot run diagnostics -- I powered down and held the "d" button when powering up, but the unit just turned on apparently without performing the diagnostics test.

May 3, 2015 3:24 PM in response to jakeworld

Here is the log from step 2:


5/3/15 3:16:12.605 PM WindowServer[177]: _CGXGetWindowOrderingGroup: Operation on a window 0x90 requiring rights 0x5 by caller System Preferences

5/3/15 3:16:22.542 PM WindowServer[177]: window a7 is already attached to window 8e

5/3/15 3:16:22.929 PM WindowServer[177]: window a7 is already attached to window 8e

5/3/15 3:16:22.937 PM WindowServer[177]: window a7 is already attached to window 8e

5/3/15 3:16:27.984 PM WindowServer[177]: _CGXGetWindowOrderingGroup: Operation on a window 0xa7 requiring rights 0x5 by caller System Preferences

5/3/15 3:17:41.152 PM com.avast.fileshield[513]: Missed 1 requests

5/3/15 3:17:41.000 PM kernel[0]: Google Chrome He (map: 0xffffff8013084960) triggered DYLD shared region unnest for map: 0xffffff8013084960, region 0x7fff89e00000->0x7fff8a000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

5/3/15 3:18:13.880 PM com.apple.prefs.backup.remoteservice[1055]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc

5/3/15 3:18:15.609 PM com.apple.backupd[1135]: Starting manual backup

5/3/15 3:18:15.816 PM com.apple.backupd[1135]: Backing up to /dev/disk1s2: /Volumes/My Passport for Mac/Backups.backupdb

5/3/15 3:18:15.954 PM com.apple.backupd[1135]: Forcing deep traversal on source: "Jake MacBook Pro" (device: /dev/disk0s2 mount: '/' fsUUID: 0F230222-3F09-3B85-A983-77A2C2DE4918 eventDBUUID: 860F5C68-F83F-4BD8-AABC-ED52B02272E9)

5/3/15 3:18:16.641 PM com.apple.backupd[1135]: Total content size: 308.83 GB excluded items size: 7.82 GB for volume Jake MacBook Pro

5/3/15 3:18:16.642 PM com.apple.backupd[1135]: Found 1740155 files (301.01 GB) needing backup

5/3/15 3:18:16.643 PM com.apple.backupd[1135]: 325.16 GB required (including padding), 1.17 TB available

5/3/15 3:19:21.592 PM com.avast.fileshield[513]: Missed 2 requests

5/3/15 3:19:30.156 PM com.avast.fileshield[513]: Missed 1 requests

5/3/15 3:20:20.000 PM kernel[0]: Google Chrome He (map: 0xffffff80132cd4b0) triggered DYLD shared region unnest for map: 0xffffff80132cd4b0, region 0x7fff89e00000->0x7fff8a000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

5/3/15 3:21:01.805 PM CalendarAgent[271]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

5/3/15 3:21:01.957 PM CalendarAgent[271]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

5/3/15 3:21:14.000 PM kernel[0]: Over-release of kernel-internal importance assertions for pid 86 (launchservicesd), dropping 1 assertion(s) but task only has 0 remaining (0 external).

5/3/15 3:22:05.740 PM sandboxd[395]: ([1080]) mdworker(1080) deny file-read-data /Users/Barry/Library/Preferences/com.apple.security.plist (import fstype:hfs fsflag:480D000 flags:10000025E diag:0 isXCode:0 uti:com.apple.application-bundle plugin:/Library/Spotlight/Application.mdimporter - find suspect file using: sudo mdutil -t 159)

5/3/15 3:22:06.576 PM com.avast.fileshield[513]: Missed 1 requests

5/3/15 3:22:22.290 PM com.avast.fileshield[513]: Missed 1 requests

May 3, 2015 4:00 PM in response to jakeworld

"Avast" is the worst of the whole wretched lot of commercial "security" products for the Mac. Not only does it fail to protect you from any real danger, it may send personal data (such as web browsing history and the contents of email messages) back to the developer without your knowledge, give false warnings, destabilize and slow down the computer, expose you to network attack, and corrupt the network settings and the permissions of files in your home folder. Removing it may not repair all the damage.

Some versions of the product also inject advertising into web pages. In short, apart from the fine print in the license agreement, Avast is indistinguishable from malware, and is arguably worse than any known malware now in circulation.

Back up all data, then remove Avast according to the developer's instructions. Restart.

If you tried to remove Avast by dragging an application to the Trash, you'll have to reinstall it and then follow the instructions linked above.

MacBook Pro (mid-2010) keeps crashing and restarting.

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