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. 

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

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.

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

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.

bdary
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.

I tried that first. TimeSpy also crashed at default clocks with the OSD on and with the 375 drivers. OSD off, at default clocks OR an overclock it ran fine.

specialkone

bdary
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.

I tried that first. TimeSpy also crashed at default clocks with the OSD on and with the 375 drivers. OSD off, at default clocks OR an overclock it ran fine.

My previous post was for the OP.  Besides, if you read his initial post, you'll see that he already stated he uninstalled PrecX and it didn't work for him.

bcavnaugh
 
Maybe you can add your Score Link or at least the Score ID Number.

http://www.3dmark.com/3dm/14191860

Luta Wicasa

bcavnaugh
 
Maybe you can add your Score Link or at least the Score ID Number.

http://www.3dmark.com/3dm/14191860

Thanks This Is Why I Wanted The Link.
64-bit Windows 10 (10.0.14393) -v-64-bit Windows 10 (10.0.10586)
 
http://www.3dmark.com/3dm/12966736  64-bit Windows 10 (10.0.10586)  Fire Strike 1.1 | 10.18.13.6851 (368.51)
 
http://www.3dmark.com/3dm/14191860 64-bit Windows 10 (10.0.14393) Time Spy 1.0 | 21.21.13.7254  (372.54)
 
You must be running the latest Windows 10 build 1511 (10586) or Version 1607 for Time Spy 1.0

I'll try with OSD off, but I doubt that's the issue, I read in another forum that it has to do with core clock fluctuation?

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?

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