Forum > GPU crunching
Large number of Errors when processing.
			_Geordie_:
			
			I recently updated my drivers and noticed that I'm getting a large number of Cuda errors (Compute error) with the latest V12 cuda app (driver stopped).
I've taken the driver back to 190.38 but am still getting a large number of compute errors and using up the daily quota rapidly.
I'm not sure whether its hardware or software - I think my hardware is good - no overheating etc etc.
Is there any way I can diagnose?
		
			Raistmer:
			
			first of all you could post link to host under question.
		
			_Geordie_:
			
			This is the host:
http://setiathome.berkeley.edu/results.php?hostid=4672231 - I've just changed this machine back to the SETI cuda client to see if that makes a difference - I'll know in the morning. (10:30pm here)
I also have another couple of machines that I don't have immediate terminal access to that are also posting errors according to SETI.
http://setiathome.berkeley.edu/results.php?hostid=4612287
http://setiathome.berkeley.edu/results.php?hostid=4093238
Edit: Just checked and the second 2 hosts are all VLAR kills as far as I can tell - (I took a sample of around 10 units from each host from the entire list of WU's errored for each host)
		
			Pepi:
			
			You are using VLAR kill app    VLAR WU (AR: 0.059975 )detected... autokill initialized, so there is no error :) It suppose to work in that way
		
			Raistmer:
			
			no, his first host has true errors:
Work Unit Info:
...............
WU true angle range is :  2.722896
Optimal function choices:
-----------------------------------------------------
name                
-----------------------------------------------------
              v_BaseLineSmooth (no other)
            v_GetPowerSpectrum 0.00023 0.00000 
                   v_ChirpData 0.01420 0.00000 
                  v_Transpose4 0.00362 0.00000 
               FPU opt folding 0.00234 0.00000 
CUFFT error in file 'c:/sw/gpgpu/seti/seti_boinc/client/cuda/cudaAcc_fft.cu' in line 62.
</stderr_txt>
But it's stock app, not opt one.
[
most likely some problem with CUFFT libraries. Maybe incompatible driver version...
]
		
Navigation
[0] Message Index
[#] Next page
Go to full version