GPU problem

Message boards : Number crunching : GPU problem
Message board moderation

To post messages, you must log in.

AuthorMessage
Mowo

Send message
Joined: 24 Aug 00
Posts: 15
Credit: 4,004,399
RAC: 0
Germany
Message 1486175 - Posted: 8 Mar 2014, 13:29:10 UTC

Hi guys,
I am using the latest NVIDIA driver for a GTX 660Ti under Win 7 Ultimate 64bit. About a two weeks ago I switched my CPU, but everything went fine with the running SETI tasks (both Astropulse and Seti v.7). Recently, and without obvious cause (for me), both Seti@home and Astropulse stopped doing GPU work and continue only with CPU work, drastically throttling speed of course.
It is no hardware issue, as other projects use the GPU to their fullest. I tried with Einstein, Milkyway and GPUGrid.
I checked my preferences and GPU is set active. Previously, I had switched the CPU off for SETI work, reserving this for other non-CUDA projects, and running both Seti and Astropulse on GPU exclusively. This isn't working anymore as well.

Does anyone havs an idea what the cause might be and how it could be fixed?

Cheers
Thomas
ID: 1486175 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1486195 - Posted: 8 Mar 2014, 14:34:43 UTC - in response to Message 1486175.  

You haven't returned any CPU work in three weeks, make sure you haven't got the Seti project suspended,
Or all the Seti CPU tasks suspended, Boinc won't ask for work if you're done eithier.

Claggy
ID: 1486195 · Report as offensive
Mowo

Send message
Joined: 24 Aug 00
Posts: 15
Credit: 4,004,399
RAC: 0
Germany
Message 1486196 - Posted: 8 Mar 2014, 14:42:17 UTC - in response to Message 1486195.  

You haven't returned any CPU work in three weeks, make sure you haven't got the Seti project suspended,
Or all the Seti CPU tasks suspended, Boinc won't ask for work if you're done eithier.

I still have a number of regular Seti tasks unfinished in my pipeline. Some have been begun on CPU, while most are on wait and not begun at all. In order to check my issue, I halted all other projects and started Seti again, but it only started the tasks as CPU, none on GPU (GPU being idle then). The same happened to those Astropulse workunits I still had. As AP runs for ages on CPU, I cancelled all of my remaining AP WU's.
It is my goal to abandon all CPU work for Seti, and let it run exclusively on GPU. And this it won't do - but vice-versa.

Mowo
ID: 1486196 · Report as offensive
Mowo

Send message
Joined: 24 Aug 00
Posts: 15
Credit: 4,004,399
RAC: 0
Germany
Message 1486224 - Posted: 8 Mar 2014, 15:50:07 UTC

I guess the problem has been solved - and it seems to have been largely located 50cm before the screen ;)
The WU's I still had were only Seti v.7 (without nvidia/CUDA appendix). Naturally, they would run only on CPU (that was my error). I cancelled all these, and now I got CUDA versions (having switched CPU off for SETI) which work according to my wishes.

Cheers
Mowo
ID: 1486224 · Report as offensive

Message boards : Number crunching : GPU problem


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.