Ever since adding the app_info.xml file to adjust gpu usage I haven't gotten any cpu tasks. can any body tell me,what do I need to do to the app_info to get it running nbody and 0.50 tasks again. I added the nbody portion of the app_info trying to get it to run, but it didn't help. Don't really under stand all this app_info stuff anyway.

Here is my current app_info:

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_0.62_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>62</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>ati14ati</plan_class>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<cmdline>--gpu-target-frequency 60
--gpu-polling-mode 1</cmdline>
<file_ref>
<file_name>milkyway_0.62_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.40_windows_x86_64__mt.exe</name>
<executable/>
</file_info>
<file_info>
<name>libgomp_64-1.dll</name>
<executable/>
</file_info>
<file_info>
<name>pthreadGC2_64.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>40</version_num>
<plan_class>mt</plan_class>
<cmdline>--nthreads=2</cmdline>
<file_ref>
<file_name>milkyway_nbody_0.40_windows_x86_64__mt.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libgomp_64-1.dll</file_name>
</file_ref>
<file_ref>
<file_name>pthreadGC2_64.dll</file_name>
</file_ref>
</app_version>
</app_info>

any assistance would be greatly appreciated.

your app_info seems to be correct, perhaps there is no wu n_body to download for the moment

server status shows over 500 wu waiting to send for n_body but none will download to my computer. Is there anythingelse I can do to get this this app up and running. maybe some preference somewhere that is required. Under messages boinc 6.10.60 states that it is requesting a cpu task but none are being sent not even 0.50 WUs

My work laptop seems to be getting 0.50 WUs, with no app_info since My GPU doesn't meet the requirements for 0.62 app, but it is not receiving n_body WUs either.

Hmmm...

Interesting. My guess would be that since N-Body has been offline for awhile you've built up enough CPU STD & LTD (from running relatively long run time MW 0.50's) that you're not asking for a lot of MW CPU work. That seems to be the case with my hosts right now after a quick look at thier CPU debt situation.

Combined with the fact this seems to be a limited replication test run, it could be you have to hit the project at just the right time to get one. ;-)

<edit> I was just looking at the average runtime stats on the Server Status page. Is it even possible for a hot i7 to run an MW 0.50 (successfully) in 36 seconds!!??

ok I just needed to wait I guess. I'm getting the n_body WU now. But for some strange reason I started getting a rash of validate errors on my 0.62s about 30 min before getting the n_body WU Don't know what up with that.

.... But for some strange reason I started getting a rash of validate errors on my 0.62s about 30 min before getting the n_body WU Don't know what up with that.

Your card is on the edge running at 950/1350. If you are water cooled, no worries, something else happening. If you are just fan cooled, its highly likely the card is extremely hot, and running too fast. If the latter turns out to be true, and it is over heating, then you will loose the card in the end. What GPU temperature is it running at? 6XXX run higher clocks, but 950/1350 is pushing it hard on air.

Re the errors, would be a good idea to bring it down a bit and see the result, suspect the validate errors would then disappear. Suggest you try 900/500 for now, just to see if it settles, can always carefully increase it later depending on temperatures and any overvolt needs. You dont need high memory at MW - keeping memory high just generates heat and a power bill.

Regards
Zy

I running at 63C right now on an unlocked HD6950 DirectCUII the one from ASUS that has the 2 100mm fans. I'm running at the cards at stock speed of 810/1250 have been for a week now. I use to run it at the 950/1350 OC but I didn't get over 66C when I ran it then. I don't really know why it is reporting that it is still running at that speed. All of completed WU are saying that I'm running at that speed even when I'm not OCing.

Nice one - you must have a well ventalated Case.

That speed reporting is wierd, and running at the speed you actually are you should not get validate errors.

Its possible ... maybe, its worth a shot .... if you have not done a clean driver install since getting the 6950, that cleaning out the driver, and re-installing it clean may do the trick. Can get wierd results at times loading over an existing driver, put that together with a new card type, and its possible the driver is not up to scratch. Long shot ... but worth a try. (Use Driver Sweeper - latest version - to clean it out)

Regards
zy

Just had another thought - you are running driver 1.4.1016

Thats not exactly old as such, but it is a while back, I cant remember the first versions to officially support 6XXX, but you bet your life the first one or two where a little flakey in the time honoured new card series fashion.

Another reason to give the driver clean install a whirl. The 11.4 Catalyst release gives out V1.4.1353. Its not impossible that earlier versions on first release of 6950s had problems, and maybe speed reporting might have been one.

Little bit of hope springs eternal I agree, but something is reporting incorrectly, the driver is the first place to eliminate as a cause - especially with mysterious validate errors.

Regards
Zy

Ok now all n_body tasks are erroring with a computing error. When I finally started getting the n_body WU they were running fine about 25 min each run time and when I got up today they all ended like this:
--------------------------------------------------------------------------------
<core_client_version>6.10.60</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
<stderr_txt>
<search_application>milkywayathome nbody 0.40 Windows x86_64 double OpenMP Crlibm</search_application>
10:29:23: Using OpenMP 2 max threads on a system with 4 processors

</stderr_txt>
]]>


--------------------------------------------------------------------------------


--------------------------------------------------------------------------------

Max time exceeded after

Run time 1.14 sec.
CPU time 2.56 sec.

can A WU really be completed in this short of a time?


A reboot did not help with this.

My Problem with the 0.62 WU erroring is getting better some still error but most are completing abd validating now.

I think that they are producing alot of bad WUs again. After checking these and noticing that the same WU after being sent to a secound computer were also erroring. not positive though some have errored out on 2 or three other computers but validate on others.