>Your system clock just jumped 156 seconds forward
When does that ever happen?
>install win10 on laptop for the second time.
>blue screen error while downloading iTunes.
>>55612085
>iTunes
Fuck off.
>walk past officer with earbuds on in phone
>hear a chime through buds the moment we pass each other.
I've never seen that happen, but I've seen SuperMicro machines that have their hardware clock set a month in the future. Fuck SuperMicro.
>>55612060
It happens if your CPU is overclocked/always turboed and Windows for whatever reason (which does happen) is unable to synchronize with it's scheduled ntp .
Your computers time is synced with the clock cycle of your CPU.
>>55612141
I don't get it
>>55611674
I'd be worried too if the internal clock was that far off from standard time.
I know that feel, OP.Jul 8 16:57:43.000 [warn] Your system clock just jumped 273 seconds forward; assuming established circuits no longer work.
WOW THIS IS SO MEME XD
>run memtest
>400 quadrillion errors instantly
17 Jul 13:07:27 ntpdate[3750]: step time server 95.158.95.123 offset 1.092441 sec
Truely fascinating stuff OP!
>>55612404
Neither do I
Still nervous.
>>55614364
>run memtest
>400 quadrillion errors instantly
>ram still werks
>>55612380
It's timed to the oscillator crystal, sure, but this isnt 1993 and CPUs dont use the PLL to adjust base frequency anymore.
The reality is that those chips/oscillators/crystals arent perfect, never have been, so far as their frequency and the passing of time are concerned.
