I have the same problem. I have a Windows XP Home, 3.4Gh HT, Memory 2.5 Gb and disk space of 1 Tb. I am not on a server, I am a single user. I run only S@H. As suggested, I set the CPU to 100%. I have not used the threading utility. For me, I am not sure it really is necessary.

I do not need to repeat all the details said in this thread. I, too get message of "Restarting Task...". I have yet to complete one unit of work for S@H in quite some time. I would like to continue, but many days, weeks or whatever of procesing time have been wasted.

I need help. I request a reply from SETI. I may need to give up processing seti.

Thanks.

Hi,Could you please try what John McLeod VII suggested here:

http://setiathome.berkeley.edu/forum_thread.php?id=42429&nowrap=true#657124

Let me know if you would like the file I created and used.

Please post a portion of the message file that is created so we may have a better idea of what is happening. Are you running any custom SETI apps? What version of Boinc are you running? Have you recently installed any new or updated your antivirus software?

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

I have the same problem. I have a Windows XP Home, 3.4Gh HT, Memory 2.5 Gb and disk space of 1 Tb. I am not on a server, I am a single user. I run only S@H. As suggested, I set the CPU to 100%. I have not used the threading utility. For me, I am not sure it really is necessary.

I do not need to repeat all the details said in this thread. I, too get message of "Restarting Task...". I have yet to complete one unit of work for S@H in quite some time. I would like to continue, but many days, weeks or whatever of procesing time have been wasted.

I need help. I request a reply from SETI. I may need to give up processing seti.

Thanks.

---

I have this same problem and problem resolved after I set the CPU usage to 100%. This CPU throttleing seems to impact SETI only as I have no problem with ClimatePrediction on the same machine.

Hey OmegaDVD.. Does setting your CPU usage to 100% fix your problem too?

Just curious..

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

The lag might have something to do with SQL or something else.

Ah, SQL. I've heard of some intermittent lag problems when using BOINC on a machine that also uses SQL. I believe the SQL service also runs at a low priority causing a slight delay when the OS has to "decide" who to give the low priority CPU time to.

We don't run SQL so it's not an issue. Many companies do, so I suppose in the same vain I would limit BOINC too.

---

Unfortunately, response times are affected.

I am really surprised to hear this. My own tests have shown that response time is affected in the microseconds range and thus not enough to really worry about. I work as an IT Admin at an Intermediate Care facility for the Mentally Ill and I have BOINC on their machines (with proper permission from the General Manager) without any lag.

In this industry I have learned to not let anything really surprise me.

The lag might have something to do with SQL or something else. The lag was expected when I originally installed the science app. and thus is not a big deal. It just gets to be a bit of a pain when people start complaining, I turn off the app. and then everything starts working ok again.

Anyways, to each their own...

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

Unfortunately, response times are affected.

I am really surprised to hear this. My own tests have shown that response time is affected in the microseconds range and thus not enough to really worry about. I work as an IT Admin at an Intermediate Care facility for the Mentally Ill and I have BOINC on their machines (with proper permission from the General Manager) without any lag.

Typical applications range from MS Works, Office, a special DB program for record keeping on the Residents, AntiVirus software, backup programs, Print Shop Deluxe (for the Activities Department), my own custom batch scripts and a web browser (they are not allowed to browse the web, but State Department reports must be filed consistently directly to the State Department of Public Health using a secure web interface).

---

None of my desktops are having trouble running at 100%. I have a couple of P4s and Athlons that I am throttleing just to increase the responsivness when using office apps and internet etc. Otherwise the employees might start complaining. Being the boss, I really don't have time to listen to it..:)

The science app runs at the lowest priority, giving all standard apps CPU time over itself. There should be no slowdown in the response time of the computer. You should try it an a few machines to see for yourself.

Actually, I have tried it and that is why the throttleing is a
must have. In theory it is a great concept to have the science app run at the lowest priority thus giving everything else the higher priority and minimizing response times. Unfortunately, response times are affected. I have found that a throttle set at ~75% has provided the best response times. Of course I don't pay attention to milliseconds or microseconds but ultimately how often I get called into the users office for unexplainable application lag etc.

Thanks for the input.

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

None of my desktops are having trouble running at 100%. I have a couple of P4s and Athlons that I am throttleing just to increase the responsivness when using office apps and internet etc. Otherwise the employees might start complaining. Being the boss, I really don't have time to listen to it..:)

The science app runs at the lowest priority, giving all standard apps CPU time over itself. There should be no slowdown in the response time of the computer. You should try it an a few machines to see for yourself.

---

Thanks for all the great help.

When I used to crunch on a regular basis, Threadmaster was the way to go if one wanted to limit the cpu usage. Setting it up was always simple though as I always set the maximum cpu usage of any app to 75% and also set the threashhold for 30 seconds. So if any app asked for more than 75% of the cpu for more than 30 seconds it automatically got throttled. Worked great.

None of my desktops are having trouble running at 100%. I have a couple of P4s and Athlons that I am throttleing just to increase the responsivness when using office apps and internet etc. Otherwise the employees might start complaining. Being the boss, I really don't have time to listen to it..:)

I can't beleive how fast this C2D and C2Q are crunching.. holy crapola..

Thanks again.

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

OK.. so that seems to have cleared it up. Any idea as to why the throttleing seems to be a function of time instead of power? Or why these Duo and Quad CPUs do not like the throttleing? Should I use Threadmaster to throttle instead of the built in method?

TIA

Throttling is based on time as that is all that we have available on all platforms. It is also checked once per second to see if you have gone over the % that you requested. This leads to patterns such as 80% being 4 seconds on and one off and 90% being 9 seconds and one off. This is not normally a problem, but if you have applications set to be evicted from memory when they are not running, it is a bit of a problem with some versions of BOINC (I am not certain when or if this was fixed.). Thread master does finer grain, BUT, it is apparently a royal pain to set up and it requires a new setup for each new version of a science application.

Almost all desktop machines and most laptops do quite well at 100% usage. Most machines are still responsive as BOINC runs the science at a priority just barely above idle.

A very few desktops have trouble running at 100%. These are almost all either clogged with dust, badly designed (poor airflow), or overclocked. Many laptops trade cooling capabilities for small size and light weight. Since laptops have to compromise on something, I will not call this bad design. They also have the same problems with dust bunnies and overclocking though.

---

BOINC WIKI

OK.. so that seems to have cleared it up. Any idea as to why the throttleing seems to be a function of time instead of power? Or why these Duo and Quad CPUs do not like the throttleing? Should I use Threadmaster to throttle instead of the built in method?

TIA

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

WOW.. This Q6600 is pumping out the packets now.. :) I have to assume that the problem is with the CPU throttleing. Since I set the CPU usage to 100%, Boinc has not crapped out. I will continue monitoring and update again tomorrow.

Thanks

That would look like it.

---

BOINC WIKI

WOW.. This Q6600 is pumping out the packets now.. :) I have to assume that the problem is with the CPU throttleing. Since I set the CPU usage to 100%, Boinc has not crapped out. I will continue monitoring and update again tomorrow.

Thanks

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

Here is the first bit...





10/9/2007 9:28:34 PM|SETI@home|[cpu_sched] Preempting 08mr07aa.8174.13160.3.6.166_1 (left in memory)
10/9/2007 9:28:34 PM|SETI@home|[cpu_sched] Preempting 07mr07am.7244.10297.16.6.123_0 (left in memory)
10/9/2007 9:28:34 PM|SETI@home|[cpu_sched] Preempting 08mr07aa.12092.3344.5.6.139_1 (left in memory)
10/9/2007 9:28:34 PM|SETI@home|[cpu_sched] Preempting 08mr07aa.12092.3344.5.6.151_1 (left in memory)
10/9/2007 9:28:35 PM||[cpu_sched] Resuming - CPU throttle
10/9/2007 9:28:35 PM|SETI@home|[cpu_sched] Resuming 08mr07aa.8174.13160.3.6.166_1
10/9/2007 9:28:35 PM|SETI@home|[cpu_sched] Resuming 07mr07am.7244.10297.16.6.123_0
10/9/2007 9:28:35 PM|SETI@home|[cpu_sched] Resuming 08mr07aa.12092.3344.5.6.139_1
10/9/2007 9:28:35 PM|SETI@home|[cpu_sched] Resuming 08mr07aa.12092.3344.5.6.151_1
10/9/2007 9:28:36 PM||[cpu_sched] Suspending - CPU throttle
10/9/2007 9:28:36 PM|SETI@home|[cpu_sched] Preempting 08mr07aa.8174.13160.3.6.166_1 (left in memory)
10/9/2007 9:28:36 PM|SETI@home|[cpu_sched] Preempting 07mr07am.7244.10297.16.6.123_0 (left in memory)
10/9/2007 9:28:36 PM|SETI@home|[cpu_sched] Preempting 08mr07aa.12092.3344.5.6.139_1 (left in memory)
10/9/2007 9:28:36 PM|SETI@home|[cpu_sched] Preempting 08mr07aa.12092.3344.5.6.151_1 (left in memory)
10/9/2007 9:28:37 PM||General prefs: from SETI@home (last modified 2007-10-09 19:53:31)
10/9/2007 9:28:37 PM||Host location: home
10/9/2007 9:28:37 PM||General prefs: no separate prefs for home; using your defaults
10/9/2007 9:28:37 PM||Reading preferences override file
10/9/2007 9:28:37 PM||Preferences limit memory usage when active to 1023.55MB
10/9/2007 9:28:37 PM||Preferences limit memory usage when idle to 1842.39MB
10/9/2007 9:28:37 PM||Preferences limit disk usage to 4.66GB
10/9/2007 9:28:37 PM||[cpu_sched] Resuming - CPU throttle
10/9/2007 9:28:37 PM|SETI@home|[cpu_sched] Resuming 08mr07aa.8174.13160.3.6.166_1
10/9/2007 9:28:37 PM|SETI@home|[cpu_sched] Resuming 07mr07am.7244.10297.16.6.123_0
10/9/2007 9:28:37 PM|SETI@home|[cpu_sched] Resuming 08mr07aa.12092.3344.5.6.139_1
10/9/2007 9:28:37 PM|SETI@home|[cpu_sched] Resuming 08mr07aa.12092.3344.5.6.151_1
10/9/2007 9:33:31 PM|SETI@home|[task_debug] result 08mr07aa.8174.13160.3.6.166_1 checkpointed
10/9/2007 9:33:31 PM|SETI@home|[task_debug] result 07mr07am.7244.10297.16.6.123_0 checkpointed
10/9/2007 9:33:31 PM|SETI@home|[task_debug] result 08mr07aa.12092.3344.5.6.139_1 checkpointed
10/9/2007 9:33:31 PM|SETI@home|[task_debug] result 08mr07aa.12092.3344.5.6.151_1 checkpointed
10/9/2007 9:34:01 PM|SETI@home|[task_debug] result 08mr07aa.8174.13160.3.6.166_1 checkpointed

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

Thanks, I will try to figure that out asap..

OK.. I have the config file loaded and collecting data. I reset the CPU throttle to 100% so that I could avoid a huge log file with the constant stopping and starting. If the issues go away then I suppose that was the problem. I certainly hope not.. Anyways, I will post the messages soon.

Thanks for the help.

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

Have we found a fix yet? Same problem.. constantly restarting... My C2D E6850 does not exibit the same problem.. I am only working on Seti.. no other projects.

C2Q 6600 / 2GB RAM Client: 5.10.20

Please help..


10/9/2007 3:48:22 PM|SETI@home|Restarting task 07mr07am.7244.10297.16.6.123_0 using setiathome_enhanced version 527
10/9/2007 3:51:55 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 3:59:00 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 4:00:59 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 4:10:34 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 4:15:11 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 4:21:13 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 4:23:41 PM|SETI@home|Restarting task 07mr07am.7244.10297.16.6.123_0 using setiathome_enhanced version 527
10/9/2007 4:34:46 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 4:44:51 PM|SETI@home|Restarting task 07mr07am.7244.10297.16.6.123_0 using setiathome_enhanced version 527
10/9/2007 4:44:58 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 4:51:21 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 4:51:56 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 4:55:48 PM||General prefs: from SETI@home (last modified 2007-10-06 16:26:55)
10/9/2007 4:55:48 PM||Host location: home
10/9/2007 4:55:48 PM||General prefs: no separate prefs for home; using your defaults
10/9/2007 4:55:48 PM||Preferences limit memory usage when active to 1023.55MB
10/9/2007 4:55:48 PM||Preferences limit memory usage when idle to 1842.39MB
10/9/2007 4:55:48 PM||Preferences limit disk usage to 4.66GB
10/9/2007 4:56:15 PM|SETI@home|Sending scheduler request: Requested by user
10/9/2007 4:56:15 PM|SETI@home|(not requesting new work or reporting completed tasks)
10/9/2007 4:56:21 PM|SETI@home|Scheduler RPC succeeded [server version 511]
10/9/2007 4:56:21 PM|SETI@home|Deferring communication for 11 sec
10/9/2007 4:56:21 PM|SETI@home|Reason: requested by project
10/9/2007 4:56:54 PM||General prefs: from SETI@home (last modified 2007-10-06 16:26:55)
10/9/2007 4:56:54 PM||Host location: home
10/9/2007 4:56:54 PM||General prefs: no separate prefs for home; using your defaults
10/9/2007 4:56:54 PM||Reading preferences override file
10/9/2007 4:56:54 PM||Preferences limit memory usage when active to 1023.55MB
10/9/2007 4:56:54 PM||Preferences limit memory usage when idle to 1842.39MB
10/9/2007 4:56:54 PM||Preferences limit disk usage to 4.66GB
10/9/2007 5:03:12 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 5:07:06 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 5:11:36 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 5:12:46 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 5:16:10 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 5:18:18 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 5:25:45 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 5:32:21 PM|SETI@home|Restarting task 07mr07am.7244.10297.16.6.123_0 using setiathome_enhanced version 527
10/9/2007 5:34:49 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 5:39:20 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 5:43:28 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 5:47:23 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 5:47:30 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527

Could you create a cc_config.xml file. Instructions are here.. Please include the <task>, <task_debug>, <file_xfer>, <sched_ops>, <cpu_sched>, and <sched_op_debug> flags. You will have to load cc_config after you create it. This can be done either by restarting BOINC, or from the Advanced View -> Advanced menu -> load cc_config (I have never actually tested the second). You should get a great deal more information, and maybe we can figure out what is happening.

---

BOINC WIKI

Have we found a fix yet? Same problem.. constantly restarting... My C2D E6850 does not exibit the same problem.. I am only working on Seti.. no other projects.

C2Q 6600 / 2GB RAM Client: 5.10.20

Please help..


10/9/2007 3:48:22 PM|SETI@home|Restarting task 07mr07am.7244.10297.16.6.123_0 using setiathome_enhanced version 527
10/9/2007 3:51:55 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 3:59:00 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 4:00:59 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 4:10:34 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 4:15:11 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 4:21:13 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 4:23:41 PM|SETI@home|Restarting task 07mr07am.7244.10297.16.6.123_0 using setiathome_enhanced version 527
10/9/2007 4:34:46 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 4:44:51 PM|SETI@home|Restarting task 07mr07am.7244.10297.16.6.123_0 using setiathome_enhanced version 527
10/9/2007 4:44:58 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 4:51:21 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 4:51:56 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 4:55:48 PM||General prefs: from SETI@home (last modified 2007-10-06 16:26:55)
10/9/2007 4:55:48 PM||Host location: home
10/9/2007 4:55:48 PM||General prefs: no separate prefs for home; using your defaults
10/9/2007 4:55:48 PM||Preferences limit memory usage when active to 1023.55MB
10/9/2007 4:55:48 PM||Preferences limit memory usage when idle to 1842.39MB
10/9/2007 4:55:48 PM||Preferences limit disk usage to 4.66GB
10/9/2007 4:56:15 PM|SETI@home|Sending scheduler request: Requested by user
10/9/2007 4:56:15 PM|SETI@home|(not requesting new work or reporting completed tasks)
10/9/2007 4:56:21 PM|SETI@home|Scheduler RPC succeeded [server version 511]
10/9/2007 4:56:21 PM|SETI@home|Deferring communication for 11 sec
10/9/2007 4:56:21 PM|SETI@home|Reason: requested by project
10/9/2007 4:56:54 PM||General prefs: from SETI@home (last modified 2007-10-06 16:26:55)
10/9/2007 4:56:54 PM||Host location: home
10/9/2007 4:56:54 PM||General prefs: no separate prefs for home; using your defaults
10/9/2007 4:56:54 PM||Reading preferences override file
10/9/2007 4:56:54 PM||Preferences limit memory usage when active to 1023.55MB
10/9/2007 4:56:54 PM||Preferences limit memory usage when idle to 1842.39MB
10/9/2007 4:56:54 PM||Preferences limit disk usage to 4.66GB
10/9/2007 5:03:12 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 5:07:06 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 5:11:36 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 5:12:46 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 5:16:10 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 5:18:18 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 5:25:45 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 5:32:21 PM|SETI@home|Restarting task 07mr07am.7244.10297.16.6.123_0 using setiathome_enhanced version 527
10/9/2007 5:34:49 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 5:39:20 PM|SETI@home|Restarting task 08mr07aa.8174.13160.3.6.166_1 using setiathome_enhanced version 527
10/9/2007 5:43:28 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527
10/9/2007 5:47:23 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.151_1 using setiathome_enhanced version 527
10/9/2007 5:47:30 PM|SETI@home|Restarting task 08mr07aa.12092.3344.5.6.139_1 using setiathome_enhanced version 527

---

Boinc Wiki




"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein

While I did not have the message timeouts however he even had yet again the very same CPU (x86 Family 15 Model 2 Pentium 4 HT Northwood core) and also this very same problem along with the timeouts on top of that and everyone that replyed asked is it a hyperthreading cpu or a duel core cpu. I myself managed to fix my same problem simply by suspending the secound task as bionic starts more than one at a time. I asssume it thinks that these are 2 completly separate CPU's as for duel core there maybe other issues due to multiple cores on the same die and due to some shared resources and possible other things I have not thought of after suspending the 2nd task the one remaining hit 30% and has kept going ever sense.

I don't think it's a HT or Dual Core issue, since BOINC doesn't care which is which (BOINC simply asks the OS how many CPUs are installed [and Windows treats HT, dual core and dual socket systems all the same] and then launches a science app for every CPU in the system up to the user's preference).

I have three Pentium 4 HTs and one Pentium D, one Core 2 Duo and two Athlon 64 X2 CPUs and none of them exhibit this problem. If BOINC inded didn't support HT or dual core CPUs properly, then logically it would manifest itself on my systems as well.

---

Jakob Creutzfeld and to anyone else who may find it usefull this is not related to a memory limit problem as when the memory limit has been reached all it does is auto suspend and the following meaaaage in the status appears "Waiting for memory" it does not or is not supposed to restart that task to 0% or download a new task first things first however. The memory limit is boinic alone if you have win xp or higher look at you task manager when its running you may need to activate the following mem usage, peak memusage, and vmem useage. Secound if you read the entire thread the guy who started it had the same problem with the same cpu also there are other threads here and over the net with the same thing please also read this tread.

http://setiweb.ssl.berkeley.edu/forum_thread.php?id=40117

While I did not have the message timeouts however he even had yet again the very same CPU (x86 Family 15 Model 2 Pentium 4 HT Northwood core) and also this very same problem along with the timeouts on top of that and everyone that replyed asked is it a hyperthreading cpu or a duel core cpu. I myself managed to fix my same problem simply by suspending the secound task as bionic starts more than one at a time. I asssume it thinks that these are 2 completly separate CPU's as for duel core there maybe other issues due to multiple cores on the same die and due to some shared resources and possible other things I have not thought of after suspending the 2nd task the one remaining hit 30% and has kept going ever sense.

Before anyone will say is there something wrong with your computer my answer is no why you ask well I run just about every diag you can think of often why because this is my professsional prduction system it is my businessss computer.

(Here is just a few test I run often with all test selected)
syssoft sandra =ok
Prime95 48Hour test =ok
memtest86 48Hour test=ok
pcmark =ok
aquamark =ok

---