Forum > GPU crunching
Some questions about vlar kill
Raistmer:
This your result because of VLAR-kill:
http://setiathome.berkeley.edu/result.php?resultid=1239075202
<core_client_version>6.6.28</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.011061 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
All other errors - not.
BMaytum:
Thanks for reply Raistmer. I now understand that exit Code -6 results from Vlar Kill code.
Admittedly, when I saw a rapid series of Cuda WU Compute Error terminations over the past 2 days, I've tried various combinations of cudart.dll and cudafft.dll versions (v2.2 mixed with earlier versions) thinking perhaps there was some incompatabilities, but I didn't keep track of those dll version combinations relative to which Cuda WUs completed and which Wus terminated with errors.
I've verified that Currently I've using v2.2 of both dll's but since I have no Cuda WUs in cache I'll have to wait & see whether I get exit code -1073741511 (0xc0000139) again. In the meantime can anyone provide insight & fix for exit code -1073741511 (0xc0000139)?? I've searched Lunatics and S@H "Number Crunching) forums for that code but found no posts for it.
Raistmer:
link on result with this code?
Jason G:
http://www.boinc-wiki.info/Unrecoverable_error_for_result_%27(result)%27_(_-_exit_code_-%27(number)%27_(%27(hex-number)%27))
[Edit: Fixed link to point to top of article page.]
BMaytum:
--- Quote from: Raistmer on 27 May 2009, 01:13:30 pm ---link on result with this code?
--- End quote ---
@ Raistmer: Here's several Cuda WUs that got exit code -1073741511 :
http://setiathome.berkeley.edu/result.php?resultid=1239045099
http://setiathome.berkeley.edu/result.php?resultid=1239045070
@ Jason G: Thanks for the Boinc Wiki link, but it doesn't list exit code -1073741511 (0xc0000139), did I miss it (or have I "discovered" or created a new one)? Just a guess: my error code is not a Boinc error, rather it's an S@H app error (or a result of me possibly mixing incompatible DLLs/EXEs together.
[Edited my text @ Jason G]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version