I have a WU which has been running for several days and seems to get stuck at a percentage complete.

Then I shutdown BOINC and relaunch and the accumulated work disappears and it restarts from a much lower percentage.

Rinse repeat.

The WU is crunching but with no percentage progress.

Just abort it

i had transfers stalled for weeks on a system that had "no more work" on gpugrid (board too slow). Aborting worked only until the next reboot. Only got rid by detaching and reattaching. may have been stuck for months as i rarely check that feature. maybe this was the "1" task the server status shows as ready to be sent. i finally got rid of it a few minutes ago.

Two more work units stalled which I had to abort.

Methinks there's a systemic problem managing WUs.

It seems related to running Firefox (knowing it has h/w acceleration options) -- I'm still playing woth the settings but I can get GPUGRID work units to stall simply by opening up YouTube and playing a video.

The WU percentage stops increasing but it still shows active.

After 10hours I exit BOINC and restart and the hours worked drops back down to the point where it stalled.

So it's still happening, and I can recreate the failure consistently.

I've restarted the project to refresh resources.

It seems related to running Firefox (knowing it has h/w acceleration options) -- I'm still playing woth the settings but I can get GPUGRID work units to stall simply by opening up YouTube and playing a video.

It seems related to running Firefox (knowing it has h/w acceleration options) -- I'm still playing woth the settings but I can get GPUGRID work units to stall simply by opening up YouTube and playing a video.

The WU percentage stops increasing but it still shows active.

After 10hours I exit BOINC and restart and the hours worked drops back down to the point where it stalled.

So it's still happening, and I can recreate the failure consistently.

I've restarted the project to refresh resources.

I had to roll back driver to 385.41 which is the latest driver not to have issues with Firefox browser. It is on Nvidia forums, I had driver "stopped responding and recovered" while browsing with Firefox.

Just wanted to say I had this problem too. The project stalled three times from 0 to 50%, then I reduced my GTX 970's memory clock from 3800 MHz (which never had any issues running another project, Milkyway@Home) to the default of 3500 MHz and the last 50% didn't stall. I don't know if it's just a coincidence or not.

I stopped running GPUGRID because of this, so if the admins want to know what project it was, just look at the last one I turned over.

I stopped running GPUGRID because of this, so if the admins want to know what project it was, just look at the last one I turned over.

I have seen similar stalls. Just now:

- Before suspending: 10 hr done, 10 min to go, yet 21% progress.
- After resuming: 2 hr done, 8.5 hr to go (also 21% progress)

Firefox was definitely playing YouTube, although I didn't investigate whether it was a cause.

I think my driver (391.35) just came via Windows-10 update so could be quite old now.

Can anyone confirm if later drivers resolve this? I'd prefer to go forwards rather than roll back, if possible.

I have seen similar stalls. Just now:

- Before suspending: 10 hr done, 10 min to go, yet 21% progress.
- After resuming: 2 hr done, 8.5 hr to go (also 21% progress)

Firefox was definitely playing YouTube, although I didn't investigate whether it was a cause.

I think my driver (391.35) just came via Windows-10 update so could be quite old now.

Can anyone confirm if later drivers resolve this? I'd prefer to go forwards rather than roll back, if possible.