• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Windows 8 RTC Bug Isolated, Fixed

btarunr

Editor & Senior Moderator
Staff member
Joined
Oct 9, 2007
Messages
47,243 (7.55/day)
Location
Hyderabad, India
System Name RBMK-1000
Processor AMD Ryzen 7 5700G
Motherboard ASUS ROG Strix B450-E Gaming
Cooling DeepCool Gammax L240 V2
Memory 2x 8GB G.Skill Sniper X
Video Card(s) Palit GeForce RTX 2080 SUPER GameRock
Storage Western Digital Black NVMe 512GB
Display(s) BenQ 1440p 60 Hz 27-inch
Case Corsair Carbide 100R
Audio Device(s) ASUS SupremeFX S1220A
Power Supply Cooler Master MWE Gold 650W
Mouse ASUS ROG Strix Impact
Keyboard Gamdias Hermes E2
Software Windows 11 Pro
Last week, overclocking achievement and leaderboards site HWBot banned benchmark submissions from PCs running Windows 8, because the operating system doesn't correctly handle real-time clock (RTC), making it easy to spoof it. A little later, it surfaced that Intel processor-based machines are worse affected by the bug, than AMD-based ones, resulting in HWBot making an exception for AMD processor-based systems. Further analysis by overclocker Christian Ney from Ocaholic unearthed the root cause of the bug, and a fix.

Christian Ney collaborated with CPU-Z author Franck Delattre, who provided a utility that reads out four system timers in real-time (ACPI, HPET, RTC, and QPC), and what DMI frequency is calculated based on each timer. At default bus frequency for an Intel processor-based system (100 MHz), all four timers yield a consistent readout, however, on changing the bus frequency using a Windows-based program, for example from 100 MHz to 95 MHz, RTC and QPC readouts go off the rails. This, however, doesn't happen when the frequency is set using the system BIOS setup program, and the system is made to boot from the changed frequency. From this testing, it can be inferred that Windows 8 doesn't use ACPI or HPET, but an internal timer. Although the bug doesn't "appear" to affect AMD platforms, under some circumstances, it can. Based on the findings, a bug-fix was found to the issue, which has to be applied using a command-line setting. Perhaps HWBot could review its Windows 8 submission policy.



View at TechPowerUp Main Site
 
Joined
Nov 7, 2009
Messages
50 (0.01/day)
...

http://hwbot.org/news/9824_breaking_windows_8_benchmark_results_no_longer_accepted_at_hwbot/

Update 24/08 – Revised Moderation Guidelines Concerning Windows 8

Following the findings of Ocaholic.ch (reference), the HWBOT moderating team has revised its rules regarding the usage of Windows 8 for benchmark submission at HWBOT. The major change is that the combination of AMD and Windows 8 is also not allowed, as in contrary to previous findings the platform is affected too. The revised rules can be found below.

1) All new Windows 8 Benchmark Results will be blocked, including for on-going competitions
2) Existing Windows 8 based benchmark submissions will be blocked if seemingly out of line, world record, or top score.
3) Existing Windows 8 based benchmark submissions will not be blocked or removed if they don’t meet the requirements above

Note: if you recall downclocking when using an Intel based Windows 8 system, please remove that result.

Exceptions to the Windows 8 rule:

1) non-overclockable notebooks may be used in combination with Windows 8
 
Joined
Jul 10, 2010
Messages
1,233 (0.23/day)
Location
USA, Arizona
System Name SolarwindMobile
Processor AMD FX-9800P RADEON R7, 12 COMPUTE CORES 4C+8G
Motherboard Acer Wasp_BR
Cooling It's Copper.
Memory 2 x 8GB SK Hynix/HMA41GS6AFR8N-TF
Video Card(s) ATI/AMD Radeon R7 Series (Bristol Ridge FP4) [ACER]
Storage TOSHIBA MQ01ABD100 1TB + KINGSTON RBU-SNS8152S3128GG2 128 GB
Display(s) ViewSonic XG2401 SERIES
Case Acer Aspire E5-553G
Audio Device(s) Realtek ALC255
Power Supply PANASONIC AS16A5K
Mouse SteelSeries Rival
Keyboard Ducky Channel Shine 3
Software Windows 10 Home 64-bit (Version 1607, Build 14393.969)
Intel was defaulted to using RTC(Software) Timers. <-- You can enable hardware timers by turning on the platform clock.
AMD was defaulted to using HPET(Hardware) Timers. <-- You can disable hardware timers by turning off the platform clock.
 
Last edited:
Joined
Feb 18, 2005
Messages
5,847 (0.81/day)
Location
Ikenai borderline!
System Name Firelance.
Processor Threadripper 3960X
Motherboard ROG Strix TRX40-E Gaming
Cooling IceGem 360 + 6x Arctic Cooling P12
Memory 8x 16GB Patriot Viper DDR4-3200 CL16
Video Card(s) MSI GeForce RTX 4060 Ti Ventus 2X OC
Storage 2TB WD SN850X (boot), 4TB Crucial P3 (data)
Display(s) 3x AOC Q32E2N (32" 2560x1440 75Hz)
Case Enthoo Pro II Server Edition (Closed Panel) + 6 fans
Power Supply Fractal Design Ion+ 2 Platinum 760W
Mouse Logitech G602
Keyboard Razer Pro Type Ultra
Software Windows 10 Professional x64
tl;dr bugfix:

run cmd as admin and paste "bcdedit /set {current} useplatformclock Yes"

(from OCaholic)
 

Easy Rhino

Linux Advocate
Staff member
Joined
Nov 13, 2006
Messages
15,585 (2.36/day)
Location
Mid-Atlantic
System Name Desktop
Processor i5 13600KF
Motherboard AsRock B760M Steel Legend Wifi
Cooling Noctua NH-U9S
Memory 4x 16 Gb Gskill S5 DDR5 @6000
Video Card(s) Gigabyte Gaming OC 6750 XT 12GB
Storage WD_BLACK 4TB SN850x
Display(s) Gigabye M32U
Case Corsair Carbide 400C
Audio Device(s) On Board
Power Supply EVGA Supernova 650 P2
Mouse MX Master 3s
Keyboard Logitech G915 Wireless Clicky
Software The Matrix
why would any chipset manufacturer default to using software timers?? especially when the majority of the operating systems will be Windows :roll: :slap:
 
Top