Hi,

I've been testing CUDA capabilities in BOINC for quite some time, but after last BOINC update, I ran into some trouble. It seems that enabling CUDA in SETI causes my computer to hang-up - black screen, running but unrensponsive, ping timeout, event log ("surprisingly") empty; this happens usually at night or after a few hours my computer is left idle. This problem occured right after I updated BOINC to the newest version. I don't really know what else to mention, if any other details are necessary, please, let me know.

If anyone has any idea, how to deal with this problem (besides downgrading back to 6.4.5), I'd be more than happy for the solution.

OS: Windows Vista Business x64 SP2 CZ
GPU: nVidia GeForce 9600GT (drivers 190.62)
BOINC: 6.6.36 x64

I guess you calculated CUDA VLAR WUs.

This kind of WUs make the PC unstable.

Look at the opt. crew site and download the Win64 Lunatics Installer.
Enable Enhanced (MB) and/or AstroPulse and/or CUDA.
[http://lunatics.kwsn.net/index.php?module=Downloads;catd=9]

For ~ 30 % speed up in CUDA calculation take the 2x .dll's (CUDA_V2.3) and copy them to the setiathome.berkeley.edu folder.
[http://lunatics.kwsn.net/index.php?module=Downloads;sa=dlview;id=208]


BTW.
I don't see a GPU in your PC list overview.
What happened?

---

BTW.
If you would like to calculate simultaneously SETI@home applications on CPU and GPU you need min. BOINC V6.6.x .

---

Hi,

thank you for your response.

1) (first of all) I am surprised that version known to be causing a computer hang-up is released as "stable" branch.

2) I've installed the "tweaked" (or at least I suppose so) SETI@Home application; enabled all three choices in the installer, along with SSE4.1 as long as I have Penryn processor.

3) I've also download the modified CUDA libraries and put them into setiathome.berkeley.edu directory, as you suggested.

I will give it a try overnight now, so we will see what'll happen.

I guess you didn't see CUDA in my PC list overview, because I disabled CUDA right after I discovered that using it causes trouble.



PS: I wrote that I am using 6.6.36, so I guess I am good for with simultaneous computing :)

...
thank you for your response.

1) (first of all) I am surprised that version known to be causing a computer hang-up is released as "stable" branch.

2) I've installed the "tweaked" (or at least I suppose so) SETI@Home application; enabled all three choices in the installer, along with SSE4.1 as long as I have Penryn processor.
...

You are welcome..


Hmm.. I don't know if the stock CUDA application make PC 'hang-ups'.. but for sure the VLARs* make the PC unstable.. or very slowly.

[* I think you know that we have different ARs of WUs here at SETI@home, right? IIRC, between 0.00x and 7.x or more AR. And only this VLARs (< 0.12) make this phenomenon]

I have no knowledge about WinVista 64bit.. and the stock_CUDA_app, on my WinXP 32bit the opt._CUDA_app is running very well and since CUDA I let run only opt._CUDA_app.


It's not so easy because of the CUDA_app..
AFAIK, the nVIDIA devs made/helped the SETI@home devs for to make/publish a CUDA app. But after release and found 'BUGs' the SETI@home devs/Lunatics opt. crew must do the work alone without the help of the nVIDIA devs for to eliminate the 'BUGs'.
[own look to the problem, nothing officially]


For AstroPulse you enabled SSE3?

---

So, two days (and nights, respectivelly) have passed and my computer is still up, so it seems your suggestions have paid off. Thank you, once again. I'll bump this thread once again after ~ one week (just to be sure). Otherwise the problem is solved :).

You are welcome..


Hmm.. I don't know if the stock CUDA application make PC 'hang-ups'.. but for sure the VLARs* make the PC unstable.. or very slowly.

[* I think you know that we have different ARs of WUs here at SETI@home, right? IIRC, between 0.00x and 7.x or more AR. And only this VLARs (< 0.12) make this phenomenon]

Actually I didn't know (I just knew "heeey, SETI@Home is CUDA-capable now!"). Could you please elaborate on this a little bit (or perhaps, more likely, hit me with some link :))?

I have no knowledge about WinVista 64bit.. and the stock_CUDA_app, on my WinXP 32bit the opt._CUDA_app is running very well and since CUDA I let run only opt._CUDA_app.


It's not so easy because of the CUDA_app..
AFAIK, the nVIDIA devs made/helped the SETI@home devs for to make/publish a CUDA app. But after release and found 'BUGs' the SETI@home devs/Lunatics opt. crew must do the work alone without the help of the nVIDIA devs for to eliminate the 'BUGs'.
[own look to the problem, nothing officially]


For AstroPulse you enabled SSE3?

Regarding the AstroPulse and SSE3 - I guess so. I've set up the newest IS available on my processor. Is there a way I can check this now, after installation?

OK, after some time, the problem actually appears to be gone. Thank you for your advices once again.