ati 4870 failing immediately

[Fire$torm]

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.

[DrBob]

...It would help if we knew someone with a 4870 that is currently running MW...

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.

[Al]

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

[Fire$torm]

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.

Thanks for the input. It is what I was hoping to hear.

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

That was my line of thinking. Which is why I suggested Moo. It has to be a batch of bad wu's. So good news for you. Bad news for MW.

[Crazybob]

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.

[Shadow]

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.

[zombie67]

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.