Looks like most of your hosts are 5.4.11. But This one is 5.2.11. Similar BOINC issues have been reported. It might be helpful if you could identify the specific host. BOINC manager seems to lose contact with the running threads. And seems to not detect when they end (generally with a no heartbeat indication) to schedule more tasks.

Which BOINC version are you running?

Take a look at my account, you'll see something similar. In my case, some of the computers I've installed R@H on re-image themselves every night. These computers are in labs and the imaging software wipes off any changes students make during the day. . . and it also kills the boinc install. Every day after they are reimaged, the machines have to reattach to the project. They are the same computer, but each can show up as hundreds of 'hosts' in the system.

It's not easy to get around the imaging software. . if we remove the boinc directory from the reimaging, anything installed in that folder will stay. Yes there are ways to lock it down but IT staffs can't spend a lot of time trying to make it perfect since Boinc isn't likely a high priority to their manager :)

this 1% bug, i think, is a big turnoff for a lot of people. especially the ones with "farms" and can not get to them daily. i had 3 computers at my 2nd job that got stuck for 6 days last week. i reset them saturday and now it looks like 2 of them are stuck on 1% again for the past 2 days. our team is even talking about moving on to something else because of the 1% bug and wasted cpu cycles. we really like rosetta as a whole but it seems to require a lot more monitoring than other projects. hope it is solved soon.

With all the ongoing complaints about WU errors, perhaps it would help if the project stated the total error rate they see in the database to put things into perspective. Judging from the ~2000 WUs I have crunched, I would guess that it must be considerably below 1% (one failed WU among 184 on my current results page). It might also be of interest to see how the error rate varies across different hosts/OS type/BOINC versions...

In fact, the overall error rate is pretty low. with the cpu time limit problem fixed, it appears that a relatively small fraction of users are having the majority of the wu probems--we wish we understood what was causing these!