Windows 7 : System clock running 60 times too fast

Anonymous
2009-12-05T23:06:14+00:00

I am a novice user of Windows 7, having had it on a new PC for less than a week.  On Thursday evening it worked fine, on Friday the system clock started running 60 times too fast.  The minutes are changing every second, the hours less frequently (i.e. not every minute).  It is playing havoc with the behaviour of the PC.  I have to keep moving the mouse or the screen turns off and the keyboard takes every keystroke and repeats it twenty or thirty times.  What can I do?

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2009-12-06T20:11:44+00:00

Hi PhilLondon,

Welcome to Microsoft Answers!

Usually, 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 w32time

w32tm /resync

Then, please restart the computer to test the issue again.

W32tm.exe is used to configure Windows Time service settings. It can also be used to diagnose problems with the time service. W32tm.exe is the preferred command line tool for configuring, monitoring, or troubleshooting the Windows Time service.

Refer this link for more information:

http://technet.microsoft.com/en-us/library/cc773263(WS.10).aspx

You also perform System File Checker.

             1.      Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command

Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the

                      password, or click Allow.

            2.      Type the following command, and then press ENTER:

sfc /scannow

               The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

  For further information, visit the below mentioned link:

http://support.microsoft.com/kb/929833

 Hope this information helped!

 Thanks and regards

 Fouzan – Microsoft support

 Visit our Microsoft Answers Feedback Forum 

 http://social.answers.microsoft.com/Forums/en- US/answersfeedback/threads/ and let 

 us know what you think.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

53 additional answers

Sort by: Oldest
  1. Anonymous
    2009-12-21T21:35:17+00:00

    A couple of days ago I started the computer and it worked!  I haven't shut it down since and won't until after Christmas.  I shall then go to my supplier (it's a brand new computer) with printouts of these threads.  It sounds very much like a motherboard issue.  Interestingly when my system came up a couple of days ago it was in windows recovery mode, there must be something different about the use of the clock in that startup.  As I said the system is working fine and incidentally the windows time service still has a status of not started, so I'm assuming that's a red herring.

    I'm also interested in a solution that doesn't include RMA.

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2009-12-30T15:22:52+00:00

    The computer was turned off last night (29 December) and turned on this morning.  The system clock problem re-appeared.  I returned the PC to the supplier this morning (an internet based provider, but thankfully close to home) and await a remedy.  I will update this thread when I hear any news.  They told me that I won't hear anything this side of the New Year.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2009-12-31T15:46:08+00:00

    I am using 64 bit Windows 7 and have the same problem too. The Windows Time Service sure could not fix the problem. It started about a month or two ago and first I thought was virus or Windows crashed, so reinstalled Windows. The problem still happens after Windows reinstalled that really didn't help to find what went wrong.

    It works perfectly for few days or even week, then problem came back. It doesn't not have specific time or occasion when the problem happens. It happens more frequently lately, say every 2 or 3 days. Sometimes after start up, the keyboard is not responding and need to restart the computer again.

    Anyway, I got a temporarily quick fix from other forums last couple months. Now whenever the problem occurs, I will shut down the computer and disconnect the AC power (wall socket). Turn the switch off at the back of the computer power supply too. Wait about 10 to 15 seconds then power up again, then problem solved. It works every time but is not permanently fix the problem though.

    I have an Asus M3A78EM motherboard. Asus again? Does anyone out there has the same problem but with another brand motherboard? Will that be the problem of Asus or the problem of Windows 7?

    I really want to have the problem fixed permanently. Please Microsoft or Asus, do something.

    Was this answer helpful?

    0 comments No comments