Incorrect performance counter

[AalaarDB]

When a CPU is overclocked from the bios, the high performance cpu counter frequency is updated. When a CPU is OCed from Windows using this tool, the counter is not updated and is set to whatever it booted up from. This leads to the interesting situation of when I OC my CPU, I can get lower reported performance!

I first found this phenomenon while benchmarking the X3 Reunion rolling demo. As I later found out my system is GPU limited with this benchmark, so OCing the fsb to change the CPU and memory yielded no performance change.

For the longest time I was benching with a fsb of 200 set from the bios and OCed from Windows. So the results followed this pattern: (fsb bios, fsb windows)
200 200 -> 25.4fps
200 220 -> 23.5fps

When I changed my fsb to 220 in the bios I finally found the pattern:
220 200 -> 27.9fps
220 220 -> 25.6fps
220 245 -> 23.2fps

25.6 * 220 / 220 = 25.60 ~= 25.4
25.6 * 220 / 245 = 23.00 ~= 23.2
25.6 * 220 / 200 = 28.16 ~= 27.9

25.4 * 200 / 200 = 25.4
25.4 * 200 / 220 = 22.72 ~= 23.5

This tells me the benchmark is GPU bound.
200 200 -> 25.4fps
220 220 -> 25.6fps

Other affected benchmarks are SiSoft Sandra 2007 and RightMark Memory Analyzer, these would be much shorter if you wanted to verify this yourself.