Among DIY PC builders who use USB audio interfaces for DTM (desktop music production) or streaming, quite a few have found themselves plagued by "pop" noises or audio dropouts every few minutes the moment they switch to an AMD system. Cases have been repeatedly reported in the DIY PC community where users suspected the cable, then the power supply, and finally the codec chip itself—replacing it without the symptoms ever disappearing. On July 9, 2026, TechPowerUp reported that the core of this issue lies not in codec chip lottery but in the bus design of the platforms adopted by Intel and AMD respectively. The key point is that even when the same Realtek ALC4082 chip is used, the wiring philosophy from the CPU to that chip is completely different between Intel and AMD.

AD

The True Nature of Patchy USB Audio Dropouts on AM5 Systems

The symptom is simple. While playing music on an AM4/AM5 motherboard equipped with a USB-connected audio codec, the audio drops out or intermittent crackling noise comes from the speakers. In one reported case, this symptom occurred every 10 to 15 minutes. On threads in AMD's official community forum, this type of instability has been reported for years in PCIe Gen4 environments.

The codec chip itself, which tends to be the first suspect, actually does have a track record. The USB-connected predecessor model, the ALC4080, has had numerous reports on user forums of random static noise occurring on boards from multiple vendors including ASUS, MSI, and Gigabyte/AORUS, with several users reporting recurrence even after firmware patches (this is not an official defect acknowledgment by any of the vendors).

But what TechPowerUp pointed out is a separate phenomenon occurring apart from this defect. Even on AMD boards equipped with the ALC4082—which shouldn't be as flawed as the ALC4080—cases have been confirmed where DPC (Deferred Procedure Call) latency spikes cause noise. A DPC latency spike refers to a phenomenon where poorly optimized drivers or hardware monopolize CPU processing time, causing interrupts for other processes such as audio to be deferred. To the human ear, this is heard as a "pop" crackling sound. In other words, even with the same codec chip, behavior varies depending on how much CPU time peripheral device processing consumes and how much of that burden spills over onto audio processing—shifting the finger-pointing from the chip itself to the processing design of its surrounding environment.

Intel's "Priority Lane" vs. AMD's Lack Thereof: The Fork Between DMI and Standard PCIe

On Intel platforms, both the legacy Azalia (HD Audio) bus and the newer USB-connected codecs terminate their wiring not at the CPU but at the chipset (PCH) side. According to TechPowerUp, Intel has smoothly integrated USB codecs by wiring them to USB 2.0 ports on the PCH. The CPU and PCH are connected via a dedicated link called DMI (Direct Media Interface), and while DMI's physical layer repurposes PCIe, it is equipped with a priority-based QoS (Quality of Service) mechanism.

This is a mechanism similar to network bandwidth control, designed so that even when an NVMe SSD or RAID card is streaming large amounts of data, audio or USB interrupts are less likely to be pushed to the back of the queue. DMI 4.0 was first adopted with the 600-series chipsets of the Alder Lake generation and carried over to the successor Raptor Lake generation (700-series). Bandwidth doubled compared to DMI 3.0, but the focus of this article is less on bandwidth itself and more on the presence or absence of "priority pass-through" control logic.

On AMD platforms too, most motherboard designers wire the USB codec to a USB 2.0 port on the chipset (FCH), no different from Intel. The difference lies beyond that point. The link connecting the AM5's FCH and SoC is standard PCI Express, which lacks a dedicated QoS mechanism like DMI. In addition, the AM5 SoC itself has a small number of built-in USB ports, which are sometimes wired directly into Infinity Fabric (the SoC's internal interconnect network) without going through the chipset.

TechPowerUp analyzes that no such priority control appears to be used on AMD's FCH-SoC link, making arbitration essentially a first-come, first-served affair. The PCIe standard itself does define priority control mechanisms via Traffic Class and Virtual Channels, so it's not that "standard PCIe means no priority control" per se. However, neither the TechPowerUp article nor AMD's official documentation contains any description of AMD's FCH-SoC link implementing or utilizing such mechanisms for audio purposes, so whether priority control is actually functioning remains an unconfirmed analysis. Even so, the article's view is that the single factor of whether priority control exists or not makes logical sense as an explanation for why the same USB codec chip behaves differently between the two camps.

AD

Is Reverting to "Legacy Circuitry Over the Latest" Really the Smart Choice?

If newer USB-connected codecs are more susceptible to being caught up in bus congestion, one hypothesis emerges: the higher-end the motherboard, the more it should revert to the legacy HD Audio approach. Indeed, some X870-series high-end boards avoid USB-connected codecs like the ALC4082, instead adopting a configuration that pairs an ALC1220-series chip via the legacy HDA connection method with an ESS Sabre-series DAC (note that the ALC1220-series part number itself can be implemented with either HDA or USB connections, so the "legacy" configuration referred to here means an implementation that chose the HDA connection). Given that mainstream-generation codecs using the HD Audio connection method have remained capped at sample rates up to 192kHz, while demand from the professional audio market for 32-bit/384kHz and DSD playback drove the shift toward USB codecs, this looks like a "throwback" that sacrifices performance in favor of stability.

However, this hypothesis breaks down with the ASRock X870E Taichi. This board adopts the USB-connected ALC4082 while pairing it with an ESS SABRE9219 DAC boasting an SNR of 130dB—a counterexample that doesn't fit the generalization that "high-end machines avoid USB codecs." To be precise, though, what this external DAC improves is the sound quality (SNR) of the analog output stage; it does not resolve the DPC latency spikes themselves that occur during the process of the ALC4082 sending data over USB. In other words, what the X870E Taichi demonstrates is neither "avoid the new chip" nor "avoid bus congestion," but rather a design decision to "accept the noise risk inherent to the USB codec while separately boosting output sound quality."

The camp that fully returns to HD Audio cuts off the risk at its root by eliminating the USB codec that is the source of the problem in the first place. Meanwhile, the camp that retains the ALC4082 while reinforcing it with a DAC chooses a path of accepting the noise risk via USB in exchange for securing output sound quality. Both are "contrarian" moves, but they head in opposite directions—and what the latter reveals is that countermeasures against DPC latency spikes cannot be completed through DAC selection alone. In the end, it comes down to a more upstream decision: which port the motherboard maker wires the USB codec to, or, if the user is using external audio equipment, which USB port they choose to connect to.

What to Check Before Buying Is Where the Port Connects

This difference in bus design isn't something you can discern just by looking at a spec sheet. In the TechPowerUp comments section, one user reported that reconnecting their external DAC to a CPU-direct USB port resolved the crackling—a single reported case. Based on this, it's recommended to check where the USB ports on an existing system connect (directly to the CPU or via the chipset) using a system information tool like AIDA64, and avoid the problematic port by plugging into a different one (this is not a guaranteed fix backed by verified testing or an official manufacturer statement). If you're buying a motherboard, taking the extra step of checking the port lineage in the block diagram or manual serves as a practical defense against trouble. USB audio interfaces from Focusrite and Universal Audio, commonly used by DTM users in Japan, are not exempt either. The same symptom could occur depending on which port they're connected to.

Intel stands to benefit. DMI's QoS mechanism becomes a selling point for overall platform stability, and USB audio's reputation ends up working in Intel's favor as a result. A personal blog called "Mixed Signal Systems Lab," run by someone claiming to be a semiconductor designer, ranks USB controller stability in the order of Intel, Renesas, Fresco Logic, ASMedia, and VIA—and by this ranking, Renesas controllers would also stand to benefit as an alternative option. However, this is not an industry-standard evaluation; it should be taken with the understanding that it's merely one expert's independent blog assessment.

On the flip side, AMD and ASMedia are left standing on the losing end. Regarding the cause of the USB instability that has been reported in AMD's official community for years, two independent theories coexist: TechPowerUp's bus design theory (the analysis that the standard PCIe link between the FCH and SoC lacks a QoS mechanism), and Mixed Signal Systems Lab's theory attributing it to the implementation quality of ASMedia's controller IP. There is not yet enough material to definitively pin down either one as the sole cause.

This isn't irrelevant to DIY PC users in Japan either. AM5 motherboards and LGA1700/1851 motherboards from ASUS, MSI, Gigabyte, and ASRock circulate in the same product lineups domestically, and those who use USB audio interfaces for DTM or streaming can factor this design difference into their decision when choosing which platform to build next.

AD

What the Next-Generation Platform Question Is Really About Is the Bus Design Philosophy Itself

As far as can be confirmed from the TechPowerUp article, there's no mention of how this design challenge might be improved in AMD's next-generation platform. Intel's DMI approach isn't a silver bullet either. Given that NVMe, USB, and audio all share DMI bandwidth, similar congestion can occur under heavy load—a point the article touches on only lightly without diving deeper. In other words, this isn't simply a story of "Intel wins, AMD loses." It's closer to the reality that a choice in design philosophy—whether to interpose priority control or make do with standard PCIe—just happens to have surfaced through the particular use case of USB audio today.

Whether AMD will give its next-generation SoC's audio path priority control, or whether it will adopt a USB controller IP from a vendor other than ASMedia, remains unannounced at this point. But as the X870E Taichi example shows, the risk inherent to onboard USB codecs itself cannot be eliminated simply by adding a DAC. The onboard wiring is left to the motherboard maker's design, and all users can do is choose which USB port to connect to when using external audio equipment, and assess a board's wiring tendencies before making a purchase.