Turbo all cores in Sandy/Ivy Xeon processor
Turbo all cores in Sandy/Ivy Xeon processor
I installed a Xeon e3-1240v2 on an Asrock Z75 Pro 3 board. These chipsets behave like the Z77 in practice. Locked Sandy/Ivy CPUs can be configured for turbo across all cores, reaching up to 400 MHz beyond the standard boost (though Intel apparently removed that feature with Haswell). Why won’t this Xeon stay above 3.6GHz on every core? The maximum turbo boost per core is only 3.8GHz. Even though I set the core ratio to "All core" and the All-core ratio to 38, it still acts like a non-overclocked chipset under stress. Is this the effect of the "multicore enhancement" introduced with these chipsets? It’s hard to find clear guidance on this today, especially since 1155 boards are less common. I’m frustrated and trying to figure it out on my own.
This might offer useful guidance https://www.overclock.net/threads/overcl...e.1712904/
I found something similar, but the person who posted last hasn't uploaded anything to YouTube. It seems the board in question is an Asrock Z75 Pro3, which doesn’t appear to have strong finite control compared to my Asus P8Z77-V LX board. I plan to replace them tomorrow to test if it will work properly. Unless my assumption about Ivy Bridge chips isn't right, I hope I can get the Xeon to run at 4.0GHz on all cores—about 3600MHz turbo plus 400MHz headroom for those CPUs.
No response. Changed the setup to an Asus P8Z77-V LX and the same issue occurred. It doesn’t let you adjust the turbo core frequency for each one. Asus multicore improvements don’t help. I tried a program named "Throttle stop" in Windows 10 on both units, but it confirmed the 4-core turbo multiplier maxed out at 3.6GHz and showed no overclocking options. So, for future builds, only the base clock matters. Or you need a very particular motherboard to tweak each core. Or maybe Intel finally closed that loophole with unlocked chips? The situation is frustrating. Womp womp.
Sure, it's true that Xeons aren't typically associated with heavy overclocking. You did a solid attempt, though.