Finally, a non-subjective question that you can answer & I can mark as legitimately "Answered" if you can assist me!
Two salient points, to start:
Issue: In the past week, my MacBook Pro has started shutting down without warning when running on battery power, despite the current battery charge remaining being reported as 53% to 65% at the time of the unannounced hard shutdown. It just completely shuts off, just as it would if you removed the battery entirely and, while using the computer with the MagSafe power plug, simply unplugged it. I should note it runs fine on AC power & charges the battery to a reported 100%.
I've followed the steps in Apple's recalibration bulletin at http://bit.ly/bMakgz) but there was no change/improvement. The problem simply recurred once the battery dipped at or below 65%. Using a free battery monitoring app called coconutBattery, I can confirm that both the OS X (10.6.3) built-in battery monitor and coconutBattery agree on the current charge state/percentage of power remaining and the current total number of battery charge cycles. I am not sure how many battery cycles is the norm for a 15-month-old MBP but mine's reporting in at 156 cycles. Both also report an abnormal battery condition: OS X reports "Service Battery" and coconutBattery reports "Check Battery."
I'm aware batteries can die/rapidly lose their peak efficiency, but this thread in the Apple support forums worries me that it could be a software issue -- http://discussions.apple.com/thread.jspa?threadID=2139186&start=1290&tstart=0
What do you think -- Is my battery already dead/dying and in need of replacement?
The question has been closed for the following reason "The question is answered, right answer was accepted" by ageekmom Jun 05 '10 at 03:05
Take out the battery and look at the connectors make sure they aren't bent or broken. Also make sure nothing is obstructing the batter from securing properly. Also take a look at the power settings and make sure everything is to your liking. If that still doesn't work I would reinstall the OS because it might be a kernel bug that just needs the OS to reinstall. Those are my solutions, if non of them work something is seriously wrong.
answered Jun 04 '10 at 02:58