High DPC Latency and OBS Studio Micro-Stuttering

High Deferred Procedure Call (DPC) latency can cause severe micro-stuttering in OBS Studio streams, even when your GPU usage sits well below 50%. This article explains how DPC latency interrupts critical frame delivery pipelines, why hardware utilization metrics fail to reflect the problem, and what specific driver, BIOS, and system power behaviors trigger these transient delays.

Understanding DPC Latency in the Streaming Pipeline

A Deferred Procedure Call (DPC) is an operating system mechanism in Windows that manages interrupt processing. When hardware tasks occur—such as a network packet arriving or an audio buffer filling—the hardware issues an Interrupt Service Routine (ISR), followed by a DPC to execute the heavier deferred work.

OBS Studio requires consistent, real-time access to the CPU and GPU to capture, compose, and encode frames at steady intervals (e.g., precisely every 16.6 milliseconds for 60 FPS). When a misbehaving driver holds the CPU in a prolonged DPC routine, it delays all other system processes. Even if your GPU is idling at 30% to 40% capacity, the compositor cannot deliver frames to the encoder on time, leading to frame drops, erratic frame pacing, and visible micro-stuttering.

Why Low GPU Load Masks the Problem

A common misconception is that stuttering must be caused by hardware saturation, such as a maxed-out GPU core or overloaded VRAM. DPC latency, however, is an operating system and driver scheduling bottleneck, not a raw throughput limitation.

In fact, maintaining a low GPU load can sometimes worsen the issue. When GPU utilization remains low, the graphics driver and system power plan actively attempt to downclock hardware components into aggressive low-power states (such as PCIe Active State Power Management or GPU P-States). When OBS suddenly demands a frame compositing pass, the transition from an idle or low-power state back to a high-performance state creates transient latency spikes that disrupt frame rendering deadlines.

The Primary Causes of DPC Latency Spikes

  1. GPU Driver Interrupts (nvlddmkm.sys or amdkmdag.sys) The primary display driver frequently causes DPC latency spikes when dynamic power-saving routines miscalculate workload changes. Variable refresh rate technologies (G-Sync/FreeSync) operating across mixed-refresh-rate multi-monitor setups can also cause the driver to delay frame presentation.

  2. Network Drivers (ndis.sys) Network interface cards (NICs), particularly Wi-Fi adapters or onboard Realtek/Intel Ethernet controllers running default Windows drivers, regularly introduce high DPC overhead. Features such as Energy Efficient Ethernet, interrupt moderation misconfigurations, and outdated network drivers frequently block system execution queues while processing high-bitrate video traffic.

  3. Audio Subsystem Drivers (portcls.sys or USB Audio) Real-time audio processing requires low-latency handling. Incompatible Realtek high-definition audio drivers, virtual audio cables, or unoptimized USB audio interface drivers can saturate the DPC queue, causing streaming software to hitch while waiting for synchronized audio/video packets.

  4. BIOS Power Configurations (C-States and SpeedShift/SpeedStep) Deep CPU sleep states (C6/C7/C8) can introduce significant wake-up penalties. When OBS and the underlying game periodically alternate between demanding and relinquishing CPU cycles, the CPU constantly enters and exits low-power states. The microsecond delays incurred during these power transitions prevent OBS from meeting strict frame submission deadlines.

  5. USB Hub and Bus Saturation Streaming setups often rely on multiple high-bandwidth USB devices plugged into the same internal root hub, such as capture cards, webcams, and external audio interfaces. If the host controller is overwhelmed or poorly optimized by system drivers, it queues high-priority hardware interrupts that stall the entire processing chain.

How to Identify and Resolve DPC Latency

  • Diagnose with LatencyMon: Run the LatencyMon utility during a test stream. Check the "Drivers" tab and sort by highest execution time to identify the exact driver file (nvlddmkm.sys, ndis.sys, etc.) responsible for the highest DPC routines.
  • Configure GPU Power Management: In the NVIDIA Control Panel or AMD Software, set the power management mode for OBS Studio (or globally) to "Prefer maximum performance" to prevent hardware downclocking during live streams.
  • Disable Hardware Power Saving: Turn off Energy Efficient Ethernet and Green Ethernet in your network adapter's device properties. In Windows Power Options, set PCIe Link State Power Management to "Off."
  • Stabilize CPU Power States: If latency spikes persist, enter your motherboard BIOS and test disabling deep C-States (leaving basic C-States enabled) to reduce wake-up latency penalties across processing cores.
  • Balance USB Controllers: Distribute high-bandwidth devices (such as USB capture cards and 4K webcams) across separate physical USB controllers rather than daisy-chaining them onto a single hub.