Featured Articles

Nvidia GTX 980 reviewed

Nvidia GTX 980 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
Nvidia adjusts GTX 980 and GTX 970 pricing

Nvidia adjusts GTX 980 and GTX 970 pricing

It appears that Nvidia has been feeling the pulse of the market and took some note from comments regarding the original…

More...
iPhone 6 and 6 Plus reviews are up and they are good

iPhone 6 and 6 Plus reviews are up and they are good

Apple is dancing the same dance year after year. It releases the iPhone and two days before they start shipping it…

More...
Amazon announces three new tablets

Amazon announces three new tablets

Amazon has just released three new tablets starting with the $99 priced 6-inch Kindle Fire HD6. This is a 6-inch tablet…

More...
PowerColor TurboDuo R9 285 reviewed

PowerColor TurboDuo R9 285 reviewed

Today we will take a look at the PowerColor TurboDuo Radeon R9 285. The card is based on AMD’s new…

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