Problem on GTX 560TI GPU

Hi Stegy,
The current school of thought is that some of these factory overclocked 560ti's need some extra GPU core voltage for stability running Cuda, the theory being that the manufacturers may have spent the effort getting them 'game stable' but overlooked Cuda/PhysX stability.

I would suggest to use something like nVidia Inspector or MSI Afterburner to put the core to 1.065Volts, and see if you get any further issues to look into after that. An alternative is to use the same program(s) to lower the clocks from the factory defaults.

For Artefact Scanning & pushing the card I use OCCT on maximum complexity for 1 hour. zero artefacts under that amount of pressure for that duration is, IMO, truly stable enough. In the longer term I'm considering turning some of my Cuda test pieces that use Seti algorithms into some kind of stress test & bench, since some kernels have been shown to push fairly hard, though doing that right is a way off.

In addition you may have better luck with newer application builds, plenty of help is available here if you consider it practical to keep an eye out for updates from time to time.

[Edit:] beyond that, there is a whole evolving checklist of things to look it in the system. While I've had no problems running my own 560to out of the box at 900MHz, I do know of one with ongoing issues, and a few that have solved theirs with care.

Jason
____________
"It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change."
Charles Darwin

Hey Stegy:

My 560ti was also throwing errors/invalids just like yours. The good news is Jason's work has almost totally eliminated my errors/invalids. Have faith, very smart minds are on this. I am not one of them. ;)
____________


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

I have Gigabyte 560 Ti card.

I did noticed, that several results are invalid (SETI@home Enhanced v6.10 (cuda_fermi))

http://setiathome.berkeley.edu/results.php?hostid=6238994&offset=0&show_names=0&state=4&appid=

I did see, that several user have issues with Cuda.

Is there any program, that can check if GPU (Cuda) calculations are OK?

I have Gigabyte 560 Ti card.

I did noticed, that several results are invalid (SETI@home Enhanced v6.10 (cuda_fermi))

http://setiathome.berkeley.edu/results.php?hostid=6238994&offset=0&show_names=0&state=4&appid=

I did see, that several user have issues with Cuda.

Is there any program, that can check if GPU (Cuda) calculations are OK?

I use to have the same problem with one of my rigs. ID: 6022669

I have 2 gtx560tis. One with stock clock 823Mhz and one with manufactured over clocked to 900Mhz. The 900Mhz was sending invalid results. Not always but often.
After many-many tests i downclock the 900Mhz to 823Mhz, and is running perfectly since then.

Maybe you can do the same just to test the card.

Have a Gigabyte 950 it runs great as LONG as you don't let it down shift to a lower speed ie there set to down clock automatically. so when going from 950 to 600 then 300 then 50... the first time it shift it would throw a WU into error. if i didnt let it down shift then it was ok.. upshift seems to not bother it. just the down shift. had to make a rule as long as boinctasks is running and or boinc manager is running then DON'T down shift.. that worked pretty well . still get errors once and awhile but its from changing WU's during long no work periods.

the card bothers me as it decided , running seti and its been on 5 mins. DOWNCLOCK to 50 mhz. also have talked to others that changed the parameters of the card to only allow the cards max speed at all times. only thing left on is shift in the power <autovolt and auto load sence> so you still get some savings vice a full on card all the time . that fixed it according to some others i have talked to .

I suggest to downclock the core speed just to see if you get valid results.
Thats what i did with a frineds card.

____________

I did set voltage on my 560ti video card to 1.065V, but I still get invalid results in my results for CUDA. So what can I do, that I wont get any invalid entries any more. (OCCT also did not return any errors in stock voltage)