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.

Also - if this is the Steam version of 3dMark - you need to go and physically remove the 3dMark folder from the steamapps/common folder, as merely deleting the "local caches" sometimes leaves behind several files that can break the software - verifying local content does not fix the corrupt/left behind files either. 

So once you "remove local cache" of 3dMark - then go delete the folder from steamapps/common, and then reinstall 3dMark, and allow it to redownload Time Spy.

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.

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

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

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

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

Experiencing same issue.

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

:D Time spy
 
PhysX on GPU
http://www.3dmark.com/spy/727942
 
PhysX on CPU
http://www.3dmark.com/spy/727955
 
i'm using latest drivers
 
not much difference :D 
 
i would think it keeps a crashing because of XOC or something else having a overlay to itself,

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?

you want to Close XOC not just turn the OSD off, could well  be, try AIDA64 see if your system is stable,  leave it to run for about 10mins if it's not stable play with your CPU clocks and/or voltage might be worth trying?