Currently Being ModeratedMar 12, 2013 12:07 PM (in response to Aroara)
Currently Being ModeratedMar 13, 2013 8:47 AM (in response to Linc Davis)
/var/log/system.log:Feb 17 15:29:22<owners>-MacBook-Air kernel: Previous Shutdown Cause: 5
/var/log/system.log:Feb 18 18:25:05 localhost kernel: Previous Shutdown Cause: 5
/var/log/system.log:Mar 2 07:46:43 <owners>-MacBook-Air kernel: Previous Shutdown Cause: -60
/var/log/system.log:Mar 6 05:39:54 localhost kernel: Previous Shutdown Cause: 0
/var/log/system.log:Mar 6 07:12:11 <owners>-MacBook-Air kernel: Previous Shutdown Cause: 0
/var/log/system.log:Mar 11 13:36:25 <owners>-MacBook-Air kernel: Previous Shutdown Cause: -2
/var/log/system.log:Mar 11 16:52:22 localhost kernel: Previous Shutdown Cause: -2
/var/log/system.log:Mar 12 11:25:16 localhost kernel: Previous Shutdown Cause: -128
/var/log/system.log:Mar 12 12:18:17 <owners>-MacBook-Air kernel: Previous Shutdown Cause: -128
I put one of each line that was different, and deleted the duplicates (because the log was pretty long and the only difference between them were the date).
Currently Being ModeratedMar 13, 2013 10:11 AM (in response to Linc Davis)
I don't mean to offend or question you, but I just got my computer back Apple after replacing the battery and the logicboard, they tested it in front of me, it was fine.
I need my laptop on a day-to-day basis. I can't afford to go without for another 5 days, so this solution is not particularly helpful, considering it's just a matter of shutting down when I close it.
I would much rather wait for the next OS X update, because this did start happening the day I installed the latest one... Coincidentally, the same day I got my computer back. There have been "rumours" on similar threads that the latest update is the problem.
It's not the end of the world -- it's just incredibly frustrating. Thanks for trying giving your time to this, though.
Currently Being ModeratedMar 13, 2013 11:08 AM (in response to Aroara)
Since then you've logged four abnormal shutdowns with unknown causes, and no normal ones. Before the repairs, you had logged one abnormal shutdown with an unknown cause and two apparently due to low power.
The reason codes are not publicly documented, but a zero or negative number means that the shutdown wasn't initiated by user action. From what I've been able to gather, these events are rarely, if ever, caused by software errors. They may be caused by corrupt SMC data, but you've ruled that out. If you wish, you can reinstall OS X, but I wouldn't expect any change from doing that. You can also reset the NVRAM, but again, I wouldn't expect any change.
That leaves hardware. The possibilites are that one of the parts that wasn't replaced is causing the problem, or that one of the replacement parts is faulty (which is not unheard of), or that the installation wasn't done right. I guess it's remotely possible that transients in your electricity supply could be responsible, but that would make sense only if the shutdowns happen exclusively when the AC adapter is connected.
That's about all I can tell you.
Currently Being ModeratedMar 13, 2013 11:36 AM (in response to Linc Davis)
(You're right, PRAM didn't work.)
Either way, i would need to wait until April to bring it in, since the end (and most stressful point) of the semester is coming up. I guess I'll just have to live with it for now and have it fixed when I can.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points