About a week ago I noticed a new behaviour. My task was 'running', the elapsed time was increasing but the remaining time was just dashes and the progress wasn't changing at all even after waiting for over 5 minutes. I suspended the project and then resumed it and the progress dropped a little but then started climbing again and very quickly passed where it had stalled. This keeps happening at random intervals though the remaining time doesn't always turn to dashes. Any suggestions?

I also encountered this exact problem on one of my machines (https://www.gpugrid.net/show_host_detail.php?hostid=394201). It happened once or twice a day for several weeks and then magically stopped for some reason that I'm not aware of.

The best advice I can give you is to update windows and your GPU drivers regularly and hope that some update makes the problem go away.

I now have a task with this same problem, so I'll try suspending and resuming the project also.

http://www.gpugrid.net/result.php?resultid=16298554

Looks like BOINC Manager has decided to let GPU workunits of another BOINC project use the GPU for at least an hour, so it will take that long for the Resume to go into effect and let me see whether it worked.

About a week ago I noticed a new behaviour. My task was 'running', the elapsed time was increasing but the remaining time was just dashes and the progress wasn't changing at all even after waiting for over 5 minutes. I suspended the project and then resumed it and the progress dropped a little but then started climbing again and very quickly passed where it had stalled. This keeps happening at random intervals though the remaining time doesn't always turn to dashes. Any suggestions?

I am having this or at least a similar behavious on my two Windows10 PCs (NOT on my two Windows XP PCs).

On the first one, the progress of the task stops, and the elapsed time, too.
The GPU clock falls back to the "default clock" value of 1058MHz (GTX750ti). No idea why it is at this speed, since there is no real load on the GPU.
I then suspend the task (or the project, result is the same), and after a few minutes the GPU clock drops to 135MHz. When this happens, I push the "resume" button, and crunching starts again.

On the other PC, all starts out as described above. The GPU clock drops to default value of 1152MHz (GTX970). However, suspending the task or the project does not help. I need to reboot the system, only then crunching continues.

Since this happens only with the Windows 10 machines, but NOT with the XP machines, it's obvious that this mis-behaviour must have to do with the later crunching software and/or the later graphic driver.

I now have a task with this same problem, so I'll try suspending and resuming the project also.

http://www.gpugrid.net/result.php?resultid=16298554

It worked for me!

[snip]

Since this happens only with the Windows 10 machines, but NOT with the XP machines, it's obvious that this mis-behaviour must have to do with the later crunching software and/or the later graphic driver.

If you have GeForce Experience installed, you can use the Feedback button at the lower right of the Drivers page to send Nvidia details about the problem once you produce a repeatable cut-down version of what causes it.