3DMark
Horrible timespy/extreme scores with 13900k and 4090
Time to add to the list of something wrong with timespy. I’m on win 11 22h2 on a msi z690 ddr4 tomahawk Wi-Fi and 13900k msi 4090 64gb 3600 mhz RAM XMP I have no stability issues with the system or windows crashing or anything nothing is overclocked just this 3dmark problem

When I first went to win 11 my timespy and timespy extreme gpu scores were 32k/19k

Now timespy gpu score is a mere 15k and extreme 16k
Timespy gpu usage is 50% or lower

Also this appears to be tied to my cpu performance I thought it was Intel management engine/Mei firmware related as some have reported on z690/790 and 13th gen and have been keeping them updated

Recently my cpuz single/ multi thread scores went from 900/16.9k for no reason to 890/16.5k for no reason and when the cpu is running in the higher mode that’s when I get the correct gpu scores in lower mode the abysmal scores and my system switches randomly

I have no idea what’s going on and like most no games are affected and in either mode port Royal and speed way score fine 25k and 10k

I’ve tried everything reinstalling 3dmark DDU different drivers so I don’t know what to do
< >
16-26 van 26 reacties weergegeven
UL_Jarnis  [ontwikkelaar] 7 mei 2023 om 1:44 
If it does not reoccur, the GPU just crashed and gave corrupted rendering. GT2 is the heavier of the two so if the test fails somewhere, it is there. If it does reoccur, unfortunately it may be a hardware issue.
Origineel geplaatst door UL_Jarnis:
If it does not reoccur, the GPU just crashed and gave corrupted rendering. GT2 is the heavier of the two so if the test fails somewhere, it is there. If it does reoccur, unfortunately it may be a hardware issue.
I have had this 4090 since like 2 weeks after launch nothing like that has ever happened. My temps are really good too. I’ve gamed for 12 hours straight before. I gamed all day today ran 5 time spy extreme and port royal stress test passed with 99.9%. Could it have been a time spy crash because event viewer says timespy workload.exe crash not even a hardware error. Must of just been random. Anyway back to the topic. 2 days ago I was getting low gpu usage in timespy/extreme and now it’s back to normal it just switches back and forth from low usage to full whenever it wants but games and modern tests are not affected
UL_Jarnis  [ontwikkelaar] 7 mei 2023 om 23:18 
Most likely the card is then fine. Any computer hardware can have really rare freak crashes. As long as it does not repeat, it is no big deal.

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.
Laatst bewerkt door UL_Jarnis; 7 mei 2023 om 23:18
I am also having the same Timespy issue. My scores have been cut in half for no reason. Running a 5900x with a 4080 FE, 128gb ddr4 @3600 and 2tb 980 pro. I really haven't been using 3dmark for benchmarking lately. I check it every now and then, but still runs like crap. All other benchmarks/games run perfectly. I dunno.......
Laatst bewerkt door RedEyedSteve; 30 jun 2023 om 4:57
Origineel geplaatst door RedEyedSteve:
I am also having the same Timespy issue. My scores have been cut in half for no reason. Running a 5900x with a 4080 FE, 128gb ddr4 @3600 and 2tb 980 pro. I really haven't been using 3dmark for benchmarking lately. I check it every now and then, but still runs like crap. All other benchmarks/games run perfectly. I dunno.......

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.
Laatst bewerkt door Swans; 21 mei 2024 om 6:36
Same issue for me as well in Time Spy. 5950x and 3080 FE.
Laatst bewerkt door rexbinary; 23 jul 2023 om 13:53
4080 +13900k, Absurdly low CPU score, yet benchmarks fine in every other test, just not working well with Timespy : ( graphics score is 28k, cpu score 16k (should be above 20 at least) ddr4 3200
Yeah, I upgraded to an RTX 4070 Super, with new faster memory, but retained my AMD 5900X. Still sporadically get weak Timespy scores, all other benchmarks are as expected and real world performance is as expected when using Perfmon to get real KPIs.

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.
Laatst bewerkt door Swans; 19 mrt 2024 om 3:24
I'm also have same problem, my physics score CPU somehow is dropped from 24k to 20k in 1 months no hardware change only updated Bios and intel ME, i did back to old bios same result, any idea what cause low physics score CPU ? RTX 4080 S with i9-14900k
Origineel geplaatst door Kekw:
I'm also have same problem, my physics score CPU somehow is dropped from 24k to 20k in 1 months no hardware change only updated Bios and intel ME, i did back to old bios same result, any idea what cause low physics score CPU ? RTX 4080 S with i9-14900k

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.
Same issue with TS CPU bench. One run it’s 26K. Another run 20K. Not power/thermal or current throttle. Can’t figure out what’s triggering this behavior.

14900KS.

It’s like some sort of scheduling issue that wasn’t present in older versions of Windows or the app.
< >
16-26 van 26 reacties weergegeven
Per pagina: 1530 50

Geplaatst op: 14 mrt 2023 om 19:40
Aantal berichten: 26