Problem on GTX 560TI GPU


log in

Advanced search

Message boards : Number crunching : Problem on GTX 560TI GPU

Author Message
Stegy
Send message
Joined: 14 May 99
Posts: 3
Credit: 1,336,203
RAC: 0
Slovenia
Message 1170934 - Posted: 14 Nov 2011, 9:29:13 UTC
Last modified: 14 Nov 2011, 9:30:54 UTC

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?

Profile jason_gee
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 24 Nov 06
Posts: 5087
Credit: 74,249,189
RAC: 6,676
Australia
Message 1170945 - Posted: 14 Nov 2011, 11:42:43 UTC - in response to Message 1170934.
Last modified: 14 Nov 2011, 11:47:52 UTC

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

Stegy
Send message
Joined: 14 May 99
Posts: 3
Credit: 1,336,203
RAC: 0
Slovenia
Message 1177104 - Posted: 10 Dec 2011, 17:35:12 UTC - in response to Message 1170945.

I did run OCCT for GPU - shader complexity 8 for 2 hours. Test did not return any errors. Currently I have 10 valid and 71 invalid work units. So what is the problem (in the mean time I did also reinstall system).

Is there bug in seti@home cuda fermi edition (6.10)?

Profile Slavac
Volunteer tester
Avatar
Send message
Joined: 27 Apr 11
Posts: 1932
Credit: 17,952,639
RAC: 0
United States
Message 1177106 - Posted: 10 Dec 2011, 17:43:19 UTC - in response to Message 1177104.

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

Profile DMMD
Avatar
Send message
Joined: 14 Feb 00
Posts: 86
Credit: 55,934,608
RAC: 0
Message 1177107 - Posted: 10 Dec 2011, 17:50:41 UTC

Interestingly, the stock Vcore on the EVGA 560ti twin is 1.065 V.
At that it is stable to the rigors of 41g.
Very interestingly as well, is the decreased performance hit to using HT and NOT reserving logical or physical cores (resource contention) on this and the gtx 580 under the beta nvidia driver 290.36 and 41g.
At least on the 560ti twin, the increased CPU load with the > 270 drivers is also not seen using Raistmer's AP masterpiece. I cannot speak to the thread safe issue under this config.....yet.

The strategic use of HT et al, at task request time is NB..........

Profile Tim
Volunteer tester
Avatar
Send message
Joined: 19 May 99
Posts: 205
Credit: 252,293,832
RAC: 88,762
Greece
Message 1177114 - Posted: 10 Dec 2011, 18:30:47 UTC - in response to Message 1170934.

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.

____________

Profile Fred J. Verster
Volunteer tester
Avatar
Send message
Joined: 21 Apr 04
Posts: 3252
Credit: 31,903,520
RAC: 119
Netherlands
Message 1177176 - Posted: 11 Dec 2011, 1:34:17 UTC - in response to Message 1177114.

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.



In the past months, I regurly encountered the GTX560Ti, unfortunatly by procusing errors. (Core-GPU-Frequency is quite high, 1.8GHz. compaired to
other FERMI GPUs. The 470 runs at 1.201GHz, the 480 @ 1.400GHz. Ofcoarse
you can OC them, but some app.s can/will crash, f.i. GPUgrid, already has a
higher GPU load, but still needs a (fast)CPU. When i upped speed from
1.4G to 1.6GHz. the WU (Long runs-8 - 12 hours on fastest card), crashed.

And on SETI, it was a (little) bit faster. Not noteworthy, though.
(I'll add the AstroPulse NVIDIA app. rev521, now)


____________

Bree
Send message
Joined: 7 Feb 00
Posts: 9
Credit: 12,468,505
RAC: 0
United States
Message 1177210 - Posted: 11 Dec 2011, 9:22:46 UTC

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 .
____________

Profile Slavac
Volunteer tester
Avatar
Send message
Joined: 27 Apr 11
Posts: 1932
Credit: 17,952,639
RAC: 0
United States
Message 1177291 - Posted: 11 Dec 2011, 18:29:17 UTC - in response to Message 1177210.

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 .


Bump your voltage up slightly, that should solve the DC issues.
____________


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

Stegy
Send message
Joined: 14 May 99
Posts: 3
Credit: 1,336,203
RAC: 0
Slovenia
Message 1178440 - Posted: 16 Dec 2011, 8:55:26 UTC - in response to Message 1170945.

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)

Profile MikeProject donor
Volunteer tester
Avatar
Send message
Joined: 17 Feb 01
Posts: 25202
Credit: 34,821,834
RAC: 21,442
Germany
Message 1178456 - Posted: 16 Dec 2011, 10:32:59 UTC


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

____________

Profile jason_gee
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 24 Nov 06
Posts: 5087
Credit: 74,249,189
RAC: 6,676
Australia
Message 1178464 - Posted: 16 Dec 2011, 11:32:51 UTC - in response to Message 1178440.
Last modified: 16 Dec 2011, 11:48:46 UTC

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)


Hi there,
I've been working extensively with some members of the GPU Users group to nail these tricky cards down completely, and we believe we have them more or less mastered now (Thank's Slavac! :D). Mine's never missed a beat since installed, straight out of the box, so it's been a challenge ;)

Our evolving checklist mostly involves the following for these cards, some of which will have already been covered.

- Ensure your PSU has sufficient current on the +12 volt rail (At least 30 Amps per 560ti card, plus whatever the rest of you system needs peak)
- If factory overclocked, raise the GPU Vcore (check)
- physically reseat the card(s) & connectors.
- Install later drivers, Use the 'clean install' advanced option (yours are old)
- avoid applications not compatible with the newer drivers (i.e. stock cuda_fermi & beta OpenCL applications & other projects that have non threadsafe applications), your stock one predates 560ti by a year or more, try the Lunatics optimised one (x41g) which is significantly more robust & threadsafe for snoozing & exiting tasks without triggering weird issues.
You'd want the 64 bit installer from Lunatics Windows Downloads
- If errors still persist, there could be some driver caching old code still to go searching for & clean out, though the above approaches have solved some really weird issues already.

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

Message boards : Number crunching : Problem on GTX 560TI GPU

Copyright © 2014 University of California