On Alder Lake and Raptor Lake (12th/13th gen), the whole game comes down to how Windows 11’s Thread Scheduler interacts with Intel’s Thread Director, and honestly most competitive titles don’t benefit from manual core pinning the way older guides claim. The scheduler is generally smart about routing your game’s primary threads to P-cores while letting background stuff drift onto E-cores, but the problem players actually hit is stray threads — a game with poor affinity handling (CS2’s Source 2 engine, some Ubisoft titles, older Unreal builds) will occasionally drop a critical render thread onto an E-core mid-match, and that’s where you see micro-stutters and 1% low spikes, not average FPS drops. If you’re on a 13700K/13900K or higher with a big E-core count, I’d strongly recommend turning off background apps and letting Thread Director do its job rather than forcing affinity via Process Lasso, because manually pinning to only P-cores often makes things worse by starving the scheduler of the flexibility it needs to rebalance.
🎮 Battlestation & Rig: i7-14700K | RTX 4070 Ti Super | 32GB DDR5 6400 CL32 | Lian Li O11 Dynamic | LG UltraGear 27GR95QE-B 27″ OLED 240Hz | Razer Huntsman V3 Pro TKL + Razer Viper V3 Pro + Pulsar Superglide Glasspad | Sennheiser HD 560S Open-Back + Creative Sound BlasterX G6 DAC
📍 London (UK)
"Chasing the silicon lottery one megahertz at a time."
