Yesterday news hit the wire about a real-time clock (RTC) bug in Windows 8 that affects how time is measured when the system is underclocked or overclocked. OCAholic did some testing and discovered that it may not be only Microsoft that is to blame, the website found that the issue only seems to occur on Intel-based systems. Intel's Sandy Bridge, Ivy Bridge and Haswell all test positive, while AMD's Trinity and AM3 platforms did not cause any issues.
Judging by the results he could determine, that the RTC Bug gets triggered only with the combination of Windows 8 and Intel. In case of AMD systems, which were based on FM2 processors as well as AM3 chips, he hasn't been able to replicate the issue. All the benchmarks he ran showed the correct results and weren't influence positively by downclocking the CPU.
Now the question remains, what is different when it comes to Intel systems compared to AMD, that could trigger this bug within Windows 8. So far one thing is for sure, it's not only Microsoft who is to blame. It looks like Intel plays a role in this game too and could also be of help solving this issue.