Effective clock readings show discrepancies across OC channels.
Effective clock readings show discrepancies across OC channels.
Update: Ran into an error in Prime95 for the first time after running more tests at about the 45 min mark. No more room to up the voltage so I dropped it from 48x to 47x and from 1.33v to 1.3v, no errors yet but it's having the same problem. Ran 4.7 effective for maybe 10-15 mins on the fresh settings, then started throttling without lighting up any throttle indications in hwinfo. Run Throttlestop and now it's 4.7 steady, it's got plenty of thermal headroom trying to run this easier OC too. I'd flash the bios to see if that helped but I don't have spare hardware if that goes wrong, and I can't do without a computer right now while waiting for parts. So without knowing what Throttlestop is fixing I don't know what I can really do about it other than grin and bear it.
This seems like a solid approach for now, and I appreciate the work you've done to resolve this issue!
CPU performance varies when threads aren't fully utilized. Once all threads are engaged, the effective clock remains consistent per thread. Start the system and test Cinebench R20 to see your real-time speeds. For more details, check the download page from TechPowerUp.
Hi @unclewebb, this seems to be the next part of my discussion. I'm currently at the office but recall that when CBr23 is running, the average Effective Clock according to HWInfo64 is 4645Mhz, with one core reaching only 4450Mhz. If I enable ThrottleStop without making any changes, the Effective Clock should remain consistent across all cores and match the stable 4800Mhz readings from discreet clocks. I'll share a screenshot once I get back later today.
You're likely experiencing odd Cinebench performance due to the CPU throttling at lower clock speeds. It seems like the processor is adjusting its speed slightly, possibly because of thermal constraints. This behavior isn't uncommon across Intel systems, though it's hard to pinpoint the exact cause without more details.
@unclewebb Here’s the update: full Effective Clock gives 16135, while the "weird" clock shows 15200. The VRM temperature stays stable at 53°C. Same as @SGTChalk, no noticeable throttle limit appearing.
As agreed, here are the screenshots: 1. When ThrottleStop isn't running, clock runs at 4600mhz. 2. With ThrottleStop active, clock drops to 4799mhz. Just enabled ThrottleStop and didn’t change anything. Not a single option adjusted. I’ve set it to auto-run via Task Scheduler now.
Sorry for the delay in responding. It seems I probably overlooked the notification email. I assumed the problem was with my old BIOS, but now it looks more like something specific to your setup—especially with one core showing a much lower effective clock than the others. I can share my thoughts if you'd like, though I don’t have much new to contribute. I’m also checking if my friend with a 10700k is open to reviewing this since it seems to be a recurring issue. It might be worth looking at their profile too.