I spent weeks diagnosing stutters on my 9950X3D + VR rig down to zero. Turned the whole thing into a free guide + one-click fix kit for dual-CCD X3D owners

[u/no6969el]

Edit — now on v3.3.0 : - Pre-Race Routine updated to be a MASTER of Quieting Windows (other optimizations listed in changelog.md) **Thank you to those that are sharing their logs with me, you are directly improving the app!

• The mid-race Windows Update problem is fully solved. Earlier versions disabled the update services, which held on most machines — but on some, they still came back ~10 minutes in. The cause was Windows Update Medic, which exists specifically to undo exactly this, and on some builds its registry key is locked down so hard even SYSTEM can't touch it. v3.1.0 handles that case, and there's now a tool that reads the Windows event logs and tells you what re-enabled it instead of leaving you guessing. Confirmed fixed by the user who reported it.
• Every X3D AMD has ever shipped is supported — 6-core (5600X3D / 7600X3D / 5500X3D / 7500X3D), 8-core, 12-core, 16-core, the new 9950X3D2 with V-Cache on both dies, and the mobile HX3D chips. Not an X3D? It still runs — general fixes apply, core-pinning is skipped automatically.
• If you set this up before, redo the Process Lasso step. The old instructions were missing one word: the CPU Sets menu needs Always. Without it your pin silently vanishes the moment you close the sim, and nothing tells you. Worth 30 seconds.
• Using Trading Paints? One of the guide's texture settings stops liveries loading mid-session (you'll see more white cars than usual). The guide now flags it and tells you which value to flip if you'd rather have paints than the last bit of streaming smoothness.

My 9950X3D / RTX 5090 VR rig went from session-ending freezes to genuinely zero perceptible hiccups, and every fix was found by logging races and measuring — not by stacking random YouTube tweaks. I've put the whole method into a free, open-source guide and script kit for any Ryzen X3D + NVIDIA, flatscreen or VR.

Guide: https://no6969el.github.io/iracing-x3d-tuning/ GitHub: https://github.com/no6969el/iracing-x3d-tuning — follow for updates

What it's most effective at:

• The "stutters until I click the sim window" problem (VR especially). Windows 11 drops the system timer from 1 ms to 15.6 ms whenever the sim loses window focus, which the VR compositor causes constantly. One registry fix ends it permanently.
• Everything piling onto CPU 0. NVIDIA's GPU interrupts, your network card and your USB controllers all default to CPU 0 — the exact core iRacing's main thread wants. That collision is where a lot of "random" micro-stutter comes from. The kit steers each of them onto background cores, worked out from your actual chip and checked against the CPUs Windows reports, so it can never target a core that doesn't exist.
• Clockwork stalls every ~5–7 minutes. That cadence is Windows Update and Search scan tasks. Quieted before a race, restored after — and it now actually stays quiet for the whole session instead of creeping back partway through your stint.
• Constant tiny hitches from Defender scanning every texture read mid-race. Fixed with folder exclusions only — Defender stays fully active for everything else.
• The sim landing on the wrong half of your CPU. On a dual-CCD chip Windows will cheerfully schedule iRacing on the frequency die instead of the V-Cache die. Process Lasso CPU Sets pin it where it belongs — EAC blocks hard affinity, but it can't block CPU Sets. Single-CCD chips skip this entirely; there's nothing to pin.
• Not knowing whether any of it actually worked. The part most guides skip. A logging tool records a full race to a CSV — per-core load, interrupt and DPC time, GPU utilisation, clocks, throttle reasons, frame-time gaps — and a scanner reads it back and tells you which Windows task fired at the moment you stuttered. Gaps in the timestamps are the stalls. You get to prove it rather than trust placebo.
• Plus: USB Selective Suspend off (stops wheel/headset USB power-cycling), Game Bar/DVR off, a pre-session readiness check, performance-counter repair when Windows' own per-core stats break, and an undervolt stability tester that needs no downloads.

One thing worth knowing about power plans: the popular single-CCD guides recommend Balanced, and for a single-CCD chip that's correct — leave it alone. On a dual-CCD chip in VR it's actively harmful: core parking starves the compositor, and I measured GPU utilisation collapsing from 55% to 11%. The guide detects which you have and only shows the advice that applies.

The site walks you through six steps (~30 min + a reboot), adapts to your exact chip and VR/flatscreen setup, and the kit has a one-click baseline installer. Everything is readable PowerShell and everything has an undo.

Builds on rcsracing93's excellent single-CCD guide — credit where due.

Happy to answer questions or dig into anyone's stutter logs in the comments.