Time Spy won't launch

[♥☠NotEhRabz☠♥]

Time spy won't launch. Collects system info then stalls. No AV running, even windows defender turned off.

[yapchagi]

I managed to fix the problem by changing the Refresh Rate to "Application Controlled" in nVIDIA control panel. The benchmark now runs just fine.

I have GTX 1080 2-Way SLI with 120 Hz monitor and G-Sync is on. Just change the refresh rate under nvidia control panel and u should be good after that.

[UL_Jarnis]

If Fire Strike works and Time Spy doesn't, something is preventing DX12 from working.

Verify you do not have shadowplay or 3d vision enabled in nvidia settings - that could break things, for example. Driver install can sometimes leave 3d vision on by default.

Beyond that, it could be some background application that isn't DX12 compatible.

If you have advanced edition, it may be worth seeing if windowed mode works - that would further narrow it to something that would mess with the full screen mode.

[KN]

Hi,

I had the exact same issue with Time Spy not running, and I just got it to work--all I had to do was turn off G-SYNC via the nVidia Control Panel.

Seemingly, turning off G-SYNC changed the "Monitor Technology" setting in "Global Settings" (under "Manage 3D Settings") to "Fixed Refresh" and "Vertical Sync" to "Use the 3D Application Setting." Note that "Set up stereoscopic 3D" was also turned off in the nVidia Control Panel, as was ShadowPlay in GeForce Experience. I don't have Plays.TV installed for my AMD card.

My system setup is as follows:
OS: Windows 10 Pro 64-bit, build 14393 (I'm a Windows Insider)
CPU: i7-3770k
Motherboard: DZ77RE-75K
RAM: 32GB Crucial Ballistix Sport DDR3-1600
Storage: Crucial 1TB MX200 SSD
GPU0: Intel HD 4000 -- Driver ver. 10.18.10.4425
GPU1: nVidia GTX 1080 -- Driver ver. 368.81
GPU2: AMD RX 480 -- Driver ver. 16.7.2
Other add-ons: PCI modem and PCI-e parallel port cards

Also, I have 3 monitors on the GTX 1080 (a 4K with FreeSync [primary monitor], a 1080P 144Hz with G-SYNC, and a 1024x768 small thing), 3 on the RX 480 (1920x1200, 1680x1050, and 1280x1024), and 1 on the HD Graphics (1280x1024). I'm willing to wager that if it worked for my setup, it'll also work for most other peoples' rigs. :)

EDIT: I turned G-SYNC back on and it worked per yapchagi's post above; the simplest fix is to manually add "3dmarktimespy.exe" to the 3D settings page and set "Monitor Technology" to "Fixed Refresh" and "Vertical Sync" to "Use the 3D application setting."

Interestingly, G-SYNC seems to skew the framerates of the other tests despite allowing them to run in fullscreen mode, which I suppose makes sense considering how G-SYNC works to begin with. But that's a matter for a separate topic. :P

[UL_Jarnis]

G-Sync indeed does reduce the scores slightly.

And 3DMark indeed requires it to be set to "use the 3d application setting" for refresh rate related options.

[yapchagi]

hmm...weird, now it doesn't run anymore...even with Refresh Rate set to application controlled...I forced G-Sync off, still no luck. Set Refresh Rate to 60 hz manually, still no luck. This benchmark is buggy!

[UL_Jarnis]

Well, does Fire Strike run normally? If it does, this is caused by something specifically preventing DX12 app from working.

[DarkSamus]

My findings with this issue...

Was running fine before my upgrade to Win 10 x64 (No Time Spy though obviously)

Installed new CPU (i7 6800K), ram (16GB or DDR4) and a new GPU (Upgraded from GTX 770 4GB to a GTX 1070 8GB)

After installing the parts and Win 10 I played around with Time Spy for a day.
Woke the next morning to se Time Spy removed from my available benchmarks even though Time Spy is still "ticked" in my DLC library.

It nows says that Fire Strike Ultra is the best test for my PC with no Time Spy option at all when yesterday Time Spy was my recommended test.

230+ filese just failed an integrity check in Steam, will report back after it completes re-downloading files.

[DarkSamus]

Time Spy has returned after downloading 58MB of files and re-installing system info.

http://www.3dmark.com/spy/131662

For comparison purposes...

New Build - Old Build
http://www.3dmark.com/compare/fs/9466892/fs/5240370#

[yapchagi]

yes, fire strike runs just fine.

[UL_Jarnis]

Цитата допису yapchagi:

yes, fire strike runs just fine.

Then something on your system is blocking DX12 application from running.

Known potential causes include Shadowplay, 3D vision, any kind of screen capture apps or apps that draw overlays on top of full screen apps, or any kind of remote desktop apps that again want to mess with full screen view.

[yapchagi]

I turned OSD off from PrecisionX OC, then Time Spy runs...So weird! considering that I have done it before with OSD on showing all the GPU usage and stuff and completing the benchmark and I have a youtube video to show it too.

[UL_Jarnis]

Not sure why, but any time the other app ties deep into guts of DirectX for stuff like drawing overlays, conflicts are possible. Especially with Time Spy being DX12.

[OGNocturnal]

Worked fine on my rig first run.custom clean install of latest nvidia geforce.no changes at all to 3dmark or any other settings.specs on profile if needed.the only thing that was changed was hardware except main SSD with windows etc and steam contents inc 3dmark.

[NahuelFF92]

Mine is not working, here are some lines of my 3dMark log :

12:12:20.640 ERROR could not parse dlc 3DMark Advanced state from value true,false
12:12:20.640 ERROR could not parse dlc state from value false,false
12:12:20.655 ERROR could not parse dlc state from value false,false
12:12:20.656 ERROR could not parse dlc state from value false,false
12:12:20.656 ERROR could not parse dlc state from value false,false
12:12:20.855 ERROR could not parse dlc state from value false,false

I did a clean install (both, 3dMark and Time Spy), nothing happen. Other benchs like API Overhead works fine.

[UL_Jarnis]

Those lines are unrelated. IF all other tests except Time Spy works, then potential causes that we know of are:

- Some background program that is not DX12 compatible blocking DX12 full screen. Anything with overlays or otherwise ties to DX are potential culprits.
- You do not have Windows 10 November Update (1511, aka build 10586) and are attempting to run mGPU. Won't work without nov update that has critical DX12 fixes related to multi-GPU
- Shadowplay or 3D Vision or PlaysTV enabled