Just now, Deathstreams said:
So basically this issue is redundant, and has no known fix?
Well, no known fix in the sense that I don't know exactly what Windows uses to poll for CPU speed. However, even if I did know, I don't think there would be a way to fix it depending on what Windows is using to source data. If there's something wrong with the hardware for instance, then there's nothing Windows can do about it.