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
    2010-02-24T23:37:30+00:00

    Thats good to hear you got straightened out. I built my pc so i have to go through asus or newegg. and to Antikropp yes my memory is listed on their compatability list. I dont remmeber the exact model but its i have 2 - 2gb stick of gskill ram

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-02-24T12:31:40+00:00

    Rob,

    I learnt today that I have received a full refund from Mesh, having handed back my system.  I will resist saying here what I think of Mesh, but the breakthrough came when they realised that the problem manifested itself when running Windows 7; they were then able to reproduce the problem; before that they had assumed that I was talking about the Bios clock.  They would not listen to any comments regarding a motherboard problem.

    Good luck.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-02-24T09:29:38+00:00

    Could someone with these system time problems confirm that your memory is listed as supported by the motherboard? See the Asus website for this. I just want to rule out that this is not a memory related issue.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-02-23T11:21:11+00:00

    Rob, I don't think RAM has anything to do with this unless you are getting RAM errors.  The board sets it to 400Mhz by default.  I currently have my RAM overclocked to run at 1600Mhz (800Mhz in BIOS, it's DDR=1600Mhz).  I verified with CPU-ID.

    I hate to say it, but your board is probably the culprit.

    Since pulling my CMOS battery, I haven't had that problem again.  Even after shutting down. I have pulled power from my computer, so I can't comment on that and I'd rather not take the chance.

    All of that may be for nothing though, because I'm not out in the clear.  I'm having very small glitches with files.  I'll keep the story short, because I have troubleshot for countless hours taking factor after factor out of consideration.  Short story...

    I have a Western Digital HD Media Player that I play MKV files on through an external drive.  Had zero issues for 6+ months when using my old XP setup....ran flawlessly.  Built a new box with Windows 7 x64 and now every file I play "green screens" the media player.  Plays fine on the PC, because it can recover from glitches (artifacts) during the movie.....the media player can not.  Also, about 75% of my RARs that I download error out during extraction with "File is Corrupt" messages.  I don't believe in coincidences in this case.

    Through extensive troubleshooting I've discovered it's...

    Not the source of the file.

    Not the external HD.

    Not the media player.

    Not WinRAR.

    Not the USB cable used to transfer.

    My issue is that files are not correctly writing to my hard drive.  It's either my installation of 7 x64, my MoBo, my Hard Drive or a combination of those factors.  For some reason, it seems bits of data are being dropped or corrupt when writing to the Hard Drive.  I have my fingers crossed that it is the Hard Drive, that's the easy fix.  I really hope it isn't my Mobo, but I have a strong feeling it is.

    I'm currently downloading a file directly to my USB Drive.  I'm going to see if it presents any of the same errors.  If it works fine, then it's probably my Hard Drive that is the culprit.  If it doesn't work, it's probably new Motherboard time.  I'm also going to borrow a brand new SATA drive from work and kick 7 x64 on it.  I'll verify it works properly and then pop it in my box.  If the same issues are present, which weren't on the box from work, I know the Motherboard needs to go.

    Building a new box is supposed to be a fun experience.......it's been ____.

    I'd be willing to put money on the fact that most of your issues would probably go away if you had a different motherboard to test your system with.

    Was this answer helpful?

    0 comments No comments