Quick Answer

A USB DAC does not normally cause true input lag; it can add audio latency or USB bus delays that feel like late response. Move the DAC to a rear USB port, use 48kHz audio, disable virtual surround, and check DPC latency before replacing the USB DAC. Use NVIDIA Reflex or AMD Anti-Lag, a 1000Hz polling check, CapFrameX and target 48kHz/24-bit audio, rear USB ports, DPC latency, and USB polling checks.

Build A Clean Baseline

Use one game, one route or benchmark pass, one preset, and one fixed cap. If the setup worked before, compare today's result with one familiar game scene instead of guessing from memory. Close capture overlays, RGB panels, browser video, and extra launchers before the first run.

Settings And Hardware Checks

In Windows 11, confirm Settings > System > Display > Advanced display shows the intended refresh rate. Then review Settings > Gaming > Game Mode and Graphics > Default graphics settings for VRR and Hardware-accelerated GPU Scheduling. In the game profile, check VSync, Reflex, Anti-Lag, raw input, and any manual FPS cap.

For the USB DAC, the practical fix is to move the DAC to a rear motherboard USB port, test 48kHz audio, remove virtual surround, and check DPC latency. Relevant reference hardware includes FiiO, iFi, Creative Sound Blaster, USB Audio Class drivers, powered USB hubs. Broad SA USB DAC pricing ranges from about R800 to several thousand rand. front USB ports, long cables, and busy hubs can create audio glitches.

Buying Decision

Keep the current part if the clean test passes. If it fails, buy only against the evidence: display timing points to a monitor or cable, USB timing to a device or port, storage spikes to the SSD, and network spikes to router placement or Ethernet.

FAQ

What should I check first for input lag on this setup?

Start with refresh rate, frame cap, and a clean baseline. Then check the driver, firmware, USB, storage, wireless, or cooling item tied to the recent change.

Should I replace the USB DAC immediately?

No. Replace it only after CapFrameX, PresentMon, HWiNFO64, a ping test, Ethernet, or direct USB shows the part is the limit.

What numbers show the fix worked?

A good result has steady 1% lows and no repeated jumps above 33ms. For 240Hz play, 4.2ms is the reference; for 60fps play, 16.7ms is the target.

TIP

Practical Check

Capture one clean run, note driver version, refresh rate, frame cap, and temperature, then compare Ethernet or direct USB before replacing hardware.