Windows 7 clock is running very fast
- I'm running Windows 7 64bit RC, not as a Virtual Machine. (only OS on this box).
Athlon II X2 250 processor, 780V chipset. (Asus M3A78-CM motherboard).
If I bring up the clock on-screen the second hand is moving ridiculously fast (1 minute takes about 2.5 seconds).
Things I've tried:
I updated my BIOS to the latest version.
Note: It doesn't appear to be a hardware issue (at least with the CMOS clock), as when I'm in the BIOS the clock takes 60 seconds for 1 minute.
I had heard that the problem was possibly related to the high precision event timer, but I don't appear to have a way to disable that from the BIOS, and disabling it in the Device manager didn't do anything.
The other possibility was supposedly Cool N Quiet (which I have tried disabling from the BIOS, again with no luck).
Any idea what to try next?
Note: It was not doing this when I originally installed the OS. but Defender and my Anti-Virus find nothing so it doesn't appear to be malware... I'm not exactly sure when it started as I only noticed when I was on a web forum and animated gifs on some adverts were changing very quickly.
Answers
- I found a solution for my system. I switched the computer off at the wall and waited a few seconds, turned it back on, then waited a few more seconds before pressing the power button. Its working ok now. It hasn't repeated the problem having turned it off and on again a couple of times now.
- Marked As Answer byMLeiper Thursday, November 19, 2009 9:45 AM
All Replies
Hi Mleiper,
Mostly, this issue is caused by Windows Time service corrupt. You can try to take following steps to troubleshoot this issue.
Run the following command in a elevate privileges cmd window.net stop w32time
w32tm /unregister
w32tm /register
net start w32timeThen, please restart the computer to test the issue again.
If any error message was received when trying to take my suggestion, please let me know.
Hope it helps.- Thanks, for the suggestion.
Unfortunately, it doesn't seem to be the answer.
i.e. when I ran net stop w32time, it told me it wasn't running.
I've run the other commands, got an error on the unregister (probably because it wasn't registered), and then registered and started w32time. But a minute is still passing in 2½ seconds after a reboot. - Hi Mleiper,
I noticed you said "when I ran net stop w32time, it told me it wasn't running", maybe we found the culprit.
Could you please check following settings?
1. Click Start, type services.msc and press Enter.
2. Please locate a service named Windows Time and double click it.
3. Does the service status is Start? If not, please try to start it.
4. Please try to change the startup type to Automatic.
5. Restart the computer to check the issue still persist.
6. If the issue still persists, please let me know this service status.
Thank you for your cooperation. - There is no Windows Time service running when I bring up services.msc. (My clock is re-syncing to internet time periodically)
Today when I tried the net start w32time, I get an error message (which I didn't get yesterday).
C:\Windows\system32>net start w32time
System error 1290 has occurred.
The service start failed since one or more services in the same process have an
incompatible service SID type setting. A service with restricted service SID typ
e can only coexist in the same process with other services with a restricted SID
type. If the service SID type for this service was just configured, the hosting
process must be restarted in order to start this service.
I've just gone through the steps at http://social.answers.microsoft.com/Forums/en-US/vistaperformance/thread/6bbea43f-5575-4e78-9b52-ac766632bfc2 (although the entry was already there, will try a reboot, and come back...) - OK - When I first went into services.msc, Windows Time wasn't there at all.
Tried to start it, and got error 1290, so I re-entered the registry entry as per http://social.answers.microsoft.com/Forums/en-US/vistaperformance/thread/6bbea43f-5575-4e78-9b52-ac766632bfc2 to re-enter my HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv entry (which didn't appear to be any different, but when I rebooted, Windows Time was now in services.)
It was already flagged as automatic, but not started. I started it, and rebooted.
Again, if I go into services.msc after the reboot, it's not started, but still flagged automatic.
I changed it to automatic (delayed start), and rebooted. It now shows as started, but I still have a clock that goes forward a minute every 2½ seconds. Hi Mleiper,
Glad to hear the Windows Time sevice is back. Given the current stage, I have following suggestion;
Suggestion 1: Register dll file and reset SNTP.
============
Please run the following command in a elevate privileges cmd window.net stop w32time
w32tm /unregister
w32tm /register
regsvr32 c:\windows\system32\w32time.dll
w32tm /config /manualpeerlist:time.windows.com,0x4 /syncfromflags:MANUAL
net start w32time
Then, please test the issue again. If the issue still persists, please take the following suggestions.
Suggestion 2: Reset Windows Time Service related group policy
============
1. Click Start, click Run, type gpedit.msc , and then click OK.
2. In the Group Policy Object Editor MMC snap-in, expand Computer Configuration, expand Administrative Templates, expand System, and then click Windows Time Service.
3. In the right pane, right-click Global Configuration Settings, and then click Properties.
4. In the Global Configuration Settings Properties dialog box, click Not Configured, and then click OK.
5. Expand Windows Time Service, click Time Providers, and then set all the objects in this node to Not Configured. To do this, follow these steps: a. In the right pane, double-click Enable Windows NTP Client, click Not Configured, and then click OK.
b. In the right pane, double-click Configure Windows NTP Client, click Not Configured, and then click OK.
c. In the right pane, double-click Enable Windows NTP Server, click Not Configured, and then click OK.
Does it work?
Hope it helps.- Robinson, Thanks again, Tried that, but still no luck - rebooted after each of the two options, but clock is still going very fast. On the second option, all the items were already flagged as not configured. Is there some sort of diagnostic info you might want? - even something as simple as the list of services running, or the processes listed in Task Manager? MLeiper
- I've got exactly the same issue. The clock is spinning like crazy, the hourglass spins like crazy. The cursor blinks fast, videos and music play fast, the windows splash screen flashes quickly. The screensaver even kicks in very quickly.
When I'm in the bios, the clock is normal, it just goes crazy when windows is running. I can boot of a xp pe disk and its all normal. It ran fine for quite a few weeks and now this.
My hardware is Phenom 905e with Asus m4a785td-v evo. Slightly similar to yours.
I'm keen to get this sorted out because I need this thing working. Any further ideas would be appreciated. - I found a solution for my system. I switched the computer off at the wall and waited a few seconds, turned it back on, then waited a few more seconds before pressing the power button. Its working ok now. It hasn't repeated the problem having turned it off and on again a couple of times now.
- Marked As Answer byMLeiper Thursday, November 19, 2009 9:45 AM
- OK - that worked for me too.
Must mean there's some motherboard circuitry that still gets power even when the PC is switched off, that's not powered from the CMOS battery, but needs a physical power disconnect rather than just a shutdown to reset it... (i.e. Must be somehow linked to something like wake on lan, wake on keyboard, where I know power tends to be there after shutdown.) - but that is somehow tied into the timing circuitry (but not the CMOS clock)? - I have same mainboard with you and same issue as well. Even when I try to re-install the windows and boot from Windows CD, the installation goes very fast too.
It appears only happening on AMD chipset? - I also had the same problem with a M4A785TD-V mobo and Windows 7/ 64 bit, and my experience supports MLeiper's hypothesis above. In my case the timing went haywire from the first restart of the Windows installation. The keyboard was unusable - 20-30 duplicated characters from a momentary key press (this makes installing Windows interesting !), and no doubleclick function from the mouse. No USB devices were recognised and the monitor kept going dark after just seconds of inactivity.
After 2 days of fiddling around (changing power supplies, resetting BIOS and CMOS, etc, all to no effect) the problem has gone away this evening, after I followed the steps outlined above (thanks guys) and
1. Persevered with a basic Windows install until I could reset the parameters of Windows Time Service as described above by Robinson to Started/ Automatic
2. Shut down the PC, and unplugged all power cables and other cables to powered devices eg monitor, printer (this must allow the mobo hardware powering Windows Time to initialise properly)
3. Plugged cables etc back in and restarted
Windows started up OK and has remained OK through 4 subsequent restarts while I installed PC software. It will be interesting to see whether it still works tomorrow.
Next time I upgrade my PC I'll probably go for a Mac instead ...
