Driver Stuttering: How to Diagnose and Fix It (DDU, DPC Latency)
Driver stuttering happens when faulty, outdated, or conflicting drivers introduce delays in how your hardware talks to Windows. The problem sits at the kernel level, which is why it produces micro-stutters even while your FPS counter shows a rock-steady number. A single bad driver can add 5-50ms of delay to every frame, and those hitches never show up in Task Manager or on an FPS overlay.
The usual culprits are GPU drivers (especially right after an update), USB or audio drivers, and chipset power management drivers. Across the logs uploaded to SmoothFPS, a DDU (Display Driver Uninstaller) clean install resolves about 40% of driver-related stuttering on the first pass.
Jump straight to the fixes?
Open the Driver Fix WizardWhat "driver stutter" looks like in real gameplay
Driver-related stuttering is usually spiky and irregular. If your performance has dropped across the board rather than showing isolated hitches, start with our complete stuttering diagnosis guide to rule out the more common causes first.
- Sudden hitches in the frametime graph that don't line up with anything visually complex happening on screen.
- Average FPS looks smooth but the motion feels choppy because the frame pacing underneath is uneven.
- Stutter that shifts in character right after a driver update, a Windows update, or a new background utility or overlay installation.
Why drivers cause stutter: two common mechanisms
CPU-side stalls (ISR/DPC latency)
Drivers talk to hardware through interrupts. Every mouse click, audio sample, and network packet fires an interrupt that a driver has to service. If the driver sits too long handling that interrupt (ISR) or its follow-up deferred work (DPC), it blocks the CPU from scheduling the game's frame thread on time. The result is a missed frame deadline → visible hitch.
This category often correlates with:
- Micro-freezes that feel "system-wide"
- Audio pops or crackles arriving alongside the visual stutter
- Mouse and input feeling sticky or laggy during the spikes
- Stutter that shows up even with no game running
GPU-side stalls (render pipeline, compilation, presentation)
The graphics driver is the translation layer between a game engine and the GPU. Stutter appears on this side when the driver or engine forces an expensive piece of work at the wrong moment, and you usually see it as sudden GPU utilization drops:
- Shader compilation / pipeline creation (common source of "first-time" hitches)
- Driver overhead (extra CPU time preparing draw calls and GPU commands)
- VRAM/resource management (streaming + eviction can cause bursts of work)
- Presentation/compositor behavior (how frames are displayed via Windows)
This category often looks like:
- The Windows desktop runs smoothly, but the game hitches
- Some titles are affected much more than others
- A new driver or game patch suddenly changes how smooth things feel
Drivers most commonly involved (it's not "just GPU")
Frametime instability, random-feeling hitches, driver-level regressions after an update, overlay conflicts with Steam or Discord, and differences in behavior between DX11 and DX12/Vulkan paths.
Stutter that arrives paired with audio pops or crackles, plus timing spikes from switching output devices or leaving audio enhancements enabled.
Periodic spikes, especially on Wi-Fi adapters with power-saving enabled, and local frametime spikes during online games when the driver wakes the radio.
Asset streaming stutter in open-world titles, and short freezes when the driver handles a burst of background IO from another process.
Spikes during device reconnects, polling rate changes, and wireless dongle wake-sleep behavior.
Scheduling and timer behavior changes, device power state transitions, and laptop-specific power management. Misconfigured power states can also trigger thermal throttling issues on top of the stutter.
Why driver stutter often "starts suddenly"
Most driver stutter cases start after a change, not out of nowhere. If you can pin down what changed right before the stutter began, you're already halfway to the fix. Common triggers:
- GPU driver update (new features, new regressions, new shader cache behavior)
- Windows update (scheduler tweaks, security patches, or kernel changes that propagate down to drivers)
- New hardware or peripheral adds a new driver to the stack, which can conflict with existing ones
- New overlay, capture, or RGB utility that hooks into the render pipeline
- Game update with new shaders, new pipeline states, or a changed renderer path
None of these prove driver stutter on their own, but they narrow the search and tell you where to look first.
Driver stutter vs other common stutter types
| Comparison | Key difference |
|---|---|
| Driver stutter vs CPU bottleneck | CPU bottleneck: FPS drops consistently in busy scenes, in predictable patterns. Driver stutter: irregular spikes that can fire even when the scene is visually quiet. |
| Driver stutter vs shader compilation | Shader stutter: first-time hitches that fade as the shader cache fills in. Driver stutter: keeps firing randomly, and can affect the Windows desktop too. |
| Driver stutter vs streaming/IO stutter | Streaming stutter: tied to loading new assets or areas, and repeats in the same spots each time. Driver stutter: fires without any obvious loading trigger. |
| Driver stutter vs network "lag" | Network lag: rubber-banding, delayed hits, or desync — gameplay-level symptoms. Driver or DPC spikes: whole frame skips at once as a visual hitch, sometimes paired with an audio pop. |
Why diagnosing driver stutter is tricky
Driver problems can look like almost anything because:
- Average FPS can stay high while frametimes are unstable.
- A single bad driver might only misbehave under specific games, APIs, or device combinations.
- Multiple small issues can stack together: an overlay, a driver regression, and a bad power state all contributing at once.
That's why the fastest path is usually isolating the category first — figuring out whether you're looking at a GPU pipeline problem or a DPC/system driver timing issue — before you start changing anything.
Safety notes & warnings
Driver troubleshooting is a fast way to make a working system worse if you aren't careful. A few things to keep in mind before you start:
They tend to install the wrong driver version or bundle unrelated changes like registry tweaks and privacy settings you didn't ask for.
They're useful when you're chasing a specific fix, but any of the three can introduce new regressions and fresh instability that takes hours to unwind.
Replacing them with a generic vendor driver can break device features like fan control, RGB, special buttons, or proprietary power profiles. Check your OEM's support page first.
Running them on the wrong driver or outside Safe Mode can temporarily kill your display output or leave the system unable to boot. Have a recovery plan ready before you click anything.
Both can introduce a whole new set of instability issues that have nothing to do with your original stutter, and you'll waste time chasing problems you created yourself.
What information is most useful before moving to the fix path
You don't have to change a thing to learn where the problem is. A few minutes of observation usually tells you:
- When the stutter started, and what update or change happened right before it
- Whether the stutter only affects games or shows up system-wide on the desktop, in audio, or in your input response
- Whether one title is affected or many, which tells you if it's engine-specific or system-level
- What overlays, capture tools, or RGB utilities are running in the background when the stutter hits
- Which renderer the game is using (DX11 vs DX12 vs Vulkan) and whether switching APIs changes the stutter behavior
Having these facts in hand stops the trial-and-error cycle before it starts and sends you to the right fix first.
How to Diagnose and Fix Driver Stuttering
Work through these in order. Each step builds on what you learned in the previous one, so don't skip ahead.
Run LatencyMon to Identify the Culprit
What it does: Surfaces which driver on your system is eating the most CPU time during latency spikes.
For deeper hardware-level monitoring alongside LatencyMon, pair it with HWiNFO to track system metrics live.
- Download LatencyMon (free) from resplendence.com
- Click "Start" and play for 5-10 minutes while reproducing the stutter conditions
- Go to the "Drivers" tab
- Sort by "Highest execution (ms)"
- Any driver consistently above 1000 µs is the problem. After your fixes, you want that number below 500 µs
GPU Driver: Clean Install with DDU
When to use: Your GPU driver (nvlddmkm.sys or amdkmdag.sys) is at the top of LatencyMon's list, or you're hitting any driver-related problem on the GPU side.
- Download DDU (Display Driver Uninstaller) from guru3d.com
- Download the latest GPU driver directly from NVIDIA or AMD, but don't install it yet
- Boot into Safe Mode (Settings → Recovery → Advanced Startup → Restart Now → Troubleshoot → Startup Settings → Safe Mode)
- Run DDU → Select your GPU vendor → Click "Clean and Restart"
- After the reboot, install your downloaded driver right away before Windows tries to fetch its own
Try an Older Driver Version (Rollback)
When to use: The stutter started right after a driver update, or the DDU clean install on the latest version didn't resolve it.
For GPU drivers: Run DDU one more time, then install an older known-good version:
- NVIDIA: nvidia.com/Download/Find.aspx (Advanced Driver Search)
- AMD: amd.com/en/support/previous-drivers
For other drivers: Device Manager → Right-click device → Properties → Driver tab → Roll Back Driver
Fix Audio Driver Latency (Common Culprit)
Realtek audio (RTKVHD64.sys) is one of the most common DPC latency offenders.
Options:
- Update to the latest Realtek driver from your motherboard manufacturer's support page, not from Windows Update
- Try the generic Windows audio driver: Device Manager → Sound → Update Driver → Browse → Let me pick → High Definition Audio Device
- Disable audio enhancements: Right-click speaker icon → Sounds → Playback → Properties → Advanced → Uncheck "Enable audio enhancements"
Fix Network/Wi-Fi and USB Latency
Wi-Fi adapters are a notorious source of DPC spikes, especially with power-saving enabled on the driver.
- Device Manager → Network Adapters → Your Wi-Fi → Properties → Power Management → Uncheck "Allow computer to turn off"
- Same adapter → Advanced tab → find "Power Saving Mode" or similar → set to Disabled/Maximum Performance
- If you're using a USB Wi-Fi adapter, try a different USB port — preferably a USB 3.0 or 3.1 port on the motherboard rather than on the case.
USB controllers (Wdf01000.sys): update the chipset drivers from your motherboard manufacturer's support page. Generic Windows USB drivers rarely fix USB-side latency on their own.
Prevent Windows from Reinstalling Bad Drivers
Problem: Windows Update keeps auto-installing drivers it considers generic matches, and those aren't always the ones tuned for your hardware. This is a common trigger for Windows 11 stuttering issues.
Solutions:
- Option A: Download Microsoft's "Show or hide updates" troubleshooter (wushowhide.diagcab) and use it to block the specific driver update that's causing trouble.
- Option B: Settings → Windows Update → Advanced options → Optional updates → Driver updates → uncheck the problematic drivers one by one.
- Option C (Windows Pro or Enterprise): Open Group Policy (gpedit.msc) → Computer Configuration → Administrative Templates → Windows Components → Windows Update → enable "Do not include drivers with Windows Updates" to block driver updates wholesale.
Want the wizard to walk you through? Jump to the Driver Fix Wizard →
Known Driver Issues (2025-2026)
This section tracks recent driver releases that caused widespread stuttering for a lot of users. If your symptoms line up with a row below, the fix is usually quick.
NVIDIA
| Driver | Issue | Fix |
|---|---|---|
| 546.xx - 550.xx | High DPC latency on RTX 40 series, stuttering in DX11 games | Roll back to 545.xx or wait for 551+ |
| 555.xx | Frame pacing issues with G-Sync + frame limiters | Use RTSS limiter instead of driver limiter |
| Any with GeForce Experience overlay | Intermittent micro-stutters every few seconds | Disable overlay (Alt+Z → Settings → In-Game Overlay → Off) |
AMD
| Driver | Issue | Fix |
|---|---|---|
| 24.1.1 - 24.3.x | Shader cache corruption causing repeat stutter in DX12 games | Delete shader cache folder, update to 24.5+ |
| 24.7.x | RDNA 3 cards (RX 7000) frametime spikes in Vulkan games | Use DX12/DX11 mode if available, or rollback |
| Any with Anti-Lag+ enabled | Game crashes and anti-cheat bans | Disable Anti-Lag+ in Adrenalin per-game settings |
Intel (Arc)
| Driver | Issue | Fix |
|---|---|---|
| 31.0.101.5xxx | Severe shader compilation stutter in DX9/DX11 games | Use DX12 if supported, or wait for driver maturity |
| General Arc drivers | Lower performance in older (DX9/DX11) titles | Expected behavior — Arc optimized for DX12/Vulkan |
Not sure this is actually your issue?
Upload your HWiNFO log — if a driver problem is the cause, the analyzer confirms it in under a minute with your real sensor data.
Frequently Asked Questions
Can drivers cause stuttering even with high FPS?
Yes, and this is the signature of driver-caused stuttering. Your FPS counter can read a rock-solid 120 FPS while individual frames are being delayed at the kernel level by 5-50ms due to DPC (Deferred Procedure Call) latency. The hitches only show up in frametime graphs, never in the FPS average, which is why the counter lies to you. Use LatencyMon to see the real delays.
How do I do a DDU clean install for GPU drivers?
Five steps: 1) Download DDU (Display Driver Uninstaller) and your target GPU driver before starting, 2) Boot into Safe Mode by holding Shift while clicking Restart, 3) Run DDU and select 'Clean and restart', 4) After the restart, install your new driver with 'Clean installation' checked, 5) Reboot normally. The process wipes out every leftover trace of old drivers that could conflict with the new one. Critical: don't let Windows auto-install a driver before you install yours manually.
What is DPC latency and why does it affect games?
DPC (Deferred Procedure Call) latency is how much CPU time a driver eats while handling its deferred work, like responding to hardware events. When a driver runs long, the CPU can't deliver the game's next frame to the GPU on time, and the frame arrives late at the monitor. You see it as a stutter even though the GPU finished rendering the frame on schedule.
Is stutter always caused by the GPU driver?
No, GPU drivers are the most visible culprit but not the only one. Audio drivers, network and Wi-Fi drivers, USB controllers, and chipset drivers all sit deep enough in the kernel to cause frametime spikes. Driver stutter is often a 'stack' problem, meaning multiple drivers are contributing at the same time and you have to work through the list rather than expecting a single smoking gun.
Why did stuttering start after a Windows/driver update?
Updates can introduce regressions, shift how the Windows scheduler hands out CPU time, change power management behavior, or quietly alter the way drivers interact with the kernel. A system that was stable yesterday can become stuttery today with no hardware change at all. When stutter starts right after an update, roll back that specific update as your first move.
What's the difference between shader stutter and driver stutter?
Shader stutter shows up the first time the engine encounters a new effect or area, and it fades once the shader cache fills in. Driver and DPC stutter doesn't fade. It keeps firing randomly and often affects multiple games, and in bad cases you can see the hitches on the Windows desktop itself, which is how you know caching isn't the issue.
What is DDU and when should I use it?
DDU (Display Driver Uninstaller) is a free tool that strips out every trace of your GPU driver, including registry entries and file remnants a regular uninstall leaves behind. Reach for it when you're switching GPU brands, when persistent driver issues haven't responded to normal uninstall and reinstall, or when you need a clean slate. Always run it from Safe Mode so Windows doesn't interfere with the removal.
How do I know which driver is causing the problem?
LatencyMon (free) surfaces which driver is burning the most DPC and ISR time. Launch it and play the game where the stutter reproduces. The Drivers tab shows execution times per driver; anything consistently above 1000 µs is a problem, and after your fixes you want to land under 500 µs. The usual suspects are audio drivers (Realtek shows up often), network drivers, and USB controllers.
Is it safe to roll back to an older driver?
Yes, rollback is one of the safest troubleshooting moves you can make. Windows keeps the previous driver version on the system, so you can revert without downloading anything: Device Manager → right-click the device → Properties → Driver tab → Roll Back Driver. For GPU drivers specifically, older versions are archived directly on the NVIDIA and AMD websites if the in-OS rollback isn't available.
Why does Windows keep reinstalling a driver I uninstalled?
Windows Update auto-reinstalls whatever driver it considers a better match, which is how it brings back the one you specifically removed. Three ways to stop it: run Microsoft's 'Show or hide updates' tool to block the specific driver, pause Windows Update for a few weeks while you stabilize, or on Pro and Enterprise editions, use Group Policy to disable automatic driver updates entirely.
Next step
If driver issues look like the culprit for your stutter, run the guided fix wizard:
Open the Driver Fix Wizard