Hey everyone.

Lately I tend to get MB workunits (CUDA) that just sit there and won't even start until I restart BOINC. Workunit 433919613 is the latest one. It's been at 0% for the past 2 and a half hours. I've only seen happen with CUDA workunits since my CPU crunches Astropulse. I'm using Raistmer's V11 app with V 6.6.20.

Can anyone tell me what's going on?

cheers

Dude, You need to read the cuda Q&As in the Q&A section here.

This is an on going issue with cuda. What I do is suspend that WU and then unsuspend it, Cuda will start another and then restart the one before at some point. I have.. and for what ever reason.. had the same WU hang every time it re-starts. Just abort that one and move on.
My systems actually have a task scheduler setup that shuts-down/kills the boinc.exe every hour and restarts it a minute later. I cant be here 24/7 to watch the systems and it was getting old to find out that a WU hung 5 minutes after I left for work. Dont use windows Task Scheduler.. it sucks. I got a free one HERE.

You will need to setup 3 task. On that will start the boinc.exe that has NO schedule set.
A 2nd that checks if the boinc.exe window exist (minimized or not. It dont matter).
If this 2nd task dont find the boinc.exe, it runs the first unscheduled task.(The 2nd task is set to check every minute).
And.. a final one that is set to run every hour that will kill the boinc.exe window if it exists.

I dont use the Boinc Manager to run the boinc.exe core client, I let the task scheduler launch(run) it. If I run Boinc Manager, It finds it using the GUI-RPCs (Graphic User Interface - Remote Procedure Calls). When I exit Boinc Manager, I leave the apps running. Dont run Boinc Manager when you dont need to be watching it, it eats a small bit of CPU time. Every bit of CPU time that can be saved is MORE WUs crunched!
This set up works extremely well for CPU-GPU setups.

-- Mike

---

Not Ready Reading BRAIN. Abort/Retry/Fail?

Dude, You need to read the cuda Q&As in the Q&A section here.

Yeah, you are right, I should have done that, sorry.


As for your advice, I'll give it a shot, thanks.

---

I managed to set it up with no problems whatsoever. Very intuitive and works very well. Thanks for the tasks setup info btw.

---

Dude, You need to read the cuda Q&As in the Q&A section here.

This is an on going issue with cuda. What I do is suspend that WU and then unsuspend it, Cuda will start another and then restart the one before at some point. I have.. and for what ever reason.. had the same WU hang every time it re-starts. Just abort that one and move on.
My systems actually have a task scheduler setup that shuts-down/kills the boinc.exe every hour and restarts it a minute later. I cant be here 24/7 to watch the systems and it was getting old to find out that a WU hung 5 minutes after I left for work. Dont use windows Task Scheduler.. it sucks. I got a free one HERE.

You will need to setup 3 task. On that will start the boinc.exe that has NO schedule set.
A 2nd that checks if the boinc.exe window exist (minimized or not. It don't matter).
If this 2nd task don't find the boinc.exe, it runs the first unscheduled task.(The 2nd task is set to check every minute).
And.. a final one that is set to run every hour that will kill the boinc.exe window if it exists.

I don't use the Boinc Manager to run the boinc.exe core client, I let the task scheduler launch(run) it. If I run Boinc Manager, It finds it using the GUI-RPCs (Graphic User Interface - Remote Procedure Calls). When I exit Boinc Manager, I leave the apps running. Dont run Boinc Manager when you don't need to be watching it, it eats a small bit of CPU time. Every bit of CPU time that can be saved is MORE WUs crunched!
This set up works extremely well for CPU-GPU setups.

-- Mike

I've setup System Scheduler(the Free one), I'm able to run Boinc.exe(Hidden or not) and I have two Window Watchers setup and so far all is ok. Of course to watch Boinc/Seti There is the now flawed BoincView 1.4.2 which has no idea that some tasks are being done on the video card or use Boinc Manager which is less flawed in this regard, sigh.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Dude, You need to read the cuda Q&As in the Q&A section here.

This is an on going issue with cuda. What I do is suspend that WU and then unsuspend it, Cuda will start another and then restart the one before at some point. I have.. and for what ever reason.. had the same WU hang every time it re-starts. Just abort that one and move on.
My systems actually have a task scheduler setup that shuts-down/kills the boinc.exe every hour and restarts it a minute later. I cant be here 24/7 to watch the systems and it was getting old to find out that a WU hung 5 minutes after I left for work. Dont use windows Task Scheduler.. it sucks. I got a free one HERE.

You will need to setup 3 task. On that will start the boinc.exe that has NO schedule set.
A 2nd that checks if the boinc.exe window exist (minimized or not. It don't matter).
If this 2nd task don't find the boinc.exe, it runs the first unscheduled task.(The 2nd task is set to check every minute).
And.. a final one that is set to run every hour that will kill the boinc.exe window if it exists.

I don't use the Boinc Manager to run the boinc.exe core client, I let the task scheduler launch(run) it. If I run Boinc Manager, It finds it using the GUI-RPCs (Graphic User Interface - Remote Procedure Calls). When I exit Boinc Manager, I leave the apps running. Dont run Boinc Manager when you don't need to be watching it, it eats a small bit of CPU time. Every bit of CPU time that can be saved is MORE WUs crunched!
This set up works extremely well for CPU-GPU setups.

-- Mike

Oh and the program didn't fix My problem with WU's being stuck, But It is a cool program(And the DOS type window is a nice touch) and I've decided to get a CoolerMaster 1250w Real Power Pro 80+ psu in June 2009 and that's as soon as I can get the thing as It will set Me back about $242.46 or so, My $250 stimulus check ought to be in the Bank by then, If I get the check earlier then so much the better.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I did solve the problem finally on My PC, You need to read this thread and It's here. Mind You, One needs to create a file known as: Number_of_GPUs
and being a text file, It needs a number inside, If one has 1 gpu, put a number "1" inside and save the file where ones WU's are stored(minus the quotes or any text, Just the number), Since I have 2 gpus, I put a "2" inside instead, I'm not having that problem now. And You need to use an app_info file and have all the needed files(libfftw3f-3-1-1a_upx.dll, cufft.dll and cudart.dll) like I do from Raistmer's V10 gpu app and the MB_6.08_mod_CUDA_V11_USE_CROSS_WATCH.exe file in the folder where Your WU's are stored. And You can also incorporate the AK Seti app for Your cpu as well If one is using 6.6.20 and I'm not going to worry about older Boincs. If You want a good app_info file goto My websites main page and You'll find 4 files there which are V9(any will do), Only the app_info file inside the zipped file(rar file in that, It makes downloading easier) is what You need and I've got to update those files to V10 one day. Oh and except for the AK files there, The others are 32bit Windows files, The AK files are 64bit Windows files.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's