If you google the error message, you'll see a lot if hits (like this). Most of them blame an Asus motherboard and say you can go into the BIOS and disable the chassis intrusion setting, or check the relevant jumper on the motherboard and make sure it is jumped.

-x16wda (September 27, 2015, 06:38 PM)

If your clock is off by that much each passing day, you might be replacing the CMOS battery on your motherboard. These are not expensive , very available and easy to replace, even if you don't/won't do computer hardware repair. Because of previous posts in different threads on this forum, I know you have an older system and batteries on motherboards usually last between 3 to 5 years. 

Once you have done that, also check the regional settings to see if your computer is in the correct time-zone. That can also cause unexpected hour jumps. Especially when you are in a time zone that uses one system for DST and the (MS) server that verifies your clock using another DST system. This is always messy around May and October of each year.

For example: the US uses DST and apply this when each celestial equinox occurs. Most of the other countries that use DST, use the end of seasons as the moment to apply DST. There is usually a two/three week difference between those DST events.

Although this doesn't seem like a big deal for most people, it is a major source of headache for programmers that actually need to apply this properly in applications. Kind of a 'Damned if you do, damned if you don't'-deal, while being in a 'between a rock and a hard place'-kinda situation.

-Shades (September 27, 2015, 08:20 AM)