3DMark11 - Win7 - Time measurement not available

[alancsalt]

At OCN we are seeing results in Win7 showing "Time measurement data not available".

 

We also see "Time measurement inaccurate" which Futuremark specifically states on its explanation page is not acceptable to them. http://www.3dmark.com/support/troubleshooting-my-results/#validation.anomaly.TIME_MEASUREMENTS_NOT_AVAILABLE

 

They do not have a heading for, or explain "Time measurement data not available", but do exclude results with that error.

 

What is the HWbot position on this particular error?

[der8auer]

Happened to me aswell several times and we internally discussed such results already in the past and checked them as valid on HWBot.org.

 

Of course the results are not valid if the error appears on Windows 8.

[Massman]

Not sure why the timing mechanism is going off on Windows 7. It's a alert system that was implemented only very recently to deal with the Windows 8 downclocking problem.

 

Either the timer mechanism is broken, or there is a real timer issue and we have been dealing with bugged runs on Windows7 unknowingly.

[FM_Jarnis]

This message means "SystemInfo was disabled or your SystemInfo was older than 4.19, so there is no data about the RTC clocks in the result file. We can't say if your result had funky RTC business or not".

 

And yes, the RTC verification is done on all OSes and on all benchmarks as there are other ways to trick the same effect that Win 8 caused unexpectedly (nope, not going to detail on that...)

 

If you are getting this on SI 4.23, it would imply that the system is not fully stable (the SI process crashed during the benchmark run so it could not get the required RTC data)

 

If you see this on stock clock system, we would like to hear all the details.

Edited December 13, 2013 by FM_Jarnis

[alancsalt]

Ours are on overclocked systems. I keep a overclock list thread. Currently allowing "not available", but not "not accurate" with Win7.

 

Systems may not be fully stable, but stability is not a requirement, just a result. As long as it's stable enough to complete the bench. Quite common with Win7 to get "not available" and that's with the latest sysinfo..

Edited December 15, 2013 by alancsalt

[FM_Jarnis]

Ours are on overclocked systems. I keep a overclock list thread. Currently allowing "not available", but not "not accurate" with Win7.

 

Systems may not be fully stable, but stability is not a requirement, just a result. As long as it's stable enough to complete the bench. Quite common with Win7 to get "not available" and that's with the latest sysinfo..

 

Up to you what rules you follow.

 

Futuremark Hall of Fame requires systems that are actually stable enough to keep SystemInfo process from crashing during the run (which would lead to "not available" error with latest SystemInfo). This is because without it, there is no way to tell if RTC was being messed with.

 

Note that allowing "not available" but disallowing "not accurate" means by your rules it is possible to cheat with the RTC. Would be trivially easy to set up so that SI process is killed during the benchmark run to "cover" any RTC mungling... And yes, it is confirmed possible to cheat the RTC also on Win 7. Just not as trivially (or by accident) as on Windows 8.

 

If you have a reproducible "not available" error on confirmed stable system, please email us the details (hardware config, any result files you have etc.) and we'll investigate.

Edited December 19, 2013 by FM_Jarnis

[sumonpathak]

the problem is still there

Win 7,perfectly stable system.

[Chi-Kui Lam]

futuremark has more than 1 threads(too much) to collect RTC data and make sure the time measure is correct,

If OS Tweaks too much and affect the Win Threads Priority which related to system info, you almost get this error.