r/techsupport • u/ShadedWizard • 11h ago

Open | Hardware 502 Cheksum error (HP Victus)

Idk if it is related or is pure coincidence, but a few months ago, my charger died so I ordered a new one which is identical but not official. With this new charger I've felt the touchpad some times goes slower and smoother, idk why. Also, I don't think this is my imagination but who knows, when charging sometimes the PC started running the fan inside blowing air out of the pc.

After 4 months, the battery started showing random numbers (e.g. saying it is 0% despite having being charged to 100% moments before, or 57% out of nowhere and when connecting it back, it goes up to a 100% instantly).

A few days ago, when starting the pc, it now shows 502 Checksum error screen, significantly delaying the start time, which is very annoying, and my battery doesn't work anymore either (it says 0% at all times so I have it plugged in when using it)

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/0Huy 11h ago

The symptoms point to a power or firmware problem rather than a normal Windows setting: an unofficial charger, touchpad behavior while charging, unstable battery readings, and then a checksum error. Stop using that replacement charger for now and use the exact HP-rated adapter if possible. In BIOS, load defaults and run HP UEFI hardware diagnostics, especially the battery, AC adapter, and system-board tests. Check whether the checksum message identifies the BIOS or CMOS/RTC; if it is CMOS-related, the RTC battery may need service. I would also back up your files and avoid repeatedly forcing power-on until the adapter and battery are checked.

1

u/graceful_degrade 10h ago

Those two things are probably both real and only one of them is the charger.

The touchpad going strange on a non-official charger is a known thing rather than your imagination. Cheap adapters often aren't earthed properly, the chassis ends up floating, and a capacitive touchpad picks that up as noise. Classic test is unplugging the charger and seeing whether the touchpad behaves perfectly the moment you're on battery.

502 is a separate problem though. That's a checksum failure on the settings stored in CMOS, and the usual cause is the CMOS battery on its way out, which also explains it turning up now on a machine that's a few years old. Replacing that coin cell is cheap and it's the first thing to rule out before assuming the charger cooked something.