CPU time reportedly incorrectly

[SDRR]

This is my first post to this forum, so
be gentle. I've been crunching for OC seti
for about 4 months. I started w/screensaver
but changed to CLC after about month. Since
then I've been gradually reducing my avg time/
work unit because they were so high from using
the screensaver. Then yesterday for some reason
I had a wu that (according to seti spy log) took
571.916 CPU hours to complete. Strange, since I dl'd the wu at 12:20:39 pm and sent results in at
6:15:59 pm and I only use one machine?? Has anyone
else had this happen? Anyway to fix this?
TIA

[Basher]

Is it just the one work unit? If so did you adjust your clock? That would do that. BTW a late welcome to the team :)

[SDRR]

Thanks Basher. Yeah it's just the one unit, but I had finally boken under 7 hrs/wu and that took me back up to 8.5 hrs/wu. When you only have 348, an
extra 513 hours can really up the average.

Sorry I didn't answer your question, no I didn't change my clock. I leave my machine on 24/7 but will do a restart every 3 or 4 days when Win98 starts to act a little quirky and I did this yesterday, but it has never caused this before.

[Thelemac]

Welcome to the forums! :)

Are you sure your clock didn't accidentally get jarred or something when you restarted? I've had that problem a couple of times.

Otherwise, there's the possibility that it's just some random error or that you maybe got one of those infamous WUs that messes things up. Haven't heard of a complaint on the times like that, but I suppose it's possible.

[SDRR]

Thanks Thelemac.
I checked my clock and it's fine. Jeez, 519 hours is like 3 weeks. I hope this is just an isolated case. I'm using SetiDriver along with SetiSpy, I wonder if either of them could have caused it to happen?? Looking at my SetiSpy.log file, I don't have any double digit times, all single and one TRIPLE :eek: .

[Sir-Epix]

Originally posted by SDRR
Thanks Thelemac.
I checked my clock and it's fine. Jeez, 519 hours is like 3 weeks. I hope this is just an isolated case. I'm using SetiDriver along with SetiSpy, I wonder if either of them could have caused it to happen?? Looking at my SetiSpy.log file, I don't have any double digit times, all single and one TRIPLE :eek: .

Is it just on Seti Spy that it is reporting this or on the Berkeley pages too? I have noticed some mistakes by the servers. Like giving my team an extra 67 work units out of no where. I think that they might be having problems at their end.

[SDRR]

My computer definitely reported the 571hr wu to Berkeley because my avg CPU time/WU is up to 8.5 from just under 7 on the Seti site as well. I don't know what part of my system was at fault, be it hardware, OS, CLC, Seti Spy or Driver. I'm inclined to agree with Thelemac, that it was just a strange WU that threw my system for a loop. Thank you for your input, Sir-Epix.

[deez]

Welcome to the forum...I have also noticed this recently but only once and mine was reported as a 70.922hr WU but it only took 22 hours to complete according to log file.

I didn't think much of it since it is not on either one of my main crunchers, just thought it to be strange