Maybe this is my fault, for putting cudafft.dll in the Program Files\BOINC folder instead of in Documents and Settings\All Users\Application Data\BOINC\Projects\setiathome.berkeley.edu\
:(

I corrected that today.


http://setiathome.berkeley.edu/result.php?resultid=1312209686

Work Unit Info:
...............
WU true angle range is : 0.433577
After app init: total GPU memory 536543232 free GPU memory 205757696
Cuda error 'cudaAcc_CalcChirpData_kernel2' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_CalcChirpData.cu' in line 106 : unspecified launch failure.
CUFFT error in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_fft.cu' in line 139.


http://setiathome.berkeley.edu/result.php?resultid=1312209475

Work Unit Info:
...............
WU true angle range is : 0.415292
After app init: total GPU memory 536543232 free GPU memory 205757696
Cuda error 'cudaAcc_CalcChirpData_kernel2' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_CalcChirpData.cu' in line 106 : unspecified launch failure.
CUFFT error in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_fft.cu' in line 139.

http://setiathome.berkeley.edu/result.php?resultid=1312208701

Work Unit Info:
...............
WU true angle range is : 0.439247
After app init: total GPU memory 536543232 free GPU memory 201956608
Cuda error 'cudaAcc_CalcChirpData_kernel2' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_CalcChirpData.cu' in line 106 : unspecified launch failure.
CUFFT error in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_fft.cu' in line 139.

http://setiathome.berkeley.edu/result.php?resultid=1312208283

Work Unit Info:
...............
WU true angle range is : 0.445652
After app init: total GPU memory 536543232 free GPU memory 201956608
Cuda error 'cudaAcc_CalcChirpData_kernel2' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_CalcChirpData.cu' in line 106 : unspecified launch failure.
CUFFT error in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_fft.cu' in line 139.

---

PAul

[IMG][/IMG]

After app init: total GPU memory 536543232 free GPU memory 205757696

It seems like your videocard has too little free videomemory for CUDA-processing... Did you try a reboot and saw the next completed result after the reboot? You should find what is eating your videomemory...

For example, my Vista eats much less videomemory:

Total GPU memory 805306368 free GPU memory 691068928

Hi, from my 8500GT :Total GPU memory 536870912 free GPU memory 453632000
After app init: total GPU memory 536870912 free GPU memory 360308736


and from my 9800GTX Device 1 : GeForce 9800 GTX/9800 GTX+
totalGlobalMem = 536543232
sharedMemPerBlock = 16384
regsPerBlock = 8192
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1890000
totalConstMem = 65536
major = 1
minor = 1
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 16
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce 9800 GTX/9800 GTX+ is okay
SETI@home using CUDA accelerated device GeForce 9800 GTX/9800 GTX+
V12 modification by Raistmer
Priority of worker thread rised successfully
Priority of process adjusted successfully
Total GPU memory 536543232 free GPU memory 491839488
After app init: total GPU memory 536543232 free GPU memory 489332736

RESULT
WU

---

You seem to be running 6.6.36. This version had a problem that under certain conditions when switching CUDA tasks the old one is left in CUDA memory which is probably why you sometimes see you have less free memory than you expect. Once you hit this condition then all the following tasks fail.

The good news is this is fixed in 6.6.37 but this version is still only a test version so using it is at your own risk.

---

GPU Users Group

Thanks, I'll live with this then until 6.6.37 (or later) is released.
Optimised apps and the new CUDA libraries are making a terrific difference.

PAul

---

PAul

[IMG][/IMG]

I also noticed from your results that your are using the optimized app which includes the VLAR kill component - perhaps because you used the Lunatics unified installer?

There is a version of the app now on Lunatics which does not include the kill aspect. CudaMB V12 non-VlarKill. Will require some manual tweaking to use but I'm happy to assist if you need any help.

If you are getting a lot of errors and aborts you could run short of tasks to run.

It might be worth looking at the Reschedule tool on the Lunatics site which allows you to move the VLAR tasks to your CPU for processing rather than aborting them. [VLAR tasks run very slowly on the Graphics card]


John.

---

GPU Users Group