Ah! Thanks ... now how to read this?
<stderr_txt>
setiathome_CUDA: Found 1 CUDA device(s):
Device 1 : GeForce GT 240
totalGlobalMem = 497745920
sharedMemPerBlock = 16384
regsPerBlock = 16384
warpSize = 32
memPitch = 2147483647
maxThreadsPerBlock = 512
clockRate = 1750000
totalConstMem = 65536
major = 1
minor = 2
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 12
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce GT 240 is okay
SETI@home using CUDA accelerated device GeForce GT 240
V12 modification by Raistmer
Priority of worker thread rised successfully
Priority of process adjusted successfully
Total GPU memory 497745920 free GPU memory 477425664
setiathome_enhanced 6.02 Visual Studio/Microsoft C++
Build features: Non-graphics CUDA VLAR autokill enabled FFTW USE_SSE x86
CPUID: AMD Phenom(tm) II X6 1090T Processor
Cache: L1=64K L2=512K
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.420137
After app init: total GPU memory 497745920 free GPU memory 477425664
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x75BA22A1
Engaging BOINC Windows Runtime Debugger...
Were thise work units moved from gpu to CPU???
See this.......aborting by elapsed time limit exceeding usually marked in stderr by additional info lines. here no such info...
http://boincfaq.mundayweb.com/index.php?language=1&view=480
Also more info available when Seti forums come back online. See the forums there.
Were thise work units moved from gpu to CPU???
Ah! Thanks ... now how to read this?
<stderr_txt>
setiathome_CUDA: Found 1 CUDA device(s):
...
</stderr_txt>
<message>and a few lines above that,
- exit code -12 (0xfffffff4)
</message>
<exit_status>-12</exit_status>If you see any other number, let us know: I must say, my first instinct on reading your initial report that they happened at the exact same second was that it might be a return of the -177s, but only you can tell until the servers are back up.
See this.......
http://boincfaq.mundayweb.com/index.php?language=1&view=480
Also more info available when Seti forums come back online. See the forums there.
Were thise work units moved from gpu to CPU???
Also, have a look just a couple of lines above <stderr.txt>. If Carola's right, you should see<message>and a few lines above that,
- exit code -12 (0xfffffff4)
</message><exit_status>-12</exit_status>If you see any other number, let us know: I must say, my first instinct on reading your initial report that they happened at the exact same second was that it might be a return of the -177s, but only you can tell until the servers are back up.
My first reaction is that they are -177 since they all occured at the same instant during processing. That was also my experience with the -177 errors.
My first reaction is that they are -177 since they all occured at the same instant during processing. That was also my experience with the -177 errors.
Damn it - just found some "Computation Error" for CPU units too. 5 WUs. All at the EXACT same time.You need to be certain exactly what they are - search client_state, don't just rely on our speculation.
Is this an indication for -177 errors?
By the way: What exactly is this -177 error?
You need to be certain exactly what they are - search client_state, don't just rely on our speculation.
It will show that on web page by adding corresponding message to stderr.
You can edit/install <flops> field for this app_version.
... It would be nice if the BOINC client would show this - and not just "Computation error". Especially at times when SETI is offline.
I guess FLOPS causes the -177. After I removed FLOPS its working again. Ah those estimates ... a pain in the ass!