I've 'switched off' Milky Way as a source of Tasks. I spent 1.6 million CPU seconds only for the Task to blow up 20 or so hours before the deadline. In the 'Number Crunching' Board I see plenty of concurrent references to Users with similar behaviour. But I haven't seen any explanation from Milky Way Experts.
Here's the message from the death of my exploding Task.

772937494 577749921 578820 22 Jun 2014, 3:40:43 UTC 4 Jul 2014, 0:22:43 UTC Error while computing 888,657.72 1,642,079.00 --- MilkyWay@Home N-Body Simulation [/b][/b]

I've 'switched off' Milky Way as a source of Tasks. I spent 1.6 million CPU seconds only for the Task to blow up 20 or so hours before the deadline. In the 'Number Crunching' Board I see plenty of concurrent references to Users with similar behaviour. But I haven't seen any explanation from Milky Way Experts.
Here's the message from the death of my exploding Task.

772937494 577749921 578820 22 Jun 2014, 3:40:43 UTC 4 Jul 2014, 0:22:43 UTC Error while computing 888,657.72 1,642,079.00 --- MilkyWay@Home N-Body Simulation [/b][/b]

I believe that is WAAAAAY too long for an N-Body unit to run, next time abort it and move on to the next unit. Your valid N-Body units took about 14,000 and 6,000 seconds, if you pass double the 14k number and the percentage complete isn't about 90=%, I would move on. Not EVERY unit runs on every machine, some units are just too full of things that our pc's can't figure out. Aborting them puts them back in the queue for someone else to try, as long as you don't abort hundreds of units over a short period of time it won't make a bit of difference to your crunching.

I've 'switched off' Milky Way as a source of Tasks. I spent 1.6 million CPU seconds only for the Task to blow up 20 or so hours before the deadline. In the 'Number Crunching' Board I see plenty of concurrent references to Users with similar behaviour. But I haven't seen any explanation from Milky Way Experts.
Here's the message from the death of my exploding Task.

772937494 577749921 578820 22 Jun 2014, 3:40:43 UTC 4 Jul 2014, 0:22:43 UTC Error while computing 888,657.72 1,642,079.00 --- MilkyWay@Home N-Body Simulation [/b][/b]

I believe that is WAAAAAY too long for an N-Body unit to run, next time abort it and move on to the next unit. Your valid N-Body units took about 14,000 and 6,000 seconds, if you pass double the 14k number and the percentage complete isn't about 90=%, I would move on. Not EVERY unit runs on every machine, some units are just too full of things that our pc's can't figure out. Aborting them puts them back in the queue for someone else to try, as long as you don't abort hundreds of units over a short period of time it won't make a bit of difference to your crunching.

Check the task, Mikey. Result ID 772937494

It was Exit status 196 (0xc4) EXIT_DISK_LIMIT_EXCEEDED like all the others - nothing to do with time.

Until the administrators and developers here learn how to drive their BOINC server properly, n(o)body is going to get any work done.