GV-N560OC-1GI Also known As The Gigabyte 560

[The_Soldier]

So what can I say? As an Nvidia fanboy I went and got this card as I thought the Palit 460 was the pups nuts. Overclockable was an understatement.  So I got my card and I have to say this too over-clocks.  But into the second day I started to get the white and black flashing screen on BC2 which as I have found out was to do with TDR's.  I also started to get crashes on other apps like 3d mark11. With all of this happening I have underclocked it to the Nvidia stock clocks as opposed to the overclock by gigabyte.
The question I have for gigabyte is when are you releasing a new bios to sort out this and many other problems with the 560.  Obviously with the drivers being in their infancy this is also a factor and so when are getting a driver update?
Over at the Nvidia forum it seems that this card is popping up over and over again.  Come on gigabyte we want answers and a solve for all the crashes. Many thanks..

[The_Soldier]

Ok I have found a solution which maybe what the problem was with all the gigabyte cards... basically a bad overclock. I have now got an overclock with mine. Pics are attached...
As you can see I have bypassed the gigabyte overclock and everything is stable. Apps and games that would not run (3dmark11, bc2) now run perfectly fine and the card reaches a top temp of 78 degrees after half hour of stress testing with bc2 which slams the core at 99% and never drops.

I suggest cranking up the voltage because I honestly think that is the reason why the overclock that comes with the card is unstable. You can also see I have dropped the memory after cranking up the core..
Let me know how you get on...

Forgot to mention that Heaven still crashes but not because of a driver restart which indicates it is not the voltages or card but the actual driver...

[Dark Mantis]

Well I am glad to see that you managed to find a solution to the problem. If it was that straightforward though why hasn't Gigabyte sorted it yet?

[The_Soldier]

lol.. you tell me? Being a keen builder and overclocker I just assumed that seeing it was a factory overclock there would be no major issues and that when apps/games crashed that it was due to the driver.  BUT, it wasn't till I actually thought about past experiences when it comes to overclocking that 9 times out of 10 when you see the driver stopping/restarting then (within overclocking) it was usually it did not have enough juice to keep up or an overclock where you have overshot the sweet spot so to speak.  You've seen the pics... you've seen the overclock.. Everything works BAR Heaven.. but with Heaven the driver doesn't stop it actually comes up with a dx11 driver problem (within Heaven) and not an Nvidia driver stop/restart..

So you tell me mate? Or have I just got lucky?

[Dark Mantis]

Well we shall see won't we?