Unexpected Reboots

I have a iMac Retina 5k, 27 inch, Late 2015 that has been working just great until I installed OS X 10.11.4.


Since then I get unexpected reboots; from the log the unexpected reboots are "Previous shutdown cause: -128"


This is a 3 day log.


Apr 1 20:23:20 iMac kernel[0]: Previous shutdown cause: 3

Apr 2 10:25:24 localhost kernel[0]: Previous shutdown cause: 5

Apr 2 11:37:13 wrf-iMac kernel[0]: Previous shutdown cause: 5

Apr 3 09:30:34 localhost kernel[0]: Previous shutdown cause: 5

Apr 3 13:08:27 wrf-iMac kernel[0]: Previous shutdown cause: -128

Apr 3 15:28:37 wrf-iMac kernel[0]: Previous shutdown cause: -128

Apr 3 17:27:23 wrf-iMac kernel[0]: Previous shutdown cause: -128

Apr 3 17:31:35 wrf-iMac kernel[0]: Previous shutdown cause: -128

Apr 3 20:55:33 wrf-iMac kernel[0]: Previous shutdown cause: 5

Apr 3 21:03:28 wrf-iMac kernel[0]: Previous shutdown cause: 5

Apr 3 21:34:24 localhost kernel[0]: Previous shutdown cause: 5


There are no externals plugged into the ports and I am using the Magic wireless Keyboard and Magic 2 wireless Mouse.


I have already taken it to local Apple Store and left it for 5 days for them to find the cause; they said they could find nothing wrong with it.


And yes I have reinstalled OS X 10.11.4, after wiping the drive, 4 times. I have also reset the PRAM and SMC.


Anyone have an ideas.

Posted on Apr 3, 2016 8:19 PM

Reply
22 replies

Apr 4, 2016 4:32 AM in response to wrfulton

I have exactly the same computer (mine is 1.2TB fusion drive) , exactly the same symptoms after the 10.11.4 update with no earlier problems, exactly the same experience at the local Apple Store.

Subsequent Apple telephone call yesterday with Apple Customer Service prompted the reply from the assistant, after consulting a senior advisor, that this is somehow "normal" i.e. the clean system restore carried out by the Apple Store over their network has somehow become corrupted and I should use Command R and do yet another system restore. She agreed to phone back today to see if I have had any further problems.

I did what they said, and then last night had the usual -128 'unclean shutdown' diagnostic. Now awaiting phone call.


Meanwhile I thought I would try the last option I have: i.e. restoring my last 10.11.3 Time Machine backup and going from there.

Previously, before contacting Apple I had tried to do this and an error came up telling me it could not erase the iMac hard disk, and I ended up in an endless restore circle unable to get back to a normal reboot and disk utility found no HD, so obviously the HD had been semi-deleted!!


This time that did not happen, the HD was deleted and I am currently in an 8 hour wait (3.1% so far) while the old system is restored.

I'll let you know later where I get to today. If 10.11.3 works fine for more than a day or so, then it is clearly a 10.11.4 problem.


PS: This iMac was new at beginning of December and had to have a new screen by middle of January. Hence my quality assurance doubts about these new iMacs, originally thinking my hard disk was failing. I'm more convinced now that this is a 10.11.4 issue and my 30 year loyalty to Apple is not too much in doubt.

Apr 4, 2016 6:04 AM in response to miguelh

Apple call-back: new assistant informed of the latest developments and concludes with me that it may be an issue with 10.11.4 after all and restoring 10.11.3 will be decisive.

IF I get problems with 10.11.3, then we both conclude it has to be hardware. Only then can I consider future options - if it is hardware, then QA is then definitely a serious consideration. At this price for an iMac, I couldn't afford to rely on them further for my crucial freelance medical work.


At my age plan B is always imperative, so if I had not still got my old iMac (5 years old, never a problem and still going strong) I would be in a financial/professional black hole!


Fingers crossed 10.11.3 works and the only question then will be waiting for a fully compatible OSX 10+ to arrive ...

Apr 4, 2016 8:03 AM in response to wrfulton

I have the same machine and same problem. There is another thread on this issue that I responded to here 5k iMac reboots on it's own after installing 10.11.4


Bottom line is that it seems to be affecting a number of different users with late 2015 Retina iMacs and the spontaneous rebooting problem began with the installation of 10.11.4 whereas no such problem occurred with 10.11.3 and earlier.

Apr 4, 2016 9:32 AM in response to miguelh

I have now taken a different track:


In System Pref -> Energy Saver I have changed the following settings:


I Never let the display turn off ( Screen Saver is set to 10 mins )


I Prevent computer from sleeping


I do not let the hard driver sleep when possible


I do not enable power nap.


I did this last night after posting my problem and have not had a restart since ( not a big window so I will post about this experiment again )


Good Luck to Us All.

Apr 4, 2016 12:43 PM in response to wrfulton

It happened again, another reboot so fiddling with sleep does not effect it.


Screen, keyboard, mouse all froze, about 10 secs later screen went black then the reboot chime and login screen.


No panic message, no Diagnostic Repot log created.


from System log, All Messages


4/4/16 2:23:09.582 PM com.apple.WebKit.WebContent[878]: <<<< MediaValidator >>>> mv_TestCodecSupportUsingDecoders: Unrecognized codec 1

4/4/16 2:23:15.098 PM Safari[712]: KeychainGetICDPStatus: keychain: -25300

4/4/16 2:23:15.098 PM Safari[712]: KeychainGetICDPStatus: status: off

4/4/16 2:23:15.000 PM kernel[0]: Limiting closed port RST response from 278 to 250 packets per second

4/4/16 2:23:38.000 PM kernel[0]: Limiting closed port RST response from 348 to 250 packets per second

4/4/16 2:23:54.000 PM kernel[0]: Limiting closed port RST response from 357 to 250 packets per second

4/4/16 2:24:13.000 PM kernel[0]: Limiting closed port RST response from 347 to 250 packets per second

4/4/16 2:24:15.000 PM kernel[0]: Limiting closed port RST response from 304 to 250 packets per second

4/4/16 2:24:26.000 PM kernel[0]: Limiting closed port RST response from 343 to 250 packets per second

4/4/16 2:24:42.000 PM kernel[0]: Limiting closed port RST response from 332 to 250 packets per second

4/4/16 2:24:57.000 PM kernel[0]: Limiting closed port RST response from 271 to 250 packets per second

4/4/16 2:25:03.346 PM Safari[712]: CoreAnimation: failed to receive fence reply: 10004003

4/4/16 2:25:03.346 PM WindowServer[171]: CoreAnimation: timed out fence b75b

4/4/16 2:25:03.346 PM WindowServer[171]: CoreAnimation: failed to send fence reply: 10000003

4/4/16 2:25:04.119 PM locationd[78]: NETWORK: requery, 0, 0, 0, 0, 28, items, fQueryRetries, 0, fLastRetryTimestamp, 481489483.5

4/4/16 2:25:10.614 PM Safari[712]: KeychainGetICDPStatus: keychain: -25300

4/4/16 2:25:10.614 PM Safari[712]: KeychainGetICDPStatus: status: off

4/4/16 2:25:30.000 PM kernel[0]: Limiting closed port RST response from 401 to 250 packets per second

4/4/16 2:25:33.293 PM Safari[712]: tcp_connection_destination_handle_tls_close_notify 87 closing socket due to TLS CLOSE_NOTIFY alert

4/4/16 2:25:33.293 PM Safari[712]: tcp_connection_tls_session_error_callback_imp 87 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32

4/4/16 2:25:33.295 PM Safari[712]: tcp_connection_destination_handle_tls_close_notify 89 closing socket due to TLS CLOSE_NOTIFY alert

4/4/16 2:25:33.295 PM Safari[712]: tcp_connection_tls_session_error_callback_imp 89 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32

4/4/16 2:25:33.296 PM Safari[712]: tcp_connection_destination_handle_tls_close_notify 88 closing socket due to TLS CLOSE_NOTIFY alert

4/4/16 2:25:33.296 PM Safari[712]: tcp_connection_tls_session_error_callback_imp 88 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32

4/4/16 2:25:38.000 PM kernel[0]: Limiting closed port RST response from 304 to 250 packets per second

4/4/16 2:26:03.000 PM kernel[0]: Limiting closed port RST response from 338 to 250 packets per second

4/4/16 2:27:32.814 PM WindowServer[171]: _CGXRemoveWindowFromWindowMovementGroup: window 0xcb is not attached to window 0xce

4/4/16 2:27:33.033 PM Safari[712]: tcp_connection_tls_session_error_callback_imp 93 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

4/4/16 2:27:41.751 PM Safari[712]: KeychainGetICDPStatus: keychain: -25300

4/4/16 2:27:41.751 PM Safari[712]: KeychainGetICDPStatus: status: off

4/4/16 2:28:04.781 PM Safari[712]: KeychainGetICDPStatus: keychain: -25300

4/4/16 2:28:04.781 PM Safari[712]: KeychainGetICDPStatus: status: off

4/4/16 2:28:37.063 PM WindowServer[171]: _CGXRemoveWindowFromWindowMovementGroup: window 0xcb is not attached to window 0xce

4/4/16 2:28:37.367 PM Safari[712]: tcp_connection_tls_session_error_callback_imp 100 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

4/4/16 2:28:38.257 PM com.apple.xpc.launchd[1]: (com.apple.WebKit.WebContent.29B5079A-3C34-4404-A067-BBE373108023[886]) Service exited with abnormal code: 1

4/4/16 2:28:45.339 PM Safari[712]: KeychainGetICDPStatus: keychain: -25300

4/4/16 2:28:45.339 PM Safari[712]: KeychainGetICDPStatus: status: off

4/4/16 2:30:34.000 PM bootlog[0]: BOOT_TIME 1459798234 0


anything there I am not sure.

Apr 5, 2016 5:09 AM in response to Terry Murphy

Restoring 10.11.3 yesterday from Time Machine backup after 8 hours went OK and I was hopeful of a cure.

Unfortunately, at 23:20 I got the usual black screen of death and reboot, this time without needing to log in again.

Then today at 12:46 the screen went dead again but this time rebooted into Log-in mode.


Conclusion: the 10.11.4 update has nothing to do with things, even if it might have triggered the fault in some people's cases.

Comparing responses here with the stories on the other 5k iMac reboots on it's own after installing 10.11.4 thread, there are several slightly differing scenarios, but the root problem is the same: a limited edition expensive iMac with serious QA problems, whether in hardware or software. In my case, I already had a hardware problem with a new screen required after only 45 days from new. Now this!


Where we go from here, I don't know, but I shall be back to a long conversation with Apple right now to push things on - using up time I really don't have to spare.

Anybody know if there is any chance of a decent refund?

I could get 6 reliable Lenovo PCs for this money and continue earning my income in peace with 5 backup machines ...

Apr 5, 2016 12:05 PM in response to wrfulton

It just occurred to me that when I took the iMac into the apple store for a fix they used a wired keyboard and wired mouse ( not my wireless keyboard and mouse ).


On the off-chance it make a difference I dug out an old wired keyboard and wired mouse and have restarted the iMac; I also turned off Bluetooth.


Hopefully this make a difference; will post tomorrow on how many unexpected reboots I get.

Apr 5, 2016 1:24 PM in response to wrfulton

I had a long conversation with a Senior Support Advisor and can call him back directly from now on.

They agreed to collect my computer and use an Approved Repair Service provider.


I discussed a lot of the issues others like yourselves have brought to light, and the opinion seems to be that it is hardware more than software, especially when I said I had restored 10.11.3 and still have the same problem - in fact 10.11.3 has just crashed out back to log-in THREE times in the last half hour.


Further to your comment above, I have a wireless magic trackpad 2 but a wired keyboard on my machine - the very odd thing is that not only does the keyboard freeze with the screen before the black reboot screen appears, but also the bluetooth connected trackpad - normally this has a physical movement and audible click, and only by moving the lock switch is this turned off. So the freeze must also turn off the physical mechanism via the bluetooth connection.

Certainly the Senior advisor and the service provider both asked me today about any connected peripherals. You may have a point, but I still think it is a more complex hardware issue and we are clutching at straws. See the other thread for the range of self-fixes already tried without success.


One commentator raised the idea of an AMD graphics fault which showed similar symptoms in a games machine he previously had with an AMD inside. Since I had a screen fault that was cured by fitting a new screen one month after buying this iMac, I have to wonder if the graphics connection might be an underlying cause, hence the odd times when the computer crashes but comes straight back to life from the black screen without requiring a log in - it is as if the screen had just given up with an overload of some kind and rebooted itself without affecting the main OS itself. Anybody any ideas??


Best of luck.

Apr 6, 2016 1:08 PM in response to wrfulton

With a wired keyboard and wired mouse (bluetooth disabled) I have had 2 unexpected reboots in 24 hours.


I have now taken screen shots in Console that show the reboots and the lack of kernel panics and have made an appt. at the local Apple Store. So another day of lugging this machine around.


Will post the outcome of the Apple Store visit next week when they are done.

May 7, 2016 1:36 PM in response to wrfulton

Ive got the same problem, bought iMac in Feb, ever since update it started the random rebooting and developed a problem with the bluetooth. When it is first switched on the bluetooth is disabled, the only way to solve it is to restart the iMac via keyboard shortcut. (i use a wired keyboard).

Trouble is I'm over the 14day return period so could you please advise me on who to contact in regards to getting this solved , its draining me.


Thanks in advance.


Kind Regards

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Unexpected Reboots

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