Advertisment



Browsing this Thread:   1 Anonymous Users




« 1 2 (3)


Re: Windows RTC Bug only Intel Systems affected?
#21
Started insulating
Started insulating


See User information
Windows XP SP2: Disabling CPI/HPET makes the QPC use the TIP (1.19 MHz) but then you loose all the advantages of the ACPI system (to force it you need to force the driver "Standard PC" for computer).

I will try other combinations.

btw, to make Windows XP use the right timer source for the QPC (aka a timer source that has a fixed frequency) you need to edit the BOOT.ini file and add the parameter "/usepmtimer".

Posted on: 2013/8/24 12:41
Twitter Facebook Google Plus Linkedin Del.icio.us Digg Reddit Mr. Wong Top


Re: Windows RTC Bug only Intel Systems affected?
#22
Webmaster
Webmaster


See User information
Quote:

Christian Ney schrieb:
In Windows XP, QPC is affected too since it uses the TSC. RTC seems to be ok so far. I will try some other stuff.


So ... in other words you can cheat with Windows XP?

Posted on: 2013/8/24 15:16
Twitter Facebook Google Plus Linkedin Del.icio.us Digg Reddit Mr. Wong Top


Re: Windows RTC Bug only Intel Systems affected?
#23
Started insulating
Started insulating


See User information
No
XP isn't as retarded as Windows 8 :p

Posted on: 2013/8/24 21:55
Twitter Facebook Google Plus Linkedin Del.icio.us Digg Reddit Mr. Wong Top


Re: Windows RTC Bug only Intel Systems affected?
#24
Started insulating
Started insulating


See User information
I am testing FutureMark's new SystemInfo 4.20 now, results on Monday when the online validation process will be updated since timer inconsistencies check will only happen on submitting the result online.

Posted on: 2013/8/30 12:44
Twitter Facebook Google Plus Linkedin Del.icio.us Digg Reddit Mr. Wong Top


Re: Windows RTC Bug only Intel Systems affected?
#25
Started insulating
Started insulating


See User information
Been cooperating with FutureMark, now 3DMark and PCMark runs on Windows 8 can be trusted when they meet the following requirements:
- ORB Link
- Use of SystemInfo 4.20 or newer. download it here (not yet on FM's website)

How does it work:
At the moment it's a "dirty" fix since it requires online check and isn't built into the benchmark for offline check but it has one good thing, it will affect all benchmarks at once. Just need to update SystemInfo (make sure to uninstall any previous version of SystemInfo to not create any conflict. Should be ok but you never know) and submit the file online via the benchmark or the upload form.
The new SI will check and monitor/log 3 different timers. When submiting online the site's engine will check the values and if one timer is off (RTC in this case) the result will not be valid and you will get the following error:
"Time measuring inaccurate. Results are invalid."

Here is an exemple:

Windows 8 + System Info 4.19 no downclocking (aka RTC is in line)
http://www.3dmark.com/3dm11/7103162 result is valid*

Windows 8 + System Info 4.19 + downclocking (aka RTC is fooled)
http://www.3dmark.com/3dm11/7103148 result is valid*

Windows 8 + System Info 4.20 no downclocking (aka RTC is in line)
http://www.3dmark.com/3dm11/7103178 result is valid

Windows 8 + System Info 4.20 + downclocking (aka RTC is fooled)
http://www.3dmark.com/3dm11/7103163 result is invalidated (Time measuring inaccurate. Results are invalid)


*At the moment, FM will add later a warning-type notice like: Invalid, Time measuring cannot be checked, please use latest version of SystemInfo when benchmarking under Windows 8



Time measuring inaccurate

This message indicates funny business with the system clock during benchmark run. In most cases, this means that, no, you cannot cheat in 3DMark by adjusting Windows timers during benchmark run or otherwise tampering with the measurements done by the benchmark. If this message persists and you have not done anything out of the ordinary, it may indicate a hardware issue with the real time clock of your system or a presence of a background program that somehow twists the time-space continuum of your operating system in such a way that this anti-cheat detection is tripped

Posted on: 2013/9/2 13:59

Edited by Christian Ney on 2013/9/2 14:17:22
Edited by Christian Ney on 2013/9/2 14:45:37
Edited by Christian Ney on 2013/9/2 14:47:17
Edited by Christian Ney on 2013/9/3 15:57:33
Twitter Facebook Google Plus Linkedin Del.icio.us Digg Reddit Mr. Wong Top


Re: Windows RTC Bug only Intel Systems affected?
#26
Started insulating
Started insulating


See User information
You can now download 4.20 from FM's website here. Just clic "Download and install Futuremark SystemInfo" should get you 4.20. changelog hasn't been added yet.

EDIT, FM:
"
Okay, SystemInfo 4.20 is now available

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

SystemInfo Version 4.20
Updated August 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.

Posted on: 2013/9/4 9:55

Edited by Christian Ney on 2013/9/4 11:47:17
Edited by Christian Ney on 2013/9/4 11:48:01
Twitter Facebook Google Plus Linkedin Del.icio.us Digg Reddit Mr. Wong Top


Re: Windows RTC Bug only Intel Systems affected?
#27
Started insulating
Started insulating


See User information
FM_Janis:

Just to clarify, this update appplies to following benchmarks;

- PCMark 05
- PCMark Vantage
- PCMark 7
- PCMark 8
- 3DMark03
- 3DMark05
- 3DMark06
- 3DMark Vantage
- 3DMark 11
- 3DMark

For 3DMark03, you must use the latest version which uses separate SystemInfo (early 03 versions used different built-in scan tech that cannot be updated)

Posted on: 2013/9/15 14:04
Twitter Facebook Google Plus Linkedin Del.icio.us Digg Reddit Mr. Wong Top




« 1 2 (3)




[Advanced Search]


Re: Windows RTC Bug only Intel Systems affected? [Processors] - ocaholic