Gradual Degradation of 3DMark Fire Strike Produces Unreliable Results
Guest, in Software News
Hey there. I have an M17x R4 which had its’ initial GPU die. That in turn caused gpu fan to go up to 4500-4600 rpm. I have since successfully installed 980m, but it seems that GPU fan is stuck at that speed. I’ve set up A15 bios (locked), but it didn’t help. PSA gives me error 2000-0511 on video fan, which, according to dell forums, means either software or hardware issue. Neither can I control the fan speed in HWInfo - the program tells me gpu sensors/readings are disabled (despite actually showing respected readings in “sensors” tab).
Am I missing something here or is it just faulty gpu fan?
For those that are not already aware of the issue, the folks at Futuremark seem to be struggling to keep a consistent product in the latest 3DMark benchmark. In particular, Fire Strike. Sometime around the release of Time Spy things started getting screwy with Fire Strike and now it seems with every Fire Strike GUI update the effect is lowered benchmark scores, and specifically the physics portion of the benchmark.
Kudos to @Papusan for noticing this months ago. He been going back and forth with Futuremark about the problem and it seems they are either ignoring him or don't care. Maybe because most people are not observant enough to notice or care.
Some people might say you cannot compare results across benchmark software versions, but that shouldn't hold water here. There is a leaderboard and searchable database of results and if there is not a high degree of consistency between GUI versions the results in their database will become irreleant, as will their leaderboard. The search filter does not have a field to filter by GUI version, so we can expect the results from the database and leaderboard to be misleading, inaccurate and unreliable.
You will notice from the examples posted below that with each new version of Fire Strike the scores get lower and lower. These examples are consecutive runs on the same day, same machine, and identical CPU and GPU settings. The only thing that changes is Fire Strike benchmark results. We need Futuremark to understand and correct this.
Here is a similar example from @Papusan: http://www.3dmark.com/compare/fs/11036017/fs/11035883
If you agree this is a problem and want it to be fixed, please complain to Futuremark and let them know they need to put the brakes on and not do anything else with 3DMark until they have this mess under control. Gimmicky features are one thing, but inconsistent benchmark results makes 3DMark unreliable.
This post has been promoted to an article