Only Intel Machines Affected by Windows 8 RTC Bug?

[btarunr]

HWBot.org blanket-banning benchmark submissions from Windows 8 machines sent ripples across the PC enthusiast community. Overclocker Christian Ney from OCaholic.ch spent some time trying out different combinations of hardware and operating system to check if Windows 8 RTC (realtime-clock) bug affects benchmarks consistently, on all hardware platforms. His findings are interesting, and one can draw the inference that only Intel processor-based machines could be affected by the bug, not AMD-based ones.

Ney observed the Windows 8 RTC bug to affect benchmark results only on Windows 8 machines running Intel LGA1150 "Haswell," LGA1155 "Ivy Bridge," and LGA1155 "Sandy Bridge," and not AMD AM3 and FM2 platforms. The issue didn't surface on any system running the older Windows 7 operating system. With it, it's clear that it's not just Microsoft that has to do some troubleshooting, Intel has to, as well. HWBot.org may have just saved itself time and pointless "bias" debates by blanket-banning Windows 8.

View at TechPowerUp Main Site

 

[Totally]

HWBot.org may have just saved itself time and pointless "bias" debates by blanket-banning Windows 8.

...and thus feeding the anti-win8 trolls. Case and point, the earlier article on the subject with a poll taking a jab the OS.

 

[Massman]

In the meantime, HWBOT already acknowledged AMD not being affected and updated its moderation guidelines.

Following up on the recent developments on the topic of Windows 8 RTC, read the updated news item here, Head of Moderating Christian Ney has updated the moderation rules regarding the usage of Windows8. Here is a list of the updated rules:

Exceptions to the Windows 8 rule:

1) AMD-based systems may be used in combination with Windows 8
2) We are still debating on how to address non-overclockable notebooks

Also, Intel clock drifting disappears when going from an Intel, to AMD, back to Intel system. That points to Windows 8 not selecting the right RTC, and causing RTC bias on Intel systems only.

We also received a couple of emails debating the topic of which is to blame, Windows 8 or Intel CPUs. Based on the information we gathered from clock drift problem on various operating systems and hardware platforms, we are still of the opinion that Windows 8 is the root cause of the problem. Windows 8 seems to be using a different source to fetch “real time” on an Intel based system compared to an AMD based system. It’s still guess why and which at the moment, but it seems to be related to the power saving features integrated in Windows 8. With Windows 7 unaffected, and Windows 8 affected on all Intel platforms (including old generations), the root of the problem lies with Windows 8. Having the Intel system unaffected when coming from and AMD Windows 8 installation indicates that the correct timers are available on Intel too, but unused by Windows 8.

http://hwbot.org/news/9824_breaking_windows_8_benchmark_results_no_longer_accepted_at_hwbot/

 

[AsRock]

...and thus feeding the anti-win8 trolls. Case and point, the earlier article on the subject with a poll taking a jab the OS.

Not any worse than the MS BS and what they pull. And of course there is anti win8 people one it's human nature two that MS bring it on them selfs by not giving what a shit load of people wanted which was not much..

Then when MS failed to push Metro on all ( as it seems thats what they wanted ) throw another knife at the people saying there be no updates to DX11.1, regardless if gamers need it or not it's more MS BS.

BTW because you don't agree with some thing don't make some one a troll..

 

[Totally]

BTW because you don't agree with some thing don't make some one a troll..

I perfectly understand that everyone does not like the same things, but the individuals I am referring to are disliking something for the sake of disliking as if it's the cool thing to do (and according to your post it is) for illogical reasons, and will hop on the soapbox whenever an opportunity presents itself.

 

[pigulici]

I perfectly understand that everyone does not like the same things, but the individuals I am referring to are disliking something for the sake of disliking as if it's the cool thing to do (and according to your post it is) without any logical reason, and will hop on the soapbox whenever an opportunity presents itself.

So, I don't like apple and you don't like cherry, and it is no "logical reason" for that, so to you I am a "troll",...oh humans, so easy to be cheat...

 

[Jorge]

Gee, Intel caught cheating AGAIN. Whodda thunk?

 

[Frick]

So, I don't like apple and you don't like cherry, and it is no "logical reason" for that, so to you I am a "troll",...oh humans, so easy to be cheat...

If it was like that it would not be a problem, but people tend do write their opinions about Windows 8 (and everything MS and EA has anything to do with) in inflammatory ways. It generally drifts into "troll hater" territory real quick.

 

[qubit]

In the meantime, HWBOT already acknowledged AMD not being affected and updated its moderation guidelines.



Also, Intel clock drifting disappears when going from an Intel, to AMD, back to Intel system. That points to Windows 8 not selecting the right RTC, and causing RTC bias on Intel systems only.



http://hwbot.org/news/9824_breaking_windows_8_benchmark_results_no_longer_accepted_at_hwbot/

I agree. This news article needs to be updated to reflect this, otherwise TPU could be accused of bias.

 

[Diverge]

Would this be related to why windows 8 has never showed my clock speed correctly in it's resource monitor? I always wondered why it was way off for my current clock speed and max overclock.

 

[MetalRacer]

It looks like they may have found a fix.

•To fix it: run cmd as admin and paste "bcdedit /set {current} useplatformclock Yes"

http://www.ocaholic.ch/modules/smartsection/item.php?itemid=1071

 

[erocker]

I agree. This news article needs to be updated to reflect this, otherwise TPU could be accused of bias.

Like that won't happen from some folks anyways.

It looks like they may have found a fix.

•To fix it: run cmd as admin and paste "bcdedit /set {current} useplatformclock Yes"

http://www.ocaholic.ch/modules/smartsection/item.php?itemid=1071

Nice! I hope the folks providing the benchmarks that are affected include this fix when the bench is run.

 

[qubit]

Like that won't happen from some folks anyways.

look in the mirror