Rogue 560 Ti's

Now that we have a "Validation Inconclusive" tag on our results pages, it it making it easier to track down machines that are producing large numbers of invalid results or errors.

One thing I've noticed is that better than 80% of the "big" error generators are running GTX560 Ti's and the "stock" V10 CUDA app.

Those of us that haunt the forums know there were problems with the 560 Ti when it was first released but obviously a lot of people are still not aware.

What can be done ? Would it be possible for The Project to all 560 users with a general message that a problem has been discovered with these cards and advising to upgrade their app. This would also grab the "Anonymous" users that can't be reached by PM ?

T.A.

Not sure however several iterations ago the optimization app fixed this issue with 560ti's totally.

The issue is a lot of people probably don't want to install a 'third party' app on their machine for whatever reason which makes me wonder how we can solve the issue on a large scale vs reaching out to one cruncher at a time.
____________


Executive Director GPU Users Group Inc. -
brad@gpuug.org

Not sure however several iterations ago the optimization app fixed this issue with 560ti's totally.

The issue is a lot of people probably don't want to install a 'third party' app on their machine for whatever reason which makes me wonder how we can solve the issue on a large scale vs reaching out to one cruncher at a time.

Have the copyright issues with the Lunatics Optimized Apps been resolved? Can't ask 560TI users to upgrade to Opt. Apps. when they are not available to download.

Said in another thread.
Stop sending them tasks to F up.
The servers should be able to figure in no simple terms when a rig is soaking up tasks just to screw up the processing.
There is far too much of the project's bandwidth and other resources being wasted on rouge rigs.
____________
******

"Ask not, what your kitty can do for you. Ask what you can do for your kitty."

As it is kitten, so shall it be done.

I have to agree with Mark. Stop sending them tasks. It shows up you have what ever GPU card running with such and such driver. Seems it wouldnt be to hard to shut down the rogues turning in junk. I plan on using a 560Ti but not untill I get the new updates from lunatics.( When they resolve the legal issues ) And you can bet I sure will keep an eye on that card also. And as an open invitation if it starts messing up please feel free to PM and tell me.

This issue has been going on know for a while. Now that its been showing up in the new category Hopefully it will get resolved.
____________

Work should not be distributed to machines with a

Valid : Invalid ratio of 50/50 or worse
This would allow wiggle room for those of us who do pay attention to our rigs, to find and resolve problems without interrupting the work flow.
While at the same time, cutting off the jokers running on auto pilot before they have a chance to produce truck loads of bogus work.

Work should not be distributed to machines with a

Valid : Invalid ratio of 50/50 or worse
This would allow wiggle room for those of us who do pay attention to our rigs, to find and resolve problems without interrupting the work flow.
While at the same time, cutting off the jokers running on auto pilot before they have a chance to produce truck loads of bogus work.

I don't understand, I guess, why the throttling system supposedly in place does not stop them before they amass hundreds or thousands of invalid results.
Maybe it needs a bit of tweaking....
I mean, I would not get ticked off one bit if the servers cut one of my rigs off should a GPU go wonky.

Of course, if a good running rig with a big cache goes south, you are gonna have a ton of bad results as it plows through the cache. The kitties have seen that happen here once or twice. Main thing is that the servers pick up on that fact and limit the damage to work already issued.

I have to agree with Mark. Stop sending them tasks. It shows up you have what ever GPU card running with such and such driver. Seems it wouldnt be to hard to shut down the rogues turning in junk. I plan on using a 560Ti but not untill I get the new updates from lunatics.( When they resolve the legal issues ) And you can bet I sure will keep an eye on that card also. And as an open invitation if it starts messing up please feel free to PM and tell me.

This issue has been going on know for a while. Now that its been showing up in the new category Hopefully it will get resolved.

ouch ... just noticed another wave of inconclusive ... a quick look at the wingmen ... gtx 560 ti ....

Is there a thread where you guys are keeping track of who has been PMed ?

one to add to your list : 9302233 (Murat Adas) PM sent 9pm oct 21

The thing with the server side fix, which has been pointed out before and I've seen in action, is that once a person is blocked/restricted then they can just detach and then re-attach which just resets their corruption again with a new PC ID.

Cheers.

ouch ... just noticed another wave of inconclusive ... a quick look at the wingmen ... gtx 560 ti ....

Is there a thread where you guys are keeping track of who has been PMed ?

one to add to your list : 9302233 (Murat Adas) PM sent 9pm oct 21

It's "kind of" being tracked in the "Validation Inconclusive" thread. Maybe you could post this in there.

T.A.

Work should not be distributed to machines with a

Valid : Invalid ratio of 50/50 or worse
This would allow wiggle room for those of us who do pay attention to our rigs, to find and resolve problems without interrupting the work flow.
While at the same time, cutting off the jokers running on auto pilot before they have a chance to produce truck loads of bogus work.

I don't understand, I guess, why the throttling system supposedly in place does not stop them before they amass hundreds or thousands of invalid results.
Maybe it needs a bit of tweaking....
I mean, I would not get ticked off one bit if the servers cut one of my rigs off should a GPU go wonky.

Of course, if a good running rig with a big cache goes south, you are gonna have a ton of bad results as it plows through the cache. The kitties have seen that happen here once or twice. Main thing is that the servers pick up on that fact and limit the damage to work already issued.

The server code only recognizes tasks that error out as 'Errors', while tasks that fail validation at a later date (could be up to a month or two after the task is submitted) aren't counted as 'Errors'.