Typing out a single character translating as five to six characters on screen? Mouse and keyboard operations going haywire? Timer related programs such as advertisements, animated gifs, screen savers, and cursors changing a little too quickly? If you’re experiencing any one of these problems then your Windows time service may be running too fast, while the BIOS functions normally.
Here are a set of steps that you could try, to address this problem in Windows 7.
Ensure that the Windows Time Service is up and running automatically on system start. To achieve this, run the following commands at the elevated command prompt.
Stop the service -> net stop w32time
Unregister the program -> w32tm /unregister
Register the program again-> w32tm /register
Register the time service dll -> regsvr32 c:\windows\system32\w32time.dll
Start and synchronize the timer
- net start w32time
- w32tm /resync
You could also simply use the appropriate user interface to carry out the same steps.
You can also set group policies for the timer service, set the option to “Not configured” in the Global Configuration Settings, Configure, and the Enable Windows NTP Client, and Windows NTP Server tabs.
Power off the system by disconnecting all cables from the main power source, and after about half an hour, power on and start up the system. The timer service will be set right on start up, only temporarily for another couple of weeks before the problem resurfaces again.
You can still try to troubleshoot the Windows Time Service using W32tm.exe. For additional information you could look up this technet article.
Those who regularly power off their systems are unlikely to face this issue. The problem has been attributed to certain internal circuits retaining power even after the system has been shut down and only a physical power off would cut supply to those circuits.
It also seems like the problem is widely prevalent in ASUS motherboards and a few random cases on Dell machines. Check with your manufacturer regarding this issue and go in for a new motherboard if required – a few ASUS users have had the issue rectified with a new motherboard.
