Okay, step by step, please visit the many times mentioned Result Status page and copy the lines into a post for the work units you posted above. A line would typically look like:

dddt0101a0038_ ZINC04146649-0001_ 06_ 0-- Lapsed-01 Pending Validation 09/05/2007 07:49:47 09/11/2007 07:45:56 4.83 51.0 / 0.0

The 566.10 hours looks like a job that ran over it's time out. Did you never see that no progress was made in the Tasks Tab of BOINCmgr? On the second WU I'll reserve the response until the requested lines have been copy/pasted.

I fear you have a machine with an issue of hanging on the occasional HPF2 job. If you can isolate the machine by linking it to a specific profile (very easily created and standard called school, work, home) and deselect HPF2 in the device profile you'd not have to worry about that client. DDDT and FA@H are stable, but HPF2 has the strange looping. Closing the project and restarting usually makes it run proper. 566 hours is a pity... that's nearly 4 weeks. You might want to consider setting up BOINCview for remote monitoring.

I'll ask the techs as it was understood previously that CPU time-out was 2 weeks i.e. 296 hours and wallclock 3 weeks.

Hello KerSamson,
There is a known bug in HPF2 which causes some work units to get caught in an infinite loop. We have never been able to locate the bug because the same work unit will run fine if it is run again on the same computer. This is probably a problem with an uninitialized memory location or an out of bounds memory access. This problem can be solved by restarting the HPF2 work unit from the last check point. I think it has happened twice on my computer. I know it has happened once.

Sekerob has posted in Start Here: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=16378

Lawrence