P15xSM clock becomes inaccurate slowly.

So I've noticed this for a while but never put much thought into it but it's starting to be annoying.

I have this P157SM and another brand work laptop side by side.

I notice about once a week the P157SM time is about 15-30 seconds behind because randomly I will see the time on it vs. the other laptop and they don't match by 1 min (which is really seconds because one just turned sooner).
I open up the Date and Time on both and the Clevo/Sager is always behind.

If I tell the P157SM to update from the internet source in Windows it updates fine and is correct but slowly over time it gets out of sync again.
It seems like every day it gets a few seconds behind which is a lot...

The laptop is always plugged into AC power and charged so I doubt it's CMOS battery related as even if you remove that so long as the machine has a battery or power cable everything is retained, plus I can leave CMOS in and remove power and laptop battery and everything is retained.

The only thing I can think of is the clock generator that maintains system clocks is just inaccurate/poor at it's job.

Anyone else ever notice similar? I guess it would be hard short of having two machines you can compare down to the second level though but just wondering.

It's annoying because that probably means MB replacement which sucks for something silly like system clock though I know technically it's more involved vs. that because the clock generators are relied on by a number of other things like chip speeds etc., or at least use to be.

 

BIOS clock time is simply a function of the clock signal, it looks like that is out for some reason, so yes a motherboard replacement or regular clock synchronisation.

 

OCD much? Lol.

Sent from my SM-N9005

 

No but when you do things that are time specific and sensitive it adds up.

NTP was created to account for small differences or human inaccuracy, like a few seconds, (fwiw technically time slows down every year as the earths rotation does anyway), but for time purposes 30 seconds a week is a lot.

What good is a clock that can't tell time? It's no good.

I am not so picky that I need it to be dead exact but when every few weeks I notice it's a minute + off it's silly to have to keep fixing it.

I've got 10 year old systems with no NTP running that track better time lol.

I can technically just modify the default NTP to do it more often I guess but just wanted to see if anyone else had noticed similar ever.

 

It's not usual for the systems, so the timing circuit is obviously not quite calibrated right.