Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
Sadly we do not know what triggers the under-utilization of 4090 in Time Spy, but it is something outside the benchmark code. We already checked and are quite sure the engine just tries to render graphics... it literally cannot control something like this. Issue must be either driver or OS side.
Based on number of results with unusually low scores in the database, this is still fairly rare.
Same issue for me. Timespy with Win11 gives me scores about 1/3rd lower than they should be, same setup in Win10 is fine, and it's only Timespy, no other 3DMark benchmark is affected, not other vendors tools are affected, and real world gaming performance is not affected.
5900X and RTX3080.
When I get these poor Timespy scores, my GPU temperature is low, which implies it's not being driven properly by the CPU, but my CPU score is itself not low.
https://www.3dmark.com/compare/spy/45633545/spy/45437293#
I put it down to Timespy being very old now, and perhaps not catering for modern setups, because Speedway works with no issues at all.
Have you got the Speedway benchmark in 3dMark? How does that perform? For me, I just don't bother with Timespy now, it's too unreliable, and the only answer we got from the 3dMark developer was, "it's your hardware", when it obviously wasn't, so I just assumed they were not interested in looking into it as Timespy itself is so old, and they've superseded it with Speedway, and have another brand new benchmark coming soon, so kind of understandable their efforts are focused on that.
14900KS.
It’s like some sort of scheduling issue that wasn’t present in older versions of Windows or the app.