Short story is written above) Another reason to blame Microsoft![]()
![]()
Breaking! Windows 8 Benchmark Records No Longer Accepted At HWBOT - Benchmark Result Veracity Compromised
-
-
Im sure this will be patched.
-
3DMark will not have this problem as they will just create newer version and HWBot will ask people to give results using it but what to think about old SuperPi or else which will not make any patched version? -
bigtonyman Desktop Powa!!!
Yea kinda lame, I'm sure some sort of fix will be made somehow though.
-
From personal experience with benchmarks Windows 8 numbers were on par with Windows 7 from my old P79 machine with a Q9200 overclocked but only with the multipliers. This was both with 3DMark and SuperPI. Now multipliers may nit affect the RTC but FSB overclocking may. This, FSB change, I was unable to do with the machines I have here...................
-
So could anyone explain why this is a Microsoft problem? The only way it can be explained is if the system clock (not the RTC - Real Time Clock) uses a FSB dependent timer. The RTC uses a dedicated clock crystal and so is reliable. Now using another timer for keeping system time is logical as each RTC access is extremely slow. Now overclocking can cause problems if the system timer suddenly changes frequency but whose is the fault then?
-
@Megol, stop being devil's advocate. You are not doing this well anyway.
-
It is FSB apparently is the issue if you read some of the news posts. Now I am not sure if Windows 8 uses the hardware RTC or a software one or some hybrid code. M$ tends to keep a tight lid on these things..............
Edit;
http://www.pcr-online.biz/news/read...n-from-overclocking-and-benchmark-site/031698
Microsoft's SHAME! Windows 8 Benchmark Records No Longer Accepted At HWBOT! Benchmark Result Veracity Compromised
Discussion in 'Windows OS and Software' started by James D, Aug 19, 2013.