![]() ![]() One of them was totally corroded, and tested at 0 Volts & 0 Amperes. The other one tested at 1.5 Volts and 4.1 Amperes - still "good".Ī brand-new battery (same manufacturer and same lot) tested at 6.2 Amperes - excellent! I recently removed the 2 AA batteries from my smoke-detector, because it did not signal anything when I pressed the "test" button. Both batteries were installed, a year ago. > I could try another one but two others from the same packaging have worked perfectly fine. It's just a pain in the ass ultimately when it's backfiring like I'm not sure what you mean by with the etched lettering visible: I would really prefer to disable the stupid checksum comparison. Is there any way to get HP to weigh in on this? There is definitely something suspect with their BIOS/firmware, as I had another HP laptop that is only about a year old throw the same 502 checksum error around the middle of October, but it's totally fine now. Are you referring to a motherboard-specific warranty? I couldn't tell you exactly how old the board itself is, but it's definitely not less than 1 year old. I don't know why tbe battery would be a dud, I could try another one but two others from the same packaging have worked perfectly fine.Īs I said before, the machine is out of warranty. I'm not sure what you mean by with the etched lettering visible, but the positive terminal + is facing up and the negative one is facing down, just like the battery before it, which was the original battery. ![]() Erm, ok for some reason that screenshot is gone now. It's kinda bizarre that the BIOS shows the correct date normally though, like in my screenshot. Thanks for your reply and explaining the timestamps. The first does not show the latest 502 error as I took this picture after replacing the battery. The device is out of warranty according to HP Smart Assistant. ![]() I would just disable the **bleep** checksum feature myself if I knew how. It seems like maybe the power is going out at some point in the night which is causing the CMOS data to reset? Or it has nothing to do with that and it's actually a software issue?ĭoes anyone have any experience with this? It's extremely aggravating. After booting it gave me the 502 error message one more time, and then it seemed to boot normally, but now the next morning, the 502 error message is coming up again. I held the power button down at various steps to clear the CMOS data as described in the article. This entailed me removing the base, opening the case as gently as possible, and removing the old CR2032 3V battery and replacing it with a brand new energizer brand battery of the same type and voltage. I took a picture of the BIOS system log which shows the 502 errors occurring, but I can't seem to interpret the timestamps, maybe someone could help me with that as well.Īnyways, I followed the instructions on for generic reset of CMOS, since the product page for Z5N92AA does not appear to list specific steps as described. Recently it has started booting slowly and/or when this happens, before it will boot into Windows, the HP firmware displays the message I placed in the post title, which is similar to "The CMOS Checksum is invalid (502)" error. Hello, my problem is with a HP 24-e014 All-in-One Desktop PC with product SKU Z5N92AA running Windows 10 Home Edition (64bt). Business PCs, Workstations and Point of Sale Systems.Printer Wireless, Networking & Internet.DesignJet, Large Format Printers & Digital Press.Printing Errors or Lights & Stuck Print Jobs.Notebook Hardware and Upgrade Questions. ![]()
0 Comments
Leave a Reply. |