jihadjoe wrote:^ The article mentions the problem is with downclocking, not overclocking.
We can also demonstrate the Windows8 RTC problem with the Windows Time. Have a look at the videos below. In one of the videos, we underclocked the base clock frequency by 6%. After 5 minutes, Windows Time was already 18(!) seconds behind real time. When overclocking the base clock frequency, we can see the opposite effect. We overclock by roughly 4%, and after two minutes, Windows Time is 3 seconds ahead of real time.
Glorious wrote:The crux of this really comes down to the problem that there isn't any reliable way to get a high-precision, high-accuracy timer on Windows. Depending on your windows boot switches and hardware combination the HAL might actually be using anything from the TSC to some PIC off the PCI bus on the motherboard.
JBI wrote:I wonder if there is a boot-time option to force Windows 8 to use a particular timing source. Might be worth looking into.
Glorious wrote:There are new options in bcdedit that look interesting:
It would be interesting to see what enabling them would do in reference to this problem.
Setting the venerable useplatformclock would be interesting too.
Users browsing this forum: Bing [Bot] and 5 guests