4501mhz or lower pls.

@subaruwc Max frequency shown at XTU result and monitoring is the one that the Mhz cap applies to, if there is something that is not clear please read the thread related to this competition.

so i can submit anything if xtu shows below 4501mhz? lol

This was not my decision alone - if XTU max freq during bench shows 4,5ghz or below, result is OK, cpuz can fluctuate, this way 4ghz was handled and 4,5ghz will be handled as well

How come at the time of the screenshot xtu is reporting eist (or slow mode) enabled (low orange line),while it says 4500 right next to it and 4507 at cpu-z.Don't these three reporting have to be on par?

What Demac said/wrote.

XTU keeps reading cpu frequency in Real-Time which is (after bench) 4.5 GHz but based on the graph it should be lower (???)

EDIT: Seems like he paused the monitoring.

If the current speed is 4.5ghz in the xtu,then the orange graph shows higher clock when the test ran,then whats the purpose of the core limit ? it should be 4.5ghz DURING testing,not during screenshot making...

If you do not agree on this result - report it for further check

nope. just strange. but I dont want to ruin the competition with whining or throw shit at somebody I dont even know,just pissed of by shitty xtu eff and try to understand if the high mem / uncore and newer version of windows is the key.

nope. just strange. but I dont want to ruin the competition with whining or throw bunnyextraction at somebody I dont even know,just pissed of by bunnyextractionty xtu eff and try to understand if the high mem / uncore and newer version of windows is the key.

the thing for me is that hwbot doesnt take into consideration CPU-Z which means that graph and monitoring of XTU is the only way to check the frequency. So IMO, rules should be strict regarding these two (graph & monitoring) for the above reason.