My computer recently developed an error where the hardware clock displays the time as follows

System date [Mon 31/63/25755]
System time [63:28:25]

The clock runs.

I’ve tried all the usual tactics: remove CMOS battery, short the pins to force a reset, put fresh battery, reflash BIOS. Nothing.

On boot, I get an error on reading the hardware clock and the system defaults to 3 of September, 2025.

I think I’m looking at a mobo heading to the e-waste bin.

The board in question is a GygaByte AB350M-DASH. It still runs but it’s a bit annoying having to set the system clock every single time I boot up the machine.

Any advice on the matter is welcome.

  • emotional_soup_88English
    2·
    12 days ago

    I second this. If you can deal with those microconnections to an NTP server, search for how to enable NTP. On a systemd Linux system it should be a timedatectl option, I think.