So who's running the SETI CUDA client then?
- Thread starter TheTross
- Start date
Soldato
Hello There 
, up and running on my GTX's user name same as here but you already know that 
, up and running on my GTX's user name same as here but you already know that
Ta very muchly, added 
Soldato
As above, running on my two GTX 260s until the end of the gauntlet - Happy
- Happy
As above
As above as above
Soldato
Running 2 8800GS for the gauntlet - dekez
Added
Crikey, I've got me work cut out for the next few weeks with the news
Crikey, I've got me work cut out for the next few weeks with the news
Associate
CUDA client here for the gauntlet weeks
Ta
Yay!
I've added you, but please post a thread about those errors if you're stuck - it'll probably be something simple
Soldato
I'm in as well - just for the gauntlet weeks and run up.
think xp/drivers/CAD is giveing me the 50% cpu issues (did you F@H some time back)
think xp/drivers/CAD is giveing me the 50% cpu issues (did you F@H some time back)
well, so far on my 260, there has been 12 errors since 24th august- all with this error:
<core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.029390 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
however, looks like for most of these, there's someone else who has errored on them as well, but usually someone with very long compute time (ie non CUDA i guess) that has completed the WU.
<core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.029390 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
however, looks like for most of these, there's someone else who has errored on them as well, but usually someone with very long compute time (ie non CUDA i guess) that has completed the WU.
Last edited:
I believe the VLAR WUs are renowned for taking a very long time to process for no extra benefit, so much so that people who find they're running them tend to abort them. By the 'autokill initialised' message I assume you're using the VlarKill driver, which automatically detects and aborts all VLAR WUs.
So as long as the normal CUDA WUs are being completed successfully there's no problem at your end.
So as long as the normal CUDA WUs are being completed successfully there's no problem at your end.
So much for for my rig.... Had it running for cuda 24 hours before I lost it. Everything has just gone pear shaped after installing the latest motherboard updates from msi. 
boot-up takes forever and it always loads up the realtek hd audio panel (and it just gets worse when trying to access the drives). System restore hasnt work so looks like its a ghost back-up made yesterday. Hopefully be back up and running in a few hours. Having to post from my N97...... Just not the same as the 40" sony.
boot-up takes forever and it always loads up the realtek hd audio panel (and it just gets worse when trying to access the drives). System restore hasnt work so looks like its a ghost back-up made yesterday. Hopefully be back up and running in a few hours. Having to post from my N97...... Just not the same as the 40" sony.
Associate
Just to let you know I'm now running the CUDA client