3DMark
Time Spy won't launch
Time spy won't launch. Collects system info then stalls. No AV running, even windows defender turned off.
< >
Wyświetlanie 76-90 z 98 komentarzy
Lucille 9 kwietnia 2017 o 10:49 
Same now here, after upgrade to Windows Creator Update I get stucked at Collecting System Info!

When deactivating System Info, then it get stucked at Benchmark running, of course without running it... ;)
Ostatnio edytowany przez: Lucille; 9 kwietnia 2017 o 10:50
Lucille 9 kwietnia 2017 o 11:02 
Reinstalling solved this.
Doesn't solve my issue with not starting Time Spy.

Always the same error, no matter if I deactivate Anti-virus, reinstall, change desktop resolution, etc.
API Overhead feature test runs...

Oooops error message:

File: dx_shader_compiler.cpp Line: 282 Function: class std::unique_ptr<class eva::graphics::shader_reflection,struct std::default_delete<class eva::graphics::shader_reflection> > __cdecl eva::graphics::dx::dx_shader_compiler::reflect_shader(const class eva::graphics::shader_bytecode &,const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &) const Expression: D3DReflect(bytecode.pointer(), bytecode.size(), IID_ID3D11ShaderReflection, reinterpret_cast<void**>(native.receive())): DirectX call failed [-2005530516]. :
Ostatnio edytowany przez: Phoenixflieger; 2 maja 2017 o 13:56
UL_Jarnis  [producent] 3 maja 2017 o 0:46 
Shader cache corrupted.

Delete compiled shaders folder at

yoursteamfolder\steamapps\common\3DMark\dlc\time-spy-test\
THX! Solved.

I did deinstalled 3DMark earlier and re-installed it, but looks like you have to wipe clean all folders manually instead of using a deinstaller.

Now I know that DX12 games are not something I have to look forward to with my current 4-5 year old system.
NirvashOne 1 sierpnia 2018 o 9:20 
hate to revive a dead topic but im encountering this error aswell. All other benchmarks run fine except time spy DX12. tried deleting the shader folder to no avail.



Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: Z97X-UD5H-BK
BIOS: F8 (type: UEFI)
Processor: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
Memory: 16384MB RAM
Available OS Memory: 16292MB RAM
Page File: 7599MB used, 11124MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 120 DPI (125 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.17134.0001 64bit Unicode

GPU is a 1080ti with the latest drivers
Ostatnio edytowany przez: NirvashOne; 1 sierpnia 2018 o 9:21
yapchagi 2 sierpnia 2018 o 0:39 
oh wow i actually don't remember how i fixed mine
UL_Jarnis  [producent] 3 sierpnia 2018 o 2:37 
Początkowo opublikowane przez Rägnarök:
hate to revive a dead topic but im encountering this error aswell. All other benchmarks run fine except time spy DX12. tried deleting the shader folder to no avail.



Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: Z97X-UD5H-BK
BIOS: F8 (type: UEFI)
Processor: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
Memory: 16384MB RAM
Available OS Memory: 16292MB RAM
Page File: 7599MB used, 11124MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 120 DPI (125 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.17134.0001 64bit Unicode

GPU is a 1080ti with the latest drivers

Most likely a background program interfering. Email a result file from a failed run to info@futuremark.com and I'll take a look. Autosaved files, even from failed runs, are in Documents/3DMark/
NirvashOne 5 sierpnia 2018 o 0:46 
sending the latest failed run in now
NirvashOne 5 sierpnia 2018 o 0:47 
PCMark10 also fails
FireFlower 14 czerwca 2020 o 18:31 
Timespy won't launch for this reason also: You have made custom resolution for your display (overclocked profile) with nvidia control panel. Return to any regular standard resolution & refresh rate will fix this issue.
UL_Jarnis  [producent] 15 czerwca 2020 o 5:02 
This is true - overclocked display panels are not supported. Sorry.
e33et 15 czerwca 2020 o 6:23 
Początkowo opublikowane przez UL_Jarnis:


I've also got issue since the last update, my specs are,

AMD Ryzen 7 2700X, 32GB @3000MHz, 2x 1080 8GB SLI, recently updated nvidia drivers and deleted shader folder,

Only Firestrike works not Time Spy and i'm on lastet Windows 10 Pro x64 updated!

Kind regards
e33et
Ostatnio edytowany przez: e33et; 15 czerwca 2020 o 6:25
UL_Jarnis  [producent] 15 czerwca 2020 o 7:28 
Nothing has been changed in the test, so most likely you have a background program that prevents exclusive full screen DX12 mode. Most commonly either EVGA PrecisionX or MSI Afterburner overlays breaking things.

Or some remote desktop software or VMWare which also tie deep into DirectX.
Ostatnio edytowany przez: UL_Jarnis; 15 czerwca 2020 o 7:28
e33et 15 czerwca 2020 o 7:57 
Początkowo opublikowane przez UL_Jarnis:
Nothing has been changed in the test, so most likely you have a background program that prevents exclusive full screen DX12 mode. Most commonly either EVGA PrecisionX or MSI Afterburner overlays breaking things.

Or some remote desktop software or VMWare which also tie deep into DirectX.

Here is my error explanation message when trying to run TimeSpy;

"File: dx_command_queue.cpp Line: 37 Function: __cdecl eva::graphics::dx::dx_command_queue::dx_command_queue(const class eva::graphics::dx::dx_device &,enum eva::graphics::command_list_type,int,bool) Expression: device.native()->CreateCommandQueue( &m_desc, IID_PPV_ARGS(m_native.receive())): DirectX call failed [-2005270523]. :"
< >
Wyświetlanie 76-90 z 98 komentarzy
Na stronę: 1530 50

Data napisania: 14 lipca 2016 o 18:25
Posty: 98