Windows Losing Serious Time or Not Advancing

There is a condition that can occur in Windows that may affect GLOBALCOM and GCK devices.  This can manifest itself in several ways such as a system that keeps going back to the last boot time or last time the system clock was manually set.  One way to diagnose this is to set the system  time via the usual tool tray access.  Then look in Windows Event Viewer at the System log.  There you should see a Kernel-General log entry for when you set the time.  If you see a second log entry right away that pushes time back a fraction of a second, then this system has the problem discussed here.  If you let this system run unattended for an hour or more, and come back and check on the System log, you will find that time was pushed back again to the last time the clock was set.  

What is going on is that there is a "System CMOS/Real Time Clock" driver in Windows (under System Devices in Device Manager) that tries to set the hardware clock chip (the one you see in BIOS), and periodically compares the chip to Windows time.  At some point it thinks Windows time has gotten way out of whack and forces the clock back to match the CMOS Real Time Clock (which is stuck on the last boot or system set time).  This is all explained online in the following article:

You can read that article for the technical details.  

This happened on an older Johnstown board 1100ACS in Engineering recently.  The fix was kinda like described in the article.  Instead of trying to re-flash the UEFI (BIOS) firmware, I just reset CMOS. However, in my case I tried the least invasive reset, just resetting CMOS passwords. (On Johnstown board, put the boot jumper in Maintenance position, pins 2-3, and in BIOS select "Reset Passwords" under Maintenance tab.) This was enough of a reset to fix it.  Note, if doing a full reset (e.g., remove the battery) be sure to restore necessary settings to BIOS as described in Production Work Instructions for setting up 1100/1200/IP100 hardware for the first time (e.g., WI 8.2-4.IED06).