Using 6.4.5 last yesterday, 2 blue screens:

Error code 100000ea, parameter1 8855c2c8, parameter2 89966940, parameter3 bacfbcbc, parameter4 00000001.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

One of my teammates had the same problem on his box. If I roll back to 6.3.x - what was the last recommended version? 6.3.19?

After 6.3.19 rollback, everything is great and stable (except GPUGrid won't pick up new work when high-priority tasks are running on my CPU, but that's a different issue.)

Stay away from 6.4.5.

I also rollback to 6.3.21; almost everything is fine now.

On a quad system, this causes one cpu to be dedicated to the gpugrid task. There is no need for this as I was getting 11 hours gpu completion with 5 tasks running and it is no different with 4 tasks running. This has dropped my overall credit production down.

I assume going back to 6.4.1 might fix this???


With 6.4.1, I was using about 800 seconds of CPU time to process an 11 hour ET job. Now it is taking 22,000 seconds to do the same job. There seems no way to disable the high priority for the gputask. They (BOINC) are not calculating the coprocessor efficiency and utilization correctly.

This is what I'm seeing after "upgrading" from 6.4.1 to 6.4.5. Now my quad will run only 4 tasks instead of 5. I'm going to try going back to 6.4.1.

Edit: Just moved back to 6.4.1 and the quad has returned to running 5 tasks. I'd avoid the new 6.4.5.

Didnt work for me - 6.4.1 picked up with the same 4 tasks and high priority for gpugrid. I suspect there is some adaptive algorithm, learning and/or a resource file that needs to be undone. If you are back at 5 tasks I suspect that very shortly they may go to high priority on you.

Did the 5 tasks come up immediately or did you to wait for a current gpugrid job to get done? When I saw there was no change I re-installed 6.4.5. At least 6.4.5 got the 11 hours correct at 6.4.1 was showing 90 days to complete.

The 5 tasks started right away. After using 6.4.5 my estimated times are way off though. They were pretty close before. Something changed by installing 6.4.5.

How could it be, that the 6.4.5 is be the "Recommended version" here and on the Berkeley-Server? All is running fine with the 6.3.21, with the 6.4.2 and 6.4.3 is a only a little problem the DCF (HighPrioMode), but with the 6.4.5 you can't run GPUGrid without babysitting the boxes all the time.

Is the failure only on the server of GPUGrid and come with the calculated estimted time with the WU on our boxes? Then please stop this WUs with the wrong calculated time.

---

On my Windows x64 and BOINC-Manager x64 i got the Message:
18.12.2008 09:50:19|GPUGRID|Message from server: No work sent
18.12.2008 09:50:19|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
18.12.2008 09:50:19|GPUGRID|Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
18.12.2008 09:50:19|GPUGRID|Message from server: Full-atom molecular dynamics is not available for your type of computer.

Is there no Client for?

with the 6.4.2 and 6.4.3 is a only a little problem the DCF (HighPrioMode), but with the 6.4.5 you can't run GPUGrid without babysitting the boxes all the time.

The 6.4.3 works fine. No Problem and 2 new WU last night. Even when a normal task run in highpriomode. :)

---

Constant dripping wears away the stone. :)

Well, I just built a new computer with a Nvidia 9800 GT with 1 G VRAM and got three tasks right off the bat. I could not log into the web site so I went with NNW until that was resolved.

I checked this morning and Voila, my account allowed me to log on (Praise something)...

But, when I tried to fetch work... I got the message that there was no work for my Cell processor type (Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.)

I did a project reset and it looks like it is downloading a task ...

And an immediate failure with computation error.

So, two successes and two computation errors. Is this common?

I am running video driver 6.14.11.8048 and BOINC 6.4.5

Hmmm, it is downloading another task ...

Computation error ...

Another computation error ...

{edit}Down-leveled BOINC to 6.2.19 but have the 0 seconds asked for ... so will have to wait to see if I get more work later{/edit}

As far as I see you have received it.
uW10579-SH2_US-3-40-SH2_US200000

Just upgraded to 6.4.5 and did a reset. Got two WU for my 2 280's and when it tried to download more got this:

12/18/2008 9:32:47 PM|GPUGRID|Sending scheduler request: Requested by user. Requesting 518336 seconds of work, reporting 0 completed tasks
12/18/2008 9:32:52 PM|GPUGRID|Scheduler request completed: got 0 new tasks
12/18/2008 9:32:52 PM|GPUGRID|Message from server: No work sent
12/18/2008 9:32:52 PM|GPUGRID|Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
12/18/2008 9:32:52 PM|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.

My estimated completion time started low and is going up rather that starting high and going down. However they are not running in high priority and show only 0.03 CPU's. That would be a huge improvement over 0.9 CPU's in 6.3.21.

Now all I need to do is sleep infront of my rig with the alarm set every 6 hrs to download new WU.

Glad tomorrow is the last day of work for 2 wks.

Pat

Update: Changed the number of days of work to 4 and was able to download two more WU. We'll see in the morning if I don't have to babysit.

No more "babysitting" with 6.4.5 ;-)

I run one GPU on Vista-32 and another on Vista-64 with 6.4.5 BOINC. The all on to similar hardw. After some days of troubles and newbee try-&-fail, I may report that I solved my issues on the 64-system by exclusively run others Boinc 64-applications at the same time with the GPU-apps. Last day I tried to extend again the range of apps running on the 64-sys with some 32-apps and it didn't took many hours before I got a sys.restart to handle with.
Solution was to detach again all apps that do not run on 64 bits arch. and to synchronize right after the restart. I didn't inquire which one of those 32-apps that caused the mess. & I do not intend to do so either... Merry Christmas !

I ment CUDA-apps on GPU... Not only GPU!

It doesn't even think to get new WUs for my GPU. But even if I force it to get WUs, there are running only 2 tasks: gpugrid and CPU-task. What's wrong?

It seems that all of us using different boic managers 6.4.5.....

It doesn't even think to get new WUs for my GPU. But even if I force it to get WUs, there are running only 2 tasks: gpugrid and CPU-task. What's wrong?

It seems that all of us using different boic managers 6.4.5.....

Well, I am running 6.5.0 ...

As far a the problem mentioned by Dr. Anderson which has as a symptom this issue (won't fetch work) affects both versions 6.4.5 and 6.5.0 ... we can brute force it to make it go. I am using a higher share and larger queue and that has been working for me to this point. I just got another task automagically when I turned in the last one processed. So, I have one in flight and one pending on the i7 machine.

On the slower machine I have yet to run off the first task and have a pending ... but it looks like that card is so slow that it will take nearly two days to run one task for this project. (8800 class card I think, noper, 8500 GT and 40 hours to get to 41% done ... I may just run these two tasks and not waste my time that is way too slow to run the risk of blowing the task).

Using 6.5.0, runnig 3 tasks at last. acemd takes 10 to 15% CPU time.

Using 6.5.0, runnig 3 tasks at last. acemd takes 10 to 15% CPU time.

It was much lower with the dot 56 version of the Science Application. Which was pulled for some other buglet ... well, after the new year maybe we will see a revised version that will drop the CPU usage.

I am not sure, but it looks to me like I have a 33 some hour task which is twice as long as normal ... my par is about 17 hours (historically) on the 9800 GT card.

I had a task on the 8800 and I am not sure I am going to make the deadline on it on the 29th ... the second task I had on that machine I had to kill as there was no way I was going to get the first one done and then the second by the deadline ...