1) Message boards : Number crunching : [coproc] message spam in boinc log (Message 44268)
Posted 5 days ago by Profile Retvari Zoltan
These messages showing up because you've turned on coproc_debug in the cc_config.xml file.
2) Message boards : Number crunching : "This computer has finished a daily quota of 3 tasks" - impossible ! (Message 44265)
Posted 5 days ago by Profile Retvari Zoltan
You can't do anything about it, just wait.
Your host received a couple workunits from the bad batch named ADRIA_2OV5_CONF_CLOSED, and these failed workunits used up the daily quota of your host. This host will receive work from the server only tomorrow.
3) Message boards : Number crunching : ADRIA_2OV5_CONF_CLOSED (Message 44264)
Posted 5 days ago by Profile Retvari Zoltan
That's a bad batch, all workunits from this batch have failed on my hosts too.
4) Message boards : Graphics cards (GPUs) : New Gianni tasks take loooong time... a warning (8-12-16) (Message 44245)
Posted 8 days ago by Profile Retvari Zoltan
So it looks like a GTX970 (at stock on a weak system) will take 31 to 32h to crunch these on Linux-x64. That suggests the WDDM overhead for these is at least 12.5% but probably closer to 16%.

A GTX980 is ~17% faster (stock) than a GTX970 so would still take over 24h to complete on Linux (over 26h). If it was overclocked by ~10% then it might be able to just about complete inside 24h if the system was tuned to do so (SWAN_SYNC used, high CPU clock and fast RAM...).

GTX 980 @ 1388MHz, GDDR5 @ 3505 MHz, i3-4160, WinXP, SWAN_SYNC on, no other tasks: 19h 24m 26s
It's almost (~8m) missed the 24h bonus, as it spent 5h 28m in the queue.
5) Message boards : Number crunching : How much bonus credits for reporting WU in under 24 hours? (Message 44244)
Posted 8 days ago by Profile Retvari Zoltan
I've heard there's a bonus for receiving and reporting WU's in under 24 or 12 hours but couldn't find any details. Can someone please explain?
There are two levels of bonus:
+50% for returning the result under 24 hours
+25% for returning the result under 48 hours
6) Message boards : Number crunching : Error after 4 Hours (Message 44241)
Posted 9 days ago by Profile Retvari Zoltan
Here is the task in question: https://www.gpugrid.net/result.php?resultid=15241975

It seems that the WU got unstable and terminated, but I have no idea why. No OC'ing,

Your card is factory overclocked, as according to the specifications of the GTX 980Ti on NVidia homepage its default base clock is 1000MHz, while your card's is 1190MHz according to the task's log:
<stderr_txt> # GPU [GeForce GTX 980 Ti] Platform [Windows] Rev [3212] VERSION [65] # SWAN Device 0 : # Name : GeForce GTX 980 Ti # ECC : Disabled # Global mem : 4095MB # Capability : 5.2 # PCI ID : 0000:01:00.0 # Device clock : 1190MHz # Memory clock : 3505MHz # Memory width : 384bit # Driver version : r372_53 : 37254

While it is not too much - as my GTX980Ti's are running at 1380-1400MHz - it could cause these errors if the GPU voltage is not appropriate for this frequency. Raising the GPU voltage however, will raise the GPU temperature, so it's better to reduce its frequency and/or temperature.

good PSU (Corsair HX750i), no shut downs or graphic glitches, and good cooling (GPU temps are 72C constant on 23C ambient).

Check the GPU voltage by a GPU monitoring tool like GPU-Z, Nvidia Inspector or MSI Afterburner. Setting a more aggressive fan profile to further decrease GPU temp could fix this error.
7) Message boards : Graphics cards (GPUs) : NVIDIA GT730, AMD FuryX for GPUGRID? (Message 44234)
Posted 9 days ago by Profile Retvari Zoltan

On the server status page: http://www.gpugrid.net/server_status.php

What does mean the 'error rate'?
Does this mean 22 - 56 % of the WUs finish with an error and no Credits will be granted for the calculation time?

Results marked as invalid, and workunits failing during the processing won't receive any credit.
The error rate of the different batches are more likely the error rate of the hosts processing them, not of the workunits themselves. The error usually happens right at the start of the processing, thus there are only failed workunits in the stats until the first valid results are returned (8-10 hours). So that's why the error rate starts high (above 90%) for every batch, then normalizes to ~22%. That ~22% of the hosts are using unsupported GPU, or have bad drivers, or their GPU is overclocked too much. The only known error in the GPUGrid app is if there's a dirty shutdown and the host has a fast GPU then the files needed to restart the calculation get corrupted, and either the WU will crash at restart, or restarts from 0% and the result will be invalid.
8) Message boards : Graphics cards (GPUs) : NVIDIA GT730, AMD FuryX for GPUGRID? (Message 44233)
Posted 9 days ago by Profile Retvari Zoltan
Because of my last question...
During this 5 days deadline the Credits/task will be always the same, or within 1 or 2 days upload/report and a bonus will be granted (after reading old messages in the forum) - this will still happen?
These days how big is the bonus and within which days?
So during this 5 days deadline the granted Credits will be always the same? No bonus because of quicker upload/report - within few hours or days?

These bonus rules are still applied, so +50% for returning the result within 24 hours, and +25% within 48 hours.
The granted credit is the same for every WU from the same batch, there are only two levels of bonus.

My GT730 finished this WU in 3 days + 20 hours + 50 minutes:
Long runs (8-12 hours on fastest card)

That's OK, or it should be faster?

It's OK for an OS with the WDDM overhead. You could try to set the SWAN_SYNC environmental value (it would make the GPUGrid client to use a full CPU thread/core), but it would have a little effect on a GT730. Also, you can try to suspend CPU crunching to make GPUGrid crunch faster.

It looks like the GPUGRID WU (1WU/GPU) made the GPU ~ 5 °C warmer - that could be?
GPUGRID WUs use the VGA card 'harder' than e.g. SETI (2WUs/GPU), Milkyway (2WUs/GPU), Einstein (1WU/GPU)...?

Exactly that's the reason.

What happens if the result will be uploaded/reported after the deadline - and if the wingmen didn't uploaded/reported in the meantime, the result get Credits granted nevertheless?

Yes, it's a bug in how the scheduler works. Both parties will receive the same credit, so the wingman will receive the credits without bonus if the first one returns the result while the wingman is still processing it.
9) Message boards : Number crunching : 8 hours, 42 minutes elapsed, 3 hours CPU time (Message 44226)
Posted 10 days ago by Profile Retvari Zoltan
I'm running two jobs on my main crunching PC, the new GAINNI work units and

The CPU tasks have been running World Community Grid (UGM).
My task manager says nothing of note is running in the background.

Do you mean that not even the WCG tasks?

Both tasks have a major discrepancy between elapsed time and crunching time.

What do you mean by "elapsed time" and "crunching time"?

This is a new problem for me, I'm pretty sure it wasn't happening a week ago.

Advice would be appreciated.

If the above two is what you can see on the task list page of your hosts, then this discrepancy in "CPU time" and "Run Time" is normal for a host without the SWAN_SYNC environmental value.
10) Message boards : Graphics cards (GPUs) : Don't understand why it is failing (Message 44221)
Posted 10 days ago by Profile Retvari Zoltan
Thanks for that info! I tried searching for that message but never found a good explanation of what it was trying to tell me.

There are a couple of useful threads for novices in the FAQ, for example:
FAQ - Recommended GPUs for GPUGrid crunching
However, this error message is not listed there.
You should try to use the advanced search, and extend the time limit for the search for more results.

Out of curiosity, BOINC tells GPUGRID what card I have. Why doesn't GPUGRID throw an error /before/ it sends the work? I feel kinda bad that I took up work that just errored out like that.

That's just sloppy business from GPUGrid's part, you should not feel bad.
This behavior applies to the brand new GTX 10X0 cards as well, because these are CC6.1 cards, and fail every workunit with the same error, still the GPUGrid scheduler will send them work (until their daily quota reaches 0).

Next 10