Since I moved up into the 372. driver family, TimeSpy errors out shortly after the Demo everytime. I don't know if this is due to a corrupt SystemInfo file, or what, but I have un-installed 3DMark several times as well as tried several different drivers from 372.70 - 375.76, with no success. I have also un-installed Evga PrecisionX OC 6.0.8 thinking it could have to do with the tuner.
No dice, I get half way through 2nd graphics test in TimeSpy, then it just errors out with a 0 score. Some users have said it has to do with the core clock fluctuating throughout the tests, but this is not a problem in Firestrike Benchmark. Any ideas on troubleshooting this would be helpful
Sean J. 

It could be to high of an Overclock on the CPU or the GPU or Both.
We have not had the best Drivers for a while now from NVIDIA so it could all be the New Drivers.
For me I have found that Driver 368.81 is the most stable Driver out ATM.
Is this Score Current? http://www.3dmark.com/3dm/12966736
TimeSpy is also the Only DirectX 12 Benchmark that I know of ATM.
Are you running the Current Version of TimeSpy. v2-1-2973 is the current version.

Have you ever run Time Spy successfully?
Anything in event viewer when it errors?

Luta Wicasa
Have you ever run Time Spy successfully?
Anything in event viewer when it errors?

"Since I moved up into the 372." But the OP has not Posted and older run.

bcavnaugh
But the OP has not Posted and older run.

 
That's why I asked....he only has his July run of FS in his sig. No mention of any previous Time Spy runs at all.

My Timespy crashes but firestrike works still I will be glad to have a new great driver for Dec.

I've been using 372.90 since release with no issues. Onliest time it fails Time Spy is when I push too hard

Yeah I have a few successful TimSpy scores 6650-6700 score but with the 368 driver family. Running same OC's as with this run just with 368.95 driver.
Yes the Firestrike in my signature is current, its with an older driver but its my best score ran.

Are you running the OSD in Precision XOC when you run TimeSpy? If yes, try turning it off and TimeSpy will likely run successfully to completion. I was having the same problem but with the OSD off TimeSpy ran fine.
 
I don't think the problem is specific to a version of Precision XOC. 6.0.7 used to work fine for me but before I disabled the OSD I tried 6.0.7 again  and it now crashes TimeSpy with OSD on. I think the problem is a combination of Precision XOC OSD and the latest Nvidia driver sets. I didn't go back and try the older drivers but if I remember correctly the 372.90 drivers and Precision XOC with OSD ran TimeSpy fine for me. So the problem might be the 375 Nvidia drivers.

You could try running Time Spy with default GPU clocks just to see if it completes.  That may shed some light on this.  Sometimes as newer drivers come out for newer generations of GPU's, they make performance improvements which can cause a once stable GPU OC to no longer be stable under certain circumstances.