Over the last couple of weeks I've had big problems with tasks not getting anywhere, and eventually timing out. About three-fourths of the tasks that BOINC tries to process (SETI@home_Enhanced 6.03) run, using a full CPU, but never show any progress percentage moving. The other quarter of the tasks progress as expected, and finish in a few hours. The ones which hang end up running about 4 days, and then abort themselves on a work unit timeout. I've started aborting the hung ones manually if they still show 0% progress after 30 minutes or so of CPU time. The ones that progress normally will be 10% or so after 30 minutes.

Running on WinXP SP3.

Any suggestions?

D

---

In your preferences, do you have set xx in Use at most xx percent of CPU time to less than 100%? If so, reset it to 100%. The "CPU throttling" is known to cause problems on some machines. If you get heat or response time problems when running on full load, set in your preferences On multiprocessors, use at most 1 processors (Enforced by version 5.10 and earlier) or On multiprocessors, use at most 50 % of the processors (Enforced by version 6.1+). That results in an over all usage of 50% for BOINC tasks and should prevent your computer from overheating.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

I'm having the same issue one of my 2 XP Pro SP2 machines. Astropulse work units are not affected by this, however. They always progress correclty. But a couple of times a week when I check on this one XP machine I will see it working on a couple of SETI@home work units that have accumulated a ton of CPU time but are still at 00.000% progress. I have found that if I just close BOINC and restart it, that fixes it for the affected workunits.
All of my machines are set to use 100% of CPU time and 100% of CPUs.
The affected machine is an Athlon 64 X2 3800+ with 2 GB of RAM running the 32 bit version of XP Pro SP2.

Steve

---

That's how I have it set: 100% of one cpu, out of the two on my machine.

Steve's suggestion of starting and restarting the boinc service seems to do the trick!!

D

---

That's how I have it set: 100% of one cpu, out of the two on my machine.

Steve's suggestion of starting and restarting the boinc service seems to do the trick!!

D

For you it could be the version of BOINC that you're using. 6.2.19 is the recomended version, but since Steve is using that version and his dual core is having the same problem, could be both those versions are a problem and I'm thinking maybe going back to 5.10.45 might be a better suggestion for you both.

I can't remember anyone with that version having this problem (could be wrong and maybe you've already tried 5.10.45 or someone has a heads up about this version regarding this problem) so it might be worth a try to finish up the WU's in your cache, set No New Tasks and give the 5.10.45 a shot. I've seen others that were able to restart them the way Steve suggests, but I've seen quite a few where that has become less and less effective as time goes on. Haven't seen any success stories from a detach or reset of project either, but I guess that could be an option too, unless you're ok with just stoping and restart BOINC when needed.

---

For you it could be the version of BOINC that you're using. 6.2.19 is the recomended version, but since Steve is using that version and his dual core is having the same problem, could be both those versions are a problem and I'm thinking maybe going back to 5.10.45 might be a better suggestion for you both.

It shows 6.2.19 in Help>About BOINC Manager, but on each line in the task view under "Application" it says "Seti@home Enhanced 6.03".
IOW, I guess the BOINC version is 6.2.19, but the seti@home WU processor is 6.03.
All of my computers are like this. Is this not normal?

---

It shows 6.2.19 in Help>About BOINC Manager, but on each line in the task view under "Application" it says "Seti@home Enhanced 6.03".
IOW, I guess the BOINC version is 6.2.19, but the seti@home WU processor is 6.03.
All of my computers are like this. Is this not normal?

Yes, it is normal. The BOINC manager and SETI@home are two separate applications, with different version numbers. The Astropulse application is also separate.

---

Cruiser
Gateway GT5692 L-f-S Edition
-Phenom X4 9650 CPU
-4GB 667MHz DDR2 RAM
-500GB SATA HD
-Vista x64 SP1
-BOINC 6.2.19 32-bit client
-SSE3 optimized 32-bit apps

Well, as suggested, I let the pending work units finish and then down-graded to 5.10.45. Under that version I was not able to get any work unit to advance. All WU just accumulated CPU time with no advancement in percentage complete. I tried starting and stopping the BOIC UI, the BOINC service, and rebooting the machine. No help. I went back to 6.2.19 and now I am back to the original issue. I have to start and stop BOINC frequently to get a new WU to register progress. Something else I have just had happen that makes this even worse, is that now I have an issue where one WU is advancing correctly and one is not, and restarting BOINC simply switches which one is working correctly. The one that was hung will start advancing and the one that was advacning will just accumulate CPU time with no change in progress %.

---

Well, as suggested, I let the pending work units finish and then down-graded to 5.10.45. Under that version I was not able to get any work unit to advance. All WU just accumulated CPU time with no advancement in percentage complete. I tried starting and stopping the BOIC UI, the BOINC service, and rebooting the machine. No help. I went back to 6.2.19 and now I am back to the original issue. I have to start and stop BOINC frequently to get a new WU to register progress. Something else I have just had happen that makes this even worse, is that now I have an issue where one WU is advancing correctly and one is not, and restarting BOINC simply switches which one is working correctly. The one that was hung will start advancing and the one that was advacning will just accumulate CPU time with no change in progress %.

Hi Steve, is it possible you could list your settings for processor usage regarding when computing is allowed, and disk and memory usage. Also, I'm curious what result you'd get if you set your cpu usage to one cpu

---

Well, as suggested, I let the pending work units finish and then down-graded to 5.10.45. Under that version I was not able to get any work unit to advance. All WU just accumulated CPU time with no advancement in percentage complete. I tried starting and stopping the BOIC UI, the BOINC service, and rebooting the machine. No help. I went back to 6.2.19 and now I am back to the original issue. I have to start and stop BOINC frequently to get a new WU to register progress. Something else I have just had happen that makes this even worse, is that now I have an issue where one WU is advancing correctly and one is not, and restarting BOINC simply switches which one is working correctly. The one that was hung will start advancing and the one that was advacning will just accumulate CPU time with no change in progress %.

Should also mention that in some other threads I've read, other people have had some success with similar problems by using opti apps. If it's something you'd be interested in trying for MB or AP, you should check out this message.

---