avoidwork

Q: 5k iMac reboots on it's own after installing 10.11.4

Hi,

 

I installed 10.11.4 on March 24 (I believe), and since that day my iMac has been unstable. It reboots on it's own, like a kernel panic but never logging a kernel panic. This reboot doesn't seem to be triggered by software I run, as I've been removing things to try to isolate the problem.

 

Yesterday Apple Support had me reinstall the os via cmd-r boot option, and that did not solve the problem... it just ate up an hour of my time.

 

Any suggestions? My iMac went from super stable to super unstable; it's worse than my Windows gaming pc for stability now.

iMac (Retina 5K, 27-inch, Late 2015), OS X El Capitan (10.11.4), 32GB ram

Posted on Mar 29, 2016 4:57 AM

Close

Q: 5k iMac reboots on it's own after installing 10.11.4

  • All replies
  • Helpful answers

Page 1 of 7 last Next
  • by Linc Davis,

    Linc Davis Linc Davis Mar 29, 2016 5:37 AM in response to avoidwork
    Level 10 (207,915 points)
    Applications
    Mar 29, 2016 5:37 AM in response to avoidwork

    Does it completely shut down and restart with a chime, or does it just log you out?

  • by avoidwork,

    avoidwork avoidwork Mar 29, 2016 6:02 AM in response to Linc Davis
    Level 1 (11 points)
    Desktops
    Mar 29, 2016 6:02 AM in response to Linc Davis

    It's a complete shut down. Sometimes it happens while I'm sitting at the machine using it, sometimes when I'm sitting there not using it... sometimes when no apps are running. There's nothing obvious to me in the log files, via Console.app; there are now 4 powerstats files per day when the reboots happen. The logs do not contain a timestamp in the name, and I haven't bothered to read every file (20+ now), so there might be a rhythm/pattern to the reboots + logs, but it's not obvious to me as an end user.

     

    The software is inconsistent between reboots, sometimes I have chrome open... sometimes not. Only my drobo is consistent across all the reboots, and it's usually in low power mode because the machine is not doing it's intended job due to reboots.

  • by Linc Davis,

    Linc Davis Linc Davis Mar 29, 2016 7:24 AM in response to avoidwork
    Level 10 (207,915 points)
    Applications
    Mar 29, 2016 7:24 AM in response to avoidwork

    Please search the log for the text "Previous shutdown." What do you find?

  • by avoidwork,

    avoidwork avoidwork Mar 29, 2016 7:26 AM in response to Linc Davis
    Level 1 (11 points)
    Desktops
    Mar 29, 2016 7:26 AM in response to Linc Davis

    Hi,

     

    I'll have to pick this up in roughly 7hr, as I'm at work now and away from the machine. I lost most logs due to the reinstall unfortunately, but I'll do the search when I get back to it!

  • by avoidwork,

    avoidwork avoidwork Mar 29, 2016 2:11 PM in response to Linc Davis
    Level 1 (11 points)
    Desktops
    Mar 29, 2016 2:11 PM in response to Linc Davis

    Hi,

     

    `system.log` has a single entry:  "Mar 29 01:26:27 blacky kernel[0]: Previous shutdown cause: -128"

     

    ^ That looks about right time wise for the reboot/login screen I encountered this morning when I woke up.

     

    `system.log.0.gz` has a single entry: "Mar 28 18:46:01 blacky kernel[0]: Previous shutdown cause: 5"

     

    `install.log` has some entries related to the OS reinstall

  • by avoidwork,

    avoidwork avoidwork Mar 29, 2016 2:16 PM in response to avoidwork
    Level 1 (11 points)
    Desktops
    Mar 29, 2016 2:16 PM in response to avoidwork

    I looked up that error, and I am very confused... "-128 userCanceledErr User canceled an operation" ... what could I possibly cancel while I was afk & sleeping?

  • by Linc Davis,

    Linc Davis Linc Davis Mar 29, 2016 2:17 PM in response to avoidwork
    Level 10 (207,915 points)
    Applications
    Mar 29, 2016 2:17 PM in response to avoidwork

    A negative shutdown code may indicate a hardware problem. The precise meaning of the codes is not publicly documented. They are not the same as error codes.

    If you haven't already done so, you can try resetting the System Management Controller. Otherwise, or if the reset has no effect, see below.

    Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.

    Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.

    If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

    Keeping your confidential data secure during hardware repair

    Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.

    *An SSD doesn't need to be zeroed.

  • by avoidwork,

    avoidwork avoidwork Mar 29, 2016 2:18 PM in response to Linc Davis
    Level 1 (11 points)
    Desktops
    Mar 29, 2016 2:18 PM in response to Linc Davis

    Ok, thanks for the information! I have another support call scheduled in about 10minutes, I'll mention this error code in the log and your suggestion for an appointment.

  • by Fil-mac,

    Fil-mac Fil-mac Mar 29, 2016 2:58 PM in response to Linc Davis
    Level 1 (13 points)
    Desktops
    Mar 29, 2016 2:58 PM in response to Linc Davis

    hey there

    im experiencing random restarts with a chime and i have no clue what to do.

    Screen goes black for a second and then there's the chime and back to the login screen... the whole process may last around 2-3 seconds but i dont think its normal.

    I bought my imac 5k retina 2 months ago with the default hardware.

     

    Any idea what to do?

  • by avoidwork,

    avoidwork avoidwork Mar 30, 2016 5:02 AM in response to avoidwork
    Level 1 (11 points)
    Desktops
    Mar 30, 2016 5:02 AM in response to avoidwork

    I removed java from the iMac yesterday, hoping that it was the cause of the unstable behavior (upgraded around the same time), but unfortunately it is not. The rebooting has minimized to once in the morning since the OS reinstall, but the code remains -128 even though the message changed:

     

    2016-03-30 3:07:00.000 AM kernel[0]: Previous shutdown cause: -128

     

    Then there's this:

     

    2016-03-30 3:07:01.096 AM locationd[83]: locationd was started after an unclean shutdown

     

    'unclean shutdown' :/

  • by avoidwork,

    avoidwork avoidwork Mar 30, 2016 5:16 AM in response to avoidwork
    Level 1 (11 points)
    Desktops
    Mar 30, 2016 5:16 AM in response to avoidwork

    It appears to have a partition issue upon reboot.

     

    2016-03-30 3:07:00.000 AM kernel[0]: disk1s1: alignment error.

    2016-03-30 3:07:00.000 AM kernel[0]: disk1s1: alignment error.

    2016-03-30 3:07:00.000 AM kernel[0]: disk1s3: alignment error.

    2016-03-30 3:07:00.000 AM kernel[0]: disk1s3: alignment error.

    2016-03-30 3:07:01.000 AM kernel[0]: disk2: alignment error.

    2016-03-30 3:07:01.000 AM kernel[0]: disk2: alignment error.

  • by avoidwork,

    avoidwork avoidwork Mar 30, 2016 1:54 PM in response to avoidwork
    Level 1 (11 points)
    Desktops
    Mar 30, 2016 1:54 PM in response to avoidwork

    Had another reboot while at work:

     

    2016-03-30 10:51:12.000 AM kernel[0]: Previous shutdown cause: -128

     

    So, at least the code is consistent.

  • by po09,

    po09 po09 Mar 30, 2016 4:52 PM in response to avoidwork
    Level 1 (4 points)
    Desktops
    Mar 30, 2016 4:52 PM in response to avoidwork

    Apologies in advance if it's inappropriate to post log output.


    I will remove if it is a problem.


    I'm also having the same issue on my 5K iMac.  Random Reboots sometime multiple times a day. Occurring after updated to 10.11.4

     

    I've clear PRAM and SMC.

    I have also reinstalled OS X.  Complete reinstall erased drive.

     

    Issue still persists.

     

    -128 SHUTDOWN CODE

     

    Here is some output regarding how frequently the reboot occur:

     

    last reboot

    reboot    ~                        Wed Mar 30 18:24

    reboot    ~                        Tue Mar 29 22:45

    reboot    ~                        Tue Mar 29 20:06

    reboot    ~                        Tue Mar 29 09:30

    reboot    ~                        Mon Mar 28 23:00

    reboot    ~                        Mon Mar 28 12:11

    reboot    ~                        Sun Mar 27 19:10

    reboot    ~                        Sun Mar 27 09:20

    reboot    ~                        Sat Mar 26 19:39

    reboot    ~                        Sat Mar 26 10:13

    reboot    ~                        Sat Mar 26 09:44

     

    I've looked through console can't pinpoint an exact cause.

     

    At first this error was corresponding right before each reboot:

     

    CalendarAgent[413]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/plain; charset="utf-8"].]


    I removed all calendar accounts to see if that was the cause.


    It seemed to help the issue a bit because only 1 reboot so far today. But had another one while AFK at 6:24pm.


    Here is the console output from the 6:24pm reboot:


    Mar 30 18:18:28 Kurama identityservicesd[240]: <IMMacNotificationCenterManager: 0x7fdc43c569f0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fdc43d6bdf0 {name = _NSDoNotDisturbEnabledNotification}

    Mar 30 18:18:28 Kurama imagent[291]: <IMMacNotificationCenterManager: 0x7fc9b1e2d470>: notification observer: com.apple.FaceTime   notification: __CFNotification 0x7fc9b1e90a90 {name = _NSDoNotDisturbEnabledNotification}

    Mar 30 18:18:28 Kurama identityservicesd[240]: <IMMacNotificationCenterManager: 0x7fdc43c569f0>:    NC Disabled: NO

    Mar 30 18:18:28 Kurama imagent[291]: <IMMacNotificationCenterManager: 0x7fc9b1e2d470>:    NC Disabled: NO

    Mar 30 18:18:28 Kurama sharingd[268]: 18:18:28.130 : Purged contact hashes

    Mar 30 18:18:28 Kurama sharingd[268]: 18:18:28.130 : Discoverable mode changed to Off

    Mar 30 18:18:28 Kurama sharingd[268]: 18:18:28.130 : BTLE scanning stopped

    Mar 30 18:18:28 Kurama identityservicesd[240]: <IMMacNotificationCenterManager: 0x7fdc43c569f0>:   DND Enabled: YES

    Mar 30 18:18:28 Kurama imagent[291]: <IMMacNotificationCenterManager: 0x7fc9b1e2d470>:   DND Enabled: YES

    Mar 30 18:18:28 Kurama imagent[291]: <IMMacNotificationCenterManager: 0x7fc9b1e2d470>: Updating enabled: NO   (Topics: (

    Mar 30 18:18:28 Kurama identityservicesd[240]: <IMMacNotificationCenterManager: 0x7fdc43c569f0>: Updating enabled: NO   (Topics: (

    Mar 30 18:18:28 Kurama identityservicesd[240]: <IMMacNotificationCenterManager: 0x7fdc43e68240>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fdc43d66200 {name = _NSDoNotDisturbEnabledNotification}

    Mar 30 18:18:28 Kurama identityservicesd[240]: <IMMacNotificationCenterManager: 0x7fdc43e68240>:    NC Disabled: NO

    Mar 30 18:18:28 Kurama identityservicesd[240]: <IMMacNotificationCenterManager: 0x7fdc43e68240>:   DND Enabled: YES

    Mar 30 18:18:28 Kurama identityservicesd[240]: <IMMacNotificationCenterManager: 0x7fdc43e68240>: Updating enabled: NO   (Topics: (

    Mar 30 18:18:28 Kurama WindowServer[162]: device_generate_desktop_screenshot: authw 0x7fea14820400(2000), shield 0x7fea14853a00(2001)

    Mar 30 18:18:28 Kurama WindowServer[162]: device_generate_lock_screen_screenshot: authw 0x7fea14820400(2000)[0, 0, 0, 0] shield 0x7fea14853a00(2001), dev [2560,1440]

    Mar 30 18:18:28 Kurama WindowServer[162]: no sleep images for WillPowerOffWithImages

    Mar 30 18:22:07 Kurama syslogd[40]: ASL Sender Statistics

    Mar 30 18:24:52 localhost bootlog[0]: BOOT_TIME 1459376692 0

     

    I have not reached out to apple support as of yet.

     

    Thoughts?

  • by po09,

    po09 po09 Mar 30, 2016 6:10 PM in response to po09
    Level 1 (4 points)
    Desktops
    Mar 30, 2016 6:10 PM in response to po09

    Got done with Apple Support.

     

    Escalated my case, but didn't really get closure.

     

    They couldn't tell me what -128 code represented other than their resources led them down troubleshooting kernel panics.

     

    However, I had completed their troubleshooting steps prior to the call because I referenced this thread.

     

    So......

     

    They asked me to remove all 3rd party applications because of interoperability with new updates.

     

    I get it...but still a canned answer.  I also said the same 3rd party apps are installed on my Macbook Pro so not sure if directly relevant.

     

    Also performed Apple Diagnostic Hardware test.  No issues were found.

     

    Short answer...uninstall all the things and see if it happens again.  /sigh

     

    Anyways, lets entertain them and maybe it is a third party app.

     

    I have the following installed since my last reinstall.

     

    Chrome

    VLC

    Transmission

    TeamViewer

    DropBox

    Spotify

    Flash (dun dun dun)

     

    Anything match others who are having issues?

     

    This isn't my primary machine so to test I have uninstalled all things as asked.

     

    I'll let you know if the issue persists.

Page 1 of 7 last Next