Did you remove all drivers before installing the new card?

Two things can cause the error you're receiving.
 
#1 An unstable video card.
#2 Corrupt msi afterburner/precision x installation.
 
Here is what I suggest you do to try and figure out where your problem is coming from...
 
#1 Perform a clean installation of video drivers.

1. Uninstall Precision X/Afterburner if installed, make sure to select "no" to saving profiles if asked.  Reboot the PC now if you had to uninstall PX or Afterburner.
2. Download & save graphics driver 353.06 to your desktop. Run the graphics installer located on your desktop once the download is complete. 
3. Select custom advanced install, under custom installation options uncheck all options except the physx system software, if you have a 3D capable monitor and would like to use 3D at some point please select both 3D options, check mark perform clean install, then click next to install the driver, reboot when asked.
4. Do not reinstall msi afterburner/precision x at this point.

#2 Rerun 3dmark. No more crashing/error here means you had a corrupt msi afterburner/precision x installation. You can now safely reinstall msi afterburner/precision x, do not install both choose one or the other, I recommend afterburner but you can choose whichever you like.
 
If you're still crashing/receiving the error after removing msi afterburner/precision x & performing a clean installation of video drivers due the following...
 
#1 Install afterburner.
#2 Downclock the card by setting the core & memory offsets to -105. Click the apply button to save the changes. Leave afterburner open while rerun the benchmark with the card downclocked. No crashing here means your factory overclock on your card is unstable. You can choose to RMA the card due to faulty factory overclock (highly recommended), try increasing/decreasing the voltage at factory clocks to see if it helps stabilize factory clocks, or leave the card downclocked and just deal with it and loose a bit of performance.

No problem. Yes, 347.88 is a typo. 

There is a newer driver that supports the 980 ti that you could try out here: http://nvidia.custhelp.co...swers/detail/a_id/3676

It's only meant to fix gsync errors, but i have had no TDR crashes so far using 353.12 (had countless TDR crashes with 352.86 and 353.06).

Thanks for the tips guys. I don't have a ton of time to test at the moment but I'll download the new driver and see if it helps the issue.

having same issue here. games will be stable at much higher clocks but firestrike will randomly crash. one time it crashed the very second the it started so its not heat at all. sometimes I can even run it with higher clocks and it does fine then come right back with lower clocks and crashes with the error in the OP. several times even the 3DMark GUI just stopped working. 

I don't know if this helps, but I read somewhere disabling 'use hardware acceleration where possible' in your browser settings (I use chrome) will stop the black screen crashes. 
 
So far it has worked wonders for me, though YMMV.

I just bought my 980 ti SC and just got this same exact problem (while running stock)
Apparently, 3Dmark will only crash if you have the precision software open + the system monitor while doing the benchmark

sniper260687
Ever since i got the GTX 980 ti i been getting game crashes everywhere, usually after 30 to 40 minutes of play.
 
Game freezes but sound continues, i cant even crt+alt+del i have to manually pushed the power button :/

Trying waiting a full minute or two and you're screen will come back. My old 980 FTW did this and if I waited a minute or 2 the screen would come back.

sniper260687
Ever since i got the GTX 980 ti i been getting game crashes everywhere, usually after 30 to 40 minutes of play.
 
Game freezes but sound continues, i cant even crt+alt+del i have to manually pushed the power button :/

 
I'm getting this too in Witcher 3. Also TDR crashes with GTA V.
Stopped using Precision x and switched to Afterburner and closed Nvidia Experience and this seems to be better. 
 
With even a slight OC in Precision X (+100 Clock +100 Mem) I was getting TDR crashes every 5-10 mins in GTA V and same freezing screen and quit to desktop in Witcher 3.
 
Significant FPS drops in GTAV too (60 FPS to 45 or so in some areas, Vsync on, 2560 x 1440, 60 Hz monitor)
 
This card seems very unstable at the moment...

Hey guys!
 
New 980 ti SC owner here.  So my card seems to run just fine, until I install Precision X.  After that, driver crashes constantly.  If I uninstall Precision X, 3DMark FireStrike demo runs fine, and without errors.
This card replaced a ref 680 GTX.  I uninstalled the drivers before removing that card, and installing the 980 ti.  I did not uninstall Precision X prior to the new card install.  I have uninstalled Precision X and reinstalled, but still get the crashes with it installed.
 
Also, I'll snag the new drivers, see if that helps.
 
Any ideas?

steve00961
Hi all. I purchased the 980 sc back in November and had this issue from day one. Spent well over 2 months the trying to find the solution and in the end did an RMA. Replacement card came same problem. Finally a simple fix, install precision x and down clock by 50mhz. Bit ridiculous if you ask me that I need to downclock the factory setting, but not had a single crash since. Hope this helps.

Hi, 
Still using the 980 sc acx 2.0, was going to step-up to 980 ti stock clock version but after using percX 16 to downclock a whopping 139mhz i stopped getting TDR's in "warframe", but stutters on high frame rates!
May be over underclocked so i will try your 50mhz so my question is did you both after burner & precX16 installed & which did you use for underclock?
 
GTX 980 SC ACX 2.0 

[SOLVED]  EVGA 980ti SC ACX 2.0+ overclocking is not stable. I had this problem where my PC was crashing every time I play Rocket League.  I managed to solve it using Precision X and lowering the Power setting to 95%. lowering the clock speed did not work for me.
 

DRY_ICE
So I just received my EVGA GTX980 Ti and decided to give it a test run. I ran the 3d Mark Demo primary tests to see how it runs. I got to the Firestrike demo and part of the way through suddenly the program crashed and I received a display driver crashed error in the task bar (Using 353.06 NV driver - clean install). I checked HW Monitor as well as Precision X and the Temp never went above 66C. The card is not overclocked and brand new replacing an EVGA GTX780 which never gave me this issue before.
 
My questions: How concerned should I be at this point? Is this a sign of bad things to come?
 
Attached below is the error log thrown up by 3dMark...................

Unexpected error running tests.
Workload work failed with error message: eva::d3d11::rendering::deferred_scene_renderer::render(): Exception thrown in worker thread.

Type:
class eva::d3d11::function_error

What:
draw_unshadowed_illumination_task for thread 1: File: device_context.cpp
Line: 818
Function: struct ID3D11CommandList *__cdecl eva::d3d11::deferred_device_context::do_finish_command_list(bool)

Expression: native()->FinishCommandList( restore_deferred_context_state, &result): DX11 call failed [-2005270522].

Device hung due to badly formed commands.
DXGI_ERROR_DEVICE_HUNG: ID3D11DeviceContext::FinishCommandList: