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: Most helpful
  1. Anonymous
    2010-01-10T03:20:04+00:00

    I am another ASUS motherboard owner with the same problem. Just build a new system with M4A785-M with an AMD phenomII. The asus support forums have a couple of threads where a bunch of people have had the same problem.

    I used the trick of turning off the power completely to get it to work again, but that's not a fix...

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-01-08T07:31:28+00:00

    Well, another Asus motherboard has problem. May be it is Asus not working with the Windows 7, since so many Asus motherboard reported the same problem. Didn't heard anything from Microsoft though, don't now when are they gonna figure out something. Anyone has the same problem but with a different brand motherboard out there?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-01-08T02:28:50+00:00

    I have the same problem with an ASUS M4A785TD-V EVO :(

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-01-03T04:46:20+00:00

    I was having the exact problem with my machine...an 7 year old Dell Dimension on W7.  I followed all of the advice on this thread but nothing worked.  I disconnected power from box and removed the battery on the board for several hours.  I replaced the battery and plugged everything back up and so far so good.  My problem was in the BIOS as I could see the clock going nuts in the PC Setup screen.  I'm not sure if this is the long term fix, but everything is back to normal now (for the past hour anyway).

    Was this answer helpful?

    0 comments No comments