windows 8.1 clock running fast post update

I have a ACER W510 with a Atom Processor, running Windows 8.1 32bit.  I never had this problem when it was running windows 8.0 32bit. No it happens most of the time, it could be after shutting done for a hour or so and turning it back on it could be off any where to a couple of hours to a couple of days.  and 90% of the time just turning auto time update of and on will fix it.

We investigated this issue and confirmed to be a bug in the OS.  This issue impacts systems that doesn't have a CMOS RTC (real time clock). On systems without a legacy CMOS RTC, the HAL exposes a virtual RTC abstraction based on the system performance counter which tells time during instances (such as early and late boot) when the kernel can’t provide reliable answers.

As part of resume from hibernate, system runs into a race condition where the virtual RTC doesn't get fixed up correctly based on the performance counter and as a result the time tracked by RTC ends up being a bit further in the future. The kernel periodically ensures that it’s view of time is in sync with the RTC, and if that happens at just the right time, the kernel could get this wrong time in the future and use it as the system time, which would persists until NTP fixes it.

We are looking into the fixing this issue. In order to expedite the roll out of this fix, it would be helpful if you can provide information about your system and how often you run into it.

Thanks,

Eliyas

I have a 64GB HP Envy x2 that has this problem and a 128GB version that does not. The only fix I've found to stop the annoyance (in the 64GB) is tweaking the registry to allow the clock to update on wide mis-settings:

Try opening the registy editor and changing the following two settings to 1000000 decimal:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\Config\MaxPosPhaseCorrection

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\Config\MaxNegPhaseCorrection

I had to really comb through the registry to come up with this. Of course there is a 45 minute to eight hour window when windows will re sync based upon the default "Special Skew" setting which can be modified in:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\Parameters

by adding a key as follows:

Period : REG_DWORD or REG_SZUsed to control how often the time service synchronizes. If a string value is specified, it must be one of special ones listed below. If you specify the string value by using the numbers (65535 for example), then create the value as a REG_DWORD. If you use the word to specify the string value (BiDaily for example), then the entry should be created as a REG_SZ.

0 = once a day

65535, "BiDaily" = once every 2 days

65534, "Tridaily" = once every 3 days

65533, "Weekly" = once every week (7 days)

65532, "SpecialSkew" = once every 45 minutes until 3 good synchronizations occur, then once every 8 hours (3 per day) [default]

65531, "DailySpecialSkew" = once every 45 minutes until 1 good synchronization occurs, then once every day

freq = freq times per day

I haven't determined whether this double word is in seconds or minutes.

I tried all of the above, newer HP desktop, Win 8.1 clock still runs fast???

So it happens on desktops too? I thought only some tablets were affected. It's definitely a bug then!

I tried all of the above, newer HP desktop, Win 8.1 clock still runs fast???