Powerbook crashing on battery power after repair

I just performed a repair of my PB (replacing a screen hinge). It's okay, except that now it freezes on battery power.
The pattern is very strange: if I reboot with the battery, it makes it all the way to the login screen and freezes when I try to type.
If I unplug it while it is already booted then the screen dims (I have it set to do that on battery power) and then freezes a second or so later.
All activity ceases, the cursor becomes unresposive. It's not that the computer is not getting power: the screen stays lit, for example (and of course, it can boot all the way to login screen on battery power; it also can operate for quite a while in single user mode on battery power; I tried it long enough to fsck the disk).
The specific symptoms of the the problem are just so bizarre that I'd suspect a software problem if I hadn't just done this big repair. (By the way, I've repaired the disk (no problems) and, even though I think it's useless, I repaired permissions too, just for good measure; neither had any effect.)
Does anyone have any clue what I could have done to precipitate such a weird problem? Could there be some screw that is over- or under-tightened? A connector that is loose? Should I just take the thing apart again and put it back together again?

Well, the problem is solved, though the mystery remains. I carefully took the computer apart again and tested it after every piece was removed. It failed every time. Finally there was not enough left to actually boot. Then I reassembled it and, behold, it works!
I removed the keyboard, modem, airport card, fan connector, and PCMCIA cage and still had a crashing system. (I'd also removed and reconnected the battery cable, and moved the DIMMs around.)
So then I just finished the job. I disconnected the following from the logic board: hard drive, DVD drive, display, speakers/mic, power button (yeah, yeah, there's a few more I could have removed and kept a bootable system, but I was starting to get bored). Then I removed the logic board, looked at it stupidly, put it back, and reconnected all those connectors.
Then it worked. (So I put back all the other stuff, and it still works.)
So presumably one of those connectors was lose, or else the logic board was somehow incorrectly mounted.
I still don't really understand how a loose connector or incorrectly mounted logic board would lead to the symptoms I was seeing, so if anyone has a hypothesis, I'd love to hear about it.

Similar Messages

Is there a fix yet for the loss of battery power after updating to Lion?

Is there a fix yet for the loss of battery power after updating to Lion? I've done the cmd-opt-shift restart and it didn't help. This problem has gone beyond annoying now - it is absolutely maddening! What is Apple's official response????

Chris: your friends are woefully uninformed, and no one should pay any attention to their bad advice.
http://www.apple.com/batteries/notebooks.html
http://support.apple.com/kb/HT1446?viewlocale=en_US
http://batteryuniversity.com/

Loses battery power after 1 hour of play

My iPod mini (first generation) loses battery power after about an hour of play.
I sent the iPod mini into Apple to replace the battery. But they said nothing was wrong with it.
That can't be true, because I remember playing my iPod for longer stretches of time than just an hour.
Thanks for any help!

The iPod battery indicator is only a very loose approximation of how much charge there actually is left.
See these.
Beef up my iPod battery.
How to accurately determine your iPod battery life.
Can I make the meter more accurate?
However, you also need to consider that the battery may need replacing.
If so, Google 'iPod batteries' for cheaper options than Apple.

X220 won't start up on battery power after BIOS update 1.24/1.25

This is a really strange issue.
I had been using my laptop with the oriiginal 1.10 (or whatever the very first one was) BIOS until yesterday with no problems. I head that there were some important fixes in the newer BIOS versions so I updated to 1.25. Everything seemed to be working fine until I went to work and turned on my laptop. It kept crashing before Windows would load (after the post screen but before any of the windows screens. It just stays black for a long time and then flashes a BSOD and restarts). I tried downgrading to BIOS 1.24 but the problem persisted.
It turns out that it does this whenever I try to start the computer without it plugged into the ac adaptor. When it is plugged in it starts up as normal but when unplugged it won't boot into windows. Once Windows is loaded I can unplug it and nothing happens but I still can't restart it without plugging it back in
Has anyone else encountered this problem? Is this a known issue? Any suggestions for what could be causing this strange behaviour?
If I can't get it figured out right away I will have to try to downgrade to the original BIOS version.

LOL! I just tried updating to 1.28 BIOS and had forgotten about the problem I had last time (when I tried updating to 1.24/1.25). I was just looking up what to do and came across this thread. I took me way too long to realize I was reading my own post from months ago! Boy am I slow.
I don't know if you are still subscribed to this thread Aamir but a hard reset is when you turn off the computer by holding down the power button until it turns off. Are you (were you) having the same issue with the newer BIOS versions as I am?
I think that the x220 is an amazing laptop spec-wise but are there ever a lot of driver/software problems! I keep trying to use the newer BIOS versions but I always have to revert to the original because Windows 7 won't start if I am on battery power (so basically anytime that I am not at home). I just bought a mSATA SSD (which is why I tried to use the newest firmware, I heard that older ones don't support them) and though the BIOS recongizes it, now Windows won't start if the SSD is installed! There is not much use in having a laptop with lots of ports and expansion options if it doesn't work when you use them!

Crashes on battery power

Totally weird. After upgrading to Yosemite a couple of months ago I get sporadic system crashes on my MacBook Pro. They occur periodically, usually once or twice a day; often when there was no apparent activity or app work being done. After several weeks of living with this, I detected the following common factors:
1 - the system does not crash if it is on mains power
2 - remaining power in the battery is usually around 30%
3 - it is not possible to generate a crash, even with these conditions in place - the crash just happens without warning.
It is not a kernel crash in the sense that the system does not goes into auto reboot. All power is lost and the power button has to be activated to bring the system back up.
For a while, I thought it might have something to do with the Parallels/Win7 VM, but the crash also recently happened again when neither of these are open.
When reviewing the Mac system logs, there was no indication of any activity or abnormal condition immediately before the crash. In fact, in most instances there were no console log entries for several minutes before the crash. I have not yet contacted Apple support, but wanted to know if any other users have experienced anything similar before I do that? Incidentally, the same MacBook Pro never crashed like this with Mavericks.

I now suspect the problem to be a faulty battery. Inspection of the battery health shows 825 cycles and only a 68% 'health'. However, the fact that the system does a sudden shutdown when 30% of battery charge is shown as remaining is troubling. I think a visit to the Genius Bar is on my calendar. The battery is only just over 2 years old.

Iphoto 9.4.2 constantly crashing on opening and after repair

I am using a MacBook Pro 15" retina. OSX 10.8.2 iphoto 11 version 9.4.2
After uploading a batch of new photos, I pressed the info button for one of the photos and iphoto quit unexpectedly.
I have tried the following:
- repairing permission
- repairing database
Immediately after however, iphoto is still crashing - and now won't open for more than a second or two.
I have also created a second iphoto library and that is working fine using iphoto.
I can also view/edit etc my iphoto library in Aperture..
Ideally I would like to merge my iphoto library with my Aperture library - but don't want to make matters worse by merging a dodgy library with a good one. I would rather repair the iphoto library first if possible.
I have backed up both onto an external drive.
Any suggestions for next steps would be appreciated.
Thanks

Forgot to add the crash report:
Process:         iPhoto [532]
Path:            /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier:      com.apple.iPhoto
Version:         9.4.2 (9.4.2)
Build Info:      iPhotoProject-710042000000000~2
App Item ID:     408981381
App External ID: 11723545
Code Type:       X86 (Native)
Parent Process: launchd [122]
User ID:         501
Date/Time:       2013-02-16 23:10:58.178 +0800
OS Version:      Mac OS X 10.8.2 (12C3006)
Report Version: 10
Interval Since Last Report:          758888 sec
Crashes Since Last Report:           35
Per-App Interval Since Last Report: 108069 sec
Per-App Crashes Since Last Report:   27
Anonymous UUID:                      174CF209-7E1D-3BC8-85E2-03AF783EFB2D
Crashed Thread: 23 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSMutableIndexSet addIndexesInRange:]: Range {2147484310, 1} exceeds maximum index value of NSNotFound - 1'
Application Specific Backtrace 1:
0   CoreFoundation                      0x9463712b __raiseError + 219
1   libobjc.A.dylib                     0x98c4b52e objc_exception_throw + 230
2   CoreFoundation                      0x94596bbb +[NSException raise:format:] + 139
3   Foundation                          0x96247c55 -[NSMutableIndexSet addIndexesInRange:] + 124
4   Foundation                          0x96273fdf -[NSMutableIndexSet addIndex:] + 48
5   iPhoto                              0x00a5b252 iPhoto + 9933394
6   iPhoto                              0x00a5a924 iPhoto + 9931044
7   Foundation                          0x9629bcc1 -[NSBlockOperation main] + 188
8   Foundation                          0x9626efb9 -[__NSOperationInternal start] + 740
9   Foundation                          0x9626ecce -[NSOperation start] + 67
10 Foundation                          0x96276dc9 __block_global_6 + 135
11 libdispatch.dylib                   0x95472f8f _dispatch_call_block_and_release + 15
12 libdispatch.dylib                   0x9546ec82 _dispatch_client_callout + 46
13 libdispatch.dylib                   0x9546ff02 _dispatch_worker_thread2 + 285
14 libsystem_c.dylib                   0x98436e12 _pthread_wqthread + 441
15 libsystem_c.dylib                   0x9841ecca start_wqthread + 30
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x954967d2 mach_msg_trap + 10
1   libsystem_kernel.dylib                  0x95495cb0 mach_msg + 68
2   com.apple.CoreGraphics                  0x98f34304 _CGSDisplayModeDescription + 155
3   com.apple.CoreGraphics                  0x98f34078 CGSGetDisplayModeDescriptionOfLength + 369
4   com.apple.AppKit                        0x915a5ea5 -[NSScreen deviceDescription] + 159
5   com.apple.AppKit                        0x915b3218 screenNumberForScreen + 35
6   com.apple.AppKit                        0x915b30a0 -[NSSurface _updateLastScreenNumber] + 41
7   com.apple.AppKit                        0x915b2321 -[NSSurface setFrame:] + 1377
8   com.apple.AppKit                        0x915b1d41 -[NSSurface syncToViewUnconditionally] + 304
9   com.apple.AppKit                        0x914c4731 -[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:] + 111
10 com.apple.AppKit                        0x91a8196c __62-[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:]_block_invoke_01982 + 43
11 com.apple.CoreFoundation                0x9458e962 __NSArrayEnumerate + 594
12 com.apple.CoreFoundation                0x9458e4e6 -[NSArray enumerateObjectsWithOptions:usingBlock:] + 102
13 com.apple.CoreFoundation                0x9458e3f5 -[NSArray enumerateObjectsUsingBlock:] + 53
14 com.apple.AppKit                        0x914c4845 -[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:] + 387
15 com.apple.AppKit                        0x91a8196c __62-[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:]_block_invoke_01982 + 43
16 com.apple.CoreFoundation                0x9458e962 __NSArrayEnumerate + 594
17 com.apple.CoreFoundation                0x9458e4e6 -[NSArray enumerateObjectsWithOptions:usingBlock:] + 102
18 com.apple.CoreFoundation                0x9458e3f5 -[NSArray enumerateObjectsUsingBlock:] + 53
19 com.apple.AppKit                        0x914c4845 -[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:] + 387
20 com.apple.AppKit                        0x91a8196c __62-[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:]_block_invoke_01982 + 43
21 com.apple.CoreFoundation                0x9458e962 __NSArrayEnumerate + 594
22 com.apple.CoreFoundation                0x9458e4e6 -[NSArray enumerateObjectsWithOptions:usingBlock:] + 102
23 com.apple.CoreFoundation                0x9458e3f5 -[NSArray enumerateObjectsUsingBlock:] + 53
24 com.apple.AppKit                        0x914c4845 -[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:] + 387
25 com.apple.AppKit                        0x91a8196c __62-[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:]_block_invoke_01982 + 43
26 com.apple.CoreFoundation                0x9458e962 __NSArrayEnumerate + 594
27 com.apple.CoreFoundation                0x9458e4e6 -[NSArray enumerateObjectsWithOptions:usingBlock:] + 102
28 com.apple.CoreFoundation                0x9458e3f5 -[NSArray enumerateObjectsUsingBlock:] + 53
29 com.apple.AppKit                        0x914c4845 -[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:] + 387
30 com.apple.AppKit                        0x91a8196c __62-[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:]_block_invoke_01982 + 43
31 com.apple.CoreFoundation                0x9458e962 __NSArrayEnumerate + 594
32 com.apple.CoreFoundation                0x9458e4e6 -[NSArray enumerateObjectsWithOptions:usingBlock:] + 102
33 com.apple.CoreFoundation                0x9458e3f5 -[NSArray enumerateObjectsUsingBlock:] + 53
34 com.apple.AppKit                        0x914c4845 -[NSView _recursiveSyncAndDisplayViewBackingSurfacesIfNeeded:] + 387
35 com.apple.AppKit                        0x9148e235 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 5883
36 com.apple.AppKit                        0x91456481 -[NSView displayIfNeeded] + 1468
37 com.apple.AppKit                        0x91455e3d -[NSWindow displayIfNeeded] + 306
38 com.apple.AppKit                        0x91455ad4 _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 994
39 com.apple.AppKit                        0x91a93b3b __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_ invoke_01253 + 58
40 com.apple.CoreFoundation                0x9458828d _runLoopObserverWithBlockContext + 29
41 com.apple.CoreFoundation                0x94558dfe __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 30
42 com.apple.CoreFoundation                0x94558d3d __CFRunLoopDoObservers + 381
43 com.apple.CoreFoundation                0x94532e16 __CFRunLoopRun + 886
44 com.apple.CoreFoundation                0x9453263a CFRunLoopRunSpecific + 378
45 com.apple.CoreFoundation                0x945324ab CFRunLoopRunInMode + 123
46 com.apple.HIToolbox                     0x9005f15a RunCurrentEventLoopInMode + 242
47 com.apple.HIToolbox                     0x9005edf5 ReceiveNextEventCommon + 162
48 com.apple.HIToolbox                     0x9005ed44 BlockUntilNextEventMatchingListInMode + 88
49 com.apple.AppKit                        0x91452a3a _DPSNextEvent + 724
50 com.apple.AppKit                        0x9145226c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
51 com.apple.AppKit                        0x914486cc -[NSApplication run] + 855
52 com.apple.AppKit                        0x913eb6f6 NSApplicationMain + 1053
53 com.apple.iPhoto                        0x000f1c99 0xe2000 + 64665
54 com.apple.iPhoto                        0x000f12e5 0xe2000 + 62181

MacBook Dies on Battery Power after 10 minutes

My wifes 13" MacBook dies after the power is unplugged after about 10 minutes. No warnings about reserve power or anything. After it dies I look at the battery indicator thats on the battery and it still shows full. When I turn the computer back on the battery reads fully charged. I'm thinking that this may not be a battery issue but something else.
Any help would be appreciated.
Paul

This is a recently common issue with Macbook Lith-ion batteries.
You have a defective battery, although AppleTech defines defective as a battery below 350 cycle counts. That's the lifetime of your $130 battery, which may average between 6-13 months depending on how you use it.
Some customers have had to buy 3 batteries in the past 2 years because AppleCare doesn't cover consumable items, eg. batteries.
check consumer comments at http://store.apple.com/1-800-MY-APPLE/WebObjects/AppleStore.woa/wa/RSLID?fnode=h ome/shopmac/macaccessories/power&revw=MA561LL/A
I'm hoping Apple will realize that a $130 macbook battery with a 350 cycle count lifetime, doesn't live up to "Apple" standards. Lith-ion batteries are known to have a 2-3 year lifetime not 6-13 months.
Customers shouldn't have to purchase AppleCare only to realize they have to continuously purchase new batteries every 6-13 months.
This is truly a manufacturer defect in my personal opinion.

Pavillion dv5 shuts down after ~5-10min on battery power?

11mo old laptop simply shuts down when running on battery power after only 5-10min after unplugging.
- Battery gauge shows fully-chaged when I unplug it
- No "low battery" warning or advice to plug in is given; it simply shuts off
If I try to turn it back on after it shuts down it will not power back on unless I plug the laptop back into the charger.
This never happens when plugged in to charger.
I know battery life can diminsh over time, but this came on all of a sudden; battery life was good (several hours) up until very recently. Now it just shuts down after a few minutes.
Appreciate any thoughts or advice - Thanks!

Laptop batteries can and do suddenly go bad. If one or two cells die, they can actually leach power from the other cells. The Smart chip inside the battery can actually go bad and shut the battery down even if the cells have power. The warranty on the battery is (usually) one year and if yours is 11 months old you can likely get HP to ship a new battery to you without returning the whole machine to them.

Powerbook G4 randomly shuts down even with full battery power

I have a three and a bit year old powerbook g4 (my apple care ran out in November) that has recently - as in the last two days - started randomly powering down without warning or error messages, regardless of how much battery power I may or may not have.
A bit of history - not sure what is and isn't pertinent.
I only recently - about six months to a year ago - switched out my recalled battery for a replacement one.
I also received a new power cord under warranty within the last year - but have had no problems before.
Before my powerbook came out of warranty, I took it into my local genius bar to have tests run to see if anything was wrong that I was not aware of, hoping to be able to get it fixed while still in warranty - it came back to me with no repairs and a clean bill of health.
I was on vacation for two weeks, and while on vacation my powerbook sat - powered down - in it's bag untouched the whole time. The problems started (or at least I first noticed them) within a few days after returning.
The other day, before any of this started, I noticed that even though the power adapter was in and glowing, the battery charging icon said "not charging".
The second time the random power-off happened, I did notice that the battery icon had an "x" in it, before it shut down.
The shutdowns are not like proper shutdown processes... one minute the computer is on, the next it's not. It's like the computer thinks there's no power, regardless of the actual charge of the battery.
I use my laptop on a laptop tray to maintain airflow underneath it and reduce overheating, but even so, the laptop seems to get very hot (although this is one of the issues I was worried about when I took it in to the genius bar before the warranty ran out, and they said it didn't get any more hot than they were supposed to), and also the power connector gets very hot. I don't know if overheating might have something to do with it?
So far I haven't noticed if it has happened while I've had the AC adapter plugged in... I think it only happens if it's running on battery, but not completely sure of this.
After the computer shuts down, I can restart it immediately (though these days it is taking longer) and I do not receive any error messages.
I usually turn off my computer when I won't be using it for a while - like before I go to bed or to work.
I recently upgraded my OS from panther to leopard, but was assured that it was compatible. I've had Leopard installed for at least three months, and the problems have only just started, so it probably doesn't have anything to do with that.
Well, that's about every possible piece of information I can think of that might be at all relevant to the situation. Does anyone have any ideas about what's happening? I have a feeling the news is going to be bad and I'll probably have to get a new computer...
Message was edited by: rraaarr

Here's the Apple article on how to reset the PMU:
http://docs.info.apple.com/article.html?artnum=14449
Possibly this might fix the problem. If not, here's a link to the MBP battery program:
http://www.apple.com/support/macbook_macbookpro/batteryupdate/
This program does NOT apply to your battery, but I think you may recognize some of the symptoms that yours is exhibiting. It also sounds like your power adapter may be getting warmer than it should, but that could have to do with the battery being defective. But if less than a year old, the power adapter should also be under its own warranty period.
If you have access to an Apple Store, you could make an appointment with the genius bar. They should be able to evaluate both the battery and the power adaptor by swapping yours out with ones that are known to be good. If not, call Apple.
Good luck!

PowerBook battery calibration - reserve battery power - Dr. Battery

Hello,
I have a new replacement battery from Dr. Battery for my 12" PowerBook G4.
I decided to calibrate the battery as described by Apple. That is, from a full charge, keep working on battery power and keep doing so when it gets to near zero when you see the 'plug in to power or computer will go to sleep' message. The reserve battery power will kick in and the computer will sleep after a few minutes; you'll see the twinkling light on the latch come on. Shortly after that, charge the battery to full.
This is how my original Apple batteries used to work, always. But the Dr. Battery battery simply crashed or shut down my PowerBook soon after the 'plug in to power or computer will go to sleep' -- the laptop couldn't/didn't go to sleep. What's more, when I restarted it, the date had reset to 1-1-1971. Does this mean that a Dr. Battery battery cannot store reserve battery power? Is there some way to fix it?
The strange thing is that the first time I calibrated in this way with this new battery in the first week of January, it *did* work like it should.
Thanks for any info.

The reason the time and other Prameter RAM settings were altered is because the G4 "12" Powerbook does not have a separate PRAM battery to maintain these values. Instead it uses a small capacitor which will maintain the PRAM settings only for a short time such as when changing a battery. The battery evidently spent it's charge when your PowerBook shut down.
I use a neat utility named coconutBattery to monitor battery status.
http://www.coconut-flavour.com/

10.4.7: powerbook battery dead after update

Just updated from 10.4.6 to 10.4.7 on my 12.1" PB G4 using the automatic Software Update application and my battery is dead. I tried resetting the PMU but no luck. The battery worked fine yesterday but I can't power-up today. The charging light integrated in the plug remains green but the battery strength only shows 1 rapidly blinking green led.
Coincidence? Anyone else have power/battery problems after this update?
1 GhZ powerbook G4 Mac OS X (10.4.6)

No problem with my 12" G4 or 17" G4 updating to 10.4.7.
Battery life remains the same as before, machines work on mains power and on battery power.
Note that before updating I logged out, to ensure that no applications were running and all other discs and devices were 'unmounted'; then I logged in again and "Repaired Permisions", using Applications>Utilities>Disk Utility; then did a Restart, and held down Apple+S to start in "Single User" mode, and ran "fsck" to check that all was OK with the hard disc; then rebooted and ran "Permissions Repair" again ..just to be prudent and to be satisfied that the machine was all in good order before applying the system software update.
I'll report back later and tell you if all went well with my Mac mini and G5 quad, but I've never had any problems with any OS update yet - all the way from 10.1 (..and System 8 and System 9 before that..)
Maybe I'm just extra careful.
P.S: Maybe you could try resetting your Power Management Unit ..but note that you'll need to reset your time and date afterwards, otherwise any files you create after that reset will have the wrong time and date, and may not appear correctly in Spotlight searches, amongst other things.

T400 doesn't hibernate after sleep (battery power)

t400 2765-A49 doesn't go to hibernation from sleep during battery power. When it's time to go to hibernation a click is heard and notebook stays in sleep mode. There's no problem during AC power. It goes to hibernation from sleep mode successfully.
I tried with Vista 32-bit and 7 64-bit. BIOS updated to the lastest one. Power Manager 2.42 and the latest 3.30. Please, tell me what other settings can I check/adjust to solve this problem?

> Where do you see the bug code when it happen?
in BlueScreenView
10 days ago, tried the first solution from here http://www.windowsxpregistrycleaner.com/windows-7-error-code-0x0000009F.html
after that no one crash
but my problem with the hibernation after sleeping on battery power still remained

Firefox crashes 2 seconds after startup. This happened after repair upgrade to Windows 7

After repair upgrade Firefox (9.0) would not work. I finally un-installed and re-installed it without success. Following your support guidelines I tried deleting my profile with partial success in that with a new profile Firefox would run once then revert back to an apparent crash after 2 seconds (as seen from task manager). After every new profile created it followed this same routine of working just the once. Any help would be appreciated.

Try a "clean reinstall" of Firefox by removing the Mozilla Firefox installation directory before reinstalling it, as explained in these articles:
*[[Basic Troubleshooting]] - see the "Reinstall Firefox" section [https://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_7-reinstall-firefox here].
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Clean_reinstall (MozillaZine's KB article is currently unavailable)
If Firefox still crashes after a clean reinstall, try the suggestions in the [[Firefox crashes]] article [https://support.mozilla.com/en-US/kb/Firefox%20crashes here] and, if possible, post a crash Report ID, as explained at the end of that article.

Battery, Power, Deep Sleep and Spotlight problems after 10.9.4 update

Hi, I have a Macbook Pro 8,1 13in (Late 2011). I updated to the latest version of Mavericks (10.9.4) and iTunes on Sunday, right after that my macbook started to goes into Deep Sleep after closing the lid, even when the battery was 80% of charge. My battery normally lasts for almost 5 hours. After it went to deep sleep, the power bottom does not respond. Also, I have noticed that spotlight process in Monitor was consuming so huge amount of resources. This problem persists in Boot Camp. There is no way to turn the machine up without plugging it to the power cord. Sometimes it charges the battery as usual, sometimes it does not recognize the battery. Suddenly, the mac goes into sleep mode while I'm using it.
I have researching and troubleshooting in order to fix this but no solution. I have reset the PRAM and SMC. I made a backup of my files and installed Mavericks from the ground with external storage in order to erase the entire disk, no solution. I made an Internet Recovery and downgraded it to Lion, it worked for 2 hours and then I upgraded again to Mavericks (10.9.0) and the same problem came again, the upgraded to 10.9.4 and no solution at all.
I have searched on internet and there are other people experiencing this problem but nobody is able to bring a valid solution.
This is my battery's health:
Battery Information:
Model Information:
Serial Number: 9G1450LRJD3MA
Manufacturer: DP
Device Name: bq20z451
Pack Lot Code: 0
PCB Lot Code: 0
Firmware Version: 201
Hardware Revision: 2
Cell Revision: 158
Charge Information:
Charge Remaining (mAh): 3204
Fully Charged: No
Charging: Yes
Full Charge Capacity (mAh): 4859
Health Information:
Cycle Count: 931
Condition: Normal
Battery Installed: Yes
Amperage (mA): 2406
Voltage (mV): 12273
System Power Settings:
AC Power:
System Sleep Timer (Minutes): 10
Disk Sleep Timer (Minutes): 10
Display Sleep Timer (Minutes): 10
Wake on AC Change: No
Wake on Clamshell Open: Yes
Wake on LAN: Yes
Current Power Source: Yes
Display Sleep Uses Dim: Yes
PrioritizeNetworkReachabilityOverSleep: 0
Standby Delay: 4200
Standby Enabled: 0
Battery Power:
System Sleep Timer (Minutes): 10
Disk Sleep Timer (Minutes): 10
Display Sleep Timer (Minutes): 2
Wake on AC Change: No
Wake on Clamshell Open: Yes
Display Sleep Uses Dim: Yes
Reduce Brightness: Yes
Standby Delay: 4200
Standby Enabled: 0
Hardware Configuration:
UPS Installed: No
AC Charger Information:
Connected: Yes
ID: 0x0100
Wattage (W): 60
Revision: 0x0000
Family: 0x0085
Serial Number: 0x008d9c78
Charging: Yes

Reseting the NVRAM/PRAM doesn't solve my problems.
Hi, since you have performed NVRAM /PRAM reset, try:
Intel-based Macs: Resetting the System Management Controller (SMC)
and if still issues persist, try: OS X: What is Safe Boot, Safe Mode?
Cheers

HT201263 my ipod touch 4th gen isnt work after a long time with 0 percent battery power.Then its not working. computer doesnt respond to my ipod .only black screen is appearing it even not wake up after reset it what can i do please help me

my ipod touch 4th gen isnt work after a long time with 0 percent battery power.Then its not working. computer doesnt respond to my ipod .only black screen is appearing it even not wake up after reset it what can i do please help me

After being connected to a charging source overnight try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar

Powerbook crashing on battery power after repair

Similar Messages

Maybe you are looking for