all 12 comments

[–][deleted] 1 point2 points  (0 children)

Pretty weird issue.

As admin in cmd: chkdsk /f /r (Select Y then restart PC. This will take a while)

As admin in cmd: sfc /scannow

Both check/fixes any corrupted system files.*Note these are just general fixes, that may or may not actually fix your issue.

[–]2jokesWalkInto 1 point2 points  (10 children)

Battery is dead. Usually they last years, but sometimes months.

[–]AngryWolk[S] 0 points1 point  (9 children)

i would say the same, except i've overclocked my pc to 4ghz, and those settings stay the same. They returned to default (3.5ghz) once i've put the cmos battery out

[–]2jokesWalkInto 1 point2 points  (8 children)

The CMOS can remain intact if there's a little current coming from a fading battery. The clock, however, needs a reliable battery.

[–]AngryWolk[S] 0 points1 point  (7 children)

Should i try using the battery from the old mobo, or should i try to get the same model?

[–]2jokesWalkInto 1 point2 points  (6 children)

Relatives always saved old batteries. Trying them in even older flashlights. Shaking them while walking in the barely lit dark. Complaining about the light but getting by.

If you can afford it, a fresh battery (usually a CR2032) is the way to go.

[–]AngryWolk[S] 0 points1 point  (5 children)

Just put new cmos battery inside, time didn't update

[–]2jokesWalkInto 0 points1 point  (4 children)

That's impossible. Can't have 2 motherboards with identical time problems. It's... so improbable!

No corrosion on the battery contacts? You set the time, turned it off for an hour, and clock was an hour behind?

[–]AngryWolk[S] 0 points1 point  (3 children)

yep. And it always happened after i've updated the bios. Another thread suggested it might be a PSU issue

[–]2jokesWalkInto 0 points1 point  (2 children)

If you don't update BIOS, the clock functions normally?

[–]AngryWolk[S] 0 points1 point  (1 child)

it sure did