| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 33
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
All depends on how busy the system is. If I would GPU crunch during use, the driver would just crash altogether and constantly on W7/W8. Maybe if you set the default back to only GPU compute when system is not in use [set a delay of e.g. 5 minutes], the test will pass and the task runs to an end.
Do disable the BOINC screensaver, set to blank with password, as the SS would compete for cycles with the GPU task. |
||
|
|
jkislenko
Advanced Cruncher Czech Republic Joined: Mar 29, 2007 Post Count: 62 Status: Offline Project Badges:
|
Thanks for help. I just returned a unit with time 34:34 and another on the way looks just fine. It looks like problem is really in GPU cycles dedicated for these units.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If you have multiple machines, use BOINC Manager or BOINCTasks or the new boinctui [text only], to monitor the GPU crunching machine from remote. This way, if you GPU crunch when crunching machine is not in use, you can monitor progress. I'm watching everything from a laptop with BT, which also stops from the GPU task unloading from memory when interrupted.
|
||
|
|
|