Unknown CUDA error

Questions and Answers : GPU applications : Unknown CUDA error
Message board moderation

To post messages, you must log in.

AuthorMessage
Tuc

Send message
Joined: 6 Mar 03
Posts: 51
Credit: 3,803,470
RAC: 0
United States
Message 865491 - Posted: 14 Feb 2009, 21:41:44 UTC

Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file 'c:/sw/gpgpu/seti/seti_boinc/client/cuda/cudaAcc_PowerSpectrum.cu' in line 56 : unknown error.


1. a link to the task that had the error.

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

2. the driver version that you are using.

180.70 (Installed yesterday)

3. OS type (XP/Vista) 32 or 64-bit.

XP 32 bit


Tuc
ID: 865491 · Report as offensive
Tuc

Send message
Joined: 6 Mar 03
Posts: 51
Credit: 3,803,470
RAC: 0
United States
Message 865493 - Posted: 14 Feb 2009, 21:43:16 UTC
Last modified: 14 Feb 2009, 21:45:15 UTC

This WU errored off, with no real information:

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

The previous ones errored with the GetPowerSpectrum

This is a 180.70 driver on Windows XP 32 bit, and no futzing with the GPU/video

Tuc
ID: 865493 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 865557 - Posted: 14 Feb 2009, 23:38:26 UTC - in response to Message 865493.  

Actually, it looks like you may be using an incorrect device driver, most probably for the GPU. All your CUDA tasks go out with exit code -1073741819 (0xc0000005). This error is based on the Windows 0xc0000005 error (Access Violation)

If you had a driver before this that worked fine, go back to that one.
If you didn't do CUDA before, try using these drivers first.

When they don't fix the problem, it's probably wise to stop using CUDA for now.


ID: 865557 · Report as offensive
Tuc

Send message
Joined: 6 Mar 03
Posts: 51
Credit: 3,803,470
RAC: 0
United States
Message 865591 - Posted: 15 Feb 2009, 1:29:09 UTC - in response to Message 865557.  
Last modified: 15 Feb 2009, 1:34:09 UTC

Actually, it looks like you may be using an incorrect device driver, most probably for the GPU. All your CUDA tasks go out with exit code -1073741819 (0xc0000005). This error is based on the Windows 0xc0000005 error (Access Violation)

If you had a driver before this that worked fine, go back to that one.
If you didn't do CUDA before, try using these drivers first.

When they don't fix the problem, it's probably wise to stop using CUDA for now.


No, no driver has ever worked. The one originally loaded on the Dell Lattitude didn't work. Someone eventually pointed me to a site that allows upgrades of non-supported (By nVidia instead of Dell) cards. I put in my PCI and this 180.X was the latest, so did that. Guess I went too far. Unfortunately they don't have 179 to support my card :

http://www.laptopvideo2go.com/drivers?dev=06eb&sub=024f1028&whql=0&lang=0&orderby=version&dir=desc&os=&os[]=xp

Any other suggestions?
Thanks!

Tuc
ID: 865591 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 865641 - Posted: 15 Feb 2009, 4:00:27 UTC - in response to Message 865591.  

Any other suggestions?

You are running an NVIDIA Quadro NVS 160M? I ask, as the drivers I pointed you to in my other post are supposed to work for that version. Of course, Dell always does things differently... ;-)

But as long as the drivers you have are at least 177.35 (the absolute minimum will Seti CUDA work reliably), it should work.
ID: 865641 · Report as offensive
Tuc

Send message
Joined: 6 Mar 03
Posts: 51
Credit: 3,803,470
RAC: 0
United States
Message 865961 - Posted: 16 Feb 2009, 2:32:08 UTC - in response to Message 865641.  

Any other suggestions?

You are running an NVIDIA Quadro NVS 160M? I ask, as the drivers I pointed you to in my other post are supposed to work for that version. Of course, Dell always does things differently... ;-)

But as long as the drivers you have are at least 177.35 (the absolute minimum will Seti CUDA work reliably), it should work.

Yea, I am. The driver is supposed to work on the card, but something about it isn't suggested for Dell Latitudes (Which I have).

Ok, will try to run something 177.35 or more, less than 180.whatever.

Tuc
ID: 865961 · Report as offensive
Tuc

Send message
Joined: 6 Mar 03
Posts: 51
Credit: 3,803,470
RAC: 0
United States
Message 866363 - Posted: 17 Feb 2009, 2:59:22 UTC - in response to Message 865641.  

Any other suggestions?

You are running an NVIDIA Quadro NVS 160M? I ask, as the drivers I pointed you to in my other post are supposed to work for that version. Of course, Dell always does things differently... ;-)

But as long as the drivers you have are at least 177.35 (the absolute minimum will Seti CUDA work reliably), it should work.


:-/ For some reason trying to go to 178 isn't going well. It was simple to go to the 180. For some reason this one wants to delete the old driver first. 10 reboots later it ends up back at the original 176 version.

Grrr...

Tuc
ID: 866363 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 866457 - Posted: 17 Feb 2009, 10:24:26 UTC - in response to Message 866363.  

10 reboots later it ends up back at the original 176 version.

What does it do with the 176 driver? Will it then recognize CUDA and run work reliably?

I ask as Seti CUDA was built on the REL 175 driver (from Nvidia), so it might just be that your 176 driver will work.
ID: 866457 · Report as offensive
Tuc

Send message
Joined: 6 Mar 03
Posts: 51
Credit: 3,803,470
RAC: 0
United States
Message 866542 - Posted: 17 Feb 2009, 22:10:45 UTC - in response to Message 866457.  

10 reboots later it ends up back at the original 176 version.

What does it do with the 176 driver? Will it then recognize CUDA and run work reliably?

I ask as Seti CUDA was built on the REL 175 driver (from Nvidia), so it might just be that your 176 driver will work.

It errors and falls back to normal operation. If it processed it with my dual 6.03 processes at the same time I'd be happy, but when CUDA is running it only runs 6.08 CUDA items. I can't seem to find a WU that it did it on, or the posting I made about it.... But it just falls back to standard CPU.

If it helps, I'll turn CUDA on, reset project, run a WU, etc.

Thanks, Tuc

ID: 866542 · Report as offensive
Profile Byron S Goodgame
Volunteer tester
Avatar

Send message
Joined: 16 Jan 06
Posts: 1145
Credit: 3,936,993
RAC: 0
United States
Message 866592 - Posted: 18 Feb 2009, 0:38:08 UTC - in response to Message 866542.  

10 reboots later it ends up back at the original 176 version.

What does it do with the 176 driver? Will it then recognize CUDA and run work reliably?

I ask as Seti CUDA was built on the REL 175 driver (from Nvidia), so it might just be that your 176 driver will work.

It errors and falls back to normal operation. If it processed it with my dual 6.03 processes at the same time I'd be happy, but when CUDA is running it only runs 6.08 CUDA items. I can't seem to find a WU that it did it on, or the posting I made about it.... But it just falls back to standard CPU.

If it helps, I'll turn CUDA on, reset project, run a WU, etc.

Thanks, Tuc

When I had discussed this with Tuc earlier in another thread, he said he was using 176.xx then and was getting "Falling back to HOST CPU processing" on all the tasks he was doing at the time.
ID: 866592 · Report as offensive
Tuc

Send message
Joined: 6 Mar 03
Posts: 51
Credit: 3,803,470
RAC: 0
United States
Message 866970 - Posted: 19 Feb 2009, 2:08:07 UTC - in response to Message 866592.  

10 reboots later it ends up back at the original 176 version.

What does it do with the 176 driver? Will it then recognize CUDA and run work reliably?

I ask as Seti CUDA was built on the REL 175 driver (from Nvidia), so it might just be that your 176 driver will work.

It errors and falls back to normal operation. If it processed it with my dual 6.03 processes at the same time I'd be happy, but when CUDA is running it only runs 6.08 CUDA items. I can't seem to find a WU that it did it on, or the posting I made about it.... But it just falls back to standard CPU.

If it helps, I'll turn CUDA on, reset project, run a WU, etc.

Thanks, Tuc

When I had discussed this with Tuc earlier in another thread, he said he was using 176.xx then and was getting "Falling back to HOST CPU processing" on all the tasks he was doing at the time.


Ok, I'm not (completely) crazy. :)

So any thoughts what to do?

Thanks Folks!

Tuc
ID: 866970 · Report as offensive
Profile Byron S Goodgame
Volunteer tester
Avatar

Send message
Joined: 16 Jan 06
Posts: 1145
Credit: 3,936,993
RAC: 0
United States
Message 867197 - Posted: 19 Feb 2009, 23:17:18 UTC - in response to Message 866970.  
Last modified: 19 Feb 2009, 23:37:56 UTC

Ok, I'm not (completely) crazy. :)

So any thoughts what to do?

Thanks Folks!

Tuc

Hi,

I am not sure there is much else to try, other than maybe lowering the resolution and colour depth, (though I'm not sure that's the problem here) in an attempt to free more of the video memory. With being limited to that one DELL driver, there is not much you can do, if that driver doesn't work. Maybe in the future, the next CUDA app will work better for you.

Edit: you may be able to use one of the PRE-COMBINED PACKAGES: Windows 32 bit Multi Beam AK v8 + Astropulse_v5.0 Science Apps and get better use out of the cpu. There's an Illustrated Guide to Installing an optimised application that can assit you with it.
ID: 867197 · Report as offensive

Questions and Answers : GPU applications : Unknown CUDA error


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.