The system clock is drifting quickly in my new Windows 8 Pro installation on a computer that ran Windows 2008 Server (Windows 7) just fine.
This is a DELL Precision M4300.
Originally I thought this was just in Windows 8. I've since put back the Windows 2008 Server hard-drive that I'd swapped out yet the problem continues. I cannot accept that this was happening before and that I just didn't notice. Over the course of a day, the clock can drift by many hours. It always seems to be slow.
I have the Internet Time sync enabled and I know how to make it happen manually.
What could be causing this, which must be a new problem? Many google search results suggest a bad CMOS battery. But I also read that Windows doesn't consult the hardware clock unless it is waking up or booting, so if the computer stays on the whole time during the drifting, I don't see how the battery could be the issue. Also, since it was not a (persistent) issue with Windows 7 I think it must be related either to the different hard drive or the different OS
(And no, it's not a virus)
I swapped back my Windows 7 drive for a few months. For the first few weeks of being back with the old drive, this new clock drift problem actually persisted! I wondered whether I had been wrong and that the drift problem had also been around in Windows 7 but I hadn't noticed. I couldn't find a solution but after a while it went away and I had a stable system clock - awake, through a sleep, reboot, not even connected to the internet for a resync it was fine.
So just today I put the Windows 8 drive back in, thinking that whatever driver or whatever was having the problem had been fixed in a patch. Well, already I'm seeing major drift again!
Is there any way that the drive itself (changing from an OCZ Agility 3 to a OCZ Vertex 4) could cause this kind of problem? I can't see how, but maybe if the drive has funny timing on the bus or something, maybe that could cause it?
I wrote to OCZ and heard back from them:
Unfortunately we have never had any cases regarding this issue with our drives. It sounds to be more of a software issue with your Windows install or a hardware issue with the system's main board. We recommend contacting Microsoft and Dell for assistance.
This is a very frustrating problem. I have to resync the clock with a time server several times in a work day.
It's not a constant drift, I don't think. Sometimes several hours can pass with no drift (rare) but within one hour it can go off by 45 minutes easily.
I'm not sure if it ever goes backward in time - that is, go to a time earlier than I synced it last. Probably not, I think that would cause major problems with file management and so on that I'm not seeing.
Here is a set of Event Log entries. When I woke up today, I noticed the clock was stuck at about 7pm last night. See how the log, which is in event order, bounces around on the time. I can't believe this system can even stay stable (otherwise) with time that jumps backwards - Surely there must be code somewhere that needs to assume a futurely direction for time! Those are the only entries from around that time.
I don't know if these errors are a cause, and effect, or just a coincidence.
Information 2/6/2013 6:58:31 PM Windows Error Reporting 1001 None Information 2/6/2013 6:59:57 PM Windows Error Reporting 1001 None Information 2/6/2013 7:01:15 PM Windows Error Reporting 1001 None Information 2/6/2013 6:58:52 PM Windows Error Reporting 1001 None Information 2/6/2013 7:00:17 PM Windows Error Reporting 1001 None Information 2/6/2013 7:01:40 PM Windows Error Reporting 1001 None Information 2/6/2013 6:59:22 PM Windows Error Reporting 1001 None Log Name: Application Source: Windows Error Reporting Date: 2/6/2013 6:58:31 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Description: Fault bucket -1469235789, type 5 Event Name: WPNConnectionFailure Response: Not available Cab Id: 0 Problem signature: P1: Data Reconnect P2: 880403f5 P3: WNP P4: IPv6v4 P5: None P6: LAN P7: 2 P8: 244 P9: P10:
Attached files: C:\Users\Jason\AppData\Local\Temp\wpn_3775682326159551384.evtx
These files may be available here:
Analysis symbol: Rechecking for solution: 0 Report Id: 1a552c3b-70b9-11e2-bed8-001e37f5f3d7 Report Status: 16 Hashed bucket: bf2d0f7d5d2d29e2ff5285f8ba408a8d Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-02-06T23:58:31.000000000Z" /> <EventRecordID>7762</EventRecordID> <Channel>Application</Channel> <Computer></Computer> <Security /> </System> <EventData> <Data>-1469235789</Data> <Data>5</Data> <Data>WPNConnectionFailure</Data> <Data>Not available</Data> <Data>0</Data> <Data>Data Reconnect</Data> <Data>880403f5</Data> <Data>WNP</Data> <Data>IPv6v4</Data> <Data>None</Data> <Data>LAN</Data> <Data>2</Data> <Data>244</Data> <Data> </Data> <Data> </Data> <Data> C:\Users\Jason\AppData\Local\Temp\wpn_3775682326159551384.evtx</Data> <Data> </Data> <Data> </Data> <Data>0</Data> <Data>1a552c3b-70b9-11e2-bed8-001e37f5f3d7</Data> <Data>16</Data> <Data>bf2d0f7d5d2d29e2ff5285f8ba408a8d</Data> </EventData> </Event>
It's definitely jumping backward in time by an hour or so - back prior to the last reset of the clock.
Here's a post describing what seems like the exact same problem:
The old laptop motherboard failed, perhaps unrelated to this clock thing. I swapped out the identical M4300 motherboard. I didn't notice right away, but the backwards-drifting clock is now happening quite dramatically with the new motherboard as well. I never noticed this happening on the old laptop though it had the same software and drivers (as far as I casually knew), but it was used much less frequently.
I took a road trip and had intermittent connectivity. I have mitigated the issue somewhat with a new Windows Scheduled Task to sync the clock every 5 minutes and on Wake - doesn't work if the clock jumps backwards far. Without connectivity, the problem is in full effect. The clock drifted backward in time of MORE THAN A WEEK within a day or two of last sync.
This is extremely frustrating and threatens my file-syncing and git repository integrity. I'm getting a few up-votes - is this because you have the problem too? Or is it just entertaining? :-P