Tons of Invalid Results

Message boards : Number crunching : Tons of Invalid Results
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
Profile dcappello
Avatar

Send message
Joined: 3 Apr 99
Posts: 261
Credit: 170,969,320
RAC: 0
United States
Message 1387441 - Posted: 3 Jul 2013, 23:00:13 UTC

So I started updating all my SETI nodes - bringing a few of them back online and put them back to work.

One rig "seasnake" http://setiathome.berkeley.edu/results.php?hostid=4038605

Is having fits with the new v7 app and lunatics new installer - everything is win7 64 bit and
so are all the installers. (install is working just fine no issues there)

I have removed (multiple times) BOINC and Lunatics - and even removed my app-info file
and I am still pulling errors - blowing through GPU units like no tomorrow - generating
a boat load of errors (sorry about that) Mark was helping me out and suggested I post up.
I am at a loss of how to fix this. Open to suggestions and ideas?

Machine details:


GPU (there are 2 of them in this rig)


Here are my selections for Lunatics


and



No errors on BOINC v7 startup that I can see:


Anybody have any ideas what I should be looking at?



ID: 1387441 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1387444 - Posted: 3 Jul 2013, 23:05:24 UTC

Hey...
Glad you posted. And a pretty complete job of it, too. Well done.

I am going to be out for the evening, so hopefully another set of eyes or two on this will come up with the solution that I could not.

Meow!
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1387444 · Report as offensive
Profile dcappello
Avatar

Send message
Joined: 3 Apr 99
Posts: 261
Credit: 170,969,320
RAC: 0
United States
Message 1387446 - Posted: 3 Jul 2013, 23:12:08 UTC

No sooner than I posted, I now see I am getting some feed back from the server
"Your App_info.xml file doesn't have a usable version of SETI@home v7."

How is this even possible - I did a fresh install of both the apps (BOINC and Lunatics) ?



Here are the contents of my app-info:


<app_info> 
    <app>
        <name>setiathome_v7</name>
    </app>
    <file_info>
        <name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</name>
    </file_info>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_intelx86</platform>
        <file_ref>
            <file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
           <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_x86_64</platform>
        <file_ref>
            <file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
           <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</name>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
	<platform>windows_intelx86</platform>
        <file_ref>
            <file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
           <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
	<platform>windows_x86_64</platform>
        <file_ref>
            <file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
           <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app>
        <name>astropulse_v6</name>
    </app>
    <file_info>
        <name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</name>
    </file_info>
    <file_info>
        <name>AstroPulse_Kernels_r1843.cl</name>
    </file_info>
    <app_version>
        <app_name>astropulse_v6</app_name>
        <version_num>604</version_num>
        <platform>windows_intelx86</platform>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda_opencl_100</plan_class>
        	<cmdline></cmdline>	
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r1843.cl</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v6</app_name>
        <version_num>604</version_num>
        <platform>windows_intelx86</platform>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_100</plan_class>
        	<cmdline></cmdline>	
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r1843.cl</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v6</app_name>
        <version_num>604</version_num>
        <platform>windows_x86_64</platform>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>cuda_opencl_100</plan_class>
        	<cmdline></cmdline>	
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r1843.cl</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v6</app_name>
        <version_num>604</version_num>
        <platform>windows_x86_64</platform>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_100</plan_class>
        	<cmdline></cmdline>	
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r1843.cl</file_name>
        </file_ref>
    </app_version>
    <app>
        <name>astropulse_v6</name>
    </app>
    <file_info>
        <name>AP6_win_x86_SSE_CPU_r1797.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>ap_cmdline_win_x86_SSE_CPU.txt</name>
    </file_info>
    <app_version>
        <app_name>astropulse_v6</app_name>
        <version_num>601</version_num>
        <platform>windows_intelx86</platform>
        	<cmdline></cmdline>	
        <file_ref>
            <file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v6</app_name>
        <version_num>601</version_num>
        <platform>windows_x86_64</platform>
        	<cmdline></cmdline>	
        <file_ref>
            <file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
    </app_version>
    <app>
        <name>setiathome_v7</name>
    </app>
    <file_info>
        <name>Lunatics_x41zc_win32_cuda42.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cudart32_42_9.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cufft32_42_9.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>mbcuda.cfg</name>
    </file_info>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_intelx86</platform>
        <plan_class>cuda42</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_intelx86</platform>
        <plan_class>cuda22</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_intelx86</platform>
        <plan_class>cuda23</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_intelx86</platform>
        <plan_class>cuda32</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_intelx86</platform>
        <plan_class>cuda50</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_x86_64</platform>
        <plan_class>cuda42</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_x86_64</platform>
        <plan_class>cuda22</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_x86_64</platform>
        <plan_class>cuda23</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_x86_64</platform>
        <plan_class>cuda32</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_v7</app_name>
        <version_num>700</version_num>
	<platform>windows_x86_64</platform>
        <plan_class>cuda50</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>Lunatics_x41zc_win32_cuda42.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cudart32_42_9.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cufft32_42_9.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>mbcuda.cfg</name>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>610</version_num>
	<platform>windows_intelx86</platform>
        <plan_class>cuda_fermi</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>609</version_num>
	<platform>windows_intelx86</platform>
        <plan_class>cuda23</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>608</version_num>
	<platform>windows_intelx86</platform>
        <plan_class>cuda</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>610</version_num>
	<platform>windows_x86_64</platform>
        <plan_class>cuda_fermi</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>609</version_num>
	<platform>windows_x86_64</platform>
        <plan_class>cuda23</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>608</version_num>
	<platform>windows_x86_64</platform>
        <plan_class>cuda</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	    <file_name>cudart32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_42_9.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mbcuda.cfg</file_name>
        </file_ref>
    </app_version>
</app_info> 

ID: 1387446 · Report as offensive
Profile arkayn
Volunteer tester
Avatar

Send message
Joined: 14 May 99
Posts: 4438
Credit: 55,006,323
RAC: 0
United States
Message 1387454 - Posted: 3 Jul 2013, 23:50:28 UTC

So what is the difference between the units that run fine and those that do not.

It looks like the ones that have completed were run on 1024MB GTX460, so it might be a problem with the 768 version.


ID: 1387454 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1387482 - Posted: 4 Jul 2013, 2:20:41 UTC - in response to Message 1387446.  

No sooner than I posted, I now see I am getting some feed back from the server
"Your App_info.xml file doesn't have a usable version of SETI@home v7."

How is this even possible - I did a fresh install of both the apps (BOINC and Lunatics) ?
...

The versions of SETI@home v7 in your app_info.xml file have temporarily become unusable because the errors have reduced their quotas to less than the number of tasks already sent today. That message has confused many into thinking something was wrong in the app_info.xml itself but that's not so in this case.

The invalid tasks I looked at didn't have any stderr content, so there's no clues to what might be happening. BOINC seems to miss capturing stderr on some systems, and that's extremely annoying when trying to track down a problem.
                                                                   Joe
ID: 1387482 · Report as offensive
tbret
Volunteer tester
Avatar

Send message
Joined: 28 May 99
Posts: 3380
Credit: 296,162,071
RAC: 40
United States
Message 1387490 - Posted: 4 Jul 2013, 3:45:42 UTC - in response to Message 1387441.  
Last modified: 4 Jul 2013, 3:51:52 UTC

You didn't show us what the "Sensor" tab says under GPU-Z. I'm not asking you to do that, but have you looked for obvious hardware issues such as over-heating from recent fan failure (look at the tachometer), loose power connections, and have you re-seated the card in the slot?

I see that you updated the driver. Did you do a "clean install?"

Obviously, I don't know what's wrong and hope you get it fixed soon (whatever "it" is). My initial guess, considering that your other card is working, is that you have a hardware issue.

If not that, then a driver issue.

I think if you had a BOINC or application issue you would have it on both cards.

But I'm guessing.

<edit> Your card is doing what my 9800GT did when it burned to a crisp. Of course, I was 800 miles away with no remote control and no way to stop it. </edit>
ID: 1387490 · Report as offensive
Profile dcappello
Avatar

Send message
Joined: 3 Apr 99
Posts: 261
Credit: 170,969,320
RAC: 0
United States
Message 1387502 - Posted: 4 Jul 2013, 5:10:17 UTC

This is all good stuff!!! So I double checked the sensors - nothing out of the ordinary there.

For reference here is the info on the other card (and also next to the original post/card)



One thing I didn't do on the driver install is I left off the "Nvidia experience"
So I went back again re-installed drivers WITH that option.

If that doesn't work I"ll pull the 768 card and see if it runs with one.

thanks for all the tips and info. :)
ID: 1387502 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1387504 - Posted: 4 Jul 2013, 5:29:41 UTC - in response to Message 1387482.  

No sooner than I posted, I now see I am getting some feed back from the server
"Your App_info.xml file doesn't have a usable version of SETI@home v7."

How is this even possible - I did a fresh install of both the apps (BOINC and Lunatics) ?
...

The versions of SETI@home v7 in your app_info.xml file have temporarily become unusable because the errors have reduced their quotas to less than the number of tasks already sent today. That message has confused many into thinking something was wrong in the app_info.xml itself but that's not so in this case.

The invalid tasks I looked at didn't have any stderr content, so there's no clues to what might be happening. BOINC seems to miss capturing stderr on some systems, and that's extremely annoying when trying to track down a problem.
                                                                   Joe

What's odd is that the tasks that do complete successfully do have a stderr.
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1387504 · Report as offensive
tbret
Volunteer tester
Avatar

Send message
Joined: 28 May 99
Posts: 3380
Credit: 296,162,071
RAC: 40
United States
Message 1387516 - Posted: 4 Jul 2013, 6:37:34 UTC - in response to Message 1387502.  

I see you got Task 3062050862 to run successfully on your 768MB GTX 460. I hope that means your problems are over.
ID: 1387516 · Report as offensive
tbret
Volunteer tester
Avatar

Send message
Joined: 28 May 99
Posts: 3380
Credit: 296,162,071
RAC: 40
United States
Message 1387574 - Posted: 4 Jul 2013, 10:24:06 UTC

Now it looks like you're trashing CPU work, as well.

I don't even know what to think.

I think I think you shouldn't leave that rig running unattended; although as fast as it has been trashing work, it's almost as quick as hitting the "Abort" button.

Good luck and let us know if you find the trouble.
ID: 1387574 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1387579 - Posted: 4 Jul 2013, 11:06:38 UTC

I am really at a loss to try to come up with any new suggestions.
He is not overclocking anything, only running 1/per on the GPUs.
Had suggested rolling back to an older NV driver, but now the CPU is throwing errors. Wondered about the app selections in the Lunatics installer, but I can't find a problem there so far.

And the vexing thing is, once in a while, both CPU and GPUs appear to finish a WU correctly. And when they don't, no stderr breadcrumbs to find.

Now you know why I threw my hands up after a few hours of trying to help him via PM and asked him to post here.

About the last SWAG I have is....
What is the PSU on this rig? Could it be failing or overloaded? Wonky PSUs have been known to throw a rig into no man's land.
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1387579 · Report as offensive
Profile morpheus
Avatar

Send message
Joined: 5 Jun 99
Posts: 71
Credit: 52,480,762
RAC: 33
Germany
Message 1387593 - Posted: 4 Jul 2013, 12:26:51 UTC
Last modified: 4 Jul 2013, 12:28:58 UTC

Maybe it's worth to take a look at the System-RAM too. In my case I have had some trouble with slightly undervoltage (0.15V) just a couple of months ago.
.:morpheus:.
ID: 1387593 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13720
Credit: 208,696,464
RAC: 304
Australia
Message 1387735 - Posted: 4 Jul 2013, 18:05:56 UTC - in response to Message 1387579.  

Had suggested rolling back to an older NV driver, but now the CPU is throwing errors.

PSU would be the most likely culprit IMHO.

Grant
Darwin NT
ID: 1387735 · Report as offensive
tbret
Volunteer tester
Avatar

Send message
Joined: 28 May 99
Posts: 3380
Credit: 296,162,071
RAC: 40
United States
Message 1387828 - Posted: 4 Jul 2013, 23:13:58 UTC - in response to Message 1387579.  



About the last SWAG I have is....
What is the PSU on this rig? Could it be failing or overloaded? Wonky PSUs have been known to throw a rig into no man's land.


...or RAM, or CPU psu on the motherboard, or a changed BIOS bus speed, or a bad CPU, or a hard drive going bad, or a cable, or...

It's at this stage I pull everything loose and re-seat it all (including CPU) with only one GPU - run chkdsk. Then swap PSU. Then RAM. Then, well, swap whatever I have laying around.

But *first* I go through the BIOS with a fresh eye and taking my time.

The "easy" thing I can think-of that happened to me is that I had a motherboard that just insisted on re-clocking the RAM to 1T even though I manually set it to 2T. The RAM was telling the motherboard to go to 1T and it kept doing it despite my insisting that it go to 2T.

It quit, but I changed too many things at once to know which thing I changed that finally made it stop changing the RAM timings.
ID: 1387828 · Report as offensive
Profile morpheus
Avatar

Send message
Joined: 5 Jun 99
Posts: 71
Credit: 52,480,762
RAC: 33
Germany
Message 1387870 - Posted: 5 Jul 2013, 3:47:38 UTC - in response to Message 1387828.  
Last modified: 5 Jul 2013, 3:47:50 UTC

[...] But *first* I go through the BIOS with a fresh eye and taking my time. [...]

+1
.:morpheus:.
ID: 1387870 · Report as offensive
Profile dcappello
Avatar

Send message
Joined: 3 Apr 99
Posts: 261
Credit: 170,969,320
RAC: 0
United States
Message 1387916 - Posted: 5 Jul 2013, 7:11:07 UTC

The mobo is a Asus P6T-SE and it is 1 rev out on BIOS - which am going to update. The PSU is
a Corsair HX650 I'll check that when I crack it open. In case you were all wondering
what "seasnake" looks like (in the coolermaster case):

ID: 1387916 · Report as offensive
Profile arkayn
Volunteer tester
Avatar

Send message
Joined: 14 May 99
Posts: 4438
Credit: 55,006,323
RAC: 0
United States
Message 1387950 - Posted: 5 Jul 2013, 8:59:06 UTC - in response to Message 1387916.  

The mobo is a Asus P6T-SE and it is 1 rev out on BIOS - which am going to update. The PSU is
a Corsair HX650 I'll check that when I crack it open.


650 might be a little low for 2 GTX460's, especially with BOINC v7 which works the GPU a little bit harder.

ID: 1387950 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13720
Credit: 208,696,464
RAC: 304
Australia
Message 1387962 - Posted: 5 Jul 2013, 9:48:18 UTC - in response to Message 1387950.  
Last modified: 5 Jul 2013, 9:48:39 UTC

The mobo is a Asus P6T-SE and it is 1 rev out on BIOS - which am going to update. The PSU is
a Corsair HX650 I'll check that when I crack it open.


650 might be a little low for 2 GTX460's, especially with BOINC v7 which works the GPU a little bit harder.


Maximum ratings- 320W for the video cards (total), 130W for the CPU. A 700-750W PSU wouldn't be working nearly as hard as a 650W unit. It's nice to have some headroom. And depending on the brand, it might not actually be able to handle a 650W load.
And if you're running the optimised application for the CPU, those AVX tweaks really do work the CPU a lot harder than the previous optimised versions did.
Grant
Darwin NT
ID: 1387962 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1388004 - Posted: 5 Jul 2013, 15:22:01 UTC - in response to Message 1387962.  

The mobo is a Asus P6T-SE and it is 1 rev out on BIOS - which am going to update. The PSU is
a Corsair HX650 I'll check that when I crack it open.


650 might be a little low for 2 GTX460's, especially with BOINC v7 which works the GPU a little bit harder.


Maximum ratings- 320W for the video cards (total), 130W for the CPU. A 700-750W PSU wouldn't be working nearly as hard as a 650W unit. It's nice to have some headroom. And depending on the brand, it might not actually be able to handle a 650W load.
And if you're running the optimised application for the CPU, those AVX tweaks really do work the CPU a lot harder than the previous optimised versions did.

If in doubt about power consumption, I always suggest kicking out $20.00 for a Killawatt meter.
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1388004 · Report as offensive
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 1388018 - Posted: 5 Jul 2013, 15:57:03 UTC

there seems to be a great deal of dust on your front panel. Not to be a clean freak but have you dusted lately. Dusting should also include opening the GPU case if it has one and cleaning out the fins. Blowing canned air into the fan or exhaust port can only knock loose a little of the build up.


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 1388018 · Report as offensive
1 · 2 · Next

Message boards : Number crunching : Tons of Invalid Results


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.