When Kevint and I were doing this in the beginning I think it was a .NET issue. I know your issue is different, just throwing that out there. In the end it was 2.0 matched to the right driver and the right ccc and Boinc version. I'm currently having the exact issue with 5830's. Going to start rolling back tomorrow. Let you know what I find. I did get success with the latest Boinc, 11.3 CCC for Primegrid.
Last edited by Clank [MM]; 07-17-11 at 01:53 AM.
CPU only seem to run fine, though I didn't run all variations yet. I'll read through the complete post at MW forum and see if anything there helps. I followed Fire$torm's directions to the letter and all tasks continue to fail at about 127 seconds at 80+% done. Here's the error message:
Stderr output
<core_client_version>6.10.60</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
<stderr_txt>
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Using SSE2 path
Found 1 CAL devices
Chose device 0
Device target: CAL_TARGET_770
Revision: 2
CAL Version: 1.4.838
Engine clock: 750 Mhz
Memory clock: 900 Mhz
GPU RAM: 1024
Wavefront size: 64
Double precision: CAL_TRUE
Compute shader: CAL_TRUE
Number SIMD: 10
Number shader engines: 1
Pitch alignment: 256
Surface alignment: 256
Max size 2D: { 8192, 8192 }
Estimated iteration time 330.481667 ms
Target frequency 30.000000 Hz, polling mode 1
Dividing into 9 chunks, initially sleeping for 0 ms
Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Using 9 chunk(s) with sizes: 176 176 176 176 176 176 176 176 192
Integration time = 200.021940 s, average per iteration = 312.534281 ms
Integral 0 time = 202.951483 s
Likelihood time = 3.230086 s
<background_integral> 0.000928726019059 </background_integral>
<stream_integral> 353.723081457166980 130.799939675965280 1464.654321262977600 </stream_integral>
<background_likelihood> -3.602249639427543 </background_likelihood>
<stream_only_likelihood> -17.295920317294978 -4.388825045143967 -4.522211712778050 </stream_only_likelihood>
<search_likelihood> -3.096088347341647 </search_likelihood>
<search_application> milkywayathome_client separation 0.82 Windows x86 double CAL++ </search_application>
00:20:30 (3416): called boinc_finish
</stderr_txt>
]]>
On the upside, PrimeGrid now seems to work without errors...Al Oh, and I have reset the project.
Last edited by Al; 07-17-11 at 01:53 AM.
Sorry it didn't work for you. For the moment I do not have anything else I can think of. Maybe take a break from it for a day or so, just to help dissipate some of the frustration.
It would help if we knew someone with a 4870 that is currently running MW.
Oh, a thought..... OK, you said Collatz crunched fine. Have you tried a couple of Moo wu's? Again, just to see.
Edit: Not that you need to do this now but when you feel like it run GPU-Z. This utility just gives detailed info on GPUs.
Last edited by Fire$torm; 07-17-11 at 02:42 AM.
Mine was working fine last month, driver ver 6.14.10.7131 (cat 10.10). Just tried some new work, all error out with the majority of them being a "exceeded elapsed time limit" error after a couple seconds and a couple with the "Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' "... bla bla bla output.
Maybe it's not me? PG fine, Collatz good to go, Moo no problem...MW - can't run anything but cpu, all gpu wu continue to fail. Guess if I want to crunch MW I'll have to do it on my Nvidia cards.
Al
Probably too late to get in on the double credit thing, but I had checked my machines out that used to run MW. All errored out with same message. Looks like there is a fix. I was able to get mt 2 XP64 machines crunching using the ap and ap_info file from Arkayn. Wasn't able to get my dual core XP32 running though. If you are running XP32, I think this would be the DL for you.
http://www.arkayn.us/forum/index.php...downfile;id=75
Hopefully that will work for you. There is a directory in there called files to copy. If you know where your MW folder is, then shut down BOINC. Run the task manager to make sure that boinc.exe is not running. Copy the files into your folder and restart BOINC. You might get a couple of errors at first, but it should straighten out. Let us know if this works.
Joined Original Message Board: Fri Jan 27, 2006 1:47 pm, Currently with 11298 Posts
If it ain't crunch'n, unplug it!
I just re-attached to MW yesterday and am having the same problem. I'm 99% certain it's a server side issue. I was getting errors and BSOD's.
All four of my ATI machines produce nothing but errors for MW. They used to work just fine. No app_info or anything. And they continue to work fine on dnetc/moo/etc.