When you (the user) do run into Cuda specific errors, such as (e.g.):
"Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file 'c:/sw/gpgpu/seti/seti_boinc/client/cuda/cudaAcc_PowerSpectrum.cu' in line 56 : unknown error."

Could you please also post:
1. a link to the task that had the error.
2. the driver version that you are using.
3. OS type (XP/Vista) 32 or 64-bit.

This makes it easier for those of us reporting all these errors to the developers and easier for the developers to come up with a fix.

---

A further request from the developers. When you report errors, could you also please:

a) state if you overclock the GPU and if so by how much?
b) tell if you have tried to clock the GPU to default speeds and still see the problem?
c) did you set the fan speed manually to anything else than default?
d) which program(s) do you use to overclock the GPU, fan etc.?
e) which program(s) do you use to keep check of the GPU?

---

Please report errors with the stock application only in this forum. When you're using Raistmer's modified application (or that of anyone else), report about its errors in the Number Crunching forum where the modifiers/optimizers can answer you.

You can recognize if you are using Raistmer's application when you see the following in the stderr.txt output of the task:

Rise priority modification by Raistmer based on rev380 of SETI@home sources
Priority of worker thread rised successfully

The stock CUDA application (6.06) will not output this message to stderr.txt

---

Please people, show some common sense on those things you cannot do when you run Seti on the GPU are all those other things that use the GPU in full.

- If you have a dedicated gaming rig, then do not run BOINC/CUDA at the same time you are playing your game, or only run it when you aren't gaming.
- When you love to watch DVDs, do not use BOINC/CUDA at the same time. This will impact your viewing experience. (stutters, slow-downs)
- When using a screen saver, remember that the GPU is used to render the screen saver's graphics. Why not just not use a screen saver and turn off your monitor before you leave, or let it go to blank?

Seti will at all times try to use the whole GPU, in full saturation for as long as there are CUDA tasks running and waiting to run. This will have an impact on anything else you do that uses the GPU.

Ways around it?
First and foremost is to exit BOINC before you start gaming or doing your other GPU intensive thing.
BOINC Manager->File->Exit, check "stop running of science applications when exiting BOINC Manager" and click OK.
Restarting BOINC Manager will also restart the BOINC service (if you installed it that way).


Second, you can suspend BOINC before you start gaming or your other GPU intensive thing. (*)
BOINC Manager->Advanced view->Activity->Suspend.
To resume folow the same path and set it back to Run based on preferences.


Third, you can have a cc_config.xml in your BOINC Data directory that will suspend your BOINC (under Windows only, I'm afraid) automatically when any of the exclusive applications you told it to look out for is detected in main memory. (*)

To do so, set up the cc_config.xml file with the following options (example of my cc_config.xml):

<cc_config>
  <options>
     <exclusive_app>Speed.exe</exclusive_app>
     <exclusive_app>Crysis.exe</exclusive_app>
     <exclusive_app>FarCry.exe</exclusive_app>
     <exclusive_app>NFSHP2.exe</exclusive_app>
     <exclusive_app>FarCry2.exe</exclusive_app>
     <exclusive_app>Fallout3.exe</exclusive_app>
     <exclusive_app>RA3.exe</exclusive_app>
     <no_gpus>0</no_gpus>
  </options>
</cc_config> 

You only need to tell what application name it needs to look out for, no need for the full path to the name.
If you already have one, you can add the <options></options> part to your existing cc_config.xml file.

Watch out with launcher files. For example, Fallout 3 uses the Fallout 3 Launcher, which does not stay in memory after you launched the game. So do not use the launcher file as the exclusive app, but the game executable's name instead.

(*) There is a problem when you have your preferences set to Leave applications in memory while suspended.
Any task still in the video card's RAM will stay there until you resume BOINC. Although it will not use your GPU, the amount of memory that a Seti CUDA tasks takes up (200MB+ of the VRAM) may still have impact on your other activities.

After a discussion I had with the developers tonight, it looks like this behaviour is set to change with a future version of BOINC. Then upon suspension of BOINC the task will be removed from the video card's memory after it has checkpointed at least once.

---

I have put together a FAQ with some questions and answers. I will be adding to it in the coming days, but at least you can already read it, here.

Have fun.

---

Exit status 1 (0x1)
2008_x64 182.08 overclocked (only shaders ) by EVGA Precision 1.6.0 fun+
http://setiathome.berkeley.edu/result.php?resultid=1203112217
http://setiathome.berkeley.edu/result.php?resultid=1203112249
http://setiathome.berkeley.edu/result.php?resultid=1203112234
http://setiathome.berkeley.edu/result.php?resultid=1203112249
GPUGrid have no errors

Exit status 1 (0x1)
http://setiathome.berkeley.edu/result.php?resultid=1203117327
http://setiathome.berkeley.edu/result.php?resultid=1203117332
http://setiathome.berkeley.edu/result.php?resultid=1203117574

my be problem in that i have 2 GPU (but they both 9600GSO and shader =1728)

and second problem is
that when add's new task(from another project) one GPU task become USE 100% CPU core !!!
if restart boinc = OK
but until NO add's new task(from another project)

Cuda error 'cufftExecC2C' in file 'c:/sw/gpgpu/seti/seti_boinc/client/cuda/cudaAcc_fft.cu' in line 63 : unknown error.

fft stands for "Fast Fourier Transformation", AFAIK. IMHO, it's very vulnerable for overcloking. So, can You switch off overclocking and watch into results from new workunits?

---

___________
WBW, Leonid

I'm using a new intel quad, an nvidia gforce 8400 video card that works with Cuda and the latest cuda driver and winXP Rev3. and the 6.6.26.

The problem is that Cuda is not running continuously, I would think I would have four processors rotating in and out of various projects and the one Cuda sticking with all the SETI 6.08 projects. Instead it processes very well but then stops and comes back an hour later.

Maybe a settings problem?

Thanks for any help.


Stacey Baird
Davao City, Philippines

---

The welfare of the people is the highest law - Cicero

If no one complains, the people must be satisfied.

Cuda error 'cudaMemcpy(dev_cx_DataArray, cx_DataArray, NumDataPoints * sizeof(*cx_DataArray), cudaMemcpyHostToDevice)' in file 'c:/sw/gpgpu/seti/seti_boinc/client/cuda/cudaAcceleration.cu' in line 259 : unspecified launch failure.

Link to task:Error
Driver: ver.182.50
OS: Win XP SP3 32-bit

---