this happens because XTU isn't even a real benchmark, i been saying this for years
i appreciate there is a component of XTU that is a benchmark, but I get the impression the measured CPU MHz is included in the benchmark calculation
we have seen repeatedly over the life of XTU, when the GHz measurement is off, the score is skewed and this issue keeps coming up
we were playing with this during country cup and were able to almost skew any score we wanted by fiddling with that realtime, but there is always the telling factor of the GHz measurement being wrong
in my long standing opinion, XTU should be removed from pointed/competition benchmarks until Intel revise the mathematics behind it. it may be to give some sort of "efficiency" calculation, which im all for, but it shouldn't impact on the score at all