UNi Xonar Drivers 1.81 (post periodically updated)

UNi Xonar drivers are Windows drivers for the following sound cards:

  • 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, CMI8787 and CMI8788 audio chip based cards: Auzentech X-Meridian & X-Meridian 2G; HT Omega Claro, Claro Plus, Claro II, Claro Halo, eClaro; Razer Barracuda AC-1; AIM Audio SC8000. View full list.

Supported OS: Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2003, Windows Server 2008, Windows Server 2012  Windows Server 2016 and Windows Server 2019.

Please note that these are modded drivers and there are limitations regarding how much the actual original drivers can be fixed this way.

Linked content:

  1. Introduction

  2. UNi Xonar Features

  3. FAQ & troubleshooting guide (upd 08.02.2019)

  4. Having problems installing UNi Xonar drivers? Refer to this topic

  5. Xonar best audio settings guide

  6. Audio known issues and workarounds

    (upd 22 Mar 2016)

  7. UNi Xonar installer addon documentation

  8. ASUS Xonar sound cards issues

  9. Xonar cards and AMD Ryzen motherboards compatibility

  10. Poll: Rate ASUS Xonar driver support


  1. Release notes

  2. Windows 10 compatibility


Page updates and announcements:

Previous post updates

DONATIONS - Donation list here

Let me first say that these drivers are free of charge for everyone. Those of you who appreciate my hard work and take pleasure in contributing, you can make a small donation (minimum $2 because of fees). Bear in mind you don't donate for ASUS/C-Media work, you do it for the work that I have done and the support I'm providing.

CONTRIBUTIONS - Contributors list here

Surely donating is not the only way you can support this project. You can submit your custom made icon, application or any other little enhancements that can make UNi Xonar better. Let's not forget about spreading the word about UNi Xonar drivers and helping other Xonar owners.


Release notes 1.81a

Driver for all supported cards. Includes 1825 audio drivers for Windows 10. Unlike previous releases, the 1825 audio driver will only work in Windows 10.

Driver changes:

  • Windows 10: Updated audio driver to 1825 (built date: 22 ‎June ‎2016, made by C-Media).
  • Updated C-Media Panel.

Other notes:

  • Replaced C-Media driver uninstaller with UNi Xonar driver cleaner.

Rev. 2 changes:

  • Added support for STXII cards in Asus Audio Center, cards will be detected as STX by Asus Audio Center but feature wise almost everything should be there.

Known issues:

  • 1825 audio drivers have an issue when the audio card is uninstalled, disabled or the drivers are overwritten, resulting in a system crash. In order to avoid the uninstall system crash I've come up with a workaround  that's presented below
  • Asus Audio Center: GX button is no longer showing. It has to do with 1825 audio drivers and there may be a reason why C-Media removed it. I'm not sure if it's worth it to bring the GX on/off control back.
  • STX II:  Asus Audio Center is missing the gain 16/32 ohms for headset.
  • Windows 10: Before updating to new version, you should uninstall the v1.81a drivers, as the update process might result in BSOD (#1).

Possible issues:

  • STX II: XonarSwitch might not work. Need more feedback on this.
  • Audio playback through headphones and SPDIF at the same time isn't possible anymore. Original report. Need more confirmations.
  • DSX & probably other cards: DTS Connect with 5.1 speakers does not work. Original report. Need more confirmations.
  • There are reports that the sound quality of these audio drivers is different. RightMarkAudio tests that I've made didn't show any significant differences between v1.81a and v1.80a.
  • The 1825 audio driver may have higher DPC latency than previous drivers. Original report. The tests that I've made didn't show any difference in DPC Latency between v1.81a, v1.80a and v1.80b drivers. Maybe it has to do with the settings that are being used. My test where done with 2.0 analog output.
  • When waking system from sleep, volume from one of the speakers could be x2 louder. Original report.

How to uninstall 1825 v1.81 drivers: In order to avoid a system crash while uninstalling 1825 drivers you will need to play an audio file before proceeding with the uninstall process. Restart system after the uninstall process is done.


Release notes 1.80

UNi Xonar installer changes:

  • Added DPI interface scaling to the installer.
  • Added card autodetection and if the audio card is not detected it will show an error message with possible reasons for that.
  • Improved driver cleaning. It uninstalls all copies of the Xonar/C-media CMI8788 drivers that are present in the Windows driver repository. By installing drivers with "Run driver cleaning" option you won't be able to use "Roll Back Driver" option for the audio card in Device Manager.
  • Changed the driver installation procedure. Added a fail safe driver installer that should help in those cases where you were required to manually install the audio driver or install it in safe mode. Silent installation is always on and its user option has been removed. If standard driver installation gets stuck (does not finish after 100 sec) it is automatically closed. If standard driver installer fails to install the drivers then an alternate driver installer is launched. If that fails too, you will get notified by the installer that driver installation failed.

Driver changes:

  • Windows XP: Added support for other CMI8788 cards.
  • Xonar DG, DGX, DG SI: Front Panel jack detection should now work if it did with the original drivers.
  • Fixed GX not being turned off by default in "Normal" configuration for the following cards Xonar D2, D2X, DG, DGX and DG SI.

Rev. 2 changes:

  • Improved and fixed some problems with the new driver installation procedure.
  • Added different messages based on why installation failed.
  • Fixed "Front Panel Microphone" not working by default.

Rev. 3 changes:

  • Increased the delay between driver cleaning and driver installation procedures. Might help in some installation failing cases.
  • Fixed the "Warning: Windows running in Test Mode or with Disable Driver Signature Enforcement is required!" message not showing up if needed in combination with the detected audio card.

The 1.80 drivers come in two variants:

  • 1.80a "Standard"

Driver for all supported cards. Replacement for 1.75a driver. Includes 1816 audio drivers for Win XP and 1823 audio drivers for Windows Vista/7/8/8.1/10.

Driver changes:

  • Windows Vista/7/8/8.1/10: Updated audio driver to 1823 (built date: 2 Jun 2015, made by C-Media).
  • Includes updated driver installer, ASUS Audio Center and C-Media Panel.

Other notes:

  • 1823 audio drivers are the first drivers released for Windows 10 by ASUS/C-Media. Whether they perform any better than 1822 or STXII 11.5 drivers remains to be seen.
  • Xonar STX II cards: Drivers work with STXII cards but the changing audio settings may not work with ASUS Audio Center and only with C-Media Panel. Installation on Windows Vista/7/8.1/10 x64 requires Windows running in Test Mode or with "Disable Driver Signature Enforcement" option.

Known issues:

  • STX II: Asus Audio Center does not work. You need to download this patched version and copy paste it over “C:\Program Files\UNi Xonar Audio\Customapp\”.

Possible issues:

  • Microphone stops working if running specific programs. If you run into this issue please report it in a reply to the original report. If you run into the issue you can switch to v1.75a drivers or connect the microphone to the onboard audio card microphone input.
  • WASAPI playback issues might occur with some soundcards
  • Occasionally when waking PC up from sleep the Xonar card does not output any sound.
  • Drivers might stop installing on Windows 10. Try 1.75a, 1.80b or 1.81a instead.
  • Windows 10 Creators Update: Windows would not boot after these drivers where installed. If you run into this problem you have to boot Windows in Safe Mode and remove the audio drivers. Original report. I could not reproduce the issue.
  • 1.80b "STXII"

Driver mainly for STX II and  STX II 7.1 cards. It does work for the other UNi Xonar supported cards too. Replacement for 1.75b driver. Includes STX II version 11.5 audio drivers (built date: 18 Feb 2014, made by C-Media).

Driver changes:

  • Includes updated ASIO (, driver installer, ASUS Audio Center and C-Media Panel.
  • Windows XP: Drivers now work for all UNi Xonar supported cards. These were not working with 1.75b drivers.

Other notes:

Rev. 2 changes:

  • Fixed "Asus Audio Center" not working properly and getting replaced by C-Media Panel when installing with "Normal - Asus Audio Center" configuration.

Rev. 3 changes:

  • Fixed some installation issues when drivers were installed on STXII cards (like missing driver uninstall entry in Programs and Features,  incorrect C-media panel name).
  • Fixed a bug where optimal card configuration was not being applied if the drivers were installed without the "Re-enable stereo upmix" option.

Possible issues:

  • Microphone stops working occasionally or when changing audio playback settings (DS->WASAPI). If you run into this issue please report it in a reply to this comment. If you frequently run into the issue you could try v1.75a drivers if possible or connect the microphone to the onboard audio card microphone input.

Previous release notes:

Release notes 1.75

UNi Xonar Installer changes:

  • Various changes and improvements done to the UNi Xonar installer.
  • Added warning message if installing the drivers would require Test Mode.
  • XonarSwitch is now automatically closed before installing the audio drivers.
  • Improved "Apply addons" function. Included .inf files from the drivers can now be dynamically altered. Documentation can be read here. Applying new 1.75 compatible versions of addons (like DHT4) will display the proper audio driver version now and users could now choose which addons they want to install once these are added to the Uni Xonar installer location.

Rev. 3 changes:

  • Fixed GX is not being turned off by default in Normal configuration for the following cards Xonar D2, D2X, DG, DGX, DG SI.

The 1.75 drivers come in two variants:

  • 1.75a "Standard"

Driver for previously supported cards. Same audio drivers as those in 1.72 (1816 for Win XP, 1822 for Windows Vista/7/8/8.1/10).

Rev.2 changes:

  • Fixed ASUS and C-Media Panels not working in Win XP.
  • Includes updated driver installer and C-Media Panel.

Known issues:

  • The installer is showing "Warning: Test mode to be enabled!" message by mistake if Xonar Xense selected as card.

Possible issues:

  • Missing Dolby Pro-Logic IIx options from C-media Panel. If you have this issue, you can use the "C-media Panel v1.62" installer addon or install v1.72 drivers.
  • 1.75b "STX II"

Driver mainly for STX II and  STX II 7.1 cards. It also works with UNi Xonar previously supported cards.

Rev.2 changes:

  • Fixed issue where installer did not apply the correct audio settings (e.g. to fix surround echo). Anyone who installed the previous 1.75b drivers should install the 1.75b rev.2.

Driver changes:

  • Includes updated ASIO ( , ASUS Audio Center and C-Media Panel.
  • Includes STX II version 11.5  audio drivers (created on 18 Feb 2014).

Other notes:

  • These drivers will work with the previously supported Xonar cards on Win Vista/7/8.1/10 but may require that you enable Windows Test Mode on 64 bit OS.
  • These drivers do not work for the other Xonar cards on Windows XP.

Known issues:

  • ASIO in 64 bit mode does not work. The cause of this issue is the 64 bit asio  dll file from the original STXII drivers.
Release notes 1.72

These drivers bring Windows 8.1 support.

Driver changes:

  • Updated audio driver to version 1822 for Windows Vista/7/8/8.1. Still using 1816 for Windows XP.
  • Includes updated driver installer, ASUS Audio Center and C-Media Panel.

Other notes:

  • New icon for UNi Xonar installer. Thanks to propheticus for his contribution.
  • ASUS Audio Center and C-Media Panel tray icons now have higher resolution icons. Useful for >100% DPI settings.

Known issues:

  • GX is not being turned off by default in Normal configuration for the following cards Xonar D2, D2X, DG, DGX, DG SI.
Release notes 1.71.1

Replacement for v1.71 driver package with configuration fixes and updated components.

UNi Xonar Installer changes:

  • Updated UNi Xonar Installer with that from v1.80a.

Driver changes:

  • Updated driver installer, ASUS Audio Center and C-Media Panel with those from v1.80a.
  • Added theoretical support for STX II cards.
  • Fixed GX not being turned off by default in "Normal" configuration for Xonar D2, D2X, DG, DGX and DG SI cards.

Known issues:

  • In some cases, WASAPI exclusive playback is interrupted by playback from other audio applications. More details here. Fix: If you don’t use S/PDIF, disable  "S/PDIF Pass-through Device (Asus Xonar...)" from Control panel->Sound. It's confirmed that the audio drivers included in v1.70 don’t have this issue.
  • Win Vista/7/8: There are reports that you cannot play sound through S/PDIF and headphones at the same time.
Release notes 1.71

Driver changes:

  • Updated audio driver to 1821 for Windows Vista/7/8  and 1816 for Windows XP.
  • Includes updated driver installer

UNi Xonar Installer changes:

  • Fixed some issues with Driver cleaning module
  • Improved and fixed some potential issues with UNi Xonar Installer

Known issues :

  • C-media Panel: Enabling and disabling "7.1 Virtual shifter" option disables stereo upmix. Use "Stereo upmix switch" to re-enable it or you can use the C-media Panel v1.62 addon (it will revert to an slightly older C-Media Panel version)
  • GX is not being turned off by default in Normal configuration for the following cards Xonar D2, D2X, DG, DGX, DG SI.
  • In some cases, WASAPI exclusive playback is interrupted by playback from other audio applications. More details here. Fix: If you don’t use S/PDIF, disable  "S/PDIF Pass-through Device (Asus Xonar...)" from Control panel->Sound. It's confirmed that the audio drivers included in v1.70 don’t have this issue.
  • Win Vista/7/8: There are reports that you cannot play sound through S/PDIF and headphones at the same time.


Release notes 1.70

Driver changes:

  • For Windows Vista/7/8 it includes 1818 audio drivers. For Win XP it includes 1814 audio drivers.
  • Includes updated versions of C-media and Asus panels.
  • Fixed HTOmega Claro 2 driver support.
  • Fixed driver signature issues for the other non-Xonar cards that were present in previous release.

Rev. 3 changes:

  • All the improvements and changes done to the UNi Xonar installer from 1.7x versions have been incorporated into this release (like support for addons).
  • Updated C-Media Panel with the one included in 1.72 release.

UNi Xonar Installer changes:

  • Added option to apply addons at driver installation.
  • Improved Low DPC Latency option. Now it allows access to C-media Panel as well. And Asus Audio Center won't autostart after driver installation like it previously did.
  • Improved Driver Cleaning process. Now it will clean the Panel and HsMgr(GX) processes startup entries too.
  • Reduced the overall installer size (from 13MB to 7MB)
  • Replaced Windows XP driver installer with the same one that's being used in Windows 7. Please report if there are any malfunctions compared to previous UNi Xonar driver releases.
  • Removed "1777 drivers + Asio 1.0". This option lives on as an addon.
  • Rev 2: Applied all UNi installer fixes from 1.71

Known issues :

  • C-media Panel: Enabling and disabling "7.1 Virtual shifter" option disables stereo upmix. Use "Stereo upmix switch" to re-enable it or you can use the C-media Panel v1.62 addon (it will revert to an slightly older C-Media Panel version)
  • GX is not being turned off by default in Normal configuration for the following cards Xonar D2, D2X, DG, DGX, DG SI.

Other notes:

  • New icon for UNi Xonar installer. Thanks to propheticus for concept and contribution.
  • ASUS Audio Center and C-Media Panel tray icons now have higher resolution icons. Useful for >100% DPI settings.

Complete Previous Release Notes

Notes about Windows 10 compatibility (updated 29 May 2020)

UNi Xonar drivers v1.64 and above will work with Windows 10. There could be some issues that you could run into depending on audio settings used. Different drivers could work differently so if you encounter any issues try installing the other UNi Xonar versions. You will have the same issues with corresponding versions of ASUS drivers.

Apart from driver issues, there could be issues solely from Windows 10 sound system that would be fixed with future Windows updates. There is also a small chance that some things could break with future Windows updates. Here are some solutions on how to prevent a forceful Windows 10 standard or version update.

Some of these issues also apply to other audio cards (Realtek, Creative, EVGA Nu Audio, ASUS Strix etc.) and external DACs.

> Find out which Windows version you have installed.

Windows 10 (multiple versions) notes

Possible issues and fixes:

  • Microphone not working - Check this guide. (thanks Shane)
  • Audio crashes - If you have “Dolby Atmos for Headphone” app installed you should remove it and replace it with the updated “Dolby Access” app in order to avoid audiosvr process stack overflow errors that are crashing the audio subsystem. (thanks Chris Leipold)
  • Popping and cracking sounds - If you have a AMD graphics card, try disabling AMD High Definition Audio Device from Device Manager->"Sound, video and game controllers". It's possible to try the same steps for Nvidia HD Audio Device if you have a Nvidia card. (thanks Marc)
  • BSOD's after system wakeup from sleep - Try UNi Xonar v1.71.1 driver. (thanks Kalle)
  • For systems with 1.81a drivers, the upgrading process to new Windows 10 version might result in BSOD (#1) causing the installation to fail. To avoid this problem, uninstall the v1.81a driver before upgrading.
  • The number of audio channels resets itself back to 2 or can't change to more than 2 channels(stereo) - This might be caused by having enabled one of the Spatial Sound options (Windows Sonic for Headphones, Dolby Access, Dolby Atmos for Headphones, DTS Sound Unbound). Check that Spatial Sound is Off by right-clicking on Windows Volume tray icon.
  • Sound playback echos. Issues within Windows 10 might cause the enabling of different sound settings, one of them causes sound playback echos that are more or less evident. To ensure you always get the best audio quality it might worth checking this from time to time. See Fix sound echos in Windows.
  • No system sounds. See these solutions.
  • Audio stutter in games. Open Windows Sound (right-click on Windows Volume tray icon-> Sounds or if missing type in Windows search: "change system sounds"), select Playback tab, double click your default playback device (for example Speakers ASUS Xonar Audio Device), go to Advanced tab and in the Default Format option select another sample rate setting and back to your original setting. The described windows and settings look similar to those this picture. (thanks Jean Paul).
Windows 10 version 2004 (May 2020 Update) notes

Known issues:


Possible issues:

  • System crashing when installing the Xonar drivers (#1). A possible solution might be to install the drivers with Windows booted in Safe mode.
  • Equalizer and other sound effects from the cards control panel do not get applied to the sound when using S/PDIF output (#1).
  • Occasional BSOD when waking the system from sleep (#1, #2, #3). The BSOD shows DRIVER_IRQL_NOT_LESS_OR_EQUAL (cmudaxp.sys) as the cause. A possible solution could be to install v 1.71.1 drivers, please provide feedback if this worked for you.
Windows 10 version 1909 (November 2019 Update) notes

Known issues:

  • Higher DPC latency which may cause massive stuttering (#1). The v1909 can be uninstalled from Control Panel->Programs and Features->View Installed Updates-> select and uninstall "Feature Update to Windows 10 Version 1909 via Enablement Package (KB4517245)". To prevent v1909 update (KB4517245) to be installed again you should use Wushowhide tool (guide on how to use it) or disable Windows Update altogether for the time being.

Possible issues:


Windows 10 version 1903 (April 2019 Update) notes

Possible issues:

Other notes:

  • Windows Sound is no longer accessible from Windows Volume-> Sounds. If you want to control the playback devices, recording devices, Windows sounds you can open Windows Sound by typing in search: change system sounds or by going to Control Panel->Sound.
Windows 10 version 1809 (October 2018 Update) notes

Before upgrading to 1809, you should uninstall the UNi Xonar drivers especially if you have v1.81a installed, as the update process might result in BSOD (#1). As a reminder, in order to avoid a system crash while uninstalling 1825 (v1.81a) drivers you will need to play an audio file before proceeding with the uninstall process. Restart the system after the uninstall process is done.

Possible issues reported so far:

  • Crashes at boot or after walking PC from sleep or hibernation (#1)
  • Audio stops working after some time (#1)
  • Inability to change the number of audio channels to other than 2 channels when using S/PDIF output if you have Speakers disabled in Windows Sound -> Playback (#1).
  • For 1825 (v1.81a) drivers, during the installation of some Windows updates the system might get a BSOD (#1).
Windows 10 version 1803 (April 2018 Update) notes (updated 13 May 2018)

Our community member Chris Leipold reports that the wake up from sleep BSOD, settings reset and not working audio server process at startup issues that where introduced with Fall Creators Update are fixed with Red Stone 4 preview (pre 1803 release).

Possible issues and fixes:

  • Microphone not working - Check this guide. (thanks Shane)
  • Audio crashes - If you have “Dolby Atmos for Headphone” app installed you should remove it and replace it with the updated “Dolby Access” app in order to avoid audiosvr process stack overflow errors that are crashing the audio subsystem. (thanks Chris Leipold)

Possible issues reported so far:

  • Settings (Bit-depth, sample rate, number of channels) reset bug when clicking the volume after restart might still happen (#1)
  • Windows might freeze when installing Xonar drivers (#1)
  • Microphone might not work even after doing the microsoft privacy toggle fix (#1)
  • S/DPIF output might not work at least for some with Xonar DG cards (#1)
Windows 10 version 1709 (Fall Creators Update) notes (updated 13 May 2018)

Reported issues so far:

  • Drivers above 1821 v1.71 may cause BSOD when waking system from sleep (#1, #2, #3). It's unclear if it is a driver issue or a Windows issue that's triggered in specific conditions that are met when using drivers above 1821 v1.71. Since ASUS/C-media driver support is pretty much dead and most people didn't have this issue until Windows 10 Fall Creators Update, people having this issue should contact Microsoft support and submit their crash dumps.
  • Card settings are being restored after each restart. A temporarily workaround would be to save your settings as a XonarSwitch profile and apply it each reboot. Anyone affected should report the issue to Microsoft. Update 6 Feb 2018: it looks like this is fixed in insider builds >= 17074, and it will be fixed in Windows 10 version 1803. Update 8 Mar 2018: this should be fixed with KB4074588 update for version 1709.
  • Default format (bit-depth and sample rate) from Windows Volume->Playback devices and the number of audio channels resets each time the Windows Volume icon is clicked (#1, #2). Anyone affected should report the issue to Microsoft. Update 8 Mar 2018: this should be fixed with KB4074588 update. Update 13 May 2018: This issue might still happen even after installing KB4074588 (#1).
  • Possible high frequency tone when playing audio.

Previous Windows 10 notes


Driver Downloads (Windows only) - click here if downloads are not showing

Standalone applications for changing settings or enhancing audio: 

1. Standalone apps pack. Based on a script made by Virus. Before running the files, close any audio source/application. Legacy, preferably use XonarSwitch and configure it with separate profiles.  Does not work correctly when used with STXII ("b") drivers. Contains:

  1. Front panel switch v3.2
  2. SampleRate switch v1.2
  3. Microphone Array Enabler v1.1 - Might be useful if you have an microphone array
  4. HDAV HDMI enabler v1.0 - This application hasn't been tested please submit feedback if it works or not. It appears it is not needed anymore.
  5. Acoustic Echo Cancellation enabler v1.0 - Useful for other Cmedia 8788 based cards that lack this setting
  6. Stereo upmix switch v1.0
  7. 7.1 virtual speaker shifter enhanced profile v1.0 - Profile created by Cu. This profile should enhance the effect of positioning in games when using Dolby Headphones and 7.1 virtual speaker shifter. Please provide feedback about this profile. Demo.
  8. Headphones ohm Amp switch v1.0  - Works only with the cards that support this.

2. Additional tweaks

  1. Disable SpeakerCompensation tweak
  2. Increase microphone volume by 3 dB tweak

3. Xonar related applications:

  1. XonarSwitch (beta) - Alternative panel to Asus Audio Center and C-Media Panel. Allows you to control various Xonar’s audio settings, define them as switchable profiles and apply them on-the-fly without having to stop the audio playback.
  2. Front Panel switch (new version) - Application that seamlessly changes between rear speakers and front panel speakers output.
  3. UNi Xonar driver cleaner - Standalone driver cleaner based on the one that's included in UNi Xonar drivers.
  4. Xonar Restoree Extended - Tool to restore Xonar cards hardware ID. The extended version includes support for Xonar STX II and Xonar DG SI cards.
  5. Xonar Driver Restart - Application that will restart the Windows Audio Service and C-media audio driver. Useful for sound loops, no audio output and other issues.
  6. Xonar Relay Restart - Application that will force the the Xonar relay switch to reinitialize. May be useful when there is no audio output after system boot or wake up from sleep. May be used instead of Xonar Driver Restart as it is quicker and does not affect running applications. This will cause a temporary 1 sec switch between rear and front panel outputs.
  7. Xonar-EQ - Control Xonar equalizer settings from your Android phone or tablet. By Sascha.

4. Auxiliary audio applications:

  • ASIOConfig - ASIO configuration viewer/changer that can be used when you can't access the Xonar ASIO Configuration directly. By djdecks.
  • SoundLock - Set the maximum output volume that sounds can be at. Can replace Xonar SVN in some cases (like limiting the volume of loud noises in movies). Works on Windows Vista and newer.
  • more...


  1. atyagi613 Jul 2020 @ 23:21

    Will there ever be newer drivers for the Xonar DS/DX PCIe?


    • CarvedInside14 Jul 2020 @ 11:11

      Don't think there will be any new audio drivers from ASUS/C-Media, and when it comes to UNi Xonar improvements, currently I don't anything new. More info about the UNi Xonar driver release process at FAQ Q&A 13.


  2. Tisusbr14 Jul 2020 @ 05:43

    I would like your opinion. I was thinking of getting an Asus Xense 7.1. And use your driver (which I already know well because I already had an X-Meridian 2G). However I have a ryzen 5 3600 on a motherboard am4 gigabyte ab350 gaming 3. However I read a lot about the incompatibilities of the pcie. This motherboard does not have an asmedia chip. Is it worth it. ?


    • CarvedInside16 Jul 2020 @ 17:41

      I don't know. You should make the decision taking into account that there is significant chance it won't work properly and if that's the case you would have to sell the card. Given that these cards are no longer supported by ASUS, I would not pay too much for it. If you decide to try the card let us know if it works properly by writing a comment in the dedicated page.
      Do you still have the X-Meridian 2G? Does it work fine on your on this Gigabyte AB350-Gaming 3? Again, let us know with a comment in the dedicated page.
      The B350 chipset is made by ASMedia.


      • Tisusbr16 Jul 2020 @ 20:32

        Unfortunately my X-Meridian 2G was normal pci. And unfortunately I did not have the conditions to import a pci to pcie adapter at the time to test. :(.
        I miss my old sound card. I am looking for something of a higher level than the ALC1220 that I have the possibility of 7.1. More thanks for your opinion more for the value it will not be worth the risk.


    • QuattroM17 Aug 2020 @ 23:23

      I have the Xense (still with the original Sennheisers). Since Febuary i have the Ryzen 5 3600. I just installed for first time the these drivers. Hadn't had any (MOBO related) issues with the card.


  3. -i.nwA_18 Jul 2020 @ 19:49

    Hi so for some reason my card randomly stopped working a couple of days ago.
    I think it's related to a windows update because the card disappeared out of the device manager completely but reappeared after i removed the latest windows updates, and even booting without forcing driver signature doesn't work.
    The card works fine in safe mode and when using asus drivers.
    EEPROM seems fine.

    Any ideas?


    • CarvedInside19 Jul 2020 @ 11:13

      1. Tell me your complete Windows 10 version.
      2. Which Xonar card do you have and which UNi Xonar drivers you tried and are no longer working?
      3. Do you know the names of the Windows updates have you uninstalled?
      4. Even with recent Windows updates uninstalled, the card only works in safe mode?
      5. If you boot in normal mode, does the card show up at all in Device Manager? It can be detected as "ASUS Xonar..." or it could be as a unknown device like "Multimedia Audio Controller" or "Unknown device".


      • -i.nwA_01 Aug 2020 @ 18:49

        Wanted to get back to you
        I was originally on 1.81a Rev.2 but after the card (Essence STX v1) stopped working i tried all drivers that were compatible with Win10 (v1.64 and up) but none worked so i rolled back to the drivers from asus's which worked.
        Unfortunately the official asus drivers had some weird rough high sound for a split second whenever you started playing audio, similar to the known white noise issue the STX cards randomly have just for a split second.

        I just now uninstalled official asus and reinstalled 1.80a Rev.3 and the card works again. I guess it's just microsoft doing microsoft things.

        The updates i originally installed where KB4497165, KB4565633 and KB4565483 but i don't know which windows version i was using back then.
        I'm now on 2004 19041.388 (Latest non beta as of 01.08.2020).

        The card didn't show up at all in device manager until i uninstalled the 3 updates. And safe mode with network drivers didn't work aswell, only normal safe mode.

        Kinda weird but everything works again so yeah.

        Also thanks for the drivers.


  4. SchwurbelMeister20 Jul 2020 @ 18:10

    Just a bit of feedback from me:
    Am using an STX II soundcard.
    I've upgraded my system from a 2014 Z97 mainboard to a recent "MSI X570 Tomahawk" with a Ryzen CPU. Win 10 v2004.
    Every time during the Asus driver install the system just restarted (without BSOD), so I gave this driver a try. Booted without driver signature enforcement, installed the non-lowLatency version, success. Worked flawlessly.

    Until today, when I literally threw my headset against my monitor because it did output a very high pitched noise and put the audio output to over 9000 percent during a youtube video. The "screeching issue", as its known here. Never had this one before.
    Did multiple driver cleans, reinstalls, strange thing, I tried to install the official Asus version again and somehow it installed and worked, no BSOD. And had the loud audio issue 5 minutes later again.
    Now I have the low latency version installed. Youtube is running constantly and no issue so far, but I honestly don't trust the soundcard any more. I still have kind of PTSD from the audio blast.

    So, thats from my end. Nothing but issues on the new hardware 🙁

    Btw, I'm still not 100% sure if the driver is even correctly installed - what should the device manager say if its working?
    My card shows up as "Speakers (ASUS Essence STX II Audio Device)" with the driver set to:
    "Provider: Microsoft"
    "Driver Date: 06/12/2019"
    "Version: 10.0.19041.1"
    "Signer: Microsoft"
    which is exactly the same info as on the onboard soundcard entry. Is it correctly installed? Does it use the wrong driver somehow? It shows at "Driver node strong name":


    • CarvedInside21 Jul 2020 @ 05:10

      The loud white noise issue has a dedicated page here where you can find read about possible solutions and other recommendations. If you encouter the issue again, try those possible solutions and let us know if any of them worked for you.

      About potential compatibility issues with the MSI X570 Tomahawk, did you by any chance changed the PCIe speed to Gen 1 for the PCIe slot where the card is plugged? If you experience any reboots when changing card settings let us and of course try the possible solutions from this page.

      As for the driver version installed, you are not looking in the right category. Look under Device Manager->"Sound, video and game controllers".
      If the card works, the driver is installed as there are no drivers offered by Microsoft.


  5. Chris Shields28 Jul 2020 @ 17:43

    Getting occasional DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD in cmudaxp.sys on resume from sleep with latest Windows 10 x64 2004. Didn't happen with previous version of Windows 10, although I've seen it before with other versions prior to that. I've tried both 1825-v1.81a-r2 and 1822-v1.75a-r3 and both occasionally BSOD. I'm guessing apart from trying other driver versions I'm out of options? I wish we could get hold hold of the source code.

    Xonar D2X/Asrock Z68 chipset motherboard


    • Meru28 Jul 2020 @ 21:15

      Try 1816/1821 v1.71. My Xonar DX works fine with these drivers.


    • CarvedInside29 Jul 2020 @ 00:24

      1. Tell me your complete Windows 10 version.
      2. Can you estimate the frequency of the BSODs, 1 at how many wake ups?
      3. This could be also be a result of a conflict with other drivers. Mention which video card and drivers you have installed and if you any other cards or devices connected to the PCIe slots or USB ports.
      4. Which Panel configuration you have selected during install? If you have Low DPC Latency or C-Media Panel, have you tried with Normal and vice versa?
      5. As Meru said, also try with v1.71a drivers.

      Let us know how these suggestions go.


      • Chris Shields29 Jul 2020 @ 03:50

        1. Version 2004 Build19041.388 (May 2020 update)
        2. Maybe 1 in 50 wake ups (every 2 weeks at 4 wake ups daily)
        3. Nvidia GeForce 1060 (most recent drivers)
        4. Low DPC Latency. Haven't tried Normal yet.
        5. Will try v1.71 drivers next, thank you.


        • CarvedInside30 Jul 2020 @ 00:18

          In this case I suggest you try with v1.71 first. If that does not work fine, try any drivers with Normal panel configuration. While I doubt this is one of those cases, in extremely rare circumstances there is a conflict with other drivers and Normal configuration with Hsmgr (GX) processes seem to work around that.

          Do you have Corsair iCue software installed?

          LE: Have you tried testing your system memory lately? Check with Memtest86+ or Windows Memory Diagnostics.


          • Chris Shields30 Jul 2020 @ 05:58

            No I don't have Corsair iCue. Memory has been tested and gets a good workout in modern games. The system is otherwise completely stable. I've always disabled Hsmgr processes and never had a problem until this update to Windows. And I always use XonarSwitch (it is excellent) to configure audio profiles. The Xonar D2X shares IRQ 16 with Intel 6 Series/C200 Series Chipset Family USB Enanced Host Controller - 1C2D and also the NVIDIA GeForce GTX 1060 6GB. I don't know whether this is known to have problems?

            The other reoccuring problem I have is the audio volume only affecting the left channel, with the right maintained. So volume can only be reduced in one speaker. This is fixed for a few weeks by uninstalling/reinstalling the driver. This could potentially be triggered by the BSOD in cmudaxp.sys.

            The earlier drivers sound slightly different to my ears (less treble). Am I imagining things?


            • CarvedInside31 Jul 2020 @ 00:17

              About the issue with volume change affecting only one channel, is it something that also appeared after Windows 10 v2004 update or you had that before and if you remember if it started after a specific Windows version update? I've seen such a issue reported before, but can't remember when and where (could have been on reddit or other forums concerning other audio cards). I think this one is 100% a Windows bug, you can contact Windows 10 support and bring this issue to them.

              Don't think the IRQ sharing is the problem. If you still have the issue with v1.71.1, then you could change the GPU IRQ as described here and see how that goes.

              I have not seen any objective proof that the sound is different with v1.71.1. I'll refer you to one of my previous comments about this topic. I have not done the new tests.


              • Chris Shields31 Jul 2020 @ 17:20

                The volume issue has always been an issue with Windows 10 since the first Windows release and across all driver versions. Something is triggering it, and it does seem to occur after the BSOD.

                Thank you for the MSI link - I wasn't aware of this. I've enabled it for the GeForce card (until the next driver update at least!)

                If you do new RMAA tests I'd be interested to know the results too. I thought perhaps the equiliser settings were applied differently on earlier drivers requiring more treble.

                Many thanks.


  6. ameneses03 Aug 2020 @ 02:32

    I have the Assus Essence STX II (think it's the ll), which is a fabulous card, but I can't explain why the latest original drivers are 2015 --that's 6 years!
    I'd really appreciate your advice regarding the drivers that are posted as UniDrivers, I've been weary of installing them and they also seem outdated.
    Any comments?


  7. Ch!llkroete09 Aug 2020 @ 19:00


    unfortunately the one of the driver files (cmudaxp.sys) is blocked by a Anticheat Client from FACEIT (faceit.com). The support say that "FACEIT Anti-Cheat is blocking certain drivers that contain known security vulnerabilities" (https://support.faceit.com/hc/en-us/articles/360014237259--Forbidden-driver-error-message-and-blocked-drivers). Is there any chance that this will be fixed? I really dont want to use the crappy original driver 🙁

    Thanks in advance and best regards,



    • CarvedInside10 Aug 2020 @ 06:14

      Hi. I can't do anything about this problem. The only ones that can fix whatever issue there is with cmudaxp.sys driver file (if there really is one) are C-Media. Now they would do something if ASUS asked them, but they probably don't care about this or any other issues, but you should inform and ask them anyway.
      Have contacted faceit support and that quote is from their reply? Because if there isn't actually a security vulnerability within cmudaxp.sys then they could whitelist the file.

      It's possible that a different driver version could work. If you find one that works let us know.


      • Ch!llkroete11 Aug 2020 @ 21:35

        Okay, I see this will be difficult :(. I asked FACEIT support what has to be done that the file will be whitelisted but I didnt receive an answer yet. Furthermore I opened a ticket to ASUS support, hoping to get a useful answer.
        But honestly, I think I will sell my soundcard and never buy any ASUS stuff again...
        As far I receive any news on that I will tell you. Thanks so far!!


        • Ribbon12 Aug 2020 @ 00:20

          I haven't used faceit anticheat in a while so I tried opening it now and it blocked the driver. Last time I used faceit ac was about a month ago together with 1825 v1.81a r2 driver and there were no issues. What driver do you use?
          Shame, it's unlikely that anything will be done about it by Asus/Cmedia and I doubt faceit is going to whitelist the driver.
          So I'd love to hear if you get any kind of response from the parties involved about the driver. I really, really don't want to go back to onboard audio whenever I feel like playing a game protected by faceit anticheat.


          • Ch!llkroete18 Aug 2020 @ 20:08

            Hi there,

            I just wanted to give you an update. The FACEIT support said I should install the newest driver version which I did and it worked. The ASUS support told me that they have tested their drivers for anti cheat and it everything is fine. So my setup now are the orginal ASUS drivers but running which XonarSwitch - which is in my case the most important tool, as I am able to justify the equalizer and other important settings. So for so far I am able to play FACEIT.
            I really appreaciate your work here guy(s?) so if there is anything else I can do for testing or so, please feel free to contact me.

            Best regards,



            • CarvedInside19 Aug 2020 @ 03:57

              Good to hear. What Xonar card do you have and which driver version you had installed when you had problems? I'm thinking that if you've installed drivers that did not have a valid signature for you card and used the "Disable driver signature" or "Test Mode" methods to install them, then it's possible that was the cause.
              Anyway, whether or not that was the case, if you still want any of the UNi Xonar features you can install the version that has the same audio driver version as the official drivers that you currently have installed.


            • Ribbon23 Aug 2020 @ 18:17

              Technically 1825 v1.81a r2 is the latest driver, but it gets blocked on my machine (XonarDG, driver signature and test mode are untouched)... I guess 1816/1823 v1.80a r3 should work fine then since it's the same 1823 driver as ASUS offers on their website ( What driver did you use before?
              And thanks for sharing your experience, if I feel like going back to Faceit it's good to know that there's at least some workaround that works (besides going back to realtek) and not every single driver is blacklisted.


  8. Dartin Bout10 Aug 2020 @ 03:39


    I have an old Auzentech Meridian soundcard that happily ran as a 5.1 DAC into my home theater using the Xonar Asios implementation and RCA cables. Last year my right side/rear speaker went silent using JRiver. In an effort to resolve the issue, I replaced the amp, the speakers, the RCA cables, the speakers cables. Nothing worked. Finally, I tried Foobar2000 and my right rear/side channel came alive!. JRiver is my preferred application and I have thousands of 5.1 files. I contacted JRiver and they said the reason that just my rt. rear/side didn't work is because these drivers are not 64 bit. I have scoured this site and found no info as to whether these are 32 bit or 64. Can someone confirm or deny this?


    • CarvedInside12 Aug 2020 @ 05:23

      Hi. First, which drivers have you installed? If I understand correctly the problem is with ASIO playback, right? The UNi Xonar drivers have both 32bit and 64bit versions of ASIO.
      If you want to check if in foobar2000 you are using 64bit or 32bit ASIO, you can go in foobar2000->Preferences->Playback->Output->ASIO and see if you have "Use 64-bit ASIO drivers" selected. But I don't think that's the issue, as it would not work at all for any speakers if the issue was with ASIO drivers. My guess, it's a problem with ASIO configuration or a bug in the version of JRiver you have. Now, you either try to see if you can find how to correctly configure it or use a different playback output like WASAPI. I would recommend this instead of ASIO, as the ASIO implementation on these cards is not that great and from what I saw it may have a worse audio quality.

      If you really want my help with JRiver, be it with ASIO or WASAPI configuration or investigate what is the issue, I could look into it but it would cost you about $15.

      Some offtopic suggestions. Use "/" instead of "\", that's the character for "or". It's "JRiver" not "J. River". I took the liberty to correct your comment so it's more easily understood.


      • Dartin Bout12 Aug 2020 @ 08:27

        I have tried the last three versions but currently using In Foobar, I do have the 64-bit checked, I'll try Wasapi but I may be operating under the delusion that I hear compression artifacts when doing so under JRiver. I also tried KS and DS in JRiver. No upmixing of channels or bitrate. I got the right side channel in everything but Asio but I still hear the artifacts in everything but FB. I'd pay the $15.


        • CarvedInside16 Aug 2020 @ 09:49

          I moved your comment that's above from a new comment to a reply to the original discussion. For future comments, please use the REPLY button on the right of the comment you are replying to.

          Never mind what I said previously about ASIO playback quality, I revisited the tests I previously did and it's fine.

          Now to the problem with JRiver and ASIO, I've investigated and I think I found how to fix the problem. In this case, if you send me $12, it's fine. So if you wish to do so, you can send me a donation following this link and add "JRiver ASIO problem" in the payment notes so I now it is from you. I'll follow up with the instructions to your e-mail address.


  9. QuattroM19 Aug 2020 @ 23:17

    Two days ago I told you your drivers worked flawless with the Xonar Xense on a MSI B450M Mortar Titanium and a Ryzen 5 3600. Later I found out I couldn't get the Mic to work. Today I had to do a reeinstall of Windows, and with UNi Xonar 1816/1823 v1.80a r3 Mic is working as well. Not 100% sure but I think last time I used UNi Xonar W10 1825 v1.81a r2. Don't know if this information is of any value for you, but still I want to let you know. Great work man! Will make a contribution.


    • CarvedInside20 Aug 2020 @ 06:05

      Thank you for the donation and the information provided. Did the microphone suddenly stopped working or you haven't checked it in a while and when you did, it did not work?
      The issue could be because of a Windows 10 bug that might be associated with a specific Windows update. Let me know if you have the issue again.


  10. Hamburgerschnack01 Sep 2020 @ 11:51

    Hi there, thanks for your development efforts, I've been using those drivers for years for my Asus Xonar D1 and generally they work flawlessly.
    Unfortunately, I've experienced an issue for quite some months now. Not sure whether it's driver related.
    While playing a game my mic not only transmits my voice but the game sounds, too.
    I've muted the mic hardware-side and deactivated all other recording devices in the windows control panel, to no avail.

    So I reckon, it's either a hardware issue (short-circuit or noise from the front panel to the sound card) or a driver issue.

    Do you have any idea on how to troubleshoot this further?
    I'm using the newest Win10 version and I think with the 1.81a driver version (though no 100% sure)


  11. pro02 Sep 2020 @ 14:42

    Also reporting random BSOD (irq less or equal, cmudaxp.sys) after wake up from sleep using 2004 W10. Xonar DX. using the R3 driver. However I also recently did a BIOS update. I'm not sure if it's the new BIOS or the 2004 updates, but I did have 2004 from before and had no issue.


    • Chris Shields04 Sep 2020 @ 12:49

      Can you estimate the frequency of the BSOD? I had the same issue only after upgrading to 2004. Changed the drivers over to v1.71.1 a month ago now and there have been no BSODs - one would very likely have happened by now so I'm guessing this fixed it (thanks @CarvedInside!) What motherboard do you have btw? I have an Asrock Z68 based board.


    • CarvedInside04 Sep 2020 @ 18:22

      1. The important part of the driver version is missing from your description, please provide that. Also provide the full version of Windows 10, which motherboard do you have and which video card.
      2. Does the problem happens always or sometimes? Can you estimate the frequency of the BSODs, 1 at how many wake ups?
      3. Have you tried with UNi Xonar v1.71.1 and Low DPC Latency configuration?
      4. The problem could be from a recent update to Windows 10 v2004. You could try uninstalling some of the recent updates following the guide here along with temporarly blocking Windows updates so they do not install again until you've tested things.


  12. Felicity10 Sep 2020 @ 09:44

    Question: is there a way to force the dgx audio center to stay in English? It seems to go by the region locale setting that Windows has. I run Japanese locale for various reasons and while I can navigate the dgx interface fine since I know all the buttons by memory by now but it's something I couldn't figure out if there was a reg setting to override it


  13. ngwoo17 Sep 2020 @ 09:29

    I have the Xonar DGX on an Asrock Z77 extreme4 motherboard, i5 3570k CPU, Windows 10 v2004.
    I can confirm that the 1.71 version of these drivers fixes the BSOD upon resume issue that seems to plague a lot of people. It was happening about 50% of the time with the latest drivers, and hasn't happened a single time with these ones.

    However, I'm experiencing an odd issue similar to the "screeching" problem that someone else has mentioned but slightly different. Occasionally (very occasionally, maybe once or twice a month) while watching a Youtube video or playing a game, although it only happened one time doing the latter, the system will lock up and play the last half second or so of audio on a permanent repeat. In the case of Youtube videos they will actually keep playing, and I will be able to manipulate windows and open the start menu, however attempting to log out/switch users/reboot will fail on a black screen and I'll need to do a hard reset to get out of this buggy state.

    I did a memtest and hard drive checks to rule out the possibility of bad ram or a failing hard drive. Since it only happens with audio playing I can only assume it's audio hardware related, but the event log doesn't provide any useful information since the system doesn't actually crash. The only pertinent entries are about the unexpected shutdown I have to do to fix it.

    Anyone else had anything like this? I know it's not exactly the same as the screeching issue, but does it seem similar enough to try some of the same fixes?


    • CarvedInside18 Sep 2020 @ 00:24

      1. Regarding the BSOD after wakeup issue, did it start after Windows was updated to v2004 or it also happened previously? Which drivers you had before and if your tried with any other version?

      2. Regarding the sound repeat issue, I don't know remember seeing someone else reporting such an issues. Yes, you should try those suggestions. Would you say you had this issue prior to Windows 10 v2004? Did you had this when you had Windows 7? When you last had this issue, which driver version did you had installed and which panel configuration had you selected during UNi Xonar driver install?


      • ngwoo18 Sep 2020 @ 01:11

        The BSOD after wakeup issue has been one that affected me on every Windows 10 version, and with every version of the drivers I tried later than the 1.71 ones, including the latest official Asus drivers. Although I've only used this card for a little over a year, so I don't have any experiences with previous versions of Windows or any Windows 10 version earlier than around the beginning of 2019.

        The sound repeat/system freeze issue didn't happen prior to v2004, as far as I can remember. No experience with this card/drivers on Windows 7, unfortunately. Last time it happened I was using the 1.71 version of the drivers with the normal Asus Audio Centre.

        I'll try as many of the screeching fixes as I can, however I don't think I'll be a very good source for troubleshooting info since the problem is so rare that a fix may be hard to confirm working. My use case also unfortunately currently requires the use of the card's recording inputs, and if I had to buy a USB microphone for troubleshooting I'd probably just buy a USB sound card and replace the Xonar card altogether with how many other troubles I've had with it.

        That said, I'll try the other fixes and if in the next few weeks I think they may have helped I'll report back. Thanks again for all the help, and for the good drivers.


        • CarvedInside24 Sep 2020 @ 00:32

          For trying the possible solution 1 that suggest disabling the Xonar cards recording inputs, you could use the onboard audio card's recording. You could try this solution last.


    • Felicity18 Sep 2020 @ 09:32

      I have had bsod on wakeup issues entirely once or twice; it was unrelated to the card. It was generally because I had voltages too high. If you don't have your system agent or IO manually set (VCCSA and VCCIO) make sure they aren't like 1.4 or something and more like 1.15, motherboards like to go overboard.


  14. aniken28 Sep 2020 @ 11:49

    Sorry I'm sure this has been asked before, but I can't search within comments:
    From the C-media Panel (or the Xonar Audio Center), there is a volume slider per speaker (e.g. left and right), by default it is set to +0dB, will increasing it to +12dB (the max) cause clipping/quality loss or will it still be within full range? Speakers are pretty quiet without that.


    • CarvedInside29 Sep 2020 @ 01:06

      If I am to answer your questions I need to know if you've previously sent me a donation. If so, send me an e-mail from that e-mail address and mention the nickname you used here. In case this is not evident from the adblock messages you've seen, I'm explaining it more here.


  15. Steve30x29 Sep 2020 @ 23:32

    Is there any way to get modified drivers working with the Xonar AE? I got this card today and theres no way to set SPDIF to 5.1 and the Sonic Studio control panel isn't much good either



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.