AV14-51 cmos battery location

Options
grayg
grayg Member Posts: 5 New User

I'm trying to perform a 'hard' reset and took off the back cover of my laptop. Can someone look at the attached picture and tell me if that is the CMOS battery where indicated with the arrow. To 'disconnect' the battery in order to clear settings, can I just pull out the connector wire? If so, I'm having trouble doing that. I used some force with small pliers but don't want to tug out the entire housing. Is there a trick to releasing the wire from the connector, i.e. disconnect the battery wires?

Answers

  • Puraw
    Puraw ACE, Member Posts: 18,206 Trailblazer

    Hi grayg, yes, that is the CMOS (RTC) battery module, the white plug is tiny (2-wire) with a handle on each side and you may need tweezers and a small screwdriver to wiggle it out by the 2 handles, don't use pliers as that will squash the plastic plug. Alternatively cut a small slit in the black plastic wrapping with a box cutter to remove the battery and replace it, then close the slit with black electrical tape.

  • grayg
    grayg Member Posts: 5 New User

    OK< thank you Purzaw! I will proceed with care. I tried wiggling it out with a couple of small screwdrivers but it's really stuck in there. I thought there might be some sort of release tab, but I don't see one.

    The electrical tape slit might be the way to go.

    As I described in a duplicate thread I posted a few days ago, my problem is that I can get to the windows screen where it asks for my password, but as soon as I put it in, the screen goes black. I can ctr-alt-del to task mgr, but everything I've tried so far is not working.

    It's out of warrantee and I couldn't find anything on Acer's website with a detailed layout of the mother board components for this model, like a service manual.

    It began with my plugging in an older USB external drive and when I 'safely' removed it, the problem started. I was able to view device mgr at one point and removed my graphics driver and it didn't help. I think it's something to do with explorer.exe being corrupt. There seem to similar unresolved issues when I go through the posts here.