CUDA error

[sunu]

@Helsionium: A direct link to a beta CUDA notebook driver for 32bit vista is:

http://www.nvidia.com/object/thankyou.html?url=/compute/cuda/2_1/drivers/181.22_notebook_winvista_32bit_english_beta.exe

[END]

I suspend all MB WU at this time, running AP only.

For what you doing this
AP can't be run on GPU at all. The best you can do is to leave BOINC as it is for now and do some board readings before next move.

Raistmer, you don't understand, all his results are error results, mixed in between the vlar killed are:

<core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
�\�����~�C (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
setiathome_CUDA: Found 1 CUDA device(s):
Cuda error 'cudaGetDeviceProperties( &cDevProp, i )' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcceleration.cu' in line 135 : initialization error.

</stderr_txt>
]]>

I suggest End should first try rebooting, if no change, uninstall your graphics drivers, then reinstall them.

Claggy

I reboot my system several times and also uninstall the driver then reinstall it again, but still the same...

[Raistmer]

No GPU OCing?
Did you try another BOINC GPU-related project? Do you experience some screen distortion or other issues in games?
(in short - can you be sure your GPU hardware OK or not ?)

[tapir]

Same CUDA error start happen after new GPU driver 185.85 , CUDA v2.2 and last CUDA.exe app added
GPU slightly oced (temps are OK)

http://setiathome.berkeley.edu/result.php?resultid=1225179782
http://setiathome.berkeley.edu/result.php?resultid=1225178181
http://setiathome.berkeley.edu/result.php?resultid=1225177531
http://setiathome.berkeley.edu/result.php?resultid=1224440485
http://setiathome.berkeley.edu/result.php?resultid=1224439755

I'm running MB_6.08_mod_CUDA_V11_AffinityLock_NoPerfLog.exe on single GPU and AP on CPU with BOINC 6.2.19 on Vista SP1
Till now everything was OK.

[Raistmer]

Errors in different kernels, some reported for CUFFT library calls (actually they can be from prev app kernel call so diagnostic is harder.
Looks like some harware/driver problems...