Title is linkbait.<p>What's happened is that there's apparently a bug with the Win8 RTC API implementation that doesn't properly calibrate for changes in the CPU BCLK, which obviously makes it useless in the presence of overclocking (beyond mere changes to the multiplier, anyway).<p>That's a bug, and a comparatively bad one (though obviously it won't affect production systems), and it should be fixed. But the lede use of "banned" makes it sounds like MS was caught "cheating" or something, which is wrong.<p>Presumably other OSes like Win7 or Linux expose the underlying ACPI RTC directly. Win8 probably tried to finesse things by using the CPU timer counters to improve precision.