Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

What type of Macbook are you using?


  • Total voters
    306
  • Poll closed .

orthorim

Suspended
Feb 27, 2008
733
350
I am not sure my crash is the same but it shares many characteristics:

- Always happens in Safari, usually on Facebook. I've since moved to Chrome for Facebook and it's never crashed since. In Safari it would happen every few days.
- Everything freezes suddenly
- The system logs have no information as to the crash - there is no kernel panic reports, nothing. No offer to send a bug report to Apple on restart either.

I tried everything to make this go away - SMC and PRAM reset, disk first aid, removed any 3rd party kernel extensions and so on, nothing helped. Switching to Chrome for Facebook mitigates it.

Because of the nature of the crash my conclusion was that it's probably the graphics driver and some funky stuff Safari is doing.

2012 Retina MBP, 15"
 

EvanHelpme

macrumors newbie
Sep 22, 2014
15
3
Not sure if you tried this but next time it happens try running this through ssh, this is like a restart, but of only the graphical part of the system that WindowServer manages.(same as respring on iOS).

Yes, I've tried that (both HUPing and completely killing WindowServer). It doesn't make any visible difference.
 

TomSonik

macrumors newbie
May 15, 2016
6
0
Germany
I have the Same issues. Try almost everything like install backup with 10.11.3, clean install. Had it know 3 times at the Apple Store for a repair. Get new logic board, new ssd and ram. Still same problem. Today I tried to install the beta of 10.11.5 but after all the freez came just 50 minutes later.

Have no clue so far. Hope for an solution with the final 10.11.5

PS: once I was in the recovery mode and even there the iMac 5K newest model freez.

 
Last edited:

Antonnn

macrumors member
Original poster
Mar 25, 2016
57
37
Since the end of march I also have to deal with the same issues. Running OSX 10.11.4 on my Macbook Pro Retina 15’’ 2,3ghz late 2013. 10 til 20 crashes (to black screen) or screen freezes per day is normal average. It happens while running multiple applications like Photoshop and Premiere Pro or just running Chrome, on the most illogical moments.

The strange part is when the Macbook Pro is AC powered with a full battery while it stands on my desktop at my office there are no crashes or freezes at all. At home with the same situation and running the same applications the problems occur. What could me the big difference? WIFI/LAN? A connected network drive? Temperature in the room?

When looking in my console for shutdown reasons, these are the most common causes:

kernel[0]: Previous shutdown cause: 3
kernel[0]: Previous shutdown cause: 128

Update:
5 minutes after updating OSX to 11.10.5 Beta (15F31a) my Macbook Pro crashed (freeze) again.

Not sure if you follow my first #1 or if you read it at all. Not sure what you mean by (crashes to black screen) so I'm assuming you mean no video on the screen but the computer is on.
First check if your macbook is affected by the gpu failure, apple is doing a recall of your exact model.
https://www.apple.com/support/macbookpro-videoissues/

Macbook pro 15 2013 has 2 graphics cards, if you have the version with two of them try switching between them and see if it crashes on both. You can switch between them by using this app https://gfx.io.
The reason it is not crashing at work if it's the issue I think it's either because at work it sits on the desk with plenty ventilation, or while it is AC powered it is not using the integrated video or viceversa.
 

la_manzana

macrumors newbie
May 3, 2016
23
14
I'm aware that it is still alive behind the scenes, although if you keep clicking and pressing on random keys it freezes completely.

Not sure if you tried this but next time it happens try running this through ssh, this is like a restart, but of only the graphical part of the system that WindowServer manages.(same as respring on iOS).
(be warned, it will restart all your apps as well so it's still not ideal even if it comes back to live)

Code:
sudo killall -HUP WindowServer


I also tried to kill the WindowServer over SSH with the HUP(=1) signal without success.
I read afterwards that the signal KILL(=9) is a harder way to kill an process as HUP.

You should maybe try this next time the freeze happen:
Code:
sudo killall -KILL WindowServer



Yes, I've tried that (both HUPing and completely killing WindowServer). It doesn't make any visible difference.

@EvanHelpme: Do you mean with "completely killing" that you already tried the hardest "-KILL" signal?
 
Last edited:

1amageek

macrumors newbie
May 15, 2016
2
0
■ After the MacBook Pro has returned from the sleep of about 10 minutes, the screen will freeze.
※ trackpad, keyboard works. Screen switching the screen you will see.

■ If you return from a long period of time of sleep, keyboard, track pad will not work. In order to re-start, only kill.

■ even after the re-start, it does not work the keyboard and track pad.
※ screen when you connect the other keyboard is not a freeze of the screen for the move.
※ visceral keyboard after the Mac is booted does not work, but to get into Safe Mode by pressing the Option at the time of start-up, there is no problem with the keyboard itself.
※ RAM reset can also be performed in the internal organs keyboard.


The next day, the keyboard is also no longer operated by the same bug. Only the power button without RAM reset also enter in safe mode is enabled.
 

Seramir

macrumors member
Nov 10, 2006
85
20
You know what the funny thing is? I'm having the same freezing issues, yet I'm NOT EVEN USING A MAC!

Yeah, my HACKINTOSH LAPTOP freezes up since the the 10.11.4 update, using Nvidia graphics and it's from 2008! ALBEIT I only had it happened maybe three times in total.
 

kjwamlex

macrumors 6502
May 13, 2016
254
275
Ugh. Experienced the issue again. But sometimes, MY MacBOok Pro 2015's trackpad respond sometimes, not always. This is quite odd. It used to not respond when it freezes.
[doublepost=1463374164][/doublepost]2016. 5. 15. 오후 9:32:46.415 hidd[93]: IOHIDEventQueue unable to get policy for event of type 11. (e00002e8)
I see bunch of those when it froze on my Macbook Pro, 2015 13" until I shut it down. very odd.
[doublepost=1463374781][/doublepost]I found these logs between bunch of IOHIDEventQueue unable to get policy for event of type 11. (e00002e8). Probably it's not just Graphic driver issue / Safari issue. Possibly OS X issue too?






2016. 5. 15. 오후 9:32:50.954 watchdogd[219]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
2016. 5. 15. 오후 9:32:57.189 Photos[2453]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 10 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?
2016. 5. 15. 오후 9:33:16.101 watchdogd[219]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
2016. 5. 15. 오후 9:33:17.103 watchdogd[219]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer)
2016. 5. 15. 오후 9:33:17.190 Photos[2453]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 20 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?
2016. 5. 15. 오후 9:33:41.248 watchdogd[219]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

2016. 5. 15. 오후 9:33:42.253 watchdogd[219]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer)
2016. 5. 15. 오후 9:34:06.338 watchdogd[219]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
2016. 5. 15. 오후 9:37:12.979 AirPlayUIAgent[305]: 2016-05-15 09:37:12.978815 PM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification
2016. 5. 15. 오후 9:37:12.984 sharingd[258]: 21:37:12.983 : BTLE scanner Powered Off
2016. 5. 15. 오후 9:37:13.000 kernel[0]: Setting BTCoex Config: enable_2G:1, profile_2g:0, enable_5G:1, profile_5G:0
2016. 5. 15. 오후 9:37:13.084 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: notification observer: com.apple.iChat notification: __CFNotification 0x7fb8114493f0 {name = _NSDoNotDisturbEnabledNotification}
2016. 5. 15. 오후 9:37:12.984 sharingd[258]: 21:37:12.983 : BTLE scanner Powered Off
2016. 5. 15. 오후 9:37:13.000 kernel[0]: Setting BTCoex Config: enable_2G:1, profile_2g:0, enable_5G:1, profile_5G:0
2016. 5. 15. 오후 9:37:13.084 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: notification observer: com.apple.iChat notification: __CFNotification 0x7fb8114493f0 {name = _NSDoNotDisturbEnabledNotification}
2016. 5. 15. 오후 9:37:13.085 imagent[306]: <IMMacNotificationCenterManager: 0x7fe283f2f680>: notification observer: com.apple.FaceTime notification: __CFNotification 0x7fe283e5d4b0 {name = _NSDoNotDisturbEnabledNotification}
2016. 5. 15. 오후 9:37:13.099 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: NC Disabled: NO
2016. 5. 15. 오후 9:37:13.099 sharingd[258]: 21:37:13.098 : Purged contact hashes
2016. 5. 15. 오후 9:37:13.099 sharingd[258]: 21:37:13.099 : Discoverable mode changed to Off
2016. 5. 15. 오후 9:37:13.099 sharingd[258]: 21:37:13.099 : BTLE scanning stopped
2016. 5. 15. 오후 9:37:13.106 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: DND Enabled: YES
2016. 5. 15. 오후 9:37:13.107 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: Updating enabled: NO (Topics: (
))
2016. 5. 15. 오후 9:37:13.107 imagent[306]: <IMMacNotificationCenterManager: 0x7fe283f2f680>: NC Disabled: NO
2016. 5. 15. 오후 9:37:13.107 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811721cc0>: notification observer: com.apple.iChat notification: __CFNotification 0x7fb811454000 {name = _NSDoNotDisturbEnabledNotification}
2016. 5. 15. 오후 9:37:13.114 imagent[306]: <IMMacNotificationCenterManager: 0x7fe283f2f680>: DND Enabled: YES
2016. 5. 15. 오후 9:37:13.114 imagent[306]: <IMMacNotificationCenterManager: 0x7fe283f2f680>: Updating enabled: NO (Topics: (
))
2016. 5. 15. 오후 9:37:13.114 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811721cc0>: NC Disabled: NO
2016. 5. 15. 오후 9:37:13.119 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811721cc0>: DND Enabled: YES
2016. 5. 15. 오후 9:37:13.119 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811721cc0>: Updating enabled: NO (Topics: (
))
2016. 5. 15. 오후 9:37:14.056 cloudfamilyrestrictionsd[325]: CFRPushManager : connection:didChangeConnectedStatus: : 0
2016. 5. 15. 오후 9:37:16.000 kernel[0]: IOPMrootDomain: idle revert, state 21
2016. 5. 15. 오후 9:37:16.111 sharingd[258]: 21:37:16.111 : Starting AirDrop server for user 501 on wake
2016. 5. 15. 오후 9:37:16.113 CommCenter[232]: Telling CSI to exit low power.
2016. 5. 15. 오후 9:37:16.000 kernel[0]: Setting BTCoex Config: enable_2G:1, profile_2g:0, enable_5G:1, profile_5G:0
2016. 5. 15. 오후 9:37:16.000 kernel[0]: en0: BSSID changed to 38:2c:4a:a1:51:3c
2016. 5. 15. 오후 9:37:16.000 kernel[0]: en0: channel changed to 153,80
2016. 5. 15. 오후 9:37:16.221 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811721cc0>: notification observer: com.apple.iChat notification: __CFNotification 0x7fb811770970 {name = _NSDoNotDisturbDisabledNotification}
2016. 5. 15. 오후 9:37:16.222 imagent[306]: <IMMacNotificationCenterManager: 0x7fe283f2f680>: notification observer: com.apple.FaceTime notification: __CFNotification 0x7fe283f4c7c0 {name = _NSDoNotDisturbDisabledNotification}
2016. 5. 15. 오후 9:37:16.238 imagent[306]: <IMMacNotificationCenterManager: 0x7fe283f2f680>: NC Disabled: NO
2016. 5. 15. 오후 9:37:16.238 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811721cc0>: NC Disabled: NO
2016. 5. 15. 오후 9:37:16.238 sharingd[258]: 21:37:16.237 : Discoverable mode changed to Everyone
2016. 5. 15. 오후 9:37:16.238 sharingd[258]: 21:37:16.237 : BTLE scanning started
2016. 5. 15. 오후 9:37:16.238 sharingd[258]: 21:37:16.238 : Scanning mode Everyone
2016. 5. 15. 오후 9:37:16.239 sharingd[258]: 21:37:16.238 : BTLE scanner Powered On
2016. 5. 15. 오후 9:37:16.247 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811721cc0>: DND Enabled: NO
2016. 5. 15. 오후 9:37:16.247 imagent[306]: <IMMacNotificationCenterManager: 0x7fe283f2f680>: DND Enabled: NO
2016. 5. 15. 오후 9:37:16.247 imagent[306]: <IMMacNotificationCenterManager: 0x7fe283f2f680>: Updating enabled: YES (Topics: (
"com.apple.ess",
"com.apple.private.ac"
))
2016. 5. 15. 오후 9:37:16.247 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811721cc0>: Updating enabled: YES (Topics: (
"com.apple.private.alloy.icloudpairing",
"com.apple.private.alloy.continuity.encryption",
"com.apple.private.alloy.continuity.activity",
"com.apple.ess",
"com.apple.private.ids",
"com.apple.private.alloy.phonecontinuity",
"com.apple.madrid",
"com.apple.private.ac",
"com.apple.private.alloy.phone.auth",
"com.apple.private.alloy.keychainsync",
"com.apple.private.alloy.fmf",
"com.apple.private.alloy.sms",
"com.apple.private.alloy.screensharing",
"com.apple.private.alloy.maps",
"com.apple.private.alloy.thumper.keys",
"com.apple.private.alloy.continuity.tethering"
))
2016. 5. 15. 오후 9:37:16.247 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: notification observer: com.apple.iChat notification: __CFNotification 0x7fb811665c90 {name = _NSDoNotDisturbDisabledNotification}
2016. 5. 15. 오후 9:37:16.252 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: NC Disabled: NO
2016. 5. 15. 오후 9:37:16.256 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: DND Enabled: NO
2016. 5. 15. 오후 9:37:16.257 identityservicesd[245]: <IMMacNotificationCenterManager: 0x7fb811453700>: Updating enabled: YES (Topics: (
"com.apple.madrid"
))
2016. 5. 15. 오후 9:37:16.673 hidd[93]: IOHIDEventQueue unable to get policy for event of type 12. (e00002e8)
2016. 5. 15. 오후 9:37:18.258 cloudfamilyrestrictionsd[325]: CFRPushManager : connection:didChangeConnectedStatus: : 1
 

Gunther04

macrumors newbie
Sep 18, 2014
7
0
Philippines
Just found out about this and voted. I have an Early 2015 13" MBP retina and also encounter OS lockups about 2x-3x a month since i updated to 10.11.4. Everything freezes.. cursor not moving, trackpad is stuck as well (cant click). Only solution was a force reboot.

Hope Apple can send an update asap!
 

seniorservice

macrumors newbie
May 16, 2016
3
0
Same problem, early 2015 13" mbp. A shame Apple didn't tell me of a known problem in an online chat support call. They recommended a visit to see a 'Genius'. Took an afternoon off work to do that, their best suggestion was to put my mbp in for a 7 day turn-around repair.

Now I've found this thread, hopefully it will be more helpful than Apple have been.
 

Osho

macrumors newbie
Apr 26, 2016
4
0
Sweden
I have this too, but not exactly the same problem.... My Mid 2014 Retina MacBook Pro hangs when I try to log back in after the screensaver locked the the screen.

Happening since at least 10.11.3 for me.

Black screen, If I swipe between desktops I can see them flicker. If I it Alt-Tab in the middle of a swipe I can see the screen. Other than that - beachball - nothing. I hear incoming mails and messages but thats all.

I took some videos of it happening today.

and
 

superuser1

macrumors newbie
May 16, 2016
2
0
I have been having two problems with my rMBP 13", one of which is identical to what many of you guys are experiencing.

Problem 1 (freezing):
(I misspoke and said August, but this happened last month, in April.)

This occurs mostly when I have a lot of cables and peripherals connected and am using external monitors, etc. (because I work at my desk and rarely use my laptop for long periods without an external monitor), although it also occurs without all of that. One quirk I noticed was that if I didn't unplug all of my peripherals when rebooting after a freeze, bluetooth would show in the menu bar as "Not available" and I wouldn't be able to enable it no matter what I did—I had to delete the com.apple.Bluetooth.plist file in /Library/Preferences and reboot with no peripherals attached to enable it again.

Apple replaced the logic board and a trackpad cable last month and this problem has only occurred once since then (within 15 minutes of restoring my Time Machine backup), and the strange bluetooth behavior did not occur at that time. Since that initial instance, the laptop hasn't frozen once. This could be pure coincidence (I've gone for long periods of time without issue before) or there could have been an underlying hardware issue in addition to whatever may possibly be wrong with OS X 10.11.4.

In any case, I'm glad they replaced the logic board, as that is at least one more potential problem fixed.

Problem 2 (probably unrelated to this thread):
Beach ball of death. A program would seem to stop responding, and shortly thereafter every program would stop responding, followed by the dock and menu bar failing to respond, and eventually I'd just have to power off the machine using the power button. Leaving the machine on in the hope that it would eventually recover somehow resulted in no change. Using force quit and attempting to kill each program one by one also did not work. Happened before and continued to happen after logic board replacement. Seems to have little or no relationship with system load.

I disabled Flash in Chrome and as far as I can recall this beachball of death thing has stopped, but since it's a relatively infrequent problem, it's difficult to be sure.

I've never had a computer without hardware problems crash this much, and that includes ancient Windows machines. It's tough to try to work around the constant possibility of a total system freeze. Let's hope they get this fixed soon—otherwise, this might be my first and last new Mac purchase.
 
Last edited:

oliversl

macrumors 65816
Jun 29, 2007
1,499
431
Holy cow I have been working with Apple Support for 2 months trying to solve this issue. I have driven 4 hours to the closest Apple Store which did nothing, I reinstalled the operating system which did nothing, I reformatted and reinstalled which did not help.

I am beyond disappointed. There is no way I will ever be buying one of these ever again. This has been the most frustrating experience I've ever had with a computer and a company.

I have the early 2015 Retina Macbook Pro.

My system freezes occur randomly, and not always in Safari.

Maybe a recall will be the solution. Did you tried installing Mountain Lion or Mavericks?
 

George TR

macrumors newbie
May 11, 2016
4
0
Russia, Saint-Petersburg
I updated to 10.11.5 and I have bad news for you.... Freezing in safari!!, even worse when they are forced to restart , even stuck on the login screen! 10.11.5 do not fix it!! (Macbook Pro 13 retina, mid 2014)
 

Vermifuge

macrumors 68020
Mar 7, 2009
2,067
1,589
Guys check for update now. 10.11.5 is out. Update and check for this issue again.

I highly doubt Apple incorporated a fix in this update. This update has been in testing log before this issue was brought to Apples attention.
 

Weaselboy

Moderator
Staff member
Jan 23, 2005
34,491
16,218
California
I updated to 10.11.5 and I have bad news for you.... Freezing in safari!!, even worse when they are forced to restart , even stuck on the login screen! 10.11.5 do not fix it!! (Macbook Pro 13 retina, mid 2014)
I have that exact model with none of those issues, so I suspect you have something else going on.
 
  • Like
Reactions: Antonnn
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.