On a system with 1070 TI and a lowly 770, I noticed a backlog of 3 gpugrid work units and the 770 was idle as milkyway had run dry. I edited the cc_config that prevented gpugrid from using 770 and rebooted. All 4 work units crashed seconds after BOINC started up. I didn't have time to suspend anything.

I have run gpugrid "longs" on 770s before, just really slow. I didn't expect this. Even the one that was 1/2 way done also died.

Anyway, I can now remove the 1070 TI from this core 2 quad and put it in my new Area51 system. No longer have to wait until the WUs finish to get started with the upgrade. They just didn't finish the way I had hoped.

So why did this happen?

So why did this happen?

I didn't know that, all I remember was I used to be able to use gtx 770, they were just slow. I missed that thread back in April about the problem.

I removed the gtx 1070 and put it into a system that had two others. Had to use liquid cooling as it was in a bad location with little air flow.


I found a new problem that was also unexpected. I switched this system from VNC to Splashtop as I need to be able to access it from out of town and that feature is part of the Splashtop package I am using.


The first time I brought up splashtop it crashed the gpugrid workunits that were on the two gtx 1070s that were connected to monitors. The one I had just added was not on a monitor and it continued running its gpugrid WU just fine. I have never seen this before and I have used Splashtop for several years. I use VNC as well to get around the 5 free pc limit.

I suspect I should have stopped BOINC from running before installing Splashtop. I assume that gpugrid "registered" for as much vram as it could and nothing was left over for Splashtop but that is just a guess.

I wonder if it would be usefull to run gpugrid with CPU=1 and GPU=0.9 or something like that. I have not have to do anything like that before and this is the first time I have seen a conflict with Splashtop and CUDA

If splashtop is like Microsoft RDP it loads a separate driver to display the remote desktop which no longer has compute capability to crunch tasks. Could be the problem. Teamviewer is fine though.

If splashtop is like Microsoft RDP it loads a separate driver to display the remote desktop which no longer has compute capability to crunch tasks. Could be the problem. Teamviewer is fine though.