1) Message boards : Number crunching : Sudden Issue with GTX570 (Message 27285)
Posted 4183 days ago by Profile K1atOdessa
I've been running this host for a long time, but as of a few hours ago it began encountering error after error. Given these are all Nathan tasks I've never had issues with, I imagine something went wrong on my system.

After a reboot, I still get the same error:

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
MDIO: cannot open file "restart.coor"
SWAN : FATAL : Cuda driver error 999 in file 'swanlibnv2.cpp' in line 1574.
Assertion failed: a, file swanlibnv2.cpp, line 59

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

</stderr_txt>
]]>

Any ideas of what I should try? I switched this over to some other projects and have completed WU's successfully, running with the same settings that have worked since I got the card. I would have expected some weird error to be fixed by the restart, so now I'm not sure. Nothing changed on my system, as it completed numerous WU's successfully since the last reboot until this point when everything hit the fan.
2) Message boards : GPUGRID CAFE : The milestone thread (Message 27076)
Posted 4210 days ago by Profile K1atOdessa
150 Million!
3) Message boards : Graphics cards (GPUs) : Nvidia 306.23 WHQL Warning (Message 27046)
Posted 4222 days ago by Profile K1atOdessa
That is interesting, and searching for drivers on Nvidia's site does send you to two different links for GTX 275 vs. GT 240, for example. And the driver details explicitly call out different cards under each link. But, the driver manual lists all cards together as supported.
4) Message boards : Graphics cards (GPUs) : NOELIA WUs getting "stuck" (Message 26615)
Posted 4271 days ago by Profile K1atOdessa
I had this happen twice on me to date (I am running Windows). One time it was 2 days before I noticed, so I just aborted (given the utilization was practically 0% and progress not moving). The 2nd time I saw it, I closed BOINC and reopened, after which the WU errored out.

Kinda a pain, but just keeping an out eye at this point.
5) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 26540)
Posted 4282 days ago by Profile K1atOdessa
It seems to have worked for me as I don't appear to be getting any cuda 31 tasks.


Same here.. Don't think I've seen a cuda3.1 in several weeks.
6) Message boards : News : New system in beta queue && long queue (Message 26471)
Posted 4291 days ago by Profile K1atOdessa
Yep.. Lots of errors on both my hosts with these "NOELIA_sh2fragment" WU's.
7) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 26377)
Posted 4298 days ago by Profile K1atOdessa
However I do not recommend to run this batch program at every startup, because it can interfere with the BOINC manager, if a CUDA3.1 task is already running when this batch program starts.


Good advice. I manually kick of the batch file after a reboot, following a check to see if a CUDA3.1 is running. They have been few and far between recently, so that's good (practically negating the need for the batch file -- but just in case...).
8) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 26369)
Posted 4299 days ago by Profile K1atOdessa
One way you can verify is to confirm that in your GPUGrid project directory (potentially at C:\ProgramData\BOINC\projects\www.gpugrid.net on Win7), the files "acemd.win.2352" (CUDA3.1) and "acemd.2562.cuda42" (CUDA4.2) are the same size.
9) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 26368)
Posted 4299 days ago by Profile K1atOdessa
This works by updating the file in the project directory. If you set up that short batch file:

4a. On Windows XP run this batch program:

SET GPUGRIDDIR=c:\Documents and Settings\All Users\Application Data\BOINC\projects\www.gpugrid.net\
COPY "%GPUGRIDDIR%acemd.2562.cuda42" "%GPUGRIDDIR%acemd.win.2352" /y

4b. On Windows 7 run this batch program (right click) as an administrator:

SET GPUGRIDDIR=c:\ProgramData\BOINC\projects\www.gpugrid.net\
COPY "%GPUGRIDDIR%acemd.2562.cuda42" "%GPUGRIDDIR%acemd.win.2352" /y


with the the following cc_config.xml file:

<cc_config>
<options>
<report_results_immediately>1</report_results_immediately>
<dont_check_file_sizes>1</dont_check_file_sizes>
</options>
</cc_config>

then it should work. I have to rerun the batch file after rebooting, but that's all the intervention I have to do. And you will potentially see a CUDA3.1 running, however it will be running using the CUDA4.2 files and be much faster.
10) Message boards : Graphics cards (GPUs) : APP names (Message 26061)
Posted 4317 days ago by Profile K1atOdessa

that worked at first, but then when the original Seti tasks finished, it
loaded GPUGrid onto that GPU.


From your computers page, it shows you using BOINC 6.10.58.


The BOINC Client Configuration page shows you must be running BOINC client 6.13 or higher to use the "exclude_gpu" option.


That's probably why it is not working for you. Try downloading BOINC 7.0.28 with the same cc_config.xml. Also, make sure you load the preferences in BOINC, forcing the client to read the information in the cc_config.xml file. If successful, you should be able to see the event log showing the exclusion.


Next 10
//