CPU/Mobo Core #0 doesn't hold clock speeds in Cinebench single-core

RadarHz

RadarHz

Disciple
cinebench r23.png

just saw that my timezone is wrongly configured

(10100F, low end H510 board)
In a 10-minute Cinebench R23 single-core run Core #0 doesn't sustain it's clock speed of 4.2GHz as long as the other 3 cores and keeps switching between 4.1GHz and 4.2. In a multi-core run I didn't see any fluctuations of this nature, all 4 cores held 4.1GHz near perfectly with sub-70 temperatures. This probably isn't a thermal throttling issue.

Is this a silicon lottery issue, or is there an actual QA problem with the unit? Perhaps a BIOS setting is inconsistent or some other Intel technology is causing this?
 
Back
Top