Changing CPU Clock crashes SETI@home running wu's

Questions and Answers : Windows : Changing CPU Clock crashes SETI@home running wu's
Message board moderation

To post messages, you must log in.

AuthorMessage
Kurt Collins WD9IGM

Send message
Joined: 16 Dec 01
Posts: 2
Credit: 49,757
RAC: 0
United States
Message 1029558 - Posted: 29 Aug 2010, 22:39:12 UTC

I've found that changing the cpu clock (manually or automatically) while seti@home wu's are running, crashes the program & system (Windows XP SP2). Suggest turning off the auto time sync in "Internet Time", and not manually changing the clock without suspending all workunits. Anyone else run into this snag?
ID: 1029558 · Report as offensive
Profile Geek@Play
Volunteer tester
Avatar

Send message
Joined: 31 Jul 01
Posts: 2467
Credit: 86,146,931
RAC: 0
United States
Message 1029588 - Posted: 30 Aug 2010, 0:58:05 UTC
Last modified: 30 Aug 2010, 1:18:05 UTC

Changing the system time (as in changing it by a number of months) has been known to mess up the work units in the cache because they become past due or unable to finish in time. I believe this was true for even a temporary change of system time.

Windows XP, by itself, is certainly capable of withstanding time changes, manually or automatically even across time zones or daylight savings time changes. If you are seeing problems with Windows XP and time changes then perhaps a remove and re-installation of Windows XP should be done.

edit-Normal time changes for daylight savings time and off and normal time settings done via internet are not a problem for Boinc, at least on my 4 boxes.
Boinc....Boinc....Boinc....Boinc....
ID: 1029588 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1029600 - Posted: 30 Aug 2010, 4:03:54 UTC - in response to Message 1029588.  

If you are seeing problems with Windows XP and time changes then perhaps a remove and re-installation of Windows XP should be done.

Windows (any flavor) isn't responsible for keeping time on your computer, so reinstalling it won't fix major problems with time.

There are time crystals in the CMOS chip on the motherboard that keep the time, these get their power from the CMOS battery. Although this battery is recharged each time the computer is turned on, it will eventually stop recharging (just as all rechargeable batteries, it has a finite life). You then have to change the CMOS battery.

In the motherboard booklet it will state what kind of battery this is, while any computer shop or watch maker (jewelry shop) will have these batteries. Make sure that the computer is powered down, (PSU button clicked to OFF as well) before changing the battery.

This will lose all information from the BIOS, resetting it to default factory settings, so if there are any changes in there that need to be done again after changing the battery, do go in there first and write them down.

After changing the battery, power back up and change the information in the BIOS again. Then save those changes to the CMOS and boot back into Windows.
ID: 1029600 · Report as offensive
Kurt Collins WD9IGM

Send message
Joined: 16 Dec 01
Posts: 2
Credit: 49,757
RAC: 0
United States
Message 1029602 - Posted: 30 Aug 2010, 4:09:45 UTC
Last modified: 30 Aug 2010, 4:14:55 UTC

I had noticed that my system clock was off by 2 minutes - this never happens. The machine is always powered up. Resetting it caused the problem. I am running another related program called Timeleft - it basically allows a skinnable sys tray clock and other time related info. Maybe that's what crashed. Thanks for your input - Kurt
ID: 1029602 · Report as offensive
Profile Gundolf Jahn

Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 446,358
RAC: 0
Germany
Message 1029629 - Posted: 30 Aug 2010, 7:36:59 UTC - in response to Message 1029602.  

I had noticed that my system clock was off by 2 minutes -

If the system clock is changed for more than 30 seconds in the wrong direction (I never can remember which one :-), the application loses the heartbeat from the client and exits, but that usually doesn't cause the operating system to crash too.

Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours
ID: 1029629 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1029658 - Posted: 30 Aug 2010, 12:28:37 UTC - in response to Message 1029602.  


Computer Clock back stops BOINC
http://setiathome.berkeley.edu/forum_thread.php?id=45717&nowrap=true


 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1029658 · Report as offensive
Profile Geek@Play
Volunteer tester
Avatar

Send message
Joined: 31 Jul 01
Posts: 2467
Credit: 86,146,931
RAC: 0
United States
Message 1029666 - Posted: 30 Aug 2010, 13:01:56 UTC
Last modified: 30 Aug 2010, 13:02:23 UTC

But............But...............

All 4 of my boxes (and Boinc) survive a 1 hour change when daylight savings time goes on or off (foreward or backwards). No Problems ever!
Boinc....Boinc....Boinc....Boinc....
ID: 1029666 · Report as offensive

Questions and Answers : Windows : Changing CPU Clock crashes SETI@home running wu's


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.