I know this does not apply to all but it does to the majority!
Yes, I too fell victim to this dreaded problem.  I tried everything I could think of.  The motherboard was of a vintage that this card should not have had any issues.  I updated the BIOS, video drivers of every version all to no avail.  I reseated all internal components, updated the PSU none of which made the problem any better.  I looked into TDR issues, driver conflicts etc.  I combed over dump-logs finding references to drivers and services of which are discussed at length on the internet in countless forums.  Nothing helped.  I was about to request an RMA when . . .
 
 . . . I sat and pondered the problem.  I pondered about in the old days, code was neat and clean.  When software engineers were careful as to where they placed their code.  Blue Screens were easier to diagnose for the reason that a Blue-Screen is a memory issue.  It now, as it always has been.  I am not speaking of memory either being good or bad but, of memory and how it gets allocated and scrutinized by the software that gets loaded into it.
 
Sometimes, just the load order can make a difference between software that works and software that does not.  When a piece of code was currently injected into a specific memory location, any subsequent write operation checks all current allocated cells.  Should a cell be currently in use, another unoccupied cell was located and utilized?  Code is no longer written as carefully as it was in the past.  If a .dll is currently in memory, current code practices often stomp all over it.  Gone are the days of pure Assembly. 
 
Assembly is a thousand times, smaller, a thousand times faster, and a thousand times cleaner.  Every code writer must check and re-check the stack and make sure that everything is correct.  In contrast these days, code is just not as clean and to add to the issue, most, but not all peripheral cards have been stripped of their on-board processors relying on the system’s CPU for instruction cycling.  Of course our video cards have on-board however, and the point is all the hand-shaking that goes on in a modern day computer is overwhelming to the best of systems.  Speed is not everything, efficiency and good code is the key.
 
The one thing that is often overlooked is this, when software is developed regardless of what it does, the manufacture has a preliminary test-bed system which is void of most of the crap that makes its way onto the average user’s computer.  They have to assure that their product/drivers are the only thing running or that little else is installed that might interfere.  It then makes it way to systems that are perhaps loaded with crap but still not bogged down with all the garbage that is on the typical computer.  They must do and assume this position to test their product.  They cannot test on a system with 50-million possible combinations of others poorly written software.  They must have a clean system to see just how their poorly written software performs.  Often their code for what ever reason, actually works and they stand behind it. 
 
After looking into my situation, I realized that I am guilty of performance-tweaking as are many if not most users.  Having every piece of software to available to check everything from Frame-Rate, Temperatures, Voltages and so on all for bragging rights I guess.  I just as reluctantly as most of you cringed at the thought of blowing away the OS start from scratch.  We’ve put so many countless hours into setting the system up and tweaking it until we were more-or-less satisfied that our system X-Mhz faster than Joe’s computer.
 
I decide to take the plunge and rebuild the system.  God I hated to do this . . . However, I did in fact recall all the software I had installed, over that past couple of years only to patch with countless updates and again to remove regretting what the registry must look like.  Another complaint of mine with regards to poorly written code:  If you placed in my registry then DAMIT, remove it.  This is another area for which software developers fail . . . Cleaning the registry after removal.  Of course some CLSIDs or other encrypted keys are created and the software/developer would have no idea as to just exactly what to remove.  You’ll notice that a typical self-help driver fix tutorial will almost always have you empty the registry of specific software related keys but there are always residuals.
 
Listen, it is a fact that, Hardware developers DO NOT sell you Beta-ware products as do Software developers . . . like the games we play.  Their code may not be perfect but, you must give them a break and refrain from bashing their products.  As for the Software engineers, well, they need to simply stop sucking their 64oz Big Gulp and write some serious code.
 
In conclusion, after reinstalling the OS and eliminating all the crap and you know to whom and to what I refer, the GTX 780 works flawlessly.  After applying all MS-Hotfixes (which scared me as well) the card is still functioning perfectly without Black Screens, Blue Screens and without Flicker or Stutter.  The fluidity of the game screens attests to this fact and I don’t need FRAPS or ASUS AI or anything else to verify that my machine is still faster than Joe’s.
 
Thank you EVGA for this great video card!