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

Macbook Pro Retina 15" Freezes Randomly - Cursor and Keyboard Unresponsive

Hello, I bought a new Macbook Pro Retina 15 inch model (top spec) around New Years this year and it has been randomly freezing up. The screen doesn't go black at all, the cursor and keyboard just become unresponsive so I have to hold down the power button and do a restart. This happens maybe once every few days. This is the third time it has happened now.


I have looked at the error logs but I'm afraid I don't really understand what they're indicating. I also have the creaking issue with the bottom of the Macbook Pro case making a creaking noise if its on my lap. Considering I paid almost £2k for this laptop I'm very disappointed with this. For the time being I have switched the automatic graphics switching off but next time, if it does crash/freeze again, I will post an error log to see what it could be.


Anybody got any ideas what can be causing this? Its roughly 1 month old, has Yosemite installed as the OS and hasn't been dropped or anything at all. My last Macbook was a 13 inch model and lasted 4 years with 1 crash throughout the entire time.

MacBook Pro with Retina display, OS X Yosemite (10.10.2)

Posted on Feb 6, 2015 12:01 PM

Reply
Question marked as Best reply

Posted on Feb 6, 2015 8:55 PM

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.

24 replies
Question marked as Best reply

Feb 6, 2015 8:55 PM in response to babymilo91

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.

Feb 7, 2015 5:46 PM in response to Linc Davis

Hello, I've done everything you said and there's only a few .hang reports but no .crash or .shutdownstall or .panic reports in that dropdown menu at all.


However, under that section there are a lot of .diag reports relating to powerstats at the time of the incidents.


Under the User Diagnostics Report tab there are .crash reports relating to com.apple.WebKit.Networking.

Feb 7, 2015 7:13 PM in response to babymilo91

Also, I have run the Etrecheck tool.


EtreCheck version: 2.1.8 (121)

Report generated 8 February 2015 03:12:16 GMT

Download EtreCheck from http://etresoft.com/etrecheck


Click the [Click for support] links for help with non-Apple products.

Click the [Click for details] links for more information about that line.


Hardware Information: ℹ️

MacBook Pro (Retina, 15-inch, Mid 2014) (Technical Specifications)

MacBook Pro - model: MacBookPro11,3

1 2.5 GHz Intel Core i7 CPU: 4-core

16 GB RAM Not upgradeable

BANK 0/DIMM0

8 GB DDR3 1600 MHz ok

BANK 1/DIMM0

8 GB DDR3 1600 MHz ok

Bluetooth: Good - Handoff/Airdrop2 supported

Wireless: en0: 802.11 a/b/g/n/ac

Battery Health: Normal - Cycle count 48


Video Information: ℹ️

Intel Iris Pro

NVIDIA GeForce GT 750M - VRAM: 2048 MB

Color LCD spdisplays_2880x1800Retina


System Software: ℹ️

OS X 10.10.2 (14C109) - Time since boot: one day 12:11:18


Disk Information: ℹ️

APPLE SSD SM0512F disk0 : (500.28 GB)

EFI (disk0s1) <not mounted> : 210 MB

Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB

Macintosh HD (disk1) / : 499.10 GB (467.70 GB free)

Core Storage: disk0s2 499.42 GB Online


USB Information: ℹ️

Apple Internal Memory Card Reader

Apple Inc. BRCM20702 Hub

Apple Inc. Bluetooth USB Host Controller

Apple Inc. Apple Internal Keyboard / Trackpad


Thunderbolt Information: ℹ️

Apple Inc. thunderbolt_bus


Gatekeeper: ℹ️

Mac App Store


Problem System Launch Agents: ℹ️

[failed] com.apple.SafariNotificationAgent.plist [Click for details]


Launch Agents: ℹ️

[loaded] com.oracle.java.Java-Updater.plist [Click for support]


Launch Daemons: ℹ️

[loaded] com.microsoft.office.licensing.helper.plist [Click for support]

[loaded] com.oracle.java.Helper-Tool.plist [Click for support]

[not loaded] org.eyebeam.SelfControl.plist [Click for support]


User Launch Agents: ℹ️

[loaded] com.google.keystone.agent.plist [Click for support]

[failed] com.spotify.webhelper.plist [Click for support]


User Login Items: ℹ️

None


Internet Plug-ins: ℹ️

SharePointBrowserPlugin: Version: 14.4.7 - SDK 10.6 [Click for support]

Silverlight: Version: 5.1.30514.0 - SDK 10.6 [Click for support]

QuickTime Plugin: Version: 7.7.3

JavaAppletPlugin: Version: Java 8 Update 31 Check version

Default Browser: Version: 600 - SDK 10.10


Safari Extensions: ℹ️

Adblock Plus


3rd Party Preference Panes: ℹ️

Java [Click for support]


Time Machine: ℹ️

Time Machine not configured!


Top Processes by CPU: ℹ️

6% WindowServer

1% hidd

1% Finder

1% fontd

0% OneDrive


Top Processes by Memory: ℹ️

326 MB Safari

258 MB com.apple.WebKit.WebContent

137 MB WindowServer

120 MB Finder

103 MB systemstatsd


Virtual Memory Information: ℹ️

10.28 GB Free RAM

3.34 GB Active RAM

1.64 GB Inactive RAM

1.53 GB Wired RAM

8.59 GB Page-ins

0 B Page-outs


Diagnostics Information: ℹ️

Feb 6, 2015, 03:00:54 PM Self test - passed

Feb 8, 2015 9:07 AM in response to babymilo91

I've booked an appointment with an Apple Genius for Friday. The creaking is still happening but there have been no further freezes so far. I am, as I've only had this for a month, going to push for a new replacement because considering the money spent this is ridiculous product quality. Apple's standards seem to have declined massively since the passing of Steve Jobs.

Feb 8, 2015 5:12 PM in response to babymilo91

Just had another lock up. At the time I was playing a video on youtube and just opened Spotify. I think it could be Spotify related.


The music was still playing but the trackpad and keyboard wouldn't respond. But the video was running fine and the music could still be heard.


Feb 9 00:46:38 xyz-MacBook-Pro.local Spotify Helper[1056]: Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650


Feb 9 00:46:38 xyz-MacBook-Pro.local Spotify Helper[1056]: The function ‘CGFontSetShouldUseMulticache’ is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance.


Feb 9 00:47:25 xyz-MacBook-Pro kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004051 - retrying


Feb 9 00:47:46 --- last message repeated 2 times ---


Feb 9 00:47:46 xyz-MacBook-Pro kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004051 (interface 0, reportID 0x0)


Feb 9 00:47:46 xyz-MacBook-Pro kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configurePower


Feb 9 00:48:45 localhost bootlog[0]: BOOT_TIME 1423442925 0


Feb 9 00:48:47 localhost syslogd[17]: Configuration Notice:

ASL Module "com.apple.AccountPolicyHelper" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

May 6, 2016 8:52 PM in response to babymilo91

Like the others above me, I also have a Macbook Pro Retina 13" early 2015 model. In the last month, I found that a few times each week, my computer freezes. And by freezing, I mean that the keyboard & trackpad are completely unresponsive. No spinning beach ball happens either.


5/6/16 10:39:39.308 PM watchdogd[363]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

5/6/16 10:39:39.309 PM SubmitDiagInfo[368]: Couldn't load config file from on-disk location. Falling back to default location. Reason: Won't serialize in _readDictionaryFromJSONData due to nil object

5/6/16 10:39:39.338 PM SubmitDiagInfo[368]: Couldn't load config file from on-disk location. Falling back to default location. Reason: Won't serialize in _readDictionaryFromJSONData due to nil object

5/6/16 10:39:50.410 PM CommCenter[254]: Telling CSI to go low power.

5/6/16 10:39:50.411 PM AirPlayUIAgent[318]: 2016-05-06 10:39:50.411286 PM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification

5/6/16 10:39:50.000 PM kernel[0]: Setting BTCoex Config: enable_2G:1, profile_2g:0, enable_5G:1, profile_5G:0

5/6/16 10:39:50.522 PM identityservicesd[274]: <IMMacNotificationCenterManager: 0x7fb54956a810>: notification observer: com.apple.iChat notification: __CFNotification 0x7fb549776860 {name = _NSDoNotDisturbEnabledNotification}

5/6/16 10:39:50.523 PM imagent[319]: <IMMacNotificationCenterManager: 0x7fcca0f26090>: notification observer: com.apple.FaceTime notification: __CFNotification 0x7fcca0e3a240 {name = _NSDoNotDisturbEnabledNotification}

5/6/16 10:39:50.541 PM identityservicesd[274]: <IMMacNotificationCenterManager: 0x7fb54956a810>: NC Disabled: NO

5/6/16 10:39:50.541 PM imagent[319]: <IMMacNotificationCenterManager: 0x7fcca0f26090>: NC Disabled: NO

5/6/16 10:39:50.548 PM identityservicesd[274]: <IMMacNotificationCenterManager: 0x7fb54956a810>: DND Enabled: YES

5/6/16 10:39:50.548 PM imagent[319]: <IMMacNotificationCenterManager: 0x7fcca0f26090>: DND Enabled: YES

5/6/16 10:39:50.548 PM identityservicesd[274]: <IMMacNotificationCenterManager: 0x7fb54956a810>: Updating enabled: NO (Topics: (

))

5/6/16 10:39:50.548 PM imagent[319]: <IMMacNotificationCenterManager: 0x7fcca0f26090>: Updating enabled: NO (Topics: (

))

5/6/16 10:40:16.000 PM bootlog[0]: BOOT_TIME 1462592416 0

Macbook Pro Retina 15" Freezes Randomly - Cursor and Keyboard Unresponsive

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