Futuremark SystemInfo v4.20 out

[FM_Jarnis]

Okay, SystemInfo 4.20 is now available

 

http://www.futuremark.com/downloads/Futuremark_SystemInfo/latest

 

SystemInfo Version 4.20

Updated September 4, 2013

 

* Updated CPUID module for improved hardware detection

* Updated AMD ADL library for improved compatibility with latest hardware

* Improved hardware scan speed by about 50%

* Added Windows RTC clock verification, results with inaccurate time measurement can now be rejected on 3DMark.com

 

----

 

...and yes, the last bit means that if you try doing some monkey business with BCLK in Windows 8 on-the-fly and break the time-space continuum of your system (RTC clock skew), 3DMark.com will reject the result as invalid.

 

We're considering the option of adding this also "built-in" to the benchmark for at least 3DMark (so online viewing would not be required) but patching the benchmark itself is a very long and complex process so this is best we could do on a short notice.

 

Also doing it like this gives us a "free" benefit - this validation check now applies to ALL Futuremark benchmarks that use SystemInfo (so 3DMark 03, PCMark05 and everything newer than that).

 

Report any issues you may have to FM support ( http://support.futuremark.com )

 

Steam versions will be updated early next week but you can already manually install this standalone update before that even when using Steam version.

Edited September 4, 2013 by FM_Jarnis

[Christian Ney]

You have a cache issue, when I clic http://www.futuremark.com/downloads/Futuremark_SystemInfo/latest it downloads 4.19. ctrl+f5 doesn't fix it.

 

In another browser or pc it's ok because I never went to http://www.futuremark.com/support/systeminfo with.

Edited September 4, 2013 by Christian Ney

[FM_Jarnis]

Direct DL link

 

http://www.futuremark.com/downloads/Futuremark_SystemInfo_v420_installer.msi

[Christian Ney]

Perfect Thanks

[knopflerbruce]

If you change the timer to one that actually works, and then change the bclk, I guess those results won't be marked as invalid?

[FM_Jarnis]

If you change the timer to one that actually works, and then change the bclk, I guess those results won't be marked as invalid?

 

They are marked as invalid only if RTC is skewed (ie. actual time taken during benchmark does not match the time taken as per RTC). It doesn't care one bit what your BCLK is, it just validates the time from multiple sources and makes sure they agree with each other.

[knopflerbruce]

Good