On another web site I had posted this information and someone suggested flushing the bios. When I had inquired I never got an explanation of what they meant by flush the bios. On this computer the bios was reset when the CMOS RTC battery was replaced.
It was reset once when I worked with HP over the telephone. And the bios was reset again when HP replaced the motherboard....
...The computer now is displaying more delayed time that it had. Typically it would display delayed times up to 1 minute 15 to 20 seconds and then reset back to approximately 5 seconds delay. How it resets on its own is unclear to me but this happened
on a regular basis...
...With the worse time delay and with the w32tm displaying unspecified I am wondering whether it is no longer synchronizing...
The time synchronization is set to synchronize once per week as per the picture above. It displays next synchronization scheduled 2/25/16 at 8:11 AM...
It also indicated that the last successful synchronization was 2/19/16 at 6:19 AM.
In contrast the administrative command prompt w32tm result indicated that the last successful synchronization was 2/18/16 8:11 AM.
How come they have different results for last successful synchronization?
I had not looked in the event log since the time synchronization was deliberately turned off to check for network related issues. If you want me to look for something there please indicate how to go about it. In the next few days I plan to reboot and follow
the steps you have above...
Flashing (not flushing) means updating the BIOS, the BIOS is firmware that enables low level functions between the hardware and the operating system. Being that HP is involved in the effort to resolve the problem, (and that they have supplied a replacement
motherboard), I would think that the BIOS would be at it's latest available version, you can ask them if it is and you should also ask them if the the latest chipset drivers are installed on your operating system. Being that the problem appears to exist with
both Linux and Windows it strongly suggests that this is a hardware problem, having the latest BIOS and chipset drivers may correct this.
If the problem lies with Windows resetting the time service with the commands given earlier will reset the service to default values, it will delete the existing SYSTEM\CurrentControlSet\services\W32Time key and write a new one (resetting the service will
also reset the list of time providers solely back to time.windows.com). The Windows time service can easily be thrown out of whack with incorrect or improper values at the W32Time key and resetting the service is a clean starting point when troubleshooting
time problems . Note that for the NTP packages to reach destination the firewall must allow UDP protocol traffic both ways (inbound/outbound) on port 123, Windows should have this properly configured but check anyway to make sure, especially so if you are
using a third party firewall.
The w32tm /resync command may also be helpful, this tells the computer that it should resynchronize its clock as soon as possible, throwing out all accumulated error statistics.
There are some reports that the time service may be erratic or gain/lose time if the service is set to start automatically and that it should be set to Automatic (Delayed Start) instead of Automatic.
In the Event Log look for warnings or errors from Event Source: W32Time.
With all of that said if this is a hardware problem increasing the time re-syncing frequency is about all the operating system can do, (and for all it's worth bad motherboard clocks are not uncommon).
John
These may be helpful:
How to Fix Time Error
(Written for Windows XP but the W32tm service is practically unchanged since Windows XP/2003)
Configuring the Time Service: Enabling the Debug Log
Windows Time Service Tools and Settings
High Accuracy W32time Requirements
(Why might the Windows clock be off by as much as 5 minutes?)
Publishers of Time and Frequency Software
(You can use third party software to synchronize your clock)
Atomic Clock Sync: a free configuration utility
(A small utility that allows you to easily configure the Windows Time service without messing with the registry or complicated command line syntax)
PRTG Manual: WMI UTC Time Sensor
(A free utility that monitors your PC time against an external time source, showing you drift in real time)
Configuring the Time Service: NtpServer and SpecialPollInterval
(Some claim this doesn't work but that is false, it may not work due to other factors - Atomic Clock can set this for you)
When SpecialPollInterval is used as a polling interval, the Windows Time service does not correct the time if the service gets into Spike state
Make Windows synchronize time more often
(If you cannot seem to get SpecialPollInterval to resync more often you can use the w32tm /resync command in a batch file or script along with the Task Scheduler to do it for you)
Using Event Viewer to Troubleshoot Problems
How to Open and Use Event Viewer in Windows 7
John