Before Auditing the Full FAQ one by one Later , There is the core unfiltered point and vision of stutter guard and the way i think:
unfiltered version — why I built this and why it isn't just a 9950X3D/X3D App:
Just moving interrupts out of CPU 0 and stopping device contention on a single core gets you 90% of the benefit on any CPU. Hybrid platforms like dual-CCD X3D and Intel P/E are what I talked about first because (1) my primary gaming PC is a 9950X3D, and (2) I wanted to show the app handles complex topologies cleanly no matter How Obscure the CPU toplogy looked like. On paper Windows schedules and balances work across cores; in reality, default Windows placement still piles GPU, USB, network, and audio interrupts and the DPCs tied to them onto CPU 0 and my app addresses that Properly ,The app Behaves Differently depend on the CPU it sees , if its a regular 9700x for example it still separates Interrupt heavy devices from each other (and away from CPU 0-1 which Generically coded apps love) , you dont need process lasso at all in fact i don't recommend separating the PROCESS affinity in process lasso on Single CCD or Single Chip processors because There aren't that many cores to spare to leave As a Sole single device interrupt handler. (I have Stutter guard on other systems but What i had benchmarked are latency Mon numbers that most of you don't want to see)
doing it on Dual CCD or intel hybrid as a gaming /Audio Workstation Profile is just a luxury The app offers , Not a requirement
I also don't know if i mentioned this in the readme or any where on the app THE PROCESS LASSO PROFILE MY APP GENERATES FOR HIGH CORE COUNT CPUS IS FOR LATENCY SENSTIVE WORK (GAMING/AUDIO WORK ONLY) , If You are running all core loads Where Through put only matters and Performance ACTUALLY scales linearly with core count (Y-cruncher, CineBench ,etc...) you do like i do Myself and have a Daily mode on hand Which just defaults affinity to all cores That is what i do on my personal rig Or The specific App that Wants throughput gets an all core exception on the gaming profile if you are forgetful Both implementations work
There is universal gain to be had on standard Windows setups that doesn't require 3D V-Cache or multiple CCDs: Stutter Guard's AMD GPU idle-power tweaks cut amdkmdag.sys wake routines and low-load clock swings (for example, MK1 capped at 60 fps where Adrenalin lacks NVIDIA's global "Prefer Maximum Performance" option and drops clocks erratically at certain exact light loads — MCLK DPM stays gated as Costly while idle-power keys are Measured), i had this happen on MK1 What helped is running AMD VSR and running the game at over 4k (Or Using the Amd idle Power Registry settings), disabling Windows/Device Manager power saving (MSPower_DeviceEnable) and link-state sleep stops D3 -> D0 wakeup DPCs across storage, network, and USB, and fixing Windows 10 2004+ per-process timer isolation cleans up wait-bound frame pacing , All the prior mentioned Device manager/Tertiary device Powersaving Features Have absolutely negligible impact To Any one on Desktop let alone someone Who is on a static overclock or Running aggressive PBO (That was One of the main Reasons of me Posting on r/Overclocking First before any other place )
My main audience (Gamers/Audio engineers) Care Mainly about consistency and stability only .
I built it as an all-in-one tool for Windows CPU/driver latency and mismanagement. The only stutters it cannot fix are :
traversal stutter (for example, a buggy asset pipeline trying to stream assets aggressively or asking too much in a short amount of time unrealistically)
shader compilation stutter (because the game is asking the CPU to compile a shader you were already supposed to see on screen — the only way that doesn't stutter is if the shader is already there or at least preloaded/compiled in the background like Microsoft ASD or AMD's newer Adrenalin 26.9.2 driver does).
I try To include as many Windows/Game Dev Related Edge cases/Fuckups as possible:
on Win10 2004+ Windows decided to introduce timer scheduling per process
(That is when Windows Decided To assign Timers per application as a power saving feature , in theory it is supposed To keep Modern Games OR Heavy latency senstive work loads Having fast timers and Background apps having slower)
In practice , like Crysis 3 (2013 , not the remaster) locking/bottlenecking around 64-65 fps , if we look at the max timer resolution a process can have on windows Which is 15.625 ms and we calculate the fps (1/ 0.015625) and we get 64hz which applied in the real world
This wasn't Research this was me playing an old game on my own System
Because The 2013 version was never coded To Ask For a 0.5 msec Timer The New Way on Win10 2004 and ownwards
Emulators like Dolphin, Rpcs3 , Pcsx2 Had the same Problems
Theoritacally any game Coded/not updated before Windows 10 2004 can have this problem , let alone lazy ports
Am i The only when who plays old games or what ?
What my app Applies is The old school system of assigning a global timer to all apps (Registry Key Read by Windows by default Not a specifically coded for aspect of the tweak) and then forcing the timer to be 0.5msec using an application That just asks for the Timer to for itself and the global timer setting that is basically amounts too (Apply the fastest Timer of all the apps asking for timers) , It doesn't interact with any other apps it just asks for a 0.5 msec the same way any application can , All other timer tools That Exist work the same way i just explained it and included it as part of an all in one solution
So, Someone else doesn't have to do Research on why That game from 2009 he played as a child or teen is a stuttery mess or frame capped on a system that can run it at a thousand fps if it actually came down to raw horse power
(GlobalTimerResolutionRequests + 0.5 ms logon holder App , gated behind Anecdotal / Everything), that exists To get the most consistent experience running any app , Running that as a scheduled task on startup on a laptop is not recommended (it wont Break anything it will just affect battery life ) , on the desktop you will have a hard time even calculating the power usage
I put my focus and the spare time i have actually improving the app , some of you mentioned Edge cases Which caused me To retest and improve the app and getting the app working on CPU topologies i haven't even sat Infront of , The Automation level of the app is ambitious to say the least (On Purpose) , Constant feed back is What keeps this improving
A generic llm FAQ is Not enough to get that point accross while also not addressing misunderstandings directly is bad for the app's reputation
I have non-X3D rigs on hand (5800H + RTX 3070 and 7700HQ + GTX 1060 Max-Q) alongside this desktop — I'm just under a tight time constraint right now due to my current commitments, The hardware is there But the time to Address absolutely every point of speculation imaginable all at the same time Then you bet i am putting that time on the app solely and i am doing my best to address all your concerns by hand , Whenever I have spare time, I spend it getting the app running the way I originally envisioned when I started.
There will also be your scheduled LLM FAQ summarization (don't worry i actually audit and Rewrite those to keep a clear conscience , every point addressed is read ,you can be sure of that) on another post
I'd be happy if some people who have the same mindset and have the spare time to A/B Test and talk to me to prove or disprove Stutter guard's effect on Gaming whether it be GPU or CPU Bound scenarios on Accurate monitoring apps like CapframeX or audio work, You are completely welcome to do so no matter your setup, that is the whole point
Repo (GPL-3.0): https://github.com/Kareem-Shabaka/stutter-guard
Latest release: https://github.com/Kareem-Shabaka/stutter-guard/releases/latest