Windows 8 overclock-related RTC bug isolated and fixed

By on August 26, 2013, 7:30 PM

Last week, a bug was discovered in Windows 8 that affects the real-time clock while overclocking, causing inaccurate benchmark results. This discovery prompted popular overclocking leaderboards site HWBOT to ban Windows 8 results from both Intel and AMD systems, as overclockers could use the bug to unfairly enhance their score.

Ocaholic's Christian Ney teamed up with CPU-Z author Franck Delattre to try and isolate the cause of the issue, using a utility that read four system timers (QPC, HPET, ACPI and the problematic RTC) in real time. At the default bus frequency of 100 MHz on an Intel-based system, each of the four clocks had the same readout, but when the bus frequency was adjusted down to 95 MHz from within Windows 8, the readout from the RTC and QPC clocks went off the rails.

Further exploration of the issue revealed that if you change the CPU frequency in the BIOS, the clocks are unaffected on boot-up, and although AMD systems are largely fine, the bug can cause issues in some circumstances. The team also confirmed that Windows 8 is the only operating system affected by the bug due to changes in the RTC's time sourcing methods.

Importantly, the bug can be fixed through a simple command line prompt. However, as the RTC is still very easy to fool in Windows 8, and it can't be guaranteed that all overclockers will apply the fix, Ocaholic believes that Windows 8 benchmarking results still can't be trusted.




User Comments: 5

Got something to say? Post a comment
4 people like this | cliffordcooley cliffordcooley, TechSpot Paladin, said:

Importantly, the bug can be fixed through a simple command line prompt. However, as the RTC is still very easy to fool in Windows 8, and it can't be guaranteed that all overclockers will apply the fix, Ocaholic believes that Windows 8 benchmarking results still can't be trusted.
If the clock can be fixed with a command from command-line prompt, why can the benchmarking tool not be programmed to sense the state of the setting that was changed?

JC713 JC713 said:

Importantly, the bug can be fixed through a simple command line prompt. However, as the RTC is still very easy to fool in Windows 8, and it can't be guaranteed that all overclockers will apply the fix, Ocaholic believes that Windows 8 benchmarking results still can't be trusted.
If the clock can be fixed with a command from command-line prompt, why can the benchmarking tool not be programmed to sense the state of the setting that was changed?

Yeah, I dont get why not...

misor misor said:

[link]

...the benchmarks themselves have 'bugs'.

bmaytum bmaytum said:

"Importantly, the bug can be fixed through a simple command line prompt."

So, please provide the command-line instruction - I'd like to check (or reset) RTC setting if needed, on my PC.

bmaytum bmaytum said:

"Importantly, the bug can be fixed through a simple command line prompt."

So, please provide the command-line instruction - I'd like to check (or reset) RTC setting if needed, on my PC.

D0h -Never mind, the CL instruction *is* stated in the linked Ocaholic article.

Load all comments...

Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...
Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.