12/31/2012 1:16:30 AM | rosetta@home | Scheduler request completed: got 0 new tasks
12/31/2012 1:16:30 AM | rosetta@home | No work sent
12/31/2012 1:16:30 AM | rosetta@home | (reached daily quota of 8 results)

I've never seen this before.

It looks like you're suffering from a bug (or bugs) which might or might not be related to a number of other people: https://boinc.bakerlab.org/rosetta/results.php?hostid=1567481. That page shows that you're not getting any granted credit for those tasks but in reality you are - if you check any of the individual tasks you'll see the granted credit against each.

googloo - can you confirm whether the computer is otherwise stable? I expect it is as it would be odd to find that all of the tasks complete fine but are then marked invalid if it's unstable. Also, can you confirm whether your GPU is doing any work on any projects?

This info might be useful:

This computer is using BOINC 6.12.34
Has an NVIDIA GeForce GT 620 (2048MB) driver: 31070

---

Computer is stable. Not using GPU. I have reset the project; hope that works. Any other ideas?

I'll post back once you've got some submitted tasks if they aren't accepted as valid.

Danny

---

It looks like you're suffering from a bug (or bugs) which might or might not be related to a number of other people: https://boinc.bakerlab.org/rosetta/results.php?hostid=1567481. That page shows that you're not getting any granted credit for those tasks but in reality you are - if you check any of the individual tasks you'll see the granted credit against each.

googloo - can you confirm whether the computer is otherwise stable? I expect it is as it would be odd to find that all of the tasks complete fine but are then marked invalid if it's unstable. Also, can you confirm whether your GPU is doing any work on any projects?

This info might be useful:

This computer is using BOINC 6.12.34
Has an NVIDIA GeForce GT 620 (2048MB) driver: 31070

One of the suspicions by some users is that the pc's with Nvidia gpu's are the ones having problems here at Rosetta. I cannot confirm or deny that, but CAN confirm that after a break my pc's, with AMD gpu's in them, ARE crunching and getting credits.

googloo - they're still erroring out. Can you try picking "suspend GPU" under the Activity menu in BOINC? I know you're not running it but it's worth a try as it's easy.

Danny

---

If suspend GPU is not help (i thinks will not) try reinstall nVidia drivers.
Few users in my team found what this bug appear on their computers after NV drivers update for latest versions. 310.70 for example (same as you use now).
Cleaning drivers and intall older version (306.97 for example) usual stop errors. (although this workaround has been successfully tried so far only on 2 computers)

One of suggestion that this errors is due new NV CUDA 5 API in 310.7 drivers. While R@H NOT use CUDA for calculations it probable conflict this something in BOINC software what damage R@H WUs.

I have had Suspend GPU checked ever since I got the GPU. Will try the older NVIDIA driver suggested by Mad Max. Thanks.

I've installed NVIDIA driver 306.97. Have to wait 13 more hours before getting new Rosetta tasks, though, as I've reached the quota. Sigh.

I've installed NVIDIA driver 306.97. Have to wait 13 more hours before getting new Rosetta tasks, though, as I've reached the quota. Sigh.

As soon as you start returning valid units you will start getting them by the handful and your daily quota will go back up to normal quickly. I think it is two for every good one returned, so after just a few more days, assuming this works, you should be crunching just fine.

Four successful tasks (not Client error) so far this morning. Thanks to all for your help.

Four successful tasks (not Client error) so far this morning. Thanks to all for your help.

Wow... does this mean you guys figured out this bug that has been plaguing everyone for so long?

---

Four successful tasks (not Client error) so far this morning. Thanks to all for your help.

Wow... does this mean you guys figured out this bug that has been plaguing everyone for so long?

I doubt it. I'm not running 7+ boinc client.

Wow... does this mean you guys figured out this bug that has been plaguing everyone for so long?

I think so. For current moment for 3 computer (from three tries) revert to old nv drivers helps avoid this error.
More peoples/computers are welcome to collect statistics and find out it really is a source of problems or not.

But in any way this is only a temporary solution...

I doubt it. I'm not running 7+ boinc client.

BOINC 7+ as a source (or at least one part of bug) is just assumption from few users. And it seems wrong assumption, at least with respect to this particular bug. Because it occurs in the early 6.x versions of the BOINC client too, and the replacement frоm 7.x to 6.x does not change anything.
Critical parts is Rosetta@Home + NV drivers (+ probable BOINC client, but no matter what version)

I am having trouble on two Intel quads and an AMD eight core, but two dual core Intels are still running without errors. I will re-install on the eight core after the problem has been sorted. If it fixes the problem, then I will consider driving three hours to fix my daughter's computer. (I told her at Christmas that Rosetta would be no problem if she would let me run it, and I don't want to tell her about these errors.)

FWIW, I'm running BOINC 6.12.34 (x64) and not 7+ because of the problem I described in this thread: https://boinc.bakerlab.org/rosetta/forum_thread.php?id=60579. The reversion to an older NVIDIA driver solved my problem in the current thread, but not in the older thread.

2 Vester
Can you tell me speed(clock) of you computer (this one:
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=1571856).
CPU clock (stok or overclocked) and RAM type/clock.
It is not a bug related. Just i (and few members of my team) curios how last AMD FX CPUs perform in R@H.

2 googloo
Yes. There are errors occurring due to incompatibility between R@H and BOINC 7+ exist. But this particular not one of them.

As to the bug described in the topic "exited with zero status but no 'finished' file ". It sometimes hit my computer too. I can not verify if revert to BOINC 6.x resolves the problem as I active use the GPU for crunch that require BOINC 7.x as minimum...
But I discovered what for me that error happens only when there is a lack of free RAM.
I am running 4-5 R@H WUs and 3-4 POEM WUs(hybrid CPU-GPU app) in parrallel (+ some non dc soft as it is NOT dedicated cruncher) with 3.5 Gb of RAM only. If R@H WUs use reasonable amounts of RAM(like 200-400 Мб per WU) all works fine. But sometime when package of WU with high RAM demand(500-700 Мб) come or 1 or few bugus WUs (with extreme RAM usage - up to 1 Gb each) computers runs out of free RAM and often that error occurs... (resulting in abort of all running WUs with "exited with zero status but no 'finished' file" rows in BOINC log)

May be BOINC 6.х check RAM usage of science apps more often and notice the excess of the limit for the RAM usage and correctly stops one or two calculation threads to free some RAM before a critical error occurs.
But while this is only a guess...

With Windows 7 the AMD FX-8150 was stable at 4.3 GHz, but it is not overclocked since I did a clean installation of Windows 8 a few days ago. It now idles at 3.6 GHz and runs at 3.9 GHz loaded. I downloaded and installed BOINC 7.0.28 and started having errors at stock speeds. I then uninstalled and looked for any remaining files before getting another download and installing again. I will try again since there is not a bug involved.

This computer, an HP Pavilion h9-1135 Phoenix water-cooled, was in the top 100 at one time. Each core isn't as good as the Intel i7, but there ARE 8 of them. I have 10 GB of PC3-10600 MB/sec DDR3 1333 RAM and could benefit from a memory upgrade (DDR3-1600). It runs loaded at 48 degrees C.



Uploaded with ImageShack.us

---

Vester.

How did you end up with 10gigs of ram that seems odd, are they the same type of ram sticks, if not that could be the problem if there not the same speed & timings

You could try it with 8gig of the same size & type to see if that works better.

just my 2c.

---