Effective clock readings show discrepancies across OC channels.
Effective clock readings show discrepancies across OC channels.
The feedback is appreciated. You can review the discussion here: I initially believed the issue was resolved using the static manual OC. Now it's working with Auto Core Multiplier and MCE enabled, but with a -0.7mV negative offset. Everything seems fine when ThrottleStop is active. It just needs to be present.
Observed unusual performance where my Effective Clock didn't reach 5100mhz despite a full load stress test. Instead, it fluctuated between 4900-5050mhz. The issue stemmed from the "Energy Efficient Turbo" setting being enabled in Auto mode. Switching it to Disabled, as recommended by BIOS, resolved the problem and brought the Effective Clock up to 5100mhz after reset.
I searched for that configuration but didn’t locate it for my mobile device. I’m also not relying on turbo mode for this version. It’s worth mentioning that after running Throttlestop, at least for me, the problem stays fixed until the next restart. So I’ve kept it active at startup and then closed it to conserve the small amount of memory it consumes. I’ve noticed similar feedback about stable clocks in hwinfo64 elsewhere, but my tests show consistent results before and after Throttlestop, matching significant changes in Cinebench R20 scores. Before applying Throttlestop, my 9600k ran at 4.7ghz with core scores between 2400-2600 in Cinebench R20, while hwinfo64 reported around 4450-4550mhz on the first core and 4550-4650 on others. After Throttlestop, hwinfo64 consistently showed 4700mhz across all cores and scored reliably in the 2800s in Cinebench R20.