I ran a task for 4 days (with other projects on Boinc) for a total of 22hrs CPU time and BOINC was saying it would need to be another 9 days based on the amount of time it still needs to run, which would mean about another 24 hrs of CPU time making it 46hrs of CPU time to complete.

Is this normal?
I have no idea what the current N-Body CPU time is needed to complete them. But I find 46 hrs a bit long or 13 days on my system also to be a bit to long.

**Task was aborted**

The runtimes for n-Body WUs are very different for each WU. I've seen up to 530000 CPU seconds on my i3 running at 1,4GHz. No need to abort them.

---

I am experiencing the same issue and I have private messaged about it with no response. I am currently at more than 15 days elapsed and more than 5 days estimated time remaining. The estimated time remaining has been growing and not shrinking this entire time. I am just shy of aborting.

It has also stayed at 75.130% complete for a week or more now.

It has also stayed at 75.130% complete for a week or more now.

Than it is probably stuck. Restart your BOINC client (or the computer if that's easier) and it should continue. If the WU is over the deadline, check if the server is still waiting for your result, it the WU has been completed and validated for two other computers, you can abort it.

EDIT: is it this WU: 1717972366?
If yes, you can probably abort it (or try to be faster than the other person and get the credit if you want). In the feature, if a WU does not show any progress for few seconds, always check in the task manager if it's using CPU, if it's not, restart your BOINC client (or pause and resume the WU if you don't have the setting to keep them in memory when paused).

---