Optimized CUDA Issues & '-12 Unknown error'


log in

Advanced search

Message boards : Number crunching : Optimized CUDA Issues & '-12 Unknown error'

1 · 2 · 3 · 4 · Next
Author Message
Profile [seti.international] Dirk Sadowski
Volunteer tester
Avatar
Send message
Joined: 6 Apr 07
Posts: 7022
Credit: 59,248,571
RAC: 20,479
Germany
Message 904386 - Posted: 6 Jun 2009, 16:30:16 UTC
Last modified: 6 Jun 2009, 16:47:12 UTC


In the old thread of Raistmer it was well to post the 'cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel - errors'.

Maybe it's well to continue?




If you would like to help the opt. crew.. please post the '-12 Unknown error'..
If you let run CUDA WUs.. look in your PC/tasks overview.. click on 'error' and look to the 'CPU time'.

If you let run Raistmer's CUDA app, the 'VLAR kill' would/could be identified with ~ 1 sec. CPU time. This results aren't for interesting.

The '-12 Unknown error' happen in the calculation of the WU, so some sec. CPU time is shown.
Then click to the Task ID and copy/paste the part of the <stderr_txt>.


It could look like this:
Exception detected inside cudaAcc_find_triplets, dumping client state
icfft=98384, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error
cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel
File: ..\analyzePoT.cpp
Line: 348

And only the [bolded] line is needed.




I found:

http://setiathome.berkeley.edu/result.php?resultid=1247662909
icfft=63129, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error

http://setiathome.berkeley.edu/result.php?resultid=1247599222
icfft=92615, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error


____________
BR



>Das Deutsche Cafe. The German Cafe.<

Profile Pappa
Volunteer tester
Avatar
Send message
Joined: 9 Jan 00
Posts: 2562
Credit: 12,301,681
RAC: 0
United States
Message 904617 - Posted: 7 Jun 2009, 1:39:13 UTC
Last modified: 7 Jun 2009, 1:40:44 UTC

A reminder, Optimized Cuda Issues are reported here or at Lunatics.kwsn.net

Stock Cuda issues are reported here Cuda Q&A

At the moment I have sticked the thread.

Regards
____________
Please consider a Donation to the Seti Project.

gejo
Send message
Joined: 28 May 99
Posts: 8
Credit: 1,606,090
RAC: 333
Netherlands
Message 905115 - Posted: 8 Jun 2009, 6:58:01 UTC

I hope this is in the right thread.

I get, on a regular basis, the following error while running CUDA:

Work Unit Info:
...............
WU true angle range is : 0.443425
Cuda error 'cudaAcc_CalcChirpData_kernel2' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcc_CalcChirpData.cu' in line 106 : unspecified launch failure.
Cuda error 'cufftExecC2C' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcc_fft.cu' in line 63 : unspecified launch failure.
Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcc_PowerSpectrum.cu' in line 56 : unspecified launch failure.
Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcc_PowerSpectrum.cu' in line 56 : unspecified launch failure.
Cuda error 'cudaAcc_summax32_kernel' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcc_summax.cu' in line 147 : unspecified launch failure.
Cuda error 'cudaAcc_summax32_kernel' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcc_summax.cu' in line 147 : unspecified launch failure.
Cuda error 'cudaMemcpy(PowerSpectrumSumMax, dev_PowerSpectrumSumMax, cudaAcc_NumDataPoints / fftlen * sizeof(*dev_PowerSpectrumSumMax), cudaMemcpyDeviceToHost)' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcc_summax.cu' in line 160 : unspecified launch failure.

Anyone any idea what could be wrong?

I used the installer from Lunatics.kwsn.net for setup.

A few work units with errors:
454791426
454791408
454675873

Profile Questor
Volunteer tester
Send message
Joined: 3 Sep 04
Posts: 362
Credit: 146,661,879
RAC: 53,790
United Kingdom
Message 905125 - Posted: 8 Jun 2009, 7:54:45 UTC - in response to Message 905115.

I hope this is in the right thread.

I get, on a regular basis, the following error while running CUDA:

cudaMemcpyDeviceToHost)' in file 'd:/BTR/SETI6/SETI_MB_CUDA/client/cuda/cudaAcc_summax.cu' in line 160 : unspecified launch failure.

Anyone any idea what could be wrong?




I have seen similar discussions about this error with no conclusions as yet. I get them myself with a Ge9600GT - same card as you but seems to happen with other cards as well.

When I have spotted these tasks before they've been reported, I have stopped BOINC, reset the task and run it again and the task runs to completion OK. So there is nothing usually wrong with the task itself. As the error relates to cudaMemcpyDeviceToHost I wondered if it was the GPU running out of memory (possibly because a number of waiting tasks still occupying memory) or some sort of memory fragmentation - the act of stopping BOINC clears the memory problem. Subsequent tasks run OK.

I have tried suspending network access and come back a few hours later and found 4 or 5 of these. I suspect if network access had been running they would just have reported and I would never have know about them.

____________
GPU Users Group



Profile gizbar
Avatar
Send message
Joined: 7 Jan 01
Posts: 586
Credit: 21,087,774
RAC: 0
United Kingdom
Message 906244 - Posted: 11 Jun 2009, 17:13:45 UTC
Last modified: 11 Jun 2009, 17:17:03 UTC

Hi guys and gals, looking for some advice, ideas, suggestions or solutions. I am running a Phenom 9850 cpu with 4Gb of ram, loads of hard disk space, and a 9800GTX+ running cuda tasks. I have installed Boinc Manager 6.6.9, and Raistmer's v9 multi pack doing MB, cuda MB and Astropulse. OS is Win XP Pro 32-bit with SP3.

My problem is that I am having cuda tasks locking up. It gets to 00.00 secs or 00.01 secs, at 0.000% and then progresses no further. There doesn't seem to be any auto-kill working and I have to abort the task manually to kill it and start a new one.

This is the last task I have just had to abort today. It's a nightmare because they freeze up while i'm at work and then it sits there doing nothing until I kill it. -- 04fe09ab.16584.19704.11.8.175_0

There doesn't seem to be any pattern to it. It does some from the series, and not others. I don't know enough about Boinc or the wu's to know how to solve this by myself.

All suggestions and solutions most welcome. Need some help here please if possible....

Or, am I just gonna have to live with it???

regards, Gizbar.
____________


A proud GPU User Server Donor!

Profile X-Files 27
Avatar
Send message
Joined: 17 May 99
Posts: 100
Credit: 107,862,964
RAC: 0
Canada
Message 906260 - Posted: 11 Jun 2009, 19:16:27 UTC

Here's the stderr_txt:


setiathome_CUDA: Found 3 CUDA device(s):
Device 1 : GeForce GTX 295
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1474875
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 30
Device 2 : GeForce GTX 260
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1500958
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 27
Device 3 : GeForce GTX 295
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1474875
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 30
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce GTX 295 is okay
SETI@home using CUDA accelerated device GeForce GTX 295
V10 modification by Raistmer
Priority of worker thread rised successfully
Priority of process adjusted successfully
Total GPU memory 939524096 free GPU memory 791842816
setiathome_enhanced 6.02 Visual Studio/Microsoft C++

Build features: Non-graphics VLAR autokill enabled FFTW x86
CPUID: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3
libboinc: 6.4.5

Work Unit Info:
...............
WU true angle range is : 0.414052
Exception detected inside cudaAcc_find_triplets, dumping client state
icfft=80754, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error
cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel
File: ..\analyzePoT.cpp
Line: 348

____________

EPG
Send message
Joined: 3 Apr 99
Posts: 110
Credit: 10,405,863
RAC: 0
Hungary
Message 906272 - Posted: 11 Jun 2009, 20:03:59 UTC - in response to Message 906244.
Last modified: 11 Jun 2009, 20:04:30 UTC

Hi guys and gals, looking for some advice, ideas, suggestions or solutions. I am running a Phenom 9850 cpu with 4Gb of ram, loads of hard disk space, and a 9800GTX+ running cuda tasks. I have installed Boinc Manager 6.6.9, and Raistmer's v9 multi pack doing MB, cuda MB and Astropulse. OS is Win XP Pro 32-bit with SP3.

My problem is that I am having cuda tasks locking up. It gets to 00.00 secs or 00.01 secs, at 0.000% and then progresses no further. There doesn't seem to be any auto-kill working and I have to abort the task manually to kill it and start a new one.

This is the last task I have just had to abort today. It's a nightmare because they freeze up while i'm at work and then it sits there doing nothing until I kill it. -- 04fe09ab.16584.19704.11.8.175_0

There doesn't seem to be any pattern to it. It does some from the series, and not others. I don't know enough about Boinc or the wu's to know how to solve this by myself.

All suggestions and solutions most welcome. Need some help here please if possible....

Or, am I just gonna have to live with it???

regards, Gizbar.


There was a lockup problem with the old CUDA dll files for a few people, that can be solved with the CUDA 2.2 dll files. The 2.2 files requries Forceware 185.85 driver. You have to put the files from the rar into
[boincdatadir]\projects\setiathome.berkeley.edu\
____________

Profile gizbar
Avatar
Send message
Joined: 7 Jan 01
Posts: 586
Credit: 21,087,774
RAC: 0
United Kingdom
Message 906380 - Posted: 12 Jun 2009, 0:56:15 UTC - in response to Message 906272.

Hi EPG, thanx for the reply. I did upgrade to forceware version 185.85, but it was causing the computer to lock up completely, and in the end had to revert back to version 181.22. Maybe this was the problem that although I upgraded the forceware version, I didn't put the new cuda 2.2 files in "[boincdatadir]\projects\setiathome.berkeley.edu\". It's late here in the UK now, nearly 2 am, so I'll live with it for tonight and tomorrow, and hopefully try to sort it when I get home from work.

Thankx for your time, and hopefully I can post back here with it sorted.

regards, Gizbar.

____________


A proud GPU User Server Donor!

EPG
Send message
Joined: 3 Apr 99
Posts: 110
Credit: 10,405,863
RAC: 0
Hungary
Message 906518 - Posted: 12 Jun 2009, 8:34:23 UTC - in response to Message 906380.

Hi EPG, thanx for the reply. I did upgrade to forceware version 185.85, but it was causing the computer to lock up completely, and in the end had to revert back to version 181.22. Maybe this was the problem that although I upgraded the forceware version, I didn't put the new cuda 2.2 files in "[boincdatadir]\projects\setiathome.berkeley.edu\". It's late here in the UK now, nearly 2 am, so I'll live with it for tonight and tomorrow, and hopefully try to sort it when I get home from work.

Thankx for your time, and hopefully I can post back here with it sorted.

regards, Gizbar.

Well, the comp. should not lock up with the new driver even without the new dll files. Does it lock up only when running Boinc or anytime? Is everything else ok with that comp.? Cooling, anti-virus...
____________

Profile X-Files 27
Avatar
Send message
Joined: 17 May 99
Posts: 100
Credit: 107,862,964
RAC: 0
Canada
Message 906683 - Posted: 12 Jun 2009, 14:38:22 UTC

Another error:


<core_client_version>6.6.36</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
setiathome_CUDA: Found 3 CUDA device(s):
Device 1 : GeForce GTX 295
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1474875
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 30
Device 2 : GeForce GTX 260
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1500958
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 27
Device 3 : GeForce GTX 295
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1474875
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 30
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce GTX 295 is okay
SETI@home using CUDA accelerated device GeForce GTX 295
V10 modification by Raistmer
Priority of worker thread rised successfully
Priority of process adjusted successfully
Total GPU memory 939524096 free GPU memory 505507840
setiathome_enhanced 6.02 Visual Studio/Microsoft C++

Build features: Non-graphics VLAR autokill enabled FFTW x86
CPUID: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3
libboinc: 6.4.5

Work Unit Info:
...............
WU true angle range is : 0.415991
Cuda error 'GetFixedPoT_kernel' in file 'd:/BTR/SETI6/SETI_MB_C


setiathome_CUDA: Found 3 CUDA device(s):
Device 1 : GeForce GTX 295
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1474875
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 30
Device 2 : GeForce GTX 260
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1500958
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 27
Device 3 : GeForce GTX 295
totalGlobalMem = 939524096
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1474875
totalConstMem = 65536
major = 1
minor = 3
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 30
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce GTX 295 is okay
SETI@home using CUDA accelerated device GeForce GTX 295
V10 modification by Raistmer
Priority of worker thread rised successfully
Priority of process adjusted successfully
Total GPU memory 939524096 free GPU memory 775258112
setiathome_enhanced 6.02 Visual Studio/Microsoft C++

Build features: Non-graphics VLAR autokill enabled FFTW x86
CPUID: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3
libboinc: 6.4.5

Work Unit Info:
...............
WU true angle range is : 0.415991
Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file 'd:/BTR/SE

____________

Profile gizbar
Avatar
Send message
Joined: 7 Jan 01
Posts: 586
Credit: 21,087,774
RAC: 0
United Kingdom
Message 906727 - Posted: 12 Jun 2009, 16:24:26 UTC - in response to Message 906518.


Well, the comp. should not lock up with the new driver even without the new dll files. Does it lock up only when running Boinc or anytime? Is everything else ok with that comp.? Cooling, anti-virus...


No lockups at all before upgrading to v185.85. Comp is overclocked from 2.5Ghz to 2.8, but temps are well within limits. I'm quite obsessive about keeping it sorted, seeing as I'm the one my friends come to, to sort out theirs when they have problems, so I need mine available. I clean it pretty regularly, virus check, spyware check every week, and it runs 24/7. All patches up to date as well. As soon as I changed back to version 181.22, the lock ups stopped. That was the only thing that had been changed. I may try it again, and see what happens.

regards, Gizbar.

____________


A proud GPU User Server Donor!

Profile [seti.international] Dirk Sadowski
Volunteer tester
Avatar
Send message
Joined: 6 Apr 07
Posts: 7022
Credit: 59,248,571
RAC: 20,479
Germany
Message 908560 - Posted: 17 Jun 2009, 23:21:11 UTC - in response to Message 904386.
Last modified: 17 Jun 2009, 23:24:37 UTC

In the old thread of Raistmer it was well to post the 'cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel - errors'.

[...]

If you would like to help the opt. crew.. please post the '-12 Unknown error'..
If you let run CUDA WUs.. look in your PC/tasks overview.. click on 'error' and look to the 'CPU time'.

If you let run Raistmer's CUDA app, the 'VLAR kill' would/could be identified with ~ 1 sec. CPU time. This results aren't for interesting.

The '-12 Unknown error' happen in the calculation of the WU, so some sec. CPU time is shown.
Then click to the Task ID and copy/paste the part of the <stderr_txt>.


It could look like this:
Exception detected inside cudaAcc_find_triplets, dumping client state
icfft=98384, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error
cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel
File: ..\analyzePoT.cpp
Line: 348

And only the [bolded] line is needed.
...


Some more:

http://setiathome.berkeley.edu/result.php?resultid=1247860143
icfft=91461, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error

http://setiathome.berkeley.edu/result.php?resultid=1251823032
icfft=66959, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error

http://setiathome.berkeley.edu/result.php?resultid=1261586993
icfft=9 (?)

____________
BR



>Das Deutsche Cafe. The German Cafe.<

Profile [seti.international] Dirk Sadowski
Volunteer tester
Avatar
Send message
Joined: 6 Apr 07
Posts: 7022
Credit: 59,248,571
RAC: 20,479
Germany
Message 909296 - Posted: 19 Jun 2009, 22:04:09 UTC - in response to Message 908560.
Last modified: 19 Jun 2009, 22:07:05 UTC

In the old thread of Raistmer it was well to post the 'cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel - errors'.
[...]
If you would like to help the opt. crew.. please post the '-12 Unknown error'..
If you let run CUDA WUs.. look in your PC/tasks overview.. click on 'error' and look to the 'CPU time'.

If you let run Raistmer's CUDA app, the 'VLAR kill' would/could be identified with ~ 1 sec. CPU time. This results aren't for interesting.

The '-12 Unknown error' happen in the calculation of the WU, so some sec. CPU time is shown.
Then click to the Task ID and copy/paste the part of the <stderr_txt>.


It could look like this:
Exception detected inside cudaAcc_find_triplets, dumping client state
icfft=98384, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error
cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel
File: ..\analyzePoT.cpp
Line: 348

And only the [bolded] line is needed.
...



One more:

http://setiathome.berkeley.edu/result.php?resultid=1267695783
icfft=41655, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error


____________
BR



>Das Deutsche Cafe. The German Cafe.<

samuel7
Volunteer tester
Send message
Joined: 2 Jan 00
Posts: 47
Credit: 2,194,240
RAC: 0
Finland
Message 910200 - Posted: 22 Jun 2009, 18:28:59 UTC
Last modified: 22 Jun 2009, 18:52:47 UTC

Here's one:
icfft=85393, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error
http://setiathome.berkeley.edu/result.php?resultid=1273107816

It's an AR=0.439437 task that ran for 933 seconds until erroring out. Normal wall clock time is about 1080 seconds on this 9800GT

Edit:
I was going to post that the other results for this wu were -9 overflows at roughly the same point of processing but maybe this was known (?).

Profile Lint trap
Send message
Joined: 30 May 03
Posts: 858
Credit: 25,807,804
RAC: 12,787
United States
Message 917043 - Posted: 12 Jul 2009, 3:56:33 UTC
Last modified: 12 Jul 2009, 3:58:01 UTC

and another one:
icfft=98692, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error

the wu is here http://setiathome.berkeley.edu/result.php?resultid=1298361430

This is with the apps supplied by the Lunatics Unified installer.

Profile TOM
Volunteer tester
Avatar
Send message
Joined: 5 Apr 01
Posts: 59
Credit: 54,930,063
RAC: 0
Germany
Message 918739 - Posted: 17 Jul 2009, 15:51:41 UTC

After installing the new Lunatics Unified Installer for Windows v0.2 i got 3 CUDA WU's, they all terminated after a few seconds. The results all looked like this:

<core_client_version>6.6.36</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
setiathome_CUDA: Found 1 CUDA device(s):
Device 1 : Quadro NVS 160M
totalGlobalMem = 268435456
sharedMemPerBlock = 16384
regsPerBlock = 8192
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1450000
totalConstMem = 65536
major = 1
minor = 1
textureAlignment = 256
deviceOverlap = 0
multiProcessorCount = 1
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: Quadro NVS 160M is okay
SETI@home using CUDA accelerated device Quadro NVS 160M
V12 modification by Raistmer
Priority of worker thread rised successfully
Priority of process adjusted successfully
Total GPU memory 268435456 free GPU memory 168546304
setiathome_enhanced 6.02 Visual Studio/Microsoft C++

Build features: Non-graphics CUDA VLAR autokill enabled FFTW USE_SSE x86
CPUID: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz

Cache: L1=64K L2=6144K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3
libboinc: 6.3.22

Work Unit Info:
...............
WU true angle range is : 0.431305
After app init: total GPU memory 268435456 free GPU memory 75223040
Cuda error 'cudaMalloc((void**) &dev_GaussFitResults' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcceleration.cu' in line 317 : out of memory.
setiathome_CUDA: CUDA runtime ERROR in device memory allocation (Step 1 of 3). Falling back to HOST CPU processing...


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x726F662F read attempt to address 0x726F662F

Engaging BOINC Windows Runtime Debugger...



********************


BOINC Windows Runtime Debugger Version 6.3.22


Dump Timestamp : 07/17/09 13:05:09
Install Directory : C:\Program Files\BOINC\
Data Directory : C:\ProgramData\BOINC
Project Symstore :
Loaded Library : C:\Program Files\BOINC\\dbghelp.dll
Loaded Library : C:\Program Files\BOINC\\symsrv.dll
Loaded Library : C:\Program Files\BOINC\\srcsrv.dll
LoadLibraryA( C:\Program Files\BOINC\\version.dll ): GetLastError = 126
Loaded Library : version.dll
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\ProgramData\BOINC\slots\2;C:\ProgramData\BOINC\projects\setiathome.berkeley.edu;srv*C:\Users\THOMAS~1\AppData\Local\Temp\symbols*http://msdl.microsoft.com/download/symbols;srv*C:\Users\THOMAS~1\AppData\Local\Temp\symbols*http://boinc.berkeley.edu/symstore


ModLoad: 00400000 00448000 C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe (6.2.0.0) (-nosymbols- Symbols Loaded)
Linked PDB Filename :
File Version : 6.02
Company Name : Space Sciences Laboratory
Product Name : setiathome_enhanced
Product Version : 6.02

ModLoad: 77520000 00127000 C:\Windows\system32\ntdll.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : ntdll.pdb
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6001.18000

ModLoad: 76ae0000 000dc000 C:\Windows\system32\kernel32.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : kernel32.pdb
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6001.18000

ModLoad: 10000000 00048000 C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\cudart.dll (6.14.11.2020) (-exported- Symbols Loaded)
Linked PDB Filename :
File Version : 6,14,11,2020
Company Name : NVIDIA Corporation
Product Name : NVIDIA CUDA 2.2 Runtime
Product Version : 6,14,11,2020

ModLoad: 00150000 00124000 C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\cufft.dll (6.14.11.2020) (-exported- Symbols Loaded)
Linked PDB Filename :
File Version : 6,14,11,2020
Company Name : NVIDIA Corporation
Product Name : NVIDIA CUDA 2.2 FFT Library
Product Version : 6,14,11,2020

ModLoad: 00bd0000 001ce000 C:\Windows\system32\nvcuda.dll (8.15.11.8603) (-exported- Symbols Loaded)
Linked PDB Filename :
File Version : 8.15.11.8603
Company Name : NVIDIA Corporation
Product Name : NVIDIA CUDA 2.2 driver
Product Version : 8.15.11.8603

ModLoad: 776e0000 0009d000 C:\Windows\system32\USER32.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : user32.pdb
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6001.18000

ModLoad: 75d90000 0004b000 C:\Windows\system32\GDI32.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : gdi32.pdb
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 6.0.6002.18005

ModLoad: 77040000 000c6000 C:\Windows\system32\ADVAPI32.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : advapi32.pdb
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6002.18005

ModLoad: 769c0000 000c3000 C:\Windows\system32\RPCRT4.dll (6.0.6002.18024) (PDB Symbols Loaded)
Linked PDB Filename : rpcrt4.pdb
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6001.18000

ModLoad: 77670000 0001e000 C:\Windows\system32\IMM32.DLL (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : imm32.pdb
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 6.0.6002.18005

ModLoad: 77170000 000c8000 C:\Windows\system32\MSCTF.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : msctf.pdb
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6000.16386

ModLoad: 76f10000 000aa000 C:\Windows\system32\msvcrt.dll (7.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : msvcrt.pdb
File Version : 7.0.6002.18005 (lh_sp2rtm.090410-1830)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 7.0.6002.18005

ModLoad: 77690000 00009000 C:\Windows\system32\LPK.DLL (6.0.6002.18051) (PDB Symbols Loaded)
Linked PDB Filename : lpk.pdb
File Version : 6.0.6002.18051 (vistasp2_gdr.090615-0258)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 6.0.6002.18051

ModLoad: 76bc0000 0007d000 C:\Windows\system32\USP10.dll (1.626.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : usp10.pdb
File Version : 1.0626.6002.18005 (lh_sp2rtm.090410-1830)
Company Name : Microsoft Corporation
Product Name : Microsoft(R) Uniscribe Unicode script processor
Product Version : 1.0626.6002.18005

ModLoad: 03a20000 000fb000 C:\Windows\system32\nvapi.dll (8.15.11.8603) (-exported- Symbols Loaded)
Linked PDB Filename : d:\bld\r185_79\drivers\nvapi\_out\win7_x86_release\nvapi.pdb
File Version : 8.15.11.8603
Company Name : NVIDIA Corporation
Product Name : NVIDIA Windows drivers
Product Version : 8.15.11.8603

ModLoad: 773d0000 00145000 C:\Windows\system32\ole32.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : ole32.pdb
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6000.16386

Get Product Name Failed.
ModLoad: 76e00000 0008d000 C:\Windows\system32\OLEAUT32.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : oleaut32.pdb
File Version : 6.0.6002.18005
Company Name : Microsoft Corporation
Product Name :
Product Version : 6.0.6002.18005

ModLoad: 77110000 00059000 C:\Windows\system32\SHLWAPI.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : shlwapi.pdb
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6000.16386

ModLoad: 75eb0000 00b10000 C:\Windows\system32\SHELL32.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : shell32.pdb
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6001.18000

ModLoad: 77240000 0018a000 C:\Windows\system32\SETUPAPI.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : setupapi.pdb
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6001.18000

ModLoad: 74fa0000 00008000 C:\Windows\system32\VERSION.dll (6.0.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : version.pdb
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 6.0.6002.18005

ModLoad: 74d10000 0019e000 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\comctl32.dll (6.10.6002.18005) (PDB Symbols Loaded)
Linked PDB Filename : comctl32.pdb
File Version : 6.10 (vista_rtm.061101-2205)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.0.6000.16386

ModLoad: 6bd20000 00115000 C:\Program Files\BOINC\dbghelp.dll (6.8.4.0) (PDB Symbols Loaded)
Linked PDB Filename : dbghelp.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 6d400000 00048000 C:\Program Files\BOINC\symsrv.dll (6.8.4.0) (PDB Symbols Loaded)
Linked PDB Filename : symsrv.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 6d3c0000 0003b000 C:\Program Files\BOINC\srcsrv.dll (6.8.4.0) (PDB Symbols Loaded)
Linked PDB Filename : srcsrv.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0



*** Dump of the Process Statistics: ***

- I/O Operations Counters -
Read: 109, Write: 0, Other 1805

- I/O Transfers Counters -
Read: 0, Write: 226, Other 0

- Paged Pool Usage -
QuotaPagedPoolUsage: 137368, QuotaPeakPagedPoolUsage: 138616
QuotaNonPagedPoolUsage: 4056, QuotaPeakNonPagedPoolUsage: 4056

- Virtual Memory Usage -
VirtualSize: 126210048, PeakVirtualSize: 134602752

- Pagefile Usage -
PagefileUsage: 55660544, PeakPagefileUsage: 63856640

- Working Set Size -
WorkingSetSize: 50913280, PeakWorkingSetSize: 59133952, PageFaultCount: 15905

*** Dump of thread ID 6292 (state: Waiting): ***

- Information -
Status: Wait Reason: UserRequest, , Kernel Time: 936006.000000, User Time: 30888198.000000, Wait Time: 4597252.000000

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x726F662F read attempt to address 0x726F662F

- Registers -
eax=06290034 ebx=ffffffff ecx=02337328 edx=02800034 esi=02800030 edi=00000000
eip=726f662f esp=0012f60c ebp=06290030
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010213

- Callstack -
ChildEBP RetAddr Args to Child
0012f608 0045eadb 02337328 02800034 02800030 06290034 !+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '726f662f'
0012f62c 00401f36 0083c1c0 02800030 06290030 00000003 MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '0045eadb'
0012f664 00519f42 004561b3 00000000 06290030 02800030 MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '00401f36'
0012f668 004561b3 00000000 06290030 02800030 00000008 MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '00519f42'
00519f42 bd7fe856 c359ffff c8680c6a e80082fe 00006cba MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '004561b3'
00519f46 c359ffff c8680c6a e80082fe 00006cba 5d89db33 MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = 'bd7fe856'
00519f4a c8680c6a e80082fe 00006cba 5d89db33 8bc033e4 MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = 'c359ffff'
00519f4e e80082fe 00006cba 5d89db33 8bc033e4 f33b0875 MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = 'c8680c6a'
00519f52 00000000 5d89db33 8bc033e4 f33b0875 3bc0950f MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = 'e80082fe'

*** Dump of thread ID 5480 (state: Waiting): ***

- Information -
Status: Wait Reason: ExecutionDelay, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 4597251.000000

- Registers -
eax=0253f880 ebx=00000000 ecx=00000005 edx=0000007c esi=0253ff48 edi=00000000
eip=77585e74 esp=0253ff04 ebp=0253ff6c
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206

- Callstack -
ChildEBP RetAddr Args to Child
0253ff00 77584780 76b29990 00000000 0253ff48 6229e653 ntdll!_KiFastSystemCallRet@0+0x0 FPO: [0,0,0]
0253ff04 76b29990 00000000 0253ff48 6229e653 00000000 ntdll!_ZwDelayExecution@8+0x0 FPO: [2,0,0]
0253ff6c 76ae1c6c 00000064 00000000 0253ff94 0045ca5b kernel32!_SleepEx@8+0x0
0253ff7c 0045ca5b 00000064 00000000 76b2d0e9 00000000 kernel32!_Sleep@4+0x0
0253ff94 775619bb 00000000 714b8049 00000000 00000000 MB_6.08_CUDA_V12_VLARKill_FPLim!+0x0
0253ffd4 7756198e 0045ca50 00000000 00000000 00000000 ntdll!___RtlUserThreadStart@8+0x0
0253ffec 00000000 0045ca50 00000000 00000000 000570e4 ntdll!__RtlUserThreadStart@8+0x0


*** Debug Message Dump ****


*** Foreground Window Data ***
Window Name :
Window Class :
Window Process ID: 0
Window Thread ID : 0

Exiting...

</stderr_txt>
]]>

any comments ?
____________

Richard Haselgrove
Volunteer tester
Send message
Joined: 4 Jul 99
Posts: 8375
Credit: 46,700,059
RAC: 19,996
United Kingdom
Message 918748 - Posted: 17 Jul 2009, 16:09:35 UTC - in response to Message 918739.

Total GPU memory 268435456 free GPU memory 168546304

any comments ?

That looks very low - Lunatics recommend 220 MB free VRAM for this release.

Reboot the machine to make sure it isn't something left over from some other graphics work, then try and reduce anything graphically-intensive which might be using memory - multiple monitors, high resolution, colour depth, Vista Aero interface, etc. etc.

Then decide (assuming it works) whether you can live with the resulting settings.

People may find this build is more suited to 512 MB video cards and above.

Jason Keil
Volunteer tester
Send message
Joined: 25 Apr 09
Posts: 35
Credit: 3,059,972
RAC: 0
United States
Message 921743 - Posted: 27 Jul 2009, 19:25:58 UTC

i just returned a -12 unknown error today.

Work Unit Info:
...............
WU true angle range is : 0.439225
After app init: total GPU memory 939524096 free GPU memory 879489024
Exception detected inside cudaAcc_find_triplets, dumping client state
icfft=147797, PoT_activity=0, PoT_freq_bin=-1SETI@home error -12 Unknown error
cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel
File: ..\analyzePoT.cpp
Line: 348

here the task number 1317692898. hope this helps.
____________

Profile Lint trap
Send message
Joined: 30 May 03
Posts: 858
Credit: 25,807,804
RAC: 12,787
United States
Message 922624 - Posted: 31 Jul 2009, 10:39:45 UTC

Another -5nnnn... error, unusual because it appears the Debugger truncated the report text.

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

Martin

Profile [seti.international] Dirk Sadowski
Volunteer tester
Avatar
Send message
Joined: 6 Apr 07
Posts: 7022
Credit: 59,248,571
RAC: 20,479
Germany
Message 922727 - Posted: 31 Jul 2009, 19:12:58 UTC - in response to Message 922624.
Last modified: 31 Jul 2009, 19:20:21 UTC

Another -5nnnn... error, unusual because it appears the Debugger truncated the report text.

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

Martin


AFAIK, - Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7C812AFB

- errors are the same like: -12 Unknown error
cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel

- errors, but the app have a little BUG in the error detection/description.

Nothing to worry about, I have a lot of this errors..


EDIT:
BTW.
I would update the nVIDIA_driver to _190.38 also would take the CUDA_V2.3 .dll's with Raistmer's new CUDA_V12_app.
Look in the CUDA area here and at the lunatics crew site.

____________
BR



>Das Deutsche Cafe. The German Cafe.<

1 · 2 · 3 · 4 · Next

Message boards : Number crunching : Optimized CUDA Issues & '-12 Unknown error'

Copyright © 2014 University of California