w32tm /query /status.....malfunctioning clock time work up and fix

how come it did not sync with the sync command?

It is now delayed to 27.9 seconds....that's about 10 to 15 seconds for the last hour

prior to the problems of the last few days with delays over 4 minutes it somehow would reset itself at about 1 min and 15 to 20 seconds.

For the hardware clock is there any way to test the hardware if problems are not detected with the onboard UEFI tests?

For windows is there any way to test if sfc /scannow finds no integrity violations?

The DISM commands with restore health don't work for windows 7 professional but the scanhealth command was ran.

It did not find any problems related to time in the CBS file.

What else can be done to work up this time problem on this new computer?

It has had time problems since its early use.

Figuring out how to save appropriate files then reinstalling windows would take me at least 8 to 12 hours.  I was getting close to doing this just to report the findings to HP as they claim it is not a hardware problem.  The HP support had thought it was the motherboard and replaced it.  One upper level HP support stated that the problem with windows 7 and Ubuntu times indicates it is not the hardware.  That did not make any sense to me.

So I am looking for something in the work up that can better define the problem.

In the clean boot would you look at the items checked and then uncheck half and then recheck and uncheck the other half?  Then depending on that result decide if to divide again in half to narrow down?  How long would you test the time delay for each step in the process?

the time delay has progressed to 16.1 seconds behind:

The last sync was at 11.53AM, so in about 2 hours it drifted by 16.1 seconds, at that rate if it stays constant it will drift by about 193.2 seconds (3.22 minutes) per day.  It doesn't appear to be a Windows problem, it seems that the hardware clock that can't keep proper time.  Other than re-syncing at shorter intervals there is not much that the operating system can do.

Note that some applications (or malware) can cause the clock to gain or lose time, you can boot to safe mode or Clean Boot and see if the problem persists.  If the problem is absent in Safe Mode or Clean Boot then there is something running in normal boot that psyches out the clock.

John

w32tm /resync displayed:

Sending resync command to local computer

The computer did not resync because no time data was available

What does that mean?

w32tm /query /status displayed last minute has 61 seconds, unspecified


Issue the w32tm /resync  command then issue the w32tm /query /status command again.

By default the Windows time service is set to resync at 7 day intervals, that can be changed by way of registry edits but it would be preferable to use a helper application to do it for you, manually editing the

\SYSTEM\CurrentControlSet\services\W32Time key requires advanced knowledge of the values and often leads to problems.  I recommend that you use Atomic Clock Sync to help you with this.

John

The earlier time error post at 11:47 AM today was the latest found in the event viewer.

The time delay is now 18.6 seconds.

Typically the time delay would rise to 1 minute and 15 to 20 seconds and then reset on its own during the day.

The time synchronization is scheduled once per week so somehow the computer is resetting the time itself without the windows time synchronization.

Over the past few days the typical 1 minute and 15 to 20 seconds did not work and the time delay progressed to over 4 minutes.  Today it was reset to exact time so it may take another day or two to see if it resets on its own at 1 minute and 15 to 20 seconds delay or whether it rises to over 4 minutes before resetting itself.

How does it reset itself?  Is that a bios process?  If so what is happening?

Any idea how to fix the time delay?