Sunday, August 18th 2013
HWBot No Longer Accepts Record Submissions from Windows 8
HWBot announced that it no longer accepts benchmark record submissions from PCs running Windows 8. It discovered that the way Windows 8 handles real-time clock (RTC), compromises the veracity of benchmark results. HWBot announced that is looking into possible solutions for the problem, and till such a time, it won't accept benchmark result submissions from Windows 8 PCs. This decision could affect leaderboards and records set using Windows 8 benches, and could greatly stunt adoption of the operating system among the professional overclocking community. A statement by HWBot reads;
As the result of weekend-time research, the HWBOT staff has decided to invalidate all benchmark records established with the Windows8 operating system. Due to severe validity problems with the Windows8 real time clock ("RTC"), benchmarks results achieved with Windows8 cannot be trusted. The main problem lies with the RTC being affected when over- or underclocking under the operating system. The operating system uses the RTC as reference clock, and benchmarks use it to reference (benchmark) time.
81 Comments on HWBot No Longer Accepts Record Submissions from Windows 8
Win8 is garbage on PC, tablets is fine.
I'll stick with Win7 till I can no longer benefit from it.
Like how much are the benches altered due to that?
On topic though, what does this "fault" in win8 actually mean? Is it that you could potentially score better with a supposedly lower clock? And where else could one notice anything about this so called "fault"?
The only thing I noticed myself when it comes to clocks in win8 is that it doesn't seem to detect any changes in bus speed. So for an instance my CPU shows as running at 3,70Ghz in task manager and performance index, while I'm actually running at 4,56Ghz because of an overclocked bus speed.
Edit: also, the poll doesn't have a "I'm already on win8 and: I do care/ I don't care".
The higher scores are completely meaningless, because the time measured is incorrect. One second on-system is, after downclock, more than one second. In the case of the adjustment from 130MHz to 122MHz, 1sec on-system is 1.06557377049sec in real time.
Windows8 Time Machine - YouTube
The thing with the benchmarking of course is that they all look for software optimisations outside of the standard operating package of any benchmark - in fact the tweaks made to software and operating systems goes beyond optimising the hardware itself, there's very little real world comparisons to the top scores and what would be achievable simply by overclocking.
That's not to say it's not a skill or an art, what these people do is mighty impressive - even if you remove extreme cooling, it's just completely divorced from reality to a point that this change really make no difference (because everyone who's into benchmarking would of realised this optimisation and would of used it up until now at some point).
Never used this HWBot anyways...
Edit: "The grapes are sour"... :D