Yup that's what it was! The OSD was flaking out the test run, turned OSD off and got a finished result-
So what's up with that EVGA? Your tuner OSD seems broken then. Looks like I will roll back to an older tuner version till a new fix is applied for Timespy.
Stock settings-
http://www.3dmark.com/3dm/16075506?

Seems odd that you stated you uninstalled PrecX and it didn't work, and now the issue is solved by just turning off the OSD?
 
From original post:
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.
 
At least you got it resolved...

bdary
Seems odd that you stated you uninstalled PrecX and it didn't work, and now the issue is solved by just turning off the OSD?
 
From original post:
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.
 
At least you got it resolved...

RMA junkie :D
 
just joking with that, as i have had "timespy" problems in the past, but i have been  looking through the forums and the "RMA" is the best possible fix and that is just bizarre to me :D
 

Sean1976
Yup that's what it was! The OSD was flaking out the test run, turned OSD off and got a finished result-
So what's up with that EVGA? Your tuner OSD seems broken then. Looks like I will roll back to an older tuner version till a new fix is applied for Timespy.
Stock settings-
http://www.3dmark.com/3dm/16075506?

Glad that worked for you. Based on my experience, I think you will see that ONLY reverting to an older version of Precision XOC isn't going to solve the problem. The problem seems to be Precision XOC AND the latest few versions of Nvidia's drivers. 372.90 and 6.0.7 were working for me in Time Spy.
 
I don't think this problem will be resolved until EVGA and Nvidia have a look at it together.  I haven't tried 375.86 yet but nothing in the release notes mentioning Precision XOC issues.