ASUS Xonar cards and AMD Ryzen AM4 motherboards compatibility report

Some AMD AM4 motherboards (Ryzen CPUs) have some compatibility issues with ASUS Xonar sound cards. These issues will manifest as system rebooting or showing a BSOD when installing Xonar drivers or when changing various Xonar settings such as switching from speakers to front panel headphones. Below you have a list that I've compiled with user reported compatibility status of their Xonar card and AM4 motherboard. The list will be periodically updated.

Boards that are listed as having compatibility issues with specific Xonar sound cards may also have issues with other PCI/PCIe cards like other sound cards, network cards, RAID cards, etc.

Note that the compatibility status may vary depending on BIOS version, on installed CPU (#1), it may vary depending on which Xonar card do you have, if it's a PCIe or PCI card, it may be affected by whether the Xonar card was plugged in a PCIe slot that is connected to the chipset or one that is connected to the CPU (1st and 2nd x16 slots on X370, X470, X570 motherboards). Particularly affected by these compatibility issues seem to be the Xonar Essence STX II cards, which have an ASMedia PCI-to-PCIe bridge instead of the PLX PCI-to-PCIe bridge that the rest of PCIe Xonar cards have. Xonar D2X looks like another card that's particularly affected. So a motherboard on which a STX II or a D2X card has problems, might actually work with a different Xonar card.

The issue caused by BIOSes with AGESA where systems are not booting while the Xonar or other PCI-e card are plugged in the motherboard is a different issue than the compatibility issues described above and which are the main subject of this page. This issue is treated separately in the "BIOSes with AGESA caution" section and it is not reflected in the entries in the compatibility list.


  1. Compatibility status list
  2. Possible solutions for BSOD and restart issues
  3. How to verify if it's stable
  4. Why it happens and what else you can do
  5. Other info & ASUS's response to these compatibility issues
  6. BIOS updates
Page updates

  • 01 Sep 2020: Updated STX II with MSI MEG X570 ACE. Added DX with ASUS X370 ROG CROSSHAIR VI HERO, Xense with MSI B450M Mortar Titanium, STX II with MSI MAG X570 Tomahawk WiFi, STX II with MSI B450 Tomahawk Max.
  • 19 Jul 2020: Added possible solution 9. Updated "Why it happens and what else you can do". Updated BIOS updates section. Added
    DGX with ASUS Prime X370-A, STX II with MSI MEG X570 ACE, STX II with ASRock X470 Taichi, DGX with Gigabyte X570 AORUS ELITE WIFI, STX II with ASUS ROG Strix X570-F GAMING, STX II with ASUS ROG CROSSHAIR VII HERO X470, STX II with Gigabyte X570 Aorus Xtreme, STX II with ASRock B450 Pro4, STX II with Gigabyte B550 Aorus Pro, STX II with ASUS TUF B550 Gaming Plus, DX with MSI B450 Tomahawk.
  • 14 May 2020: Updated "Why it happens and what else you can do". Added possible solution 8. Added other PCIe cards that are not based on CMI8788 audio chipset: AIM SC808 with Asrock X470 Taichi and Xonar Phoebus with ASUS ROG Strix X570-E Gaming. Added STX with Gigabyte X570 AORUS ELITE, STX II with MSI B450 Tomahawk Max, STX II with ASRock X570 Phantom Gaming 4, STX II with MSI MEG X570 ACE, D2X with ASUS X370 ROG Crosshair VI Hero, STX II with ASRock X570 Taichi, STX II with ASUS Prime B450-Plus, D2X with MSI B450 GAMING PLUS MAX.
  • 08 Apr 2020: Added "What else you can do" and "How to verify it is stable" sections. Added STX II with ASRock X470 Taichi, STX II with MSI MEG X570 ACE, DS with Gigabyte GA-A320M-HD2, DSX with Gigabyte B450 Aorus M, D2X with MSI MPG X570 Gaming Plus, STX with Gigabyte B450 Aorus Elite, DSX with ASUS TUF Gaming X570-Plus, STX II with ASUS TUF Gaming X570-Plus.
  • 13 Mar 2020: Updated "BIOSes with AGESA caution" section. Added DGX with MSI B450 Tomahawk Max, D2X with ASUS PRIME X570 PRO, D2X with ASUS ROG STRIX X570-E Gaming.
  • 02 Mar 2020: Added DSX with ASUS PRIME B350-PLUS, STX II with Gigabyte X570 Aorus Xtreme.
  • 19 Feb 2020: Updated STX II with MSI B450 Gaming Pro Carbon AC, added STX with MSI B450 Gaming Pro Carbon AC, DX with ASUS Prime X570 Pro, D1 with ASUS PRIME X370-A, DX with Gigabyte GA-AB350-Gaming, removed DSX with Asus Prime x570 Pro because of typo.
  • 31 Jan 2020: Added D2X with ASUS ROG Strix X570-E.
  • 24 Jan 2020: Added STX II with MSI B450 Tomahawk, STX with MSI X370 Krait Gaming.
  • 15 Jan 2020: Added DSX with ASUS TUF Gaming X570-Plus, STX II with Asus ROG Strix X570-F Gaming, STX II with Gigabyte X470 AORUS ULTRA GAMING, STX II with ASUS Prime B450-Plus.
  • 10 Jan 2020: Added D2X with MSI X570 Gaming Edge Wifi, D2X with Asus Prime X570-P.
  • 04 Jan 2020: Added STX with Gigabyte x470 Aorus Ultra Gaming.
  • 13 Dec 2019: Updated "Possible solutions for BSOD and restart issues" section and added possible solution "7. Disable Xonar's recording devices".
  • 11 Dec 2019: Added STX with MSI Tomahawk B450 Max.
  • 09 Dec 2019: Added STX II with MSI MEG X570 ACE, DX with ASRock X570 Steel Legend.
  • 08 Dec 2019: Added STX II with ASUS TUF X570-Plus (Wi-Fi).
  • 06 Dec 2019: Updated "BIOSes with AGESA caution" section. Added STX II with ASUS Pro WS X570-ACE, DX with ASUS Prime X570-P, STX II with ASUS X570 TUF GAMING X570-PLUS (WI-FI), STX II with ASRock X470 Taichi, DSX with ASUS Prime X570-Pro.
  • 26 Nov 2019: Updated "BIOSes with AGESA caution" section. Added DX with Gigabyte B450 M, STX II with MSI X570-A PRO, STX with ASUS Prime X570-P.
  • 23 Nov 2019: Updated "BIOSes with AGESA caution" section.
  • 20 Nov 2019: Updated "BIOSes with AGESA caution" section. Added D2X with Gigabyte X570 Aorus Master, STX with ASUS Prime X570 PRO, STX II with ASUS Prime X570 PRO, DX with ASUS X570 TUF Gaming Plus, DGX with ASRock X570 Taichi, DGX with ASUS X570 TUF Gaming Plus .
  • 16 Nov 2019: Added DX with MSI MEG X570 ACE, STX with MSI MPG X570 Gaming Plus, STX with ASUS Prime X570 Pro.
  • 13 Nov 2019: Added STX II with Gigabyte X570 Aorus Elite, D2X with ASUS X570 ROG Crosshair VIII Hero, DX with MSI X370 Gaming Plus, DX with ASUS Pro WS X570-ACE, DX with ASUS Prime X570-P.
  • 9 Nov 2019: Added D2X with ASUS X570 ROG Crosshair VIII Hero.
  • 8 Nov 2019: Added DG with ASUS X370 Prime Pro, DGX with Gigabyte B450 Auros M, STX II with Asus ROG Strix x570-F, DX with Asus Prime X570 Pro, STX with ASUS X570 ROG Crosshair VIII Hero, STX II with ROG Crosshair VIII Hero (Wi-Fi), STX II with TUF Gaming X570-Plus (Wi-Fi), STX with TUF Gaming X570-Plus (Wi-Fi), STX with Gigabyte X570 Aorus PRO, DX with Gigabyte X570 Aorus Pro Wifi, STX with Gigabyte X570 Aorus Master, D2X with Gigabyte X570 Aorus Master, DGX with Gigabyte X570 Aorus Elite, STX with Gigabyte X570 Aorus Elite, D2X with ASRock X570M Pro4.
  • 5 Nov 2019: Added DX with Gigabyte X570 Aorus Master.
  • 3 Nov 2019: Added "BIOSes with AGESA caution" section. Added DX with Gigabyte X570 Aorus Pro.
  • 31 Oct 2019: Added DGX with Biostar X570GT8 and DX with MSI B350 Tomahawk.
  • 24 Oct 2019: Added D2X with ASUS TUF GAMING X570-PLUS (WI-FI).
  • 18 Oct 2019: Added DSX with MSI B450 Tomahawk, STX II with MSI X570-A PRO, STX II with MSI B450 Tomahawk.
  • 08 Oct 2019: Added STX II with Gigabyte X570 Aorus Xtreme.
  • 29 Sep 2019: Added D2X with ASUS ROG STRIX X570-E Gaming.
  • 28 Sep 2019: Added STX II with ASUS Prime X570-P.
  • 26 Sep 2019: Added D2X with ASUS PRIME X570-P.
  • 21 Sep 2019: Added D2X with Gigabyte X470 AORUS ULTRA GAMING and STX with ASUS ROG Strix X470 F Gaming entries.
  • 17 Sep 2019: Added STX with ASUS ROG Strix X570-F Gaming entry.
  • 15 Sep 2019: Added DX with Gigabyte X470 Gaming 7 entry.
  • 13 Sep 2019: Added DGX with ASUS X370 ROG entry.
  • 11 Sep 2019: Updated intro and "Other info" sections. Added STX with MSI B350 and D2X with ASRock Fatal1ty X470 Gaming K4 entries. Updated "Possible solutions" with another possible solution (no. 3).
  • 02 Sep 2019: Updated table with Gigabyte X570 Aorus Master and ASUS X570 ROG Crosshair VIII Hero. Updated "Possible solutions" with another possible solution (no. 6).
  • 25 Aug 2019: Updated table with additional entries from ASUS ROG forum.
  • : Article published.

Compatibility status list (for system resets and BSODs issues)

Audio cardMotherboardWorks[works with]
Doesn't work[works with]
Xonar Essence STX II
ASRock X570 Taichi#1
ASRock X570 Phantom Gaming 4#1
ASRock X470 Taichi#1?#1, #2[9]
ASRock B450 Pro4#1
ASRock X370 Taichi#1
ASRock X370 Killer SLI#1
ASRock AB350 Pro4#1
ASUS X570 ROG Crosshair VIII Hero#1, #2
ASUS Prime X570-P#1
ASUS Prime X570 PRO#1?
ASUS Pro WS X570-ACE#1?
ASUS ROG Strix X570-F gaming#1[3]#1, #2?
ASUS TUF Gaming X570-Plus#1?
ASUS TUF Gaming X570-Plus (Wi-Fi)#1?#1, #2
ASUS TUF Gaming B550-Plus#1?
ASUS Prime X470-Pro#1?
ASUS TUF X470-Plus Gaming#1
ASUS Prime B450-Plus#1, #2#1?, #2
ASUS X370 Prime Pro#1
ASUS X370 Prime#1
ASUS X370 Pro#1
Gigabyte X570 Aorus Elite#1
Gigabyte X570 Aorus Master#1[7]
Gigabyte X570 Aorus Xtreme#1#1, #2?, #3?
Gigabyte B550 Aorus Pro#1?
Gigabyte X470 Aorus Gaming 7#1
Gigabyte B450 Aorus M#1
MSI MAG X570 Tomahawk WiFi#1?
MSI MEG X570 ACE#1, #2[3]#1[3]+[4], #2[3]+[4]
MSI X570-A PRO#1#1
MSI B450 Gaming Pro Carbon AC#1
MSI B450 Tomahawk Max#1#1
MSI B450 Tomahawk#1#1?
Xonar Essence STXASUS Prime X570-P#1
ASUS Prime X570-Pro#1*, #2
ASUS X570 ROG Crosshair VIII Hero (Wi-Fi)#1
ASUS ROG Strix X570-F Gaming#1
ASUS TUF Gaming X570-Plus (Wi-Fi)#1
ASUS Prime X470-Pro#1
ASUS ROG Strix X470 F Gaming#1
Gigabyte X570 Aorus Elite#1*, #2
Gigabyte X570 Aorus Master#1*
Gigabyte X570 Aorus Pro#1*
Gigabyte X470 Aorus Ultra Gaming#1
Gigabyte B450 Aorus Elite#1?
MSI MPG X570 Gaming Plus#1
MSI Tomahawk B450 Max#1
MSI B450 Gaming Pro Carbon AC#1
MSI X370 Krait Gaming#1
MSI B350 Tomahawk#1
Xonar Essence STASUS Prime B350 Plus#1, #2#1, #2
MSI B350 Tomahawk#1
ASUS Prime X370-a#1
Xonar D1ASUS Prime X370-A#1?
Xonar D2X


ASRock X570M Pro4#1[3]?
ASRock Fatal1ty X470 Gaming K4#1[3]
ASRock Fatal1ty B450 Gaming K4#1
ASUS PRIME X570-P#1?#1
ASUS X570 ROG Crosshair VIII Hero#1, #2?
ASUS ROG STRIX X570-E Gaming#1[4], #2[3]+[4], #3?, #4?
ASUS X370 ROG Crosshair VI Hero#1[8]
Gigabyte X570 Aorus Master#1*, #2
Gigabyte X470 Aorus ULTRA GAMING#1
MSI MPG X570 Gaming Edge Wifi#1?
MSI MPG X570 Gaming Plus#1[3]
Xonar DG w/ ASMedia
1083 PCIe-to-PCI bridge
ASUS X370 Prime Pro#1
Xonar DGXASRock X570 Taichi#1
ASRock AB350M Pro 4#1
ASUS TUF Gaming X570-Plus#1
ASUS Prime X370-A#1
Biostar X570GT8#1
Gigabyte X570 Aorus Elite#1*, #2
Gigabyte B450 Aorus M#1
MSI B450 Tomahawk Max#1
Xonar DSGigabyte GA-A320M-HD2#1[b]+[7]
Xonar DSXASUS TUF Gaming X570-Plus#1, #2?
Gigabyte B450 Aorus M#1
MSI X570 Meg Ace#1
MSI B450 Tomahawk#1
Xonar DXASUS Prime X570-P#1, #2
ASUS Prime X570-Pro#1, #2
ASUS Pro WS X570-ACE#1
ASUS TUF Gaming X570-Plus#1
ASRock X570 Steel Legend#1
ASRock Fatal1ty B450 Gaming K4#1
Gigabyte X570 Aorus Master#1
Gigabyte X570 Aorus Pro#1
Gigabyte X470 Aorus Gaming 7#1
Gigabyte B450 M#1
Gigabyte GA-AB350-Gaming#1?
MSI B450 Tomahawk#1
MSI X370 Gaming Plus#1
MSI B350 Tomahawk#1
Xonar PhoebusASUS ROG Strix X570-E Gaming#1[4]
AIM SC808ASRock X470 Taichi#1

List will be periodically updated. If you have a Xonar PCI/PCIe card and a AMD Ryzen AM4 motherboard leave a comment below with the compatibility status.

  • * Link mentions not working, but that's only with BIOSes with AGESA
  • ? Asked more details or unclear situation.
  • [3] Works with possible solution 3. Usually I place these entries under "Doesn't work" because they involve lowering the PCIe speed sometimes considerably and that can affect the speed of other devices (video card, m.2 storage devices, USB 3.1).
  • [4] Works with possible solution 4.
  • [7] Works with possible solution 7.
  • [8] Works with possible solution 8. I place these entries under "Doesn't work" because they involve sacrificing the m.2 slot and it requires significant work and additional purchases.
  • [9] Works with possible solution 9.
  • [b] Works with a BIOS update. BIOS may not be available publicly.

Possible solutions for BSOD and restart issues

Here are some things you could do that could fix or workaround the compatibility issues. These solutions are not mutually exclusive, than means sometimes a combination of multiple solutions will make it work.

1. Update the motherboard BIOS to the latest version

But avoid early AGESA BIOS versions (see "BIOSes with AGESA caution" below for more info).

2. Do a clean Windows install

If you're using the Windows installation from your previous system, do a clean Windows install.

For testing purposes you could make a secondary Windows install on a different partition, disk or in a VHD file (#1,#2). If needed, you can use EasyBCD (info, download) to edit the boot entries.

3. Switch the PCIe slot speed to Gen 3/2/1

In BIOS, try switching the PCIe connection where the Xonar card is plugged from Gen 4 to Gen 3/2/1 or from Gen 3 to Gen 2/1. This method has been described in detail here by b1tmaster0 for his ASRock Fatal1ty X470 Gaming K4. Such an option is not available for all the motherboards. Some info and other ways to do this:

  1. Location and name of the settings is board specific and may also vary with BIOS versions. For ASRock it may be under "Advanced\AMD PBS\" and may be only listed as "M.2 PCIe Switch". For MSI it may be under "Settings\Advanced\PCI Subsystem Settings\" with options called "PCI_E* - Max Link Speed". For ASUS it may be under "Advanced\Onboard Devices Configuration\" with options called "PCIEX** Mode" (pic #1). For Gigabyte it may be under "Settings\Miscellaneous\" with options called "PCIe Slot Configuration".
  2. For his ASRock Fatal1ty X470 Gaming K4, b1tmaster0 changed the "M.2 PCIe Switch" connection speed, which was for his M2 slot that was also shared with the PCIe slot where the Xonar card was placed. You can check which M2 and PCIe slots share the same connection by consulting the motherboard manual.
  3. You can figure the name/number of the PCIe slot the card is placed in by going to MSI's "Board Explorer" or Gigabyte's "System Information\Plug in Devices Info" or by consulting the motherboard's manual.
  4. "PCIe x16 Switch" or similarly named options are for setting the connection speed of the first x16 slot and it's where you usually have the GPU. Some X370/X470/X570 motherboards have the 2nd PCIe x16 length slot connected directly to the CPU. Consult the motherboard specs or manual to find out if the 2nd PCIe x16 slot is connected to the CPU or the chipset. If the 2nd PCIe x16 length slot is directly connected to the CPU, you could place the Xonar card in the 2nd x16 length slot, enable the slot by setting "PCIe x16/2×8 Switch" or similar to "2x8" and change "PCIe x16 Switch" to "Gen 1". If it works your could also try with the speedier "Gen 2". Your GPU may run a bit slower, see benchmarks here and here, which depending on your computer use case and GPU may or may not be important.
  5. "Promontory PCIe Switch" or similarly named options are for controlling the connection link between the chipset and CPU. If you don't have the option to set the connection speed for a specific PCIe slot you could try setting this to "Gen 1" and if it works your could also try with the speedier "Gen 2". This may limit the speed of the devices connected to the chipset (NVME M2/PCIe SSD), USB3.x flash drives, other PCIe cards.
4. Move the card to a different PCIe slot

Try a PCIe slot that is connected directly to the CPU, which is the 1st PCIe x16 slot, and for some X370/X470/X570 motherboards also the 2nd x16 length slot. Consult the motherboard specs or manual to find out if the 2nd PCIe x16 slot is connected to the CPU or the chipset. If it's connected to the CPU, then the 2nd x16 length slot needs to be enabled in BIOS, see the description on  possible solution 3. d. "PCIe x16 Switch".

Also try the other PCIe ports, maybe one will work.

5. Install UNi Xonar v1.71.1 driver

It might reduce the frequency of these issues or even eliminate them. For STX II cards these drivers might cause a loss of audio quality (#1), waiting more confirmations on this claim.

6. (Unlikely) Avoid IRQ sharing between Xonar card and other devices

To do so you could try switching the other devices interrupts from Line-based to MSI, see info here. Do not switch the Xonar card to MSI as it will prevent your system from booting. You can try this in conjunction with moving the card to a PCIe in which the Xonar card IRQ is shared with less devices.

7. Disable Xonar's recording devices

Especially if your system resets/crashes when using applications that transmits or can transmit sound (such as Discord, Steam, Skype, Firefox, Chrome, etc.) you should try the following solutions:

a. Disable some of Xonar's recording inputs but keep either Microphone or Line In depending on which one you use. To do so, open Windows Sound (right-click on Windows Volume tray icon-> Sounds or if it's missing type in Windows search: “change system sounds”)-> Select Recording tab-> If you use Microphone input, then right-click and select Disable for: Line In(ASUS Xonar...), ALT (ASUS X...) and AUX (ASUS X...). Then right-click on Microphone (ASUS Xonar...) and select "Set as Default" and "Set as Default Communication Device".

b. Disable all of Xonar's recording inputs and use the Microphone from the onboard audio card. Try this is the solution above does not work. To do so, open Windows Sound (right-click on Windows Volume tray icon-> Sounds or if missing type in Windows search: “change system sounds”)-> Select Recording tab-> Right-click and select Disable for: Microphone (ASUS Xonar...), Line In (ASUS X...), ALT (ASUS X...), AUX (ASUS X...), Stereo Mix(ASUS X...) and Wave (ASUS X...). Then right-click on Microphone (HD Audio.../Realtek.../SupremeFX...) and select "Set as Default" and "Set as Default Communication Device".

c. If neither of the above solutions are applicable to you as you need both the Xonar's Microphone and Line In enabled, you could try is to select Microphone (ASUS Xonar…) or Line In (ASUS Xonar…) as input device in each of the recording applications that causes a reset/crash. For Discord-> User Settings-> Voice & Video. For Steam->Friends List window-> Gear icon->Voice->"Voice input device". For Firefox and Chrome you might not be able to do this.

8. Connect the card to the first m.2 with the use of a m.2 to PCIe adaptor

This would only work for the first m.2 slot because it's the one connected directly to the CPU. If you have an m.2 SSD and can move it to one of chipsets m.2 slots, know there might be speed penalties involved at least with certain SSDs (#1). If you are interested in this method, you can read here Master-W-Steve recommendation of components in order to do this.

9. Plug the card into a PCIe riser

As it is reported here (#1), plugging the card into a PCIe riser like this could work. The speculation about why this works is that the PCIe riser has a separate power supply. It could be that the PCIe issues are caused by inadequate power delivery to the PCIe cards by the motherboard.

Please leave feedback in the comment section below if one of these methods worked for you. Mention your sound card, motherboard and its BIOS version, CPU and OS.

How to verify if it's stable

To speedup the testing and see if your system is stable or not, you can the following:

  • Install UNi Xonar drivers multiple times.
  • In an audio/video player, load some audio files and cycle through them for a couple of minutes (thanks Arconas).
  • Launch a voice chat or recording application (ie Discord, Skype etc.) and maybe try a test converstation. Do this a couple of times.

Why it happens and what else you can do

From what I can tell, the reboot issues are because of some sort of issue with PCI/PCIe signal transmission on some motherboards and this causes in case of the Xonar drivers a error which results in a system crash. It could be that the PCIe issues are caused by inadequate power delivery to the PCIe cards by the motherboard (#1). While the reboot thing could technically be fixed within the drivers, there is no one to fix this as ASUS and C-Media have given up on drivers for the Xonar cards and I have limited access and resources to do such a thing. But even with such a fix, there would still be a problem with the motherboard and how it handles the PCIe signal transmission or power delivery. In some cases these issues will be partially or fully fixed through a BIOS update (#1).

The best course of action would be for you to contact the technical support of your motherboard and let them know of this issue and ask that they look into it. You should include a link to this page to provide them with additional information. If you are having problems getting pass the low level copy-paste support, you can try contacting them through their own support forums or their Twitter or Facebook account.

Ideally this issue should also be brought up directly to AMD. Now, reaching someone there might be a bit problematic.

Other info & ASUS's response to these compatibility issues

Threads discussing these issues on ASUS ROG forums here and here.

ASUS official FAQ response about these issues here and here. The statement from ASUS that the cards (at least STX II and D2X) are not compatible is, at the very least, inaccurate, as it works with some motherboards and those Xonar cards are not the only PCIe cards affected. You would think that making both the Xonar sound cards and their own AMD Ryzen AM4 motherboards, most of which are affected by these compatibility issues, would make it much easier for ASUS to find a solution to the problem. Speaks volumes of how "great" their support is. To make matters even worse, after concluding that the cards are not compatible, they closed the main forum thread discussing this issue, thus roadblocking any community driven investigation for a possible solution.

On the topic of ASUS motherboards compatibility with sound cards, it's worth noting that you may run into issues with Creative cards as well (#1, #2). It's unclear at the moment if you will have the same problem with other motherboard brands or this problem affects mostly ASUS X570 boards.

ASUS owns ASMedia, the company that is behind the Ryzen's AM4 chipsets.

BIOS updates

Beta BIOSes and yet to be officially released BIOS versions can be found here.

I urge caution if you have a on a ASUS motherboard or from another manufacturer which does not allow you to downgrade to a previous BIOS version as a new BIOS could also cause new issues. If you have a dual BIOS motherboard, you should be fine.


The AGESA changelog mentions "Optimized PCIe® firmware to improve stability and interoperability", but AMD did not clarify what exactly does that mean and we don't know if this targets in any way the issues that people have with their PCIe soundcards. Before you update to BIOSes with AGESA you should know that these may have some stability issues(#1, #2). If you have a on a ASUS motherboard or from another manufacturer which does not allow you to downgrade to a previous BIOS version it's probably best to wait for BIOSes with AGESA v1 or v2 (info).

BIOSes with AGESA caution

Users are reporting that after updating the BIOS to a newer version that has AGESA, the system won't boot if you have the Xonar card plugged in the motherboard. This happens with other PCIe cards as well (#1, #2, #3). Most motherboards brands seem to be affected (BIOSTAR #1, Gigabyte #1+, #2, ASUS #1, #2, #3, #4, ASRock #1). If you don't want to go to the hassles of updating the BIOS again to the previous version, you should hold off the update. Also, for some motherboards it is not possible to go back to the previous BIOS (ASUS #1, #2).

Update 13 Mar 2020: The fixed BIOS versions could still have problems with other PCIe cards. As someone reports here, his system does not work when the PCIe Firewire card is plugged. If you have another PCIe card and have a motherboard from ASUS or from another manufacturer which does not allow you to downgrade to a previous BIOS version, you should probably not update the BIOS to any version with AGESA or newer. If you have a dual BIOS motherboard, you should be fine.

Update 06 Dec 2019: ASUS released on their official product pages the fixed BIOSes, at least for some of their X570 motherboards. For some of their motherboards the v1405 is the fixed one. The fix is not mentioned in the release notes, but the BIOS that follows after the initial AGESA BIOS should be the fixed one.

Update 26 Nov 2019: ASRock's fixed beta BIOS versions are now available on products BIOS pages under Beta BIOS section with the changelog listing "Improve PCIe card compatibility". For ASUS motherboards and also other manufacturers, fixed BIOS versions can be found here, for some of Asus's X570 motherboards the fixed BIOS versions are labeled 1405. You should update to these beta BIOS versions only if you are stuck with a broken BIOS with AGESA, otherwise you should probably wait for the final versions.

Update 23 Nov 2019: ASUS started distributing through forums and technical support a fixed beta BIOS for some of their motherboards (#1, #2, #3).

Update 20 Nov 2019: Gigabyte(#1) and MSI(#1, #2) released updated BIOS versions with AGESA that do not have this issue. It seems Gigabyte replaced the previous BIOS and does not list the fix in the changelog, thus I am not sure all of Gigabyte's motherboards have the fixed BIOS, but BIOSes released on 2019/11/08 or later should have the fix. MSI list in their fixed BIOS change log "Improved PCI-E device compatibility". ASRock does offer through technical support a beta BIOS for some their motherboards that also works fine (#1, #2). I am not aware that ASUS or BIOSTAR have anything yet.

If you've updated the BIOS and the system no longer boots, you could try this: remove the sound card, start the PC and enter the BIOS, look for a setting a called “Initial Display Output” or similar, set it to the PCIe slot in which the main video card is plugged in, save settings and shut down the PC, reinsert the sound card and see if system boots. If it does not, remove the sound card again and revert back to the previous BIOS.

If you run into these issues you could contact your motherboard support letting them know of the issue.

Useful for:

  • ASUS Xonar DG, Xonar DGX, Xonar DG SI, Xonar DS, Xonar DSX, Xonar D1, Xonar D2, Xonar DX, Xonar D2X, Xonar HDAV, Xonar HDAV Slim, Xonar Essence ST, Xonar Essence STX, Xonar Essence STX II, Xonar Xense.
  • Other C-media CMI8786 and CMI8788  audio chipset cards:
    • Auzentech: HDA X-Purity 7.1, X-Meridian 1G, X-Meridian 2G.
    • HTOmega: Claro, Claro Plus, Claro II, Claro Halo, eClaro.
    • Razer Barracuda AC-1.
    • TempoTec HIFIER Serenade.
  • Creative Sound Blaster Z, Sound Blaster ZxR, Sound Blaster AE-7, Sound BlasterX AE-5, Sound Blaster AE-7, Sound Blaster AE-9.
  • AMD A320, B350, X370, B450, X470, B550, X570, X399, TRX40 chipset motherboards.
Was this helpful? Please consider supporting us by making a donation.


  1. romek7112 Apr 2020 @ 14:16

    Comment moved here.


    • CarvedInside12 Apr 2020 @ 15:54

      Thanks for the update. I moved you comment to your initial report. If you have other things you want to add that relate to your initial report please reply to that comment.


  2. dudoln13 Apr 2020 @ 23:07

    Asrock Taichi X570(BIOS v2.7)+3900X+ASUS STX II in the last PCIe slot;onboard audio R1120 is not disabled
    Windows 10 64 bits(up to date) --> no issue
    Linux LMDE4 --> even easier, no need to install driver, ALSA is working just excellent, y must change only the output device.


  3. tigerdog18 Apr 2020 @ 00:15

    Asus Prime B450 (BIOS 0604) Xubuntu 19.10 linux. Onboard audio disabled. System restarts when Audacity runs about 50% of the time. Can hear the input or output select relay click right before system restarts. No restart with Windows 10 / Adobe Audition or when not using Audacity.


    • CarvedInside18 Apr 2020 @ 03:30

      What Xonar card do you have? What CPU? Have you tried any of the possible solutions, particularly 3, 4 and 7 (idea adapted to Linux of course)?


      • tigerdog18 Apr 2020 @ 17:48

        Sorry for the lack of detail. Xonar Essence STX II, Ryzen 2600.
        I have tried updating BIOS to ASUS' latest for this mobo, no change.
        I tried setting the PCIEX to Gen 2. Only options on this BIOS are 2 or 4, and it set the mode across all slots. Still reboots system about 1 time in 4.
        I will try moving to a different slot - it will be hit-or-miss, since I don't have details about hardware layout.
        I do not want to disable recording. I bought this card primarily for the better recording capability than either onboard sound or the older card I previously used. I do a *lot* of recording.


        • CarvedInside18 Apr 2020 @ 17:57

          I am suggesting disabling only the recording devices that you don't use. Keep only Microphone or Line In depending on which one you use.


          • tigerdog18 Apr 2020 @ 21:42

            Thanks for the clarification. In Linux, there does not appear to be a way to disable individual inputs (or hide them from the OS/applications) so I think I'm hosed in that department, also.
            For others with this motherboard, an Anadtech review notes that only the top PCIe x16 slot is directly connected to the CPU. All other slots are routed through the B450 chipset. This is likely due to an NVMe slot using the other CPU connection lanes, and the budget nature of this system board.

            I hate to say it, but I'm about to throw in the towel and look for another sound device. Asus has spent a lot of attention on giving good DAC performance and sound quality on the outputs but maybe recording is just an afterthought. That it is so thoroughly incompatible with one of their own mainboards just adds to the frustration.


            • CarvedInside18 Apr 2020 @ 22:27

              For disabling the recording devices, maybe this would work.

              There is another way, which has a chance of success on your system. If you don't use the M.2 slot, you could buy a M.2 to PCIe adapter and plug the card there. Some info regarding this here.


              • tigerdog19 Apr 2020 @ 00:02

                I've used the PulseAudio mixer to select/enable Line In recording - it's the only way Audacity actually gets audio in. Pulse only lets you select one recording source, so the others are "disabled". One problem happens when Audacity tries to take direct control of the hardware using ALSA. It doesn't work, but it does cause the system to try to select an input, which causes the system to reboot.

                And of course, I use an M.2 NVMe SSD... 😐


                • Master-W-Steve20 Apr 2020 @ 23:37

                  Maybe you can try an m.2 -> adapter for your sound card an an pci-e -> m.2 adapter for your nvme, maybe not the finest solution, it is a try to keep the D2X working.
                  I tried a lot of sound cards, nothing sounds like the D2X or STX II, it is terrible. The drivers are very old too, hope they keep working in future.


                  • tigerdog21 Apr 2020 @ 01:38

                    I'm using it under Linux, so old drivers are rarely depricated; even when removed from the kernel, adventurous people tend to keep them alive as add-ins.

                    Not thrilled with the idea of swapping NVMe and sound card. I may just have to suffer, or try to find some really good, professional audio ADC instead.


          • tigerdog22 Apr 2020 @ 01:10

            I've reached out to ASUS USA to see if they can be of any help. I've tried two x1 slots and the second x4 slot but have not swapped video to put it in a CPU (non-chipset) slot. I did find that hard-setting mode 2 in BIOS, and disabling the serial port, has helped some but it's still not stable in any real sense of the word.


            • tigerdog22 Apr 2020 @ 05:10

              Well, here's ASUS's take on the issue: "STXII/STXII 7.1 is not compatible with X370/B350/X470/B450/X399/X570 series MB."

              ASUS has elected to bury this in a FAQ instead of stating on the product information page. Sounds like anything we do is, at best, a workaround. I wish I had enough smarts to understand the underlying issue.


              • Tiny_Montana18 May 2020 @ 03:13

                Well that is just super ain't it! I have the Essence STX II box right here and it lists AMD Athlon 1400 or faster CPU as it's requirements. I spent a lot of money on the card, and the requirements are incorrectly stated? Are there any lawyers in here? Is this grounds for a CAL against Asus for misleading consumers ?


                • tigerdog18 May 2020 @ 16:04

                  I had exactly the same thought. FWIW, it *does* work with Athlon / AM3 systems, or at least it did on mine. I only discovered the problem when upgrading to an ASUS AM4 B450 motherboard. I gotta think, in our litiginous society, there's a law firm somewhere that would take this case. Please save your box...


                  • Tiny_Montana18 May 2020 @ 17:41

                    Lol I have all my product boxes, much to my wife's chagrin... I will certainly keep the sound card box!


            • tigerdog26 Apr 2020 @ 23:40

              Asus has stayed engaged on Twitter. Now that I've demonstrated the compatibility issue (no problem in Prime B450-Plus with EVGA Nu audio, no problem with Essence STX II in MSI 970-G45 motherboard) they've offered to "escalate" and asked for my email. It'll be fun to see where this goes.


              • CarvedInside28 Apr 2020 @ 00:34

                Good for you for insisting. I wanted to write to you to suggest that you insist because it seems like a motherboard problem and other motherboards do not have issues (generally speaking about this reboot issues, at least in case of other AM4 motherboards we don't know how they perform in this specific instance).
                Let us know how it goes.

                Btw, how pathetic it is, that more and more we have to contact the companies on Twitter to actually get some support.


                • tigerdog28 Apr 2020 @ 08:36

                  I've submitted a detailed description of the environment and issue, in a form they provided. Now we wait for their support team to figure out what's happening.


                • tigerdog01 May 2020 @ 03:15

                  Asus Support was... unsupportive. Their response would have been hilarious if it wasn't so sad. We *know* there's an incompatibility. We want to know how to work around it. If the sales literature, web site, *anything*, indicated to a potential customer about a compatibility problem, then it's our fault if we buy things that can't work together. But they don't. The only mention I can ever find is in a post-sales/support web site. I've seen class-action law suits triggered for less than this.


                • tigerdog01 May 2020 @ 22:15

                  After two weeks of wrestling with Asus tech support via email and Twitter DMs, here is a summary of their response:
                  "I do apologize if you have proactively asked for update. I am writing this email to provide you an update about your ongoing case. In accordance to the recommendation of our engineers: Please advise the customer that there's a compatibility issue and may share the FAQ below:
                  [Audio Card] System may reboot when switching the output of STX II/STX II 7.1 on X370/B350/X470/B450/X399/X570 series motherboard.

                  "Unfortunately, if the products aren't compatible we'd be unable to make them work together. What we would advise that you return the card."

                  I bought the Essence STX II in 2016, and the incompatible motherboard last year. Neither are returnable, and returning the motherboard is not feasible in any case, because it appears Asus themselves say the Essence STX II is incompatible with pretty much all Ryzen chipsets (see the FAQ). I would strongly recommend we amend this post to indicate that even Asus says we shouldn't use the two things together, and that if people want to use the Essence STX II, they should avoid Ryzen (and vice-versa.)

                  We should at least do what we can to help others avoid this dilemma.


                  • CarvedInside02 May 2020 @ 00:32

                    First, instead of writing new comments please use the reply button when replying to an existing discussion thread. I had to manually move 3 of your last 4 comments. The other one is this which is fine as a new comment.

                    Sorry to hear that. Guess with ASUS it was a long shot anyway.

                    Since the start of the post, I mention that pairing a Xonar card and a Ryzen motherboard might not work. I will see if I can change "Other info & ASUS's response to these compatibility issues" section a bit to reflect how badly ASUS doesn't want anyone to buy their motherboards. Unfortunately, there are too many people that just buy new ASUS products even if they personally had problems and are disappointed by the lack of support of their previous ASUS products.


                    • tigerdog02 May 2020 @ 01:09

                      Please accept my apologies for mis-threading. I'm thinking I'll not spend too much more time here, since I won't be using the Essence any more, but I thank you and the other members of the forum who are fighting this issue. I wish you only the best.

                    • CarvedInside03 May 2020 @ 01:44

                      No problem. Sorry could not do more. Thanks for sharing your experience. All the best to you too.

                • tigerdog01 May 2020 @ 23:54

                  and the final word from Asus: "I understand how you feel. We wouldn't want this single experience to have you lose your trust in our brand, however we are unable to grant your request of a refund. For a refund you may try to contact your place of purchase to initiate a return if its still within its return period."

                  If you use Ryzen, DON'T BUY THIS SOUND CARD. (take a look at the EVGA Nu audio card as an alternative that does work, at least with Windows, and can work with Ubuntu with correct firmware.)


  4. JJMC18 Apr 2020 @ 02:06

    I have an MSI B450 GAMING PLUS MAX/Ryzen 5 3600 and Asus Xonar D2X with the latest BIOS and although I can get the sound to work the volume seems to be capped to a maximum of maybe 5% of the normal total. Has anyone had the same issue? Has anyone been able to fix it?

    The sound works, it's just very, very, terribly low.


    • CarvedInside18 Apr 2020 @ 18:06

      Make sure the card is properly seated in the PCIe slot and check that the power connector is properly plugged into the card and to the PSU if you have modular cables.


  5. tiz23 Apr 2020 @ 19:16

    asus tuf x570 wifi bios 1407 work fine with W10 1825 v1.81a r2! 1816/1823 v1.80a r3 instant reboot and dont install.

    Admin edit: Xonar D2X
    Original report here.


    • tiz26 Apr 2020 @ 19:57

      today unluckily my pc reboot when play video from steam site.


      • CarvedInside27 Apr 2020 @ 07:15

        I moved your comment from a new comment to a reply to the original discussion. Please use the REPLY button on the right of the comment you are replying to.

        You still haven't told us which of the possible solutions have you tried, particularly in your case 3, 7 and maybe 4.


  6. tigerdog26 Apr 2020 @ 23:49

    I've learned more about the Essence STX II under Windows 10 and why it might be stable for some people. It seems that as long as the card is not asked to change modes (input select, output select, change sample rate) then it's relatively stable. So if, in your installation, the card is set to one operating mode and stays that way, it is less likely to crash. I've also discovered that with current drivers, the Essence STX II will only record at 44.1 KHz sample rate. It does not matter what sample rate is selected in the Xonar control panel. It also does not matter what sample rate or bit depth is selected in my recording software (I've tried using Adobe Audition 1.5) The file is properly sized, but the incoming stream is brick-walled at 22KHz. This might also explain why some people see fewer errors - the card may not be changing modes as requested. In Ubuntu Linux, using Pulse Audio, it *is* possible to change sample rate by editing the Pulse audio daemon.conf default entries. About 50% of the time, my system reboots when this mode-set happens. When it doesn't , the line out has audible "crackles" during the mode-set activity. I'm not sure if this helps the discussion but maybe if someone from Asus is tracking this thread, the added info will help.


  7. Buckyball18 May 2020 @ 21:41

    GIGABYTE X570 UD rev 1.0
    Xonar DGX and onboard LAN (Realtek GBE ) won't work together, tested with different BIOSes, fresh W10 install. Tested with the latest drivers (1.81a r2)


    • CarvedInside19 May 2020 @ 01:19

      Please provide more details. Like what happens when you have both installed? How did you figure out that they don't work together? Have you tried downloading the latest Realtek network drivers from the Realtek website? Did you installed the UNi Xonar drivers with Normal, Low DPC Latency or C-Media Panel configuration?


  8. STRATEGO24 May 2020 @ 17:33

    I have X370-A and I've never had issues with the original drivers and I don't have issues with latest custom(1.81a) as well.


    • CarvedInside24 May 2020 @ 18:16

      The motherboard is ASUS Prime X370-A? Which Xonar card do you have? Which CPU?


      • STRATEGO24 May 2020 @ 22:36

        Yes, that's my mobo.
        Sorry forgot to mention I have Xonar DGX.

        Oh and Ryzen 5 1600.
        Windows 10 1909(18363.836), probably will upgrade to 2004 pretty soon, if it doesn't have some stupid bugs.
        Do you need any other specs? I can probably provide you with whatever you require and do some testing if necessary.


  9. Tiny_Montana25 May 2020 @ 01:06

    Asus Essence STX II ver., Windows 10 x64 ver. 1909, MSI MEG X570 ACE ver. E7C35AMS 1.80, AMD 3900X.

    I made the following changes in the BIOS last week:

    Settings\Advanced\PCI Subsystem Settings
    PCI-E1 - Max Link Speed > Gen 3
    PCI-E3 - Max Link Speed > Gen 3
    Chipset Gen Switch > Gen 3
    Above 4G memory/Crypto Currency mining > Enabled

    I have not had a soundcard induced reboot since, as of right now. Discord was almost guaranteed to cause a reboot, but has not done so since these changes were made.
    I wish there was an option to upload images here, I suck at typing...lol
    I hope this info can help others with a similar hardware setup. I would appreciate any feed back should you decide to try the settings.


    • STRATEGO25 May 2020 @ 12:17

      You can probably use links to external img host servers like imgbb (like this https://ibb.co/WWsjbdW + I don't think wordpress allows embedding)


    • CarvedInside25 May 2020 @ 17:41

      In which PCIe slot is the STX II card plugged in?

      Thank you for the information. I also want to thank you for the donation. I've put so much time into this page, it's nice to know that there are at least some that really appreciate my efforts.


      • Tiny_Montana25 May 2020 @ 17:55

        My Essence STX II is in the bottom slot, which is on my MOBO, PCI-E5. It is a full length slot, but it is the only slot available as my 2 GPUs cover the other available slots. Still haven't had any reboots since making the changes listed above.

        You are very welcome for the donation. Sorry I couldn't do more. Tough times for a lot of folks nowadays. But I do greatly appreciate the info you have gathered here.


        • CarvedInside25 May 2020 @ 18:57

          In your case I think it's safe to revert the PCIe version to Gen 4 for PCI-E1 and PCI-E3 slots. Of course this would be only useful if you have PCIe Gen 4 video cards.
          If you haven't done anything else, the solution in your case could be either from "Chipset Gen Switch > Gen 3" or "Above 4G memory/Crypto Currency mining > Enabled" settings. Of the two, "Chipset Gen Switch > Gen 3" is most likely. Let us know if you try reverting all those other settings.

          AMD recently released AGESA which supposed to improve PCIe card compatibility, but they did not mention what this improved compatibility meant or addressed. When you will update to a new BIOS with AGESA or newer you could try reverting "Chipset Gen Switch" to Gen4 and see how your system behaves. But if you now have a perfectly working system, you should not rush into updating the BIOS. Particularly when it comes to AGESA, it seems it might have some other issues which are now being worked upon.


          • Tiny_Montana26 May 2020 @ 04:12

            No one has Gen 4 GPU's as of right now, including me! lol I will of course change it, if and when i get Gen 4 cards, but for now I'll leave it the way it is. Still no reboots. I think the chipset gen switch was likely the culprit. I changed the Above 4G memory/crypto setting just because i have way more tan 4GB of RAM, so I figured what the heck! As for the BIOS, yeah, I tried MSi's current beta with the microcode. It was an absolute mess! Caused all kinds of issues, aside from the ongoing sound card reboots. Never again will I install another Beta BIOS. But, as always thanks again for your input and time. It is greatly appreciated.


            • CarvedInside26 May 2020 @ 08:46

              You're welcome.

              The Radeon 5000 series are PCIe gen 4. Cards like Radeon 5500 and 5500XT actually benefit from it because they are wired at only PCIe x8 thus having limited bandwidth when operating in PCIe Gen 3 mode. While cards like Radeon 5700 may only benefit in certain scenarios like when you use more than the available GPU memory.

              When you have some free time maybe you can test with "Above 4G memory/Crypto Currency mining" disabled, as it would be nice to know if it has anything to do with this issue. This setting was intended for different a differnt purpuse.

              Thanks for sharing your experience with the AGESA beta BIOS.


              • Tiny_Montana27 May 2020 @ 03:25

                I was not aware that the 5000 series were Gen 4.Thanks for clarifying.

                I do realize what the Above 4G memory setting is for, I just enabled it to see what if any change it would make in how windows manages memory.

                I will be happy to disable it. I have noticed no difference in anything since enabling it. I'll report back after a few sessions of heavy use.


                • Tiny_Montana08 Jun 2020 @ 16:40

                  No change from disabling the above 4G memory setting. I did have a sound card induced instant reboot when I switched the output from DDL to headphones. Once rebooted, I was able to switch back to DDL without a reboot. Have not tried to switch to HP again since.


  10. Abue25 May 2020 @ 01:19

    A little update on the compatibility issues with Ryzen boards and Essence STX II: I contacted ASUS around the end of March 2020, spent a week talking to their support to be slapped with the message posted circa October 2019 stating that the card is not compatible with Ryzen boards (you know which post I'm talking about I hope, I don't have the link handy atm). This is after I gave them all my specs, serial numbers etc... to their engineering team which very quickly responded with that message. So, bummer, i bought this card a little over a year ago and I'm stuck with it and I can't stand playing music without since onboard sound has very low gain compared to it, so all my music/movies/games just sound so damn quiet in comparison.

    This is when my lightbulb idea came out of nowhere... There was a discussion about how the ASMEDIA PCI bridge on the card may be the culprit on how it's communicating with the Ryzen boards.... So I went on a limb here, I had a PCI extender board sitting around for a while which I was going to use on another video card but I ended up just never using it. I slotted the STX II to that board, and hooked it up to my PCI-E port (my video card has a massive backplate block which doesn't leave enough space between card and CPU cooler so I have to slot it elsewhere)....
    On first boot, it booted fine, no crashes, I did adjust the sample rate to the max setting 24bit , 192k and after fiddiling around a discord for a minute it crashed the system. So I rebooted, with a long and face thinking this won't work, and left the sample rate at 24 bit 48k. It's been over a month and a half where I haven't had a system reboot/crash or the double clicking sound happening with the audio switch crap, this problem would almost guaranteed happen twice a week to me, mostly triggered by using communication software such as discord, even happen with zoom a few times.
    I use discord daily, I spent over 2hrs just flipping channels on purpose trying to crash the system, having another person speaking in the channel while doing it, everything I tried, I did not manage to crash it.

    This included:
    1. Playing a video while switching channels in discord, speaking queueing mic while switching channels, hopping channels.
    2. Playing video + playing a game + moving channels in discord as well.
    3. Playing more than 3 video windows + game + discord + skype, etc....
    No crashes, system has been stable since.

    To clarify I'm just running the latest ASUS drivers which are ancient not the UNI xonar drivers.
    As far as settings go in the ASUS panel:
    SVN is enabled
    Sample rate = 192 - channel
    Analog out: Headphones
    Dolby Headphone is on
    gain is set to 64-300 ohms.

    The PCI-E extender cost me around $10 on ebay, not sure about make or model but it's a PCI-E to a USB connection to the extender board.

    I think this is a promising fairly cheap solution to those suffering from this or wanting to smash the sound card into a surface for satisfaction, it's worth a try. I haven't contacted ASUS tech support about it yet, but if more people end up having success with this I might ask them if they can try it in their lab settings and see if it is a solution.

    Even if this ends up crashing again eventually, I went from weekly crashes to almost 2 months of no crashes soooooo who knows, I'm happy with the results.

    As for my system:
    ASRock X470 Taichi
    Ryzen 2700x
    Radeon 390x gpu

    everything else is probably irrelevant,



    • Tiny_Montana25 May 2020 @ 06:36

      That is some great info! Thanks for posting!


    • STRATEGO25 May 2020 @ 13:04

      That's some good info, I almost bought a used STX II earlier this year, but somebody grabbed it before me, so I guess I was lucky I didn't need to encounter these bugs...


    • CarvedInside25 May 2020 @ 17:42

      PCIe extender is something like this? If not, please search for a picture and provide the link to it.
      In which PCIe slot the PCIe extender is plugged in?


      • Abue26 May 2020 @ 03:44

        Yup same thing pretty much, I have it on PCIE_1 ideally my GPU would be there but it isn't.


        • CarvedInside26 May 2020 @ 08:04

          What you've did is basically what I've written about in possible solution 4 but you've also used the PCIe extender. The PCIE_1 and PCIE_3 slots are the ones directly connected to the CPU. I think the fact that you use that PCIe slot is the sole fact responsible for the STX II card working.
          Was there a problem with plugging the card directly into the PCIE_1 slot?


          • Abue26 May 2020 @ 08:20

            Yeah, I had the card in the same slot the whole time, I can't really use any other slots. My guess is the ASMEDIA pci bridge communicates differently with the extender, it doesn't trigger the audio switch it does on the mainboard directly. weird solution but if i'll take it if it works.


            • CarvedInside26 May 2020 @ 08:53

              1. So when you had the card in the PCIe 1 slot, it did not worked correctly and once you've connected the card to the PCIe extender it worked fine?
              2. In this time between these 2 configurations, haven't you by any chance updated the BIOS or changed the PCIe gen version to 3/2/1?
              3. When you had the card connect directly to the PCIe 1 slot, did you try setting the PCIe gen version to 3/2/1?

              I'm not sure what's going on, the PCIe extender does not have a chip on it that could intermediate or alter the connection.
              Thank you for the information.


              • Abue26 May 2020 @ 09:54

                That's what I thought too. Previously for the past year I tried every configuration of the PCI GEN settings in the BIOS starting from the initial BIOS i had the board on 2.00. or something to the latest I'm running it on 3.5 now, i never went beyond 3.5 since the latest ones are for matisse cpus. None of the configuration for PCIE_1 worked or the GEN switch settings. The card always worked from the get go, as in, it loads, it plays that's fine, but the audio switch bug that causes reboots was always there, sometimes it didn't happen for a few days, other times it just repeat itself on reboot constantly everytime i'd switch a channel in discord, it would go out of control and then after a few reboots back to normal for a few days maybe. There was no consistency with the matter other than it would at least crash 1-2 times a week guaranteed when it was "stable".

                When I switched to the PCI extender i did not do any other changes to the BIOS or where the card would slot itself, it's same stuff, which I decided to share it, I'm still surprised myself, if it keeps going for another 2 months without a crash then I can safely say it's probably working for sure. My guess it's not so much the chip but the amount of power it may draw off the board at x point in time which the board itself seems to not like, since the PCI extender has its own power source, that may be the culprit, as to what exactly is happening, i have no idea, and neither does ASUS it seems like, whether they want to dedicate man power to testing it further I don't know either.


                • Abue12 Sep 2020 @ 23:36

                  Little update on this note. I have had no crashes since April ~20th until today which was triggered by Discord (as it would normally happen for me). The solution doesn't seem to be permanent but I did enjoy months of a crash free system thanks to the extender. Now, I don't know if part of this has to do with the new Windows update that came out recently which is when I started noticing very strong half second noises coming out my headphones after joining discord channels (the notification for joining/leaving channels felt like a bang in the headphones instead of an actual sound and it only started after the 2nd to last big windows update, I had another big update a couple days ago). In the end, it feels like this whole situation is a combination of driver level issues + hardware compatibility, I don't think we can point the figure exactly at one issue.


                  • CarvedInside13 Sep 2020 @ 16:51

                    Thank you for the update. Recent Windows 10 updates could be the cause of the recent crash. If you want to uninstall recent Windows 10 updates and block them maybe this article I wrote is helpful. Let us know if you find which updates exactly are responsible either the Discord crash or those unusual Discord notification sounds or anything else worth sharing.


    • tigerdog25 May 2020 @ 23:25

      Great info – thanks for posting. I think it’s my day to be slow, though: I cannot visualize the setup. I understand the STX II PCIe plugs into the extender board. From the extender, does it connect to the system via USB? Or does the extender just plug into a PCIe slot on the mobo?


      • Abue26 May 2020 @ 03:45

        The extender just has a PCI end and a USB end. The PCI end goes into your PCIE/PCI slot and the USB end goes into the extender board, you slot the sound card into the extender board.

        LE: To visualize what I'm saying, here is my temporary solution, i need to do some modding, I'd like to place an aluminum panel to sit this on right over the psu, but overall if you're not moving it this works lol.


  11. JustASuggestion04 Jun 2020 @ 18:41

    Just adding to let everyone know that the Asus XONAR DGX works well with my Gigabyte X570 AORUS ELITE WIFI motherboard. I am running the latest Uni Xonar Drivers on BIOS F11. Thanks for the drivers and support, CarvedInside!

    P.S. I am running the sound card in the second to last PCIe x1 slot which runs off the chipset and supports PCIe 4.0 standard.


  12. STRATEGO13 Jun 2020 @ 20:00

    MSI is releasing some fixes for USB sound cards, might be worth exploring if there are any improvements for PCIe sound cards as well


  13. Kimthesax02 Jul 2020 @ 12:58

    I have a ASUS ROG Strix X570-F GAMING with ASUS Essence STX II, I have finaly got it to be stable with bios update 2203. Other things i have done that may not be important longer but have improved it earlier:
    1. Installing ASIO4ALL before the driver installation
    2. Setting the PCIe port to GEN 1

    I can now change audio settings and outport without crahes .... for now, will update if the status changes.


    • Kimthesax02 Jul 2020 @ 20:36

      When I optimize the CPU and Memory settings it becomes unstable again....


      • Kimthesax03 Jul 2020 @ 17:59

        Stabilized again, actions:
        1. Card in slot PCIE_X1_2
        2. All PCIEX16 set to Gen 3
        3. All PCIE_X1 set to Gen 1

        Can change audio output without reboot and have optimized RAM and CPU settings


        • CarvedInside06 Jul 2020 @ 02:26

          Thank you for the info. I think setting PCIE_X1 to Gen 1 did the job. Let us know if situation changes in the future.


          • Kimthesax07 Jul 2020 @ 19:35

            Happy to help, i now am on all PCIE_X1 set to Gen 2 that has improved the sound card capability


            • CarvedInside08 Jul 2020 @ 08:05

              What to you mean by has improved the sound card capability?
              Xonar cards are PCIe Gen 1 and do not benefit from the additional bandwidth that PCIe Gen 2 offers.


  14. JohnRambo05 Aug 2020 @ 19:18

    Xonar DX working fine here on an ASUS X370 Crosshair VI Hero for over three years, all BIOS/AGESA versions, in combination with a 1700 and a 3900x.


  15. no1337ah17 Aug 2020 @ 14:15

    Ryzen 5 3600
    5700 XT

    STX II (ASUS drivers) working on B450 Tomahawk Max with latest BIOS



Leave a new commentReply to comment

Comment received.
Your comment may be held for moderation. If it does not show up immediately, please be patient. Comments have to comply with these rules:
  • English language only
  • Don't post insults or threats
  • Try to keep the discussion constructive and informative

We've noticed that you're using an AdBlocker

It's not just you, over 66% of our site's visitors are blocking the ads.

Please disable adblock for this website and refresh this page if you:
find the content useful want us to create more useful content and software want tech support through the comment section

The ads are placed so that there is minimal interference with page reading. There are no pop-up, pop-under or sticky ads.

Alternatively, you can support us by making a donation.