I don't normally complain about credits, but what is fair is fair, and this is not. My computer 74707 finished a unit within 24 hours and didn't get the 50% bonus. See link below.

http://www.gpugrid.net/workunit.php?wuid=3002036

This is a known problem with the new server/credit system.

When you get sent a resend, and both you and the first recipient return the task around the same time, after 5days from the original date of sending, the credit is averaged. My take on this is that it's a default routine in the server code, and would require significant testing, modification and debugging to sort out. It strikes me that the code is still very much CPU centric. This was looked into but at the time there was no easy solution.

This situation does not occur very often. Probably <<1% of tasks/credit are affected this way. In your case a GTX590 did not return the task until after 5days. Probably a seasonal/holiday thing. With the old system they would not have received credit. It might also be the case that this requires the original recipient to return/report the task before you. So the window of opportunity for this to occur is quite small.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

skgiven;

Thanks for explaining the error situation. I also lost credit on this one too;

http://www.gpugrid.net/workunit.php?wuid=2981843

Thanks for reporting. As skgiven explained, it's a problem which occurs when a slow card computes a result very close to the deadline, so the task is recreated. Even if the second user does the task in time, he gets the same credit as the first.

I'm looking at this, but the fix involves a change in the validation state machine and is therefore a very delicate matter.

Well, it happened to me again! See link below.


http://www.gpugrid.net/workunit.php?wuid=3103283

Still occurring :(
This issue has been known for sometime,please correct it.
WU here
Thanks.

What kind of points are you supposed to get from the long runs?
My 470@800core usually churns through the wu's in between 4.2-4.5hours, while the odd balls take 3.8hours or 5.5hours. I don't care about the points that much but was just wondering :D
Looks pretty much like this always

E: oh skgiven, noticed you have 470's also, you have an opinion on the "best" driver for 470 when running gpugrid?
I'm using 285.62 currently and seems to be working very nice indeed.
And I know I know, if ain't broken don't fix it! :D

Exactly! The best driver is the one you have, if it works ;P

260.99 is one of the earliest drivers that works with the present apps - I use this on one system.
Typically driver updates contain code to facilitate games better and fix the odd bug. While there might occasionally be an improvement from a driver, in theory, more often the improvements come from the developer apps. Quite often the extra driver code slows the drivers down; so the earlier the driver the better, unless the driver brings known improvements (faster or more stable). In the past it's been shown that you can gain a few percent in performance by using earlier drivers.

Obviously if you game then read the driver release notes and see if there is anything in the update for you specifically.

Don't forget to check your monitor too. There is no point updating to gain improvements at a resolution your monitor can't reach.

If you don't game then don't update because its probably not going to improve performance and there is always a chance that it will destabilize your system.

The more updates you install the closer you are to a failure, and when it arrives it might require substantial maintenance. Uninstall, driver sweep, reinstall, and you may even need to reinstall the operating system.

Sometimes if you have a card specific issue there might be a fix:
[GeForce GTX 590]: The GPU fan randomly spikes to 100% and then takes a few
seconds to return to normal.

Then there are some things that get taken away:
[NVIDIA Control Panel]: With extended mode enabled, there is no edit and delete
option on the NVIDIA Control Panel‐> Change Resolution‐>Customize window after
creating a custom resolution.

You would need to trawl through the release notes for such info.

295.73 is the latest driver. I know there are some reports of issues with this driver (well, when it was in its beta form) so I'm going to test this now. Some of the things that come with it I view this with caution; 'new physX software'. It's more likely to be NVidia getting ready for GF600 than helping anyone now!

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Been getting a tad weirdish points from the long runs.
Instead of the usual 35811 or something close to that I've been getting this kind of points.
Not that I care much but someone else might be getting similar and might care so figured I'd report here lol. Although I forgot to put my 470 to crunching clocks before I left for the weekend so it's at stock but that shouldnt affect points, only runtime afaik. Sorry on my phone cant rotate the scrn shot, took it from phone browser.

It happened to me again. See the link below:

http://www.gpugrid.net/workunit.php?wuid=3336817

It happened again! See link:

http://www.gpugrid.net/workunit.php?wuid=3365773

Here is the fifth (third in the last month or so) that I didn't receive the bonus for finishing a task within 24 hours. Maybe this problem is more common.


http://www.gpugrid.net/workunit.php?wuid=3376850

Seems to accord to resended wus? Perhaps it is taking the credits from the guy above. Only as hint for Admins ;)

---

DSKAG Austria: http://www.dskag.at

And now they are credited less than before ?

http://www.gpugrid.net/result.php?resultid=5347036

9 May 2012 | 10:04:38 UTC 10 May 2012 | 5:11:01 UTC
67,666.98 / 86,850.00


http://www.gpugrid.net/result.php?resultid=5351603

10 May 2012 | 23:33:00 UTC 11 May 2012 | 20:04:18 UTC
9 May 2012 | 10:04:38 UTC
72,725.98 / 57,900.00


The second is a bit slower than the other but well within 24hrs.
Has the crediting formula changed or perhaps I misunderstood it before : receive and sent back within 24hrs gives a 50% bonus and within 48hrs a 25% bonus ? Or have I missed some news regarding this ?

And now they are credited less than before ?

http://www.gpugrid.net/result.php?resultid=5347036

9 May 2012 | 10:04:38 UTC 10 May 2012 | 5:11:01 UTC
67,666.98 / 86,850.00


http://www.gpugrid.net/result.php?resultid=5351603

10 May 2012 | 23:33:00 UTC 11 May 2012 | 20:04:18 UTC
9 May 2012 | 10:04:38 UTC
72,725.98 / 57,900.00


The second is a bit slower than the other but well within 24hrs.
Has the crediting formula changed or perhaps I misunderstood it before : receive and sent back within 24hrs gives a 50% bonus and within 48hrs a 25% bonus ? Or have I missed some news regarding this ?

Your second workunit is a reissued one (the 5 day deadline was over), and you had bad luck with it, since the first host returned it before your host, and this canceled the 24h bonus on your host too. This is a known bug on the server side.

And this known bug will be fixed when ?????


To prevent this from re-occuring again you'll have to check the wu-deadline before going on.

Four months later and still no fix.
Seems rather disrespectful to the volunteer crunchers imo to react that inactive.

First I look for a interesting project (medical mostly) and then I get competitive, DC costs me about 60% of my annual electrical bill so I expect the people behind this project to do their best to keep it running as expected and should be, but this doesn't give me a good feeling.
I just lost one bonus but it's more the inactivity that restricts my staying with this project or just hop on.
And lets be clear on one thing : It's not our responsibility to take care of the software for a good running project. We can only donate our idle cpu-time.

This credit glitch is down to Boinc's new (>2years old) credit system and the Boinc server software. GPUGrid is a production research project, not a developer of server software or credit systems. It therefore relies on the server kit to have as few such issues as possible. A solution was looked for but not found. It's not likely to be fixed until new server side software containing a fix is used.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

So just check wether the first distribution of the WU wasn't to long ago when yous systems starts with it.

And this known bug will be fixed when ?????


To prevent this from re-occuring again you'll have to check the wu-deadline before going on.

Complain long enough and loud enough, and it will get fixed, sooner or later.

I doubt that very much. After getting some more info from my teammates it's clear the people behind this project lack enough respect for this projects participants imo. And that's more of a disappointment than loss of credits. Bye.