unihead ico2

UNi Xonar Drivers 1.80 (post periodically updated)

Page updates/changelog:

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

  • Asus Xonar: DG, DGX, DG SI, DS, DSX, D1, D2, DX, D2X, HDAV, HDAV Slim, ST, STX, STX II, Xense.

  • Other C-Media CMI8788 audio chip based cards: Auzentech X-Meridian & X-Meridian 2G; HT Omega Claro Plus, 2, Halo, eClaro; Razer Barracuda AC-1. (view full list)


UNi Xonar Features

FAQ & troubleshooting guide (updated 27 Feb 2015)

Useful tips & suggestions | Known issues & workarounds (updated 27 Feb 2013)

UNi Xonar installer addon documentation

Having problems installing UNi Xonar drivers? Refer to this topic

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

A WORD ABOUT 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 (like 2 to 5$). Bear in mind you don’t donate for ASUS & C-Media intellectual property & work, you do it for the work that I have done.

CONTRIBUTIONS – Contributors list here.

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


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.
  • Windows 10: Fix for microphone not working with some 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).
  • 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.

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
  • 1.80b “STXII”

Driver maily 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).

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.


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.

Known issues:

  • GX is not 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 “STXII”

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.

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)
  • 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 Digital Output from Control panel->Sound. It’s confirmed that the audio drivers included in 1.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 Updated 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.

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)


Release notes 1.64 rev.2

  • 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.

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.

Read Previous Release Notes


Notes about Windows 10 RTM compatibility (updated 28 Nov 2015)

UNi Xonar drivers above v1.64 will work in Windows 10 but since the audio drivers are not yet made specifically for 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.

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.

Update 28 Nov 2015: The Windows 10 Threshold 2 update does not seem to fix many of the sound issues that where present so far and it may introduce new ones. In my opinion Windows 10 is a very buggy OS, the only things working fine are the spying of its users(#1, #2) and the periodic removal of user preferences and programs(#1, #2, #3, #4).

Update 19 Oct 2015: The audio fixes from Insider Previews >= 10547 will probably be included in the upcoming “Threshold 2” update that will be released around November 2015.

Update 1 Oct 2015: The Windows 10 development team is fixing some audio issues with Windows 10. The fixes where made available for testing starting with Windows 10 Insider Preview build 10547.

100% compatible drivers when?

Because of the very slow development of the audio drivers by C-Media and the long time it takes for C-Media partners (ASUS and HTOmega) to release the new drivers it may take a while before we have a 100% compatible driver for Windows 10.  If we are lucky we will have new audio drivers in 2-3 months after Windows 10 RTM launch. As soon as new audio drivers became available I will release a new UNi Xonar drivers package.

Update 01 Oct 2015: 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.

About Chrome stutter issues on sites like YouTube. (27 Aug 2015)

Update 27 Aug 2015: The stutter issues on youtube are  fixed with the latest Chrome build released on 20 Aug 2015 (v 44.0.2403.157). Reports indicate that stutter issues are still happening for videos on other websites (eg. daily motion, facebook, instagram).

Update 7 Aug 2015: After some testing and some reading it seems that the stuttering issues are not related to the UNi Xonar drivers. I’ve got the same behavior with Realtek’s onboard audio and from what it looked liked. My guess the issue is caused either by Windows 10 or Chrome.

There is a Chromium issue opened here.

Here are some things you could try:

  • Change Chrome audio buffer size.
  • Change/keep sample rate to 44.1 kHz both in the audio panel and Windows Volume->Playback devices->(…) Audio Device Proprieties -> Advanced -> Default Format.
  • Change sample rates back and forward a couple of times.

Driver Downloads (for Windows only):

  1. UNi Xonar 1816/1823 v1.80a r3      mirror1
  2. UNi Xonar STXII 11.5 v1.80b r3      mirror1
  3. UNi Xonar 1816/1822 v1.75a r2       mirror1      mirror2
  4. UNi Xonar STXII 11.5 v1.75b r2       mirror1      mirror2
  5. UNi Xonar 1816/1822 v1.72    mirror   
  6. UNi Xonar 1816/1821 v1.71    mirror
  7. UNi Xonar 1814/1818 v1.70   mirror   
  8. UNi Xonar 1814/1815 v1.64 r2   mirror    (proven stable)
  9. Older versions : v1.63 beta; v1.62 betav1.54 ; v1.61 ; v1.53

Official addons (documentation):

  1. “1777 drivers + Asio 1.0” aka “ASIO 1.0 Patch”. Info.
  2. C-media Panel v1.62 (fixes stereo upmix turning off for v1.64 rev.1 drivers)

3rd party addons page here.

Standalone applications for changing settings : 

1. Standalone apps pack* (mirror). Legacy, preferably use XonarSwitch with separate profiles instead. 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.

*All these apps are based on scripts created by Virus. Before running the files, close any audio source/application.

2. Other Xonar related applications:

    1. Front Panel switch new versionmirror (by Virus; notes)
    2. ASIO settings viewer/changer (external link)
    3. Audio re-starter for sound loop problem for Win Vista/7/8 by Razord93 (external link)
    4. Xonar-EQ – Control Xonar equalizer settings from your Android phone or tablet. By Sascha.
    5. UNi Xonar driver cleaner v1.01


  1. Philippe    13 Jan 2016 @ 22:57   


    I am the owner of an Asus Xonar Essence ST sound card, with a Asus P6T motherboard with a Windows 7 installation. I use the UNi Xonar 1823 v1.80a r3 driver.

    I have run a batch of tests to ensure that what goes out the line-out analog output was a good signal. To do these tests, I went from a 24bits/96kHz recording I did from an analog tape player to a portable digital recorder.
    The spectral view of the original file goes like this.
    As you can see, there is a line at 33000Hz, which would not be there with a 48kHz file.
    Then, I play the file using different softwares and settings, and plug in my recorder on the soundcard’s line-out and record at 96kHz again.

    Test #1, Adobe Audition3 in ASIO mode:
    With that set up, I actually get a quite good output, with all the frequencies. However, I cannot use that set-up, because it sometimes causes a BSOD: cmudaxp.sys
    However it proves that the soundcard has the hardware capabilities of rendering such a signal.

    Test #2, Adobe Audition 3 in Direct Sound Mode:
    I have configured Direct Sound to render at large frequencies, in windows and in the driver’s panel:
    But as you can see the output has been resampled at 44100Hz(or 48Hz?)

    Test #3, Adobe Audition 3 with ASIO4ALL:
    I have installed the ASI4ALL driver, hoping this would get me a more stable ASIO interface to the soundcard. However, it doesn’t change a thing compared to the Direct Sound configuration, except some latency problems (I haven’t adjusted those parameters for the test, but I don’t doubt it can be easily fixed):
    It is still resampled at 44100Hz (or 48Hz?)

    Test #4, Adobe Audition5 in ASIO mode:
    I have also tested Adobe Auditon CS6 (Audition 5) hoping in ASIO mode it would be more stable. However, it is not better since the rendered output is resampled at 48kHz
    Note that the ADIO control panel is greyed out.

    Test #5, Adobe Audition 5 in Direct Sound Mode:
    Not better than Audition 3 in the same mode, still resampled at 44100Hz

    Test #6, Adobe Audition 5 with ASIO4ALL:
    This time I have configured ASIO4ALL to use the hardware buffer. However, it seems the setting is stuck at 44100Hz, and the output looks resampled at this frequency.

    Test #7, Winamp with Direct Sound output plugin
    While I work on music with Adobe Audition, I regularly play music using Winamp. The standard output plugin is the Direct Sound output, which I expected to be resampled according to the settings of the windows’ sound panel or soundcard’s driver panel. As before, both are configured to the highest frequency, but I’ve also tried to adjust the frequency at 96kHz. In all case I still get a 44100Hz resampled output:
    Test #8, Winamp with Kernel Streaming Output plugin
    Unfortunately, I haven’t managed to make any winamp ASIO plugin to work. But I’ve found the Kernel Streaming plugin which is supposed to by-pass the system’s interface and directly handle the driver. Unfortunately, the output is no better than the test #7.

    To conclude, it seems that the hardware has the ability to render 96kHz audio; but some software configuration seems to be interfering and it is quite frustrating. I’d be very happy if you could point me to a way to investigate. I have no idea if this is caused by the driver, some system’s configuration, or a third-party software interfering.
    Unfortunately, I don’t have the means right now to make a new fresh install of Windows 7 w/ only the driver installed; not to run the same tests with the digital S/PDIF output.

    Thank you for your help


    • CarvedInside    13 Jan 2016 @ 23:40   

      You should try 1.75a and 1.80b drivers. 1.80b has newer ASIO drivers. If those do not work better, you could try the WASAPI output (winamp will require a plugin to support that).

      For DirectSound, ASIO4ALL and KernelStreaming the Windows Playback and Asus Xonar Audio Center sample rate settings should be set to those of the source material.


      • Philippe    22 Jan 2016 @ 23:33   

        Hello !

        Thank you for qui quick reply!

        I’ve changed Windows Sound’s setting at 96kHz, as well as Asus Control Panel’s settings. Then I played my file with Winamp using Direct Sound output plugin, Kernel Streaming output plugin, and the latest version (1.0.6) of YASAPI (the WASAPI plugin).
        In all cases my signal was downsampled at 44100Hz, like on the picture I previously posted here: https://lut.im/Q7j6wB1fi0/0WP76yijM79fKIfS.png

        Then, I uninstalled ASIO4ALL and uninstalled the 1.80a driver. I restarted the computer, then installed the 1.80b driver. Then restarted the computer. Then set up windows’s sound and asus control panel at 96kHz. Then restarted the computer again.
        I re-run the same tests with winamp and the 3 plugins (Direct Sound, Kernel Streaming, YASAPI), and still got some same results.
        I have also tried Adobe Audition 5 (CS6) in ASIO mode and I still get the same results as Test #4 with my signal downsampled at 48kHz: https://lut.im/ewsPtXQE5A/jZZUcWNhyF7QtlCK.png

        Have you ever tried to run the same tests?! I’m pretty sure it’s a Windows-related issue with a part within the system resampling the signal; but I’d like to know if I’m the only one to have such downsampling, or if it happens to many installations?

        Thanks again


        • Cornea    23 Jan 2016 @ 00:02   

          Are you using a file that is 96khz for playback?


          • Philippe    23 Jan 2016 @ 22:53   

            Yes, this is what I said in my first message: “I went from a 24bits/96kHz recording”. The file I use for playback is a WAV PCM 24bits 96kHz.


        • CarvedInside    23 Jan 2016 @ 01:15   

          Hello. I don’t have Adobe Audition 5 and at the moment I do not have time to investigate this a issue. I think you are the first to bring something like this up. You could try and see how the onboard audio performs, that could answer if it’s Xonar related or something else.


    • Johnny    06 Feb 2016 @ 16:39   

      Any clue why the installer doesnt pick up any addons? Extracted the standalone pack in the same folder. Even tried creating an Addons folder to put it in, nothing detected.


      • CarvedInside    06 Feb 2016 @ 17:30   

        You’ve replied to someone else’s comment instead of posting a new comment. To post a new comment you need to use the comment form at the bottom of the comment section.
        Please redo your comment as a new comment.


  2. Peter    14 Jan 2016 @ 00:06   

    First of all, thanks so much for the great work you’ve done on developing these drivers.

    Now to my issue. Since Windows 8.1 x64 (currently on Windows 10 through an upgrade), I have had issues with sound completely cutting out. It seems to happen entirely at random, and may take place a few minutes or even a few hours after playback. Restarting the Windows Audio service always fixes it, but that’s obviously a band-aid solution.

    I have tried numerous drivers, both the official Asus ones (latest version as of this writing) as well as several UNi Xonar drivers since version v1.72, but the issue still occurs. There is no static noise of any kind, any playback simply stops in the blink of an eye.

    When sound drops, Windows still states that “This device is working properly” in Device Manager.

    An interesting thing to note is that I can still test speakers using the C-media Panel – the “Left front” / “Right front” test playbacks still work.

    At this point I’m suspecting some sort of core Windows Audio corruption.

    I’m running a Xonar DS.


    • CarvedInside    14 Jan 2016 @ 14:31   

      If you go to Event Viewer-> Applications and Services Logs-> Microsoft->Windows->Audio->Operational, are there any warnings or errors at the time of the issue occurrence?

      I too think that is may be Windows related. If you haven’t updated Windows in a while maybe you should do that first and check if you still get the issue.
      You could launch a cmd window as administrator and type: “sfc /scannow”. This will scan and attempt to fix any corruption issues with the Windows files.
      Secondly, it could be a issue with the motherboard. You should look if there are any new bios updates.
      You could also try the card in another PCI slot.

      BTW I appreciate your donation.


      • Peter    14 Jan 2016 @ 18:57   

        There are no errors or warnings listed in the Microsoft-Windows-Audio/Operational Event Viewer log.

        I always keep my installation fully updated through Windows Update.

        The result of running sfc /scannow was as follows:

        C:\WINDOWS\system32>sfc /scannow

        Beginning system scan. This process will take some time.

        Beginning verification phase of system scan.
        Verification 100% complete.

        Windows Resource Protection found corrupt files and successfully repaired
        them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
        example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
        supported in offline servicing scenarios.

        Updating the BIOS is something I’m a bit hesitant about as it can screw over one’s board in case of power outage. The latest BIOS update is from 7/12/2012 – http://www.asrock.com/mb/Intel/Z68%20Extreme4/?cat=Download&os=BIOS

        I did not have this issue when running Windows 7 Pro x64 and at that time I used the same BIOS version as now, so I suspect the issue is not located there.

        Incase the sfc /scannow run did not help, I think my best bet is to probably do a reformat + reinstall.


        • CarvedInside    14 Jan 2016 @ 21:06   

          You always had this problem since moving to Windows 8.1?

          I’ve seen stranger things happen because of the motherboard and where solved with a Bios update.
          But you are right to be hesitant as there is a small chance you could ruin your board. And we also don’t know what changed until v2.20. Which bios version do you currently have installed? Depending on how old it is compared the v2.20 it might be worth purchasing a bios chip flashed with latest update.

          As there aren’t other reports with issues like yours it is difficult to pin down the problem be to more sure in which direction to go.


          • Peter    14 Jan 2016 @ 21:19   

            The issue started a few months after updating Windows 8 to Windows 8.1, so I cannot say for sure if it was the update itself which caused it. However, during my 2+ year usage of Windows 7, I never experienced the issue.

            I’ve never flashed the BIOS, so it’s pretty old by now. I’m running v1.10.

            I understand it’s difficult to troubleshoot and in all honesty I doubt the UNi Xonar drivers are the cause of this issue.


          • Peter    16 Jan 2016 @ 18:14   

            So I tried physically removing the Xonar DS card and wiping all drivers using the uninstaller found here on the site. I also ran Driver Sweeper afterwards to wipe both Realtek as well as Asus sound card drivers. I enabled on-board audio and used the default Win10 High Definition Audio Device driver.

            Turns out that the issue still occurs, so now I can safely say that it is in fact not related to the Xonar DS card itself.

            Today I also noticed warnings popping up in Microsoft-Windows-Audio/Operational Event Viewer log, both with and without the Xonar DS installed.

            “Windows Audio encountered an error while processing a device event.
            DeviceEventType : 0x0x1 (DeviceRemoval)
            Failure Code : 0x0xE0000225”


            • CarvedInside    16 Jan 2016 @ 19:53   

              Good thinking testing with only the onboard audio card.
              I’m not sure what that Warning in Event Viewer means. Does the warning time stamp coincide with when the issue happens?

              Another thought, could the issue be with a specific player or a application that you are using? When sound cuts off if you try playing audio in other players does it work?


              • Peter    16 Jan 2016 @ 20:03   

                Yes, the warning appears when sound disappears.

                It’s not related to a specific application. The issue can occur no matter which program plays sound.


              • Peter    24 Jan 2016 @ 22:14   

                This weekend I decided to do a reformat and clean install of Win 10 x64. So far I haven’t experienced the issue again, so it looks like some sort of Windows corruption indeed was the cause.

                Running the latest UNi Xonar Drivers as of this writing.


  3. Panos    14 Jan 2016 @ 23:14   


    I have an asus xonar essence st on a gigabyte H81M-HD3 rev2.0 motherboard. When I’m using foobar witha asio drivers and asio xonar output I have a problem. When music is playing and I scloll the library in foobar I get glitches or audio stack. When I’m using jriver with asio output and asio drivers happens exactly the same. When I’m using motherboard realtek output with asio drivers I have no problem.

    If I use asio4all output audio is not working unless I go to unixonar panel and clich unclick and click again the spdif output. When audio is working and sroll the library I have again glitches…. with wasapi from the other hand everything works fine.

    The above problem is happening with windows 7 8 and 10. I’m disappointed.

    My essence st was installed in another pc I have and worked fine always with any driver.


  4. Jeippa Duippa    19 Jan 2016 @ 09:58   

    Couldn’t install Asus drivers for my Xonar Essence STX after I upgraded to Windows 10. This works lika a charm. Thank you!!


  5. Cornea    21 Jan 2016 @ 04:54   

    I have a small problem that may not be directly connected to Uni drivers.
    I use AIMP3 software to listen to music and I use Wasapi or ASIO for playback. With either of them, whenever I listen to music and browse Chrome at the same time, I get slightly popping and delays (as if the computer takes time to load Chrome first, ignoring the sound, and then continuing). So my question is: shouldn’t ASIO and Wasapi work directly with my sound card without being dependent on the CPU? Secondly, my CPU is an i5 2500 so it should be more than enough to handle both a music player and a browser? I’m very happy with AIMP3 otherwise, however could someone recommend other players for direct sound playback like ASIO and Wasapi? Thanks!


    • CarvedInside    21 Jan 2016 @ 15:51   

      ASIO and WASAPI do not bypass the CPU, they bypass Windows Audio mixer. ASIO at least in Xonar drivers implementation requires more CPU than DirectSound or WASAPI. Chrome takes all the CPU power you have if you have more tabs opening at its startup. I suggest you use the WASAPI output and try setting AIMP3 process priority higher. You can do this in AIMP Options->System-> set the Priority slider on the right to maximum. Note that if you use a Process Lasso, it will interfere with your set process priorities and should make some changes there as well.
      If that does not improve the situation switch to WASAPI non-exclusive output, that’s what I use and I don’t have any problems.
      Don’t think this is a issue with AIMP3. I consider AIMP to be the best audio player at the moment but if you wish to try with another player then try with foobar2000.


      • Cornea    21 Jan 2016 @ 17:48   

        Wow that’s a very helpful answer, thanks! I switched priority to highest and it solved the problem, I think. By the way I use ASIO by installing “ASIO4ALL V2” and by selecting “ASIO: ASUS Xonar ASIO driver” playback. Is it better to select this playback than just ASIO4ALL playback option? Is this the correct way to use ASIO through AIMP3? Are there other ways?
        By the way when I select WASAPI exclusive playback, other sources of sound do not turn off anymore (like youtube). It used to. What could have changed? Should I use Event or Push WASAPI? Thanks your your patience!


        • CarvedInside    22 Jan 2016 @ 16:27   

          ASIO4ALL is a 3rd party ASIO driver. You can use either the one with the drivers or the ASIO4ALL, don’t know which is better, I personally think that for Xonar cards the WASAPI implementation is better than ASIO and WASAPI should be just as good as ASIO in regards to sound quality.

          WASAPI exlusive playback issue is strange, are you sure you’ve set WASAPI exclusive and not WASAPI non exclusive. Anyway it might be because you’ve unticked “Exclusive mode” checkboxes from “Windows Volume -> Playback devices -> Speakers Asus Xonar(..)-> Proprieties->Advanced tab” or because of a issue with the drivers if you’ve installed v1.80a. If you’ve installed the v1.80a drivers try the 1.75a instead and see.

          Use WASAPI Event if that works fine for you.


  6. David    24 Jan 2016 @ 18:33   

    Do you have a theory pertaining to the problem addressed here?


    I’ve had this issue for as long as I own the card, on rare occasions I will get ear raped with heavy distorted sound, and ringing, causing me to throw my headphones off in shock.

    So far, in that thread, there seems to be no fix, and I’d like your take on it and if you’ve heard of this happening before?
    I look forward to your response.


    • CarvedInside    25 Jan 2016 @ 01:24   

      I’ve seen a couple of reports with this issue. Ever since I have the Xonar DX card (2008) I myself haven’t had the issue. I don’t know of any fix for these issues. It occurs to me that it might also be different issues and causes that sound similar. My thoughts on what it could be: 1) A compatibility issue with some motherboards that would make the Xonar cards malfunction at certain points. I’ve seen some strange compatibility issues with motherboards and Xonar cards so far. An example. In my search on cases with high volume white noise I’ve come across one case that supports this theory (link).
      2) Some Xonar cards have a hardware issue with one of their components.

      My recommendation is to either move to a Creative card, buy a external DAC or at least take some precautionary measures like controlling the volume with a amplifier while having Windows volume always set to 100%. Nothing is worth permanently damaging your ears.


  7. Jesús Gálvez    25 Jan 2016 @ 21:45   

    Microphone not working.
    Sonar DG Asus card .
    Windows 7 Ultimate OS Version 6.1.7601.19110 ( Win7 RTM)
    Geamibg Headset Creative Fatal1ty microphone with cable and connector green and pink
    Driver version
    The sound is very good, Xonar DG Audio Center have activated Mixer – Strengthening MIC microphone – microphone .
    Microphone helmets and work on a laptop, I put 1.75a drivers do not work , either above , I have disabled the BIOS from an on-board card, when the active had not worked. Any idea or possible solution ?.


  8. RichardHenri    29 Jan 2016 @ 23:31   

    Sometimes the sound from a video just stops working and I just hear static sound. It only happened to me on Youtube videos, not while I use players like VLC or MPC.
    It only stops when i close the tab and then I get a very high pitch sound. I need to shut everything down from the C-Media Panel.
    It happens something like once a day or so.
    Do you have any knowledge about this?

    I have the Asus Xonar Essence STX, on the v1.80a r3 driver.


    • CarvedInside    31 Jan 2016 @ 22:47   

      Hi. I don’t know a solution for this issue. There are other people discussing the problem here.
      Please clarify what you mean by “I need to shut everything down from the C-Media Panel”.


      • RichardHenri    31 Jan 2016 @ 23:05   

        I disabled it and enabled it in the mixer tab I think. This problem did not appear until I installed Windows 10.


  9. carpendale    05 Feb 2016 @ 06:29   

    I Have the Xonar D1 and running on Windows 10 64bit.
    Sometimes i have only sound on the left side on my headphones, i have google the problem and it seems that many others has that problem.
    and that there is no fix for that (only one guy in a Forum said he had chainged someting in the driver and it worked)
    But the thread ended and it is to old for an answere.
    It only worked when i restart my Computer but it is really annoying, so i have try to disable and reenable my soundcard in the device manager.
    But then i have to restart to.
    Is there any way to resete the soundcard without to restart?
    or better is there a real fix?

    i know my english sucks sorry for that 😛


    • CarvedInside    05 Feb 2016 @ 20:11   

      I don’t know of any permanent fix for the issue.
      A better way to fix this is to put your computer to sleep and then resume it. The hole operation would take like 5-10 seconds and you won’t have to close the audio applications.
      Sleep is available if you have Standby set to S3 in bios.


  10. Juri    08 Feb 2016 @ 13:21   

    I have both speakers and headphones connected to sound card. But headphones to work as headphones must be connected as front speakers. Co i connected front speakers as rear speakers. Is there any way to swap front speakers with rear speakers or change headphones jack to be rear speakers ?


    • HunterZ    08 Feb 2016 @ 21:50   

      My advice would be to use the pins on the card that are meant to be connected to a headphone jack built into the front of a computer case. That way you can hook up speakers and headphones at the same time and switch between them more easily.


  11. Murat    08 Feb 2016 @ 22:44   

    I have a Xonar D1 audio card and am running win 10 64 bit with the latest drivers (UNi-Xonar-1823-v1.80a-r3). I installed the low dpc latency version of the driver in hope to get rid of any unneaded hiccups in sound. After restarting the PC I noticed I still have a high dpc latency around 1000 us. However, I do use a astro mixamp since I was suggested to do so because I use the sennheiser game one headset which has a low impedence of 50 ohms. The amplifier is connected to the sound card via TOSlink optical cable. In the C-Media Audio panel i use six channels and S/PDIF output is set to dolby digital live. I the windows playback devices i set the default device to S/PDIF pass through device. Is the amplifier unnecessary?

    Please help


    • CarvedInside    09 Feb 2016 @ 16:23   

      Then your high DPC latency is not from the Xonar drivers. You may want to check The case of DPC latency – Part 2.
      If your amplifier is connected through the TOSLink optical cable then it is not an amplifier it’s a DAC with amplifier. This bypasses the Xonar’s DAC and op-amps when used with digital outputs (TOSLink, S/PDIF) so it makes your Xonar D1 kind of useless. Maybe your DAC has the option to connect it to the soundcard using analog cables.
      Xonar D1 has the impedance of 100ohm and its recommended that soundcards output impedance should be lower than the headphone output impedance, but your headphones might sound fine connected directly to the soundcard.
      I don’t recommend connecting the headphones directly to a Xonar card because of a issue with high pitch noise that some people get with their Xonar cards. If that would happen it could damage your hearing.


      • Marko    09 Feb 2016 @ 18:27   

        Thank you for your quick reply. Unfortunately, my headset (Sennheiser Game One) has ony a 3.5 mm jack so I can only plug it into the rear jack of the sound card without utilizing dolby digital output. Is it possible to use some sort of converter which would enable dolby digital? I use the Astro Mixamp pro to utilize virtual 7.1 surround which in my opinion sounds pretty good. I found a guide on youtube on this subject. Do you think I should ditch the mixamp and get another soundcard which has a built in amplifier for headphones? The sound quality seems pretty good right now though.


  12. Luka    10 Feb 2016 @ 08:36   

    I noticed strange problem on my DGX. Some sounds, especially short sounds like windows sounds have a “crack noise sound” at the start of the sound. this is only the case if you have no sounds running. if you listen to music then I didn’t noticed this problem.

    This problem is Esspecialy noticable if I jumping around on a youtube video stream or just pausing it.

    Any solution? I’m using v1.80a r3 – C-Media AP.


    • Luka    10 Feb 2016 @ 08:39   

      And just one more. I’m using Win 10 Pro.
      I don’t have this problem with my Realtek onboard audio, so I think OS has nothing to do with this …


    • Luka    10 Feb 2016 @ 17:09   

      I think I found problem … If I turn off smart volume (SVN) crak noise dissapear.


  13. Eros    10 Feb 2016 @ 17:31   

    “Audio re-starter for sound loop problem for Win Vista/7/8” is a good idea, but has a wrong title, but is also lacking a couple of important lines.
    It should actually be named as “driver restarter” and to be used for any (?) audio problems. It’s a must have tool for this horrid driver. Should run at Startup by default.
    According to the problems I had, I dumped this batch and wrote my own special Xonar Driver Restarter tool for resetting my Xonar DX1.
    Anyway, what the batch by Razord93 lacked and how resetting should be done, in the following order and have a 2 sec pause after each operation:
    1. Kill Xonar DX Audio Center
    2. Disable Windows Audio service (Administrative Tools > Services)
    3. Enable Windows Audio service
    4. Disable Xonar DX audio device (either with devcon.exe or manually in Device Manager, also, by disabling, the sound card makes 1 *click* sound)
    5. Enable Xonar DX audio device (soundcard produces 2 *clicking* sounds)
    6. Start Xonar DX Audio Center, and driver is ready to use.
    Killing the Xonar DX Audio Center first is very important.

    AND I managed to get rid of the high-pitch issue by actually getting rid of the official drivers from my hard drive (I bet 99%). The official driver uninstaller and UNi’s, even UNi Xonar driver cleaner, fail to fully remove the official drivers. And the presence of the leftovers are causing the problem. So, sadly, main priority is NOT to install official drivers at all. Use a 3rd party cleaner otherwise (I used Auslogic’s, CCleaner, Glary’s). In worst case, reinstall Windows. Or maybe it’s something else that those 3 tools fixed. But they did it, whatever they did. Oh, but I have not used GX function after I read that it’s devil’s handwork, so, maybe even that was the culprit…


    • CarvedInside    11 Feb 2016 @ 21:00   

      Thanks for the suggestions. Maybe you can share your driver restarter script with us.

      Which high-pitch issue you where getting, the one triggered by YouTube in Windows 10 or the general one (regardless of OS, application used)? I don’t think the driver leftovers are/where the problem cause people been having these issues on clean windows installs. Depending on which of the high-pitch issue you where getting maybe one of the Windows or browser updates fixed that. Anyway keep us informed if you start getting the high pitch issue again.


      • Eros    11 Feb 2016 @ 22:09   

        The high-pitch issue on Windows startup. Then I just restarted the driver and it was okay again. By high-pitch I think you mean +9000% volume, don’t you? But I haven’t had that issue after something fixed that. If it’s not the leftovers from official trash install, then either CCleaner, Glary’s or Auslogic’s fixed something.
        I also had the sound loop problem, when a media player crashed, due to the bad driver itself. Then I just restarted my PC. That was before I found out about the driver restarting batch, so, can’t tell if driver restarting helps instead of PC reboot. I think it was caused by GX function. I’m afraid to turn it on for tests. 😀
        The only issue I currently have occasionally, is 0 audio output after Windows startup. All audio software panels show that there should be audio, but there really isn’t. For that I have my Xonar Driver Restarter utility starting up with Windows, so I could perform audio test fast and then restart the driver if necessary.

        What I made is not a script, it’s a special utility for my DX1. Not even universal, since I lack info about other setups. It’s not even written in C/C++, but in yet another BASIC variant. 😀
        I programmed it to work on my PC. Maybe it might give inspiration for a more universal solution?


  14. Killer344    11 Feb 2016 @ 14:44   

    I’m planning to buy a Xonar DSX for the DTS connect capability exclusively (I have an x-fi forte right now, but due to IRQ issues it has the usual problems).

    The question is, can it be set to MSI mode to avoid the IRQ headache altogether? Sadly most x-fi can’t…



Leave a Reply


Your comment may be held for moderation. If it does not show up immediately, just be patient.