Here's an excerpt from the log on BOINC 6.10.19 running on fully patched Vista SP2. Note the date/time on the failed benchmark. The second benchmark was one I started manually from the BOINC client after I noticed that the first one, which was run automatically, had failed.

12/31/2009 9:28:00 AM Einstein@Home Starting task h1_1028.40_S5R4__979_S5R6a_1 using einstein_S5R6 version 301
12/31/2009 9:28:02 AM Einstein@Home Started upload of p2030_53652_85609_0108_G67.01+00.95.N_6.dm_517_0_0
12/31/2009 9:28:04 AM Einstein@Home Finished upload of p2030_53652_85609_0108_G67.01+00.95.N_6.dm_517_0_0
12/31/1999 6:00:00 PM Running CPU benchmarks
12/31/1999 6:00:00 PM Suspending computation - running CPU benchmarks
12/31/2009 10:24:33 AM [error] CPU benchmarks timed out, using default values
12/31/2009 10:24:33 AM FP benchmark ran only 0.468003 sec; ignoring
12/31/2009 10:24:33 AM FP benchmark ran only 0.967206 sec; ignoring
12/31/2009 10:24:33 AM FP benchmark ran only 0.468003 sec; ignoring
12/31/2009 10:24:33 AM FP benchmark ran only 0.982806 sec; ignoring
12/31/2009 10:24:34 AM Resuming computation
12/31/2009 10:24:40 AM Docking@Home Resuming task 3ptb_67_mod0014trypsin_55336_339340_0 using charmm34 version 623
12/31/2009 10:28:14 AM Docking@Home Starting 3ptb_67_mod0014trypsin_55334_487208_0
12/31/2009 10:28:14 AM Docking@Home Starting task 3ptb_67_mod0014trypsin_55334_487208_0 using charmm34 version 623
12/31/2009 10:44:39 AM Einstein@Home update requested by user
12/31/2009 10:44:41 AM malariacontrol.net update requested by user
12/31/2009 10:44:43 AM Einstein@Home Sending scheduler request: Requested by user.
12/31/2009 10:44:43 AM Einstein@Home Reporting 1 completed tasks, not requesting new tasks
12/31/2009 10:44:48 AM Einstein@Home Scheduler request completed
12/31/2009 10:44:53 AM malariacontrol.net Sending scheduler request: Requested by user.
12/31/2009 10:44:53 AM malariacontrol.net Reporting 3 completed tasks, not requesting new tasks
12/31/2009 10:44:58 AM malariacontrol.net Scheduler request completed
12/31/2009 10:46:44 AM malariacontrol.net Computation for task wu_65_234_266704_0_1262226614_0 finished
12/31/2009 10:46:45 AM Einstein@Home Resuming task p2030_53652_85608_0108_G67.01+00.95.N_2.dm_610_1 using einsteinbinary_ABP1 version 312
12/31/2009 10:46:47 AM malariacontrol.net Started upload of wu_65_234_266704_0_1262226614_0_0
12/31/2009 10:46:49 AM malariacontrol.net Finished upload of wu_65_234_266704_0_1262226614_0_0
12/31/2009 10:47:05 AM Running CPU benchmarks
12/31/2009 10:47:05 AM Suspending computation - running CPU benchmarks
12/31/2009 10:47:36 AM Benchmark results:
12/31/2009 10:47:36 AM Number of CPUs: 4
12/31/2009 10:47:36 AM 2347 floating point MIPS (Whetstone) per CPU
12/31/2009 10:47:36 AM 5297 integer MIPS (Dhrystone) per CPU
12/31/2009 10:47:37 AM Resuming computation

---

David Ball

Any benchmarks failing is usually contributed to your computer being busy using the CPU(s) on a higher priority application (non-BOINC). So check what was going on at that time. Else check, was Windows perhaps checking the time with the time-server at the same time?

---

The only thing running on the machine is BOINC so there shouldn't have been anything else wanting the CPU(s). I don't know how to check about the time server but maybe that was the problem. The benchmarks ran fine when I started them manually and it's been happily crunching workunits all through this. It just seemed weird, especially taking place on the last day of the year so I thought I should report it.

Thanks,

David

---

David Ball

[quoteI don't know how to check about the time server but maybe that was the problem.[/quote]
That will then show in the Windows Event Log.

---