Featured Articles

Nvidia Shield 2 shows up in AnTuTu

Nvidia Shield 2 shows up in AnTuTu

Nvidia’s original Shield console launched last summer to mixed reviews. It went on sale in the US and so far Nvidia…

More...
AMD CSO John Byrne talks ARM

AMD CSO John Byrne talks ARM

We had a chance to talk about AMD’s upcoming products with John Byrne, Chief Sales Officer, AMD. We covered a number…

More...
AMD Chief Sales Officer thinks GPU leadership is critical

AMD Chief Sales Officer thinks GPU leadership is critical

We had a chance to talk to John Byrne who spent the last two years as Senior Vice President and Chief…

More...
OpenPlus One $299 5.5-inch Full HD phone

OpenPlus One $299 5.5-inch Full HD phone

OnePlus is one of the few small companies that might disrupt the Android phone market, dominated by giant outfits like Samsung.…

More...
KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 gained a lot of overclocking experience with the GTX 780 Hall of Fame (HOF), which we had a chance to…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Monday, 26 August 2013 15:26

Windows 8 RTC bug isolated, fixed

Written by Slobodan Simic

windows logo new

Workaround exists


As you may already know, HWBot recently banned all benchmark submissions from systems running Windows 8 due to an issue with the correct real-time clock (RTC) and how it behaves when the system is underclocked or overclocked. The issue was more likely to happen on Intel- rather than AMD-based systems, so HWBot decided to exclude AMD from the list. Well known overclocker Christian Ney further investigated the issue and actully found the underlying source of the bug as well as a fix for it.

In a cooperation with Franck Delattre, the guy behind CPU-Z, which reads four system timers in real-time (ACPI, HPET, RTC, and QPC) and how the actual DMI frequency (BCLK on Intel and HTT on AMD) is calculated based on each timer, they managed to find the actual problem and conclude that the system is not affected when the frequency is set via BIOS and forced to boot on that frequency but rather only when it is set "on-the-fly". This also means that Windows 8 does not actually use ACPI or HPET as previously thought but rather an internal timer.

Although it was suspected that AMD-based systems are excluded from the issue, it appears that they are also affected albeit with much less consenquences due to the fact that Windows 8 automatically set/add the "useplatformclock" parameter to "yes" after the second boot.

The fix for the issue is quite simple as it only requires to run the "bcdedit /set {current} useplatformclock Yes" in command prompt as admin. Of course, HWBot now needs to find a way to confirm if the system is running with the correct RTC.

More here.




Last modified on Tuesday, 27 August 2013 07:47
blog comments powered by Disqus

To be able to post comments please log-in with Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments