I am getting quite a few of these across three of my machines. The task will be sat a percentage in to its computation but will be stuck, closing and restarting boinc has no effect on this "stuck" status. I also get the occasional task that just fails to start. Anyone else come across this ?

Well I did try killing the boinc_client process and then restarting it. The stuck units were still stuck, aborting them gets the computer moving again. I will double check next time I see a stuck wu that all seti stuff is shutdown and restarted and see if that makes a difference.

Wondering if this is the AMD hang? Do you run optimized apps? the generic app from seti can cause AMD CPU's to hang. I can't remember if this is a windows problem or if it hits all OSes
____________
In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

IMHO, such stuck looks as a result of using binary, compiled from initially-working source which assumes any compilator defaults - with the other version of compilator (and other defaults).

For example, initial variant of 64-bit openSUSE kernel in the 11.3 milestone 3 works if compiled by GCC 4.4.3 and doesn't with 4.4.4 - this GCC versions used different default aligning of "struct"s, 8 and 32, coordingly.

Such tasks (endlessly looping after writing baseline smoothing into the stderr.txt), are common for the stock 6.03 application of the SETI@home Beta project with 64-bit versions of Ubuntu 9.10 and openSUSE 11.2