The computer clock in my Windows 7 b7100 installation has been gaining about 30 seconds per day. I have tired setting the clock in Win7 to synchronize with time.windows.com and 4 different government servers. But with each set individually, the system clock never seems to be updated, and gains time every day.In the past few weeks I've tried going to this registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w32time\TimeProviders\NtpClientAnd changing the default value of 604800 for the DWORD 'SpecialPollInterval' to 86400 (1 day) and 3600 (1 hour). But the system never synchronized the time after waiting 1 day and 1 hour respectively. I have to do it manually every day with Win7's 'Date and Time' > 'Interent Time' > Change Settings' > 'Update Now'.This same system has never had any problem with synchronizing time with installations of Windows XP and Windows Vista in the past.Does anyone have any idea what may be causing this?ThanxTS

It's hard to tell if this is a new problem with the system clockor a coincidence with the addition of windows 7, if around this time the clock battery was starting to depleat cousing the quartz crystall to hyper vibrate.Or simply put, your BIOS battery could be on it's way out.

It's hard to tell if this is a new problem with the system clockor a coincidence with the addition of windows 7, if around this time the clock battery was starting to depleat cousing the quartz crystall to hyper vibrate.Or simply put, your BIOS battery could be on it's way out. That was suggested for users with the same problem in a couple other forums I've found on the web. It didn't solve the problem for them, but it is certainly a possibilty. My Asus motherboard is only a year or so old though... but again, the battery might be bad.The only other viable suggestion I've read about is MB chipset drivers. Is it possible that the existing drivers could be casuing this problem?ThnxTS

As you suggested, it may well be a windows 7 driver issue.

See if thereis an updated BIOS or chipset driver on the Asus download site.The newest chipset driver, however, is probably on the chipset manufacturer's website. See:http://www.amd.com/us-en/, http://www.nvidia.com/page/home.html, http://www.via.com.tw/en/index.jsp, or http://www.intel.com/p/en_US/support?iid=gg_work+home_support_downloads, depending on what chipset you have.

I was also going to suggest updating the bios but I reconsidered becouse it functioned properly with XP and vista althoughthat could solve it.

See if thereis an updated BIOS or chipset driver on the Asus download site.The newest chipset driver, however, is probably on the chipset manufacturer's website. See:http://www.amd.com/us-en/, http://www.nvidia.com/page/home.html, http://www.via.com.tw/en/index.jsp, or http://www.intel.com/p/en_US/support?iid=gg_work+home_support_downloads, depending on what chipset you have. The chipset drivers on the Asus website all date from 2007 for this P6LD2 motherboard:http://support.asus.com/download/download.aspx?SLanguage=en-usThe specifications in the P5LD2 manual lists the chipsetas:Northbridge Intel 945P Memory Controller (MCH)Southbridge Intel ICH7RI see 'Intel 945P Express Chipset' listed on thisIntel supportpage for the 'Intel 945 Express Chipset Family':http://www.intel.com/support/chipsets/sb/CS-020683.htmI want the 'Intel Chipset Software Installation Utility' download', not the one for 'Intel Matrix Storage Manager'.Following that download link I'm sent to a page to enter my operating system:http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=816Windows 7 is not listed, but there is one for Vista 32 dated 6/2/2008:http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=816&OSFullName=Windows+Vista+32*&lang=eng&strOSs=164&submit=Go%21The readme doesn't specifically list my chip, but seems it indicates that it's an installer for a broad range of what it lists as,'Chipset#: Intel(R) 4 Series Chipset'.I'll download that, see if it installs, and report back.Looking into my records, I see a note I made about updating the BIOS on 11-24-2007. So the CMOS battery on the board is a bit older than I thought. Checking the Asus BIOS update downloads:http://support.asus.com/download/download.aspx?SLanguage=en-usIt was the BIOS updatedated8-16-2007 that I installed.I see that the latest BIOS update addressed only one issue on 5-5-2009 whichwas to, "'Fix the USB 2.0 controller is disabled when BIOS default is loaded.'I guess I'm probably okay there.TS

Hmmm... I changed my mind about installing those drivers. I'd like tobe able to confirm that the drivers that will be installed are newer than the ones that the Windows 7 b7100 installer set up. But I've looked throughDevice Manager and can't find any references to an Intel 945P or ICH7R chipset.I don't want to end up with drivers that could potentially cause unforseen problems, and then not know how to reinstall the existing ones.Any thoughts?ThnxTS

I have seen this problem also recently with Windows 7 RC and its very confusing. The clock will be wrong even shortlyafter a resync with the Internet Time.It is not a battery problem. I have an older motherboard and there is notand never has been a BIOS update for Vista or Windows 7.I'm just waiting for the RTM. ... ...

This probably won't be helpful. Maybe interesting anyway. I have noticed with my Vista system that Event Viewer logs a time adjustment upon every bootup. Look in the Windows Logs > System folder. I recall it was recorded differently with SP1, but now with SP2 an entry exists very nearly after booting (make note of the time beforehand) thatsays:EventLog -Event ID 6013 - The system uptime is 25 seconds.Then the following event(andall beyond) have timestamps that have been incremented by that amount of seconds. Actually, one or maybe a few recorded events that appear later seem to be out-of-order. When you look closely, they correspond to exactly when the time was adjusted.I don't know what value this observation has for you. But you might spot this logged event and maybe discover it has a red-x or something?

EventLog -Event ID 6013 - The system uptime is 25 seconds.Then the following event(andall beyond) have timestamps that have been incremented by that amount of seconds. Actually, one or maybe a few recorded events that appear later seem to be out-of-order. When you look closely, they correspond to exactly when the time was adjusted.I don't know what value this observation has for you. But you might spot this logged event and maybe discover it has a red-x or something? I rebooted the system, had a look in the Event Viewer, andfound the entry: * 'EventLog -Event ID 6013 - The system uptime is53 seconds.' But although there three error entries during the time the system booted that show failures to load ASPI, Windows Image Acquisition (WIA), and PxHelp20 that seems to be CD-ROM related... I see no other entries that seem to berelated to time synchronization.

I don't know if I'm sending you on a wild goose chase, but that seems awfully long to me, 53 seconds. That's the uptime before Windows really starts doing anything, like starting services. Note that timestamp, then examine other logs to see what it's doing at that time. Even then, unless something screams out, I don't know how that relates or will help fix the time error you are seeing after bootup.Out of curiosity, did you find that the entry following Event ID 6013 had a timestamp that was 53 seconds (or so) later, as though it was adjusted?

I don't know if I'm sending you on a wild goose chase, but that seems awfully long to me, 53 seconds. That's the uptime before Windows really starts doing anything, like starting services.. I had just installed several Windows Updates before I rebooted the system and checked entries in the Events Viewer. Looking at past Event ID 6013 reports, the average system uptime isin fact reported as being between 20 and 23 seconds. Out of curiosity, did you find that the entry following Event ID 6013 had a timestamp that was 53 seconds (or so) later, as though it was adjusted? I went back and lookedat all Event ID 6013 entries forthe pastweek, and found that all of the entries that followed it had the exact same timestamp.Does anyone know if thereshould bean entry in the Event Viewer that might report an error when Windows attempts to synchronize the system clock to a web time server? There might be some useful information there. Butnone ofthe entries in Event Viewer> Windows Logs > System going back an entire week show an error for any kind of time service event.

Look for a Time-ServiceWarning 134such as: NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)

Look for a Time-ServiceWarning 134such as: By sorting the list bythe Event ID field, I found4 ID 134 'Time Service' entries that sayNtpClient will try again in 3473457 minutes:"NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on ''. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The requested name is valid, but no data of the requested type was found. (0x80072AFC)"2 of them have a timestamp dated today. They're in 2 of about 6 sets of entries that were made when I rebooted the system 6 different times to perform a few tests.The other 2 are dated 6/29/2009 in a couple sets of entries whenthe system was rebooted that day.3473457 minutes is 40.2 days. That's radically different from what you, bnborg, reported as 15 minutes. That sounds awfully long to be right.

You could try stopping and starting the Time Service.It can be done with services.msc or from a command prompt:sc stop w32timesc start w32timeI don't know if this will reset it, however.You could also play with configuring it with w32tm.exe, from a command prompt.Enter w32tm /? for syntax. It seems complicated.

I googled and found this thread which basically says the chipset drivers are incompatible and interfere with the normal operation of hibernation which interrupts thetime service and by updating the chipset driver the issue would be resolved butI'm not sureif this applies to your situation.http://social.answers.microsoft.com/Forums/en-US/GettingReadyforWindows7/thread/4f351840-079a-46e0-a993-68e33f5a8fdc

I finally found a solution for this problem. In a thread on the Windows Seven Forums here, I found this post:"It seems Windows 7 installs the time service set to start automatically, which in some cases it does not start automatically and windows won't update with a time server on the net. Just change the service to automatic/delayed start and reboot to test if service is actually running... remember to give it a minute to start."Go to: Control Panel > System and Security > Administrative Tools > ServicesClick the 'Standard' tab in the right frame, scrolldown to 'Windows Time' and double click the option to access settings. On the 'General' tab in the popup window, find 'Startup type' and set it to 'Automatic (Delayed Start)'. If it's not already started, click the 'Start' button in the 'Service Status' area.TS