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: Newest
  1. Anonymous
    2011-11-13T18:39:09+00:00

    Hi Everyone,

    I have the same issues as everyone else.

    System: Asus M3A48-CM, Phenom 9950 2.6, 8G Ram, WD Green 1t sata, Seagate Barracuda 1t sata, Graphics   ATI Radeon HD 4670, 

    The one drive has XP that runs flawlessly.  My win 7 has ran flawlessly until I was gone for two weeks and we lost power.  Now, it runs extremely fast with kb strokes, etc.  I have updated the bios, reformatted and now going to try to disconnect the power.

    Has Asus figured this out?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-06-26T02:54:40+00:00

    Ok so I have discovered this forum because I too am having this problem. I hope to re-ignite discussion about this!

    The computer I have is a Acer Aspire AM1201-E1721A. AMD Phenom X3 triple core. Windows Vista.

    This problem came out of nowhere and sent me on a wild goose chase. After eliminating many things and trying many different configurations i.e. starting with everything unplugged, I know how to get the computer running fine, but it isn't fixed. So I will share how I get it running and then throw some ideas around about what could be the problem and maybe you all could add to it to come up with a reason.

    To guarantee I get my computer working I do the following (with everything inside connected);

    • Disconnect the power to the power supply
    • Pull the BIOS battery
    • Pull the jumper to reset the BIOS
    • Put the jumper back on the appropriate pins to reset the jumper
    • Put the jumper back on the original pins
    • Put the BIOS battery back in
    • Plug the power back into the power supply
    • Turn it on
    • Bootup shows me that the CMOS is wrong and the date is wrong and gives me the option to load defaults F2 or enter BIOS F1, I choose F2

    The computer boots fine and works fine

    If I were to shutdown and remove the power to the power supply this will cause it to not work properly. If I do that, then I have to perform all of the above steps again for a guarantee that it work.

    What it means to not work properly is that on bootup the Vista bar that shows the scrolling animation to the right actually becomes about 3 bars going to the left (which I assume is that it is going so fast in the correct direction, that it appears to go the other way). If I can get to the animated Vista ball that has the animation doing a counterclockwise 360 (which is usually very slow) it goes at a hundred times per second. If I can actually load windows, the system tray clock shows minutes counting as seconds. In task manager, the networking graph (which usually scrolls by at a snails pace) goes by at lightning speed. It seems everything about the computer is in warp speed.

    The answer must lie in whatever situation is created when the power is removed from the power supply. And it isn't the BIOS battery which I know because it always holds the time once I set it PLUS I decided to buy a new one so I could sleep at night. As far as I always knew, the BIOS battery controls the memory in CMOS, so is there something that holds memory that is lost when you disconnect the power supply? The answer to this problem has to lie in something that has to do with loading settings under good conditions that are referred to the next time you boot and held in place by the power supply, but I don't know enough about what is loaded and held to answer the question.

    There must be someone on here that has the knowledge to solve this! I appreciate all the other solutions but I suspect that those that think they solved, actually never did. I found myself thinking it was fixed a few times until I realized the correct way to make the problem come up again.

    We have heard lots of solutions, but nothing concrete. I think I can conclude it isn't related to; OS, CMOS battery, bad RAM, BIOS firmware version, particular motherboard brands, virus and so on.

    What's causing this?!

    Thanks for any help.

    Christal

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-01-22T14:49:29+00:00

    I had to sue the supplier to get the money back (Mesh) they were completely unhelpful despite other customers having the same problems.

    I never found a definite answer myself but someone else said they updated everything (windows updates, motherboard drivers, etc) and it didn't return. I suspect some incompatibility between the Asus board and Windows, maybe one of the latest Win 7 updates had a fix. Sounds like clutching at straws but there seems to be no better theory yet? I then built a system using the Asus P7H55-M board, Intel i3, Crucial ram and Windows 7, all runs fine and not seen that problem again.

    Unplugging from the mains powers down the board and causes a cold re-start which seems to give a 1 in 5 chance of the problem occurring, leaving plugged in seems to prevent it happening, also when it happens just unplug and re-connect seems to fix it until the next time.

    Would be interesting to hear from anyone who found a definite fix?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-01-21T21:56:28+00:00

    Sooooo did anyone ever come up with a true fix for this issue?? Because Im having the same problem!!!!!!

    Was this answer helpful?

    0 comments No comments