Donate 6.18 all wu's ending in computation errors. I've set this project to NNW until they fix it. Now running Moo.
Printable View
Donate 6.18 all wu's ending in computation errors. I've set this project to NNW until they fix it. Now running Moo.
Same here, started about 3+ Hr's ago, switched to Poem for now ...
Looks like the Wu's are okay now again, tried a few Box's & didn't get any errors ...
It's doing it again. All tasks error out after about a minute. Now running Moo.
Well, Donate is out of work atm. :(
POEM has lots of work ... :p :D
Looks like they fixed the server communications problems, for the moment.
Anyone else having problems with the Donate Wu's hanging on the ATI Cards ???
Not at the moment....
If you have a high OC maybe back it/them down 25~50 Mhz? I have noticed on at least one box that a reboot fixes some of the Donate issues.
My Video Cards aren't Overclocked at all, I've been running them at their Stock Speeds for awhile now. But on the 2 7970 Box's I've tried to run the Donate the Wu's hang after a bit. Right now I started another Donate Wu & it's showing 10 Min's run time & 32% done, the Wu should be completely done by now. I can't get the app_config.xml file to work either. The BOINC MGR say's it found a app_config file for the Donate Project but it's not doing anything ??? The Wu is at 12 Min's now & 50% done ... weird
I know the last time I tried to run the Donate Project on my NVIDIA cards 580's & 570's it was taking forever to run the Wu's while others were showing much faster times, it's like I'm missing out on something but I don't have a clue what it might be ... Oh well the Video Cards needed more rest time anyway zzzzzzzzzzzzzzzzzzz lol
Ste\/e, I am not much help but for what its worth, I gave up on Donate months ago for the same thing was happening to me and my 7970's. I could not bother baby sitting the machines, I have other things to do. Looks like they still have not been able to fix the problem.
Ditto. I had the problem with tasks hanging on ATI. I got my 100M and moved on.
I had one myself this morning, so I did what was said to do and suspend it until the next has started. Then I resumed the WU and when the machine came back to the waiting WU finished it. :confused:
It could be that annoying problem windows sometimes has with driver resets. The driver restarts but the task that was running at the time doesn't.
http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx
I have a regedit file that address this issue that I applied to all my machines. It's very simple and safe to use and won't effect anything if it's not the issue with Donate. I can post it with instructions if anyone is interested.
There is a discussion about it over on the XtremeSystems forums. Scroll down to post #13
http://www.xtremesystems.org/forums/...tchdog+reg+fix
Right now I have the Wu's running faster & at the Times they should be for Stock GPU Running Speeds, I had to use the cc_config file to restrict the CPU Usage to 7 Threads leaving 1 Thread open for the 1 Donate Wu running. For some reason the Donate Wu won't take it's share of the CPU & thus running much longer than it should. Using a app_info or app_config file does nothing either, won't even run 2 Wu's like it's specified to do so in the app files. I'll have to leave them run for awhile to see if they hang or not.
I also Detached the Voplex Project from the 2 Box's I'm running Donate on. I noticed the Voplex Project was taking forever to update it's self & I was getting a lot of error's on the Donate Wu's. I suspected that the Donate Project couldn't connect to the Server & while the Voplex Project was trying to update & why I was getting the errors on the Donate Wu's anyhoot I haven't had any errors since Detaching the Voplex Project from those 2 Box's ... :)
NOTE: Just noticed the Donate Wu's were hung on both Box's so that problem still persists ... :rolleyes: ... Back to the Drawing Board ...
Guess I'll have to give up on the Project for now anyway, I did the Registry thing & got the app_config file to work so I was running 2 Wu's at a time. I ran 2 set's of 2 Wu's so I left for Town, when I got back both Wu's were stuck for the last 2.5 Hr's, just about the amount of time I was gone ... :rolleyes:
Yeah, I guess the Donate people aren't too interested in expending energy to fix the 7xxx series problem. Funny how they went so lax after they got their assistant funded..... sad sad sad
Well for me it's not only the ATI Cards, I just ran a Wu on 1 of my GTX 580's and it took 34 Min's to run, I don't thin that's a normal run time ??? I was giving it 1 CPU Core too but I'm running in HT Mode too so maybe that's the reason for the slow run time ???
Well I will see if the registry additions fix my ATI card hangs, only machine I have with one currently. The NVidia cards in the other two machines worked fine last time I ran Donate WU's on them.
Dagnabbit!!! Donate is on the fritz AGAIN...... :mad: ~X( :-q :!!
Looks like its working properly..... FTM
If you use BoincTasks (BT) to manage your boxes then there is a way to make the systems babysit themselves. The only caveat with my solution is that it only works on the local machine. So you have to set this up on each box with BT.
I set BT to run a batch file from the BT Rules section when a Donate tasks exceeds x amount of time where x is equal to average runtime + 5 minutes.
Here is a sample of my batch file Donate_Fix.bat Note: Edit directory paths to match location of boinccmd.exe
To create a rule in BT goto main menu and click Extra > BoincTasks Settings. In the pop-up window click the Rules tab.Code::@ECHO OFF
CLS
:BEGIN
C:\PROGRAM FILES (x86)\BOINC\boinccmd --project http://donateathome.org/ nomorework
C:\PROGRAM FILES (x86)\BOINC\boinccmd --project http://donateathome.org/ suspend
CHOICE /N /D Y /T 10
C:\PROGRAM FILES (x86)\BOINC\boinccmd --project http://donateathome.org/ reset
CHOICE /N /D Y /T 15
C:\PROGRAM FILES (x86)\BOINC\boinccmd --project http://donateathome.org/ resume
CHOICE /N /D Y /T 5
C:\PROGRAM FILES (x86)\BOINC\boinccmd --project http://donateathome.org/ allowmorework
C:\PROGRAM FILES (x86)\BOINC\boinccmd --project http://donateathome.org/ update
:END
Exit
(Click to enlarge)
https://dl.dropbox.com/u/3595745/Donate_Fix_small.jpg
Okay I'll have to give that a try in a few days, a little to late today to mess with it & I Have to be in the Hospital by 5:30am tomorrow morning for a Kidney Blast lol it's to try & break up a stone that's to big to pass should it start to move. If it isn't one thing it's another, not sure how I'll feel after the Kidney Blast so it may be Tues before I'll try it out, Thanks ...
F$, does the .bat file go in the same Directory where the Projects Directory is or the Directory where the boinccmd.exe is ??? Thanks, gonna give it a try since I don't feel to bad from the Kidney Treatment ...
Well the registry additions did not fix my Donate hangs either. So I guess I will try your batch file and see what it does, though I did have to change it to "C:\PROGRAM FILES\BOINC". Since that is where My Boinc program was installed.
Hey Ste\/e,
Glad to hear the blast didn't mess with the rest of you...
The /bat file can go anywhere you want. I would suggest creating a subfolder in the BOINC directory. This way if you upgrade BOINC, it hopefully won't get deleted. For me, since I use a lot of batch files I just gave them their own root level folder in a different HDD partition so they won't get lost or deleted.
Just remember to point the BoincTask rule to wherever you end up putting the .bat file
I'm going to try using Atiman to uninstall and clean up all the old driver remnants to see if that cures my hanging problem. I used it last night on the box with the 7970 and after a clean install of 12.10 I was able to run Collatz without immediate computational errors. Using driver sweeper and cc cleaner obviously didn't get rid of everything. Hoping for as good of luck on Donate.
This box has 2-5870's and a 570
3.2.0 on the DS. Okay, it didn't work out like I had hoped. For some reason, Atiman didn't want to remove anything on this box. I did use DS and cc cleaner again. I reinstalled 12.11 and now only one of the 5870's will run Donate, the other gets computational errors immediately upon starting. Prior to uninstalling and sweeping both would run Donate, but hang. I reinstalled the driver again, same problem. ATI-0 runs Donate ATI-1 fails. Right now I have 0 doing Donate and 1 doing Collatz. Both are running at factory clocks and voltages. This is just weird...any ideas. Curious to see if the one gpu running Donate hangs tomorrow morning.
I remember when I had 3x 4850s in my desktop I had to extend the Windows desktop across to the 2nd & 3rd GPU in order to get them to crunch. Can't hurt to give it a try.
BTW, since CCC 12.11 is beta, that could be your problem, or part of it. I would suggest CCC 12.6 as that is the most stable of the current versions for my setup.
The problem with the stalled tasks has nothing to do with your machines. The tasks require to communicate with the bitcoin server. If that communication (via the donate app) fails, then the BOINC task idles forever. Not sure anything can be done from the client side to fix the issue. When a burp happens, it happens. Pause/restart or abort and start a new one, makes no difference.
Thanks for the suggestions, but Donate seems to require more tending than I'm willing to give it at this point. I'll keep the atis on Collatz or mw for the time being, they both crunch perfectly. If the problems ever subside at Donate I'll give it another try.
F$, I run 2 Wu's @ a Time, they usually run about 18-20 Min's so what do I put in the 3 Choice Lines ??? Thanks, I'm trying to run Donate again, I can Babysit while I'm up but will shut the Project down when I go to bed rather than have the Wu's Hang. Will try the .bat file too, but can't do that until I know what to put in time wise for those 3 lines ...
Yes, Choice is just being used as a timer to pause before the next command is read/executed, so you can adjust the number after /T (the number of seconds) to whatever you want them to be. The 3rd choice timer may not be necessary but it doesn't hurt anything to have it. The first two Choice lines I set based on my i7 920. Suspending most any project seems to lag on my i7. So if your systems respond faster to a manual suspend or reset from within BOINC Manager, you can shorten the 1st and 2nd Choice times.
I set it up on just one Box & left the Times you had the same. I did set the rule for 21 Minutes though, I can run 2 in about 18-19 Minutes, anything over that & the Wu is probably Hung so 21 Minutes should work. I'll see if I have it right on the one Box before trying the others ...
Weird, I just happened to be watching the one Box with the .bat file & it did Suspend the 2 Wu's after 21 Min's but then after 15 Min's of Suspension it still hadn't restarted the 2 Wu's ... ??? ... I had to manually restart the 2 Wu's
EDIT: Just had another Wu's Suspend after 21 Min's but had to Manually Restart it again ... sigh ... I think I've had it with this Project, it's just a PITA to try & run ...