Featured Articles

Intel refreshes CPU roadmap

Intel refreshes CPU roadmap

Intel has revealed an update to its CPU roadmap and some things have changed in 2015 and beyond. Let’s start with the…

More...
Hands on: Nvidia Shield Tablet with Android 5.0

Hands on: Nvidia Shield Tablet with Android 5.0

We broke the news of Nvidia's ambitious gaming tablet plans back in May and now the Shield tablet got a bit…

More...
Nokia N1 Android tablet ships in Q1 2015

Nokia N1 Android tablet ships in Q1 2015

Nokia has announced its first Android tablet and when we say Nokia, we don’t mean Microsoft. The Nokia N1 was designed…

More...
Marvell launches octa-core 64-bit PXA1936

Marvell launches octa-core 64-bit PXA1936

Marvell is better known for its storage controllers, but the company doesn’t want to give up on the smartphone and…

More...
Nvidia GTX 970 SLI tested

Nvidia GTX 970 SLI tested

Nvidia recently released two new graphics cards based on its latest Maxwell GPU architecture, with exceptional performance-per-watt. The Geforce GTX 970…

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

 

Facebook activity

Latest Commented Articles

Recent Comments