sprite

9251 Comments

  1. Rob02 Oct 2015 @ 21:05

    HI !! I have got some annoying problem with my DX card and it seems that it has been a common problem for several users in the past and recently. The problem is that ever since i installed Win 10 x64 right channel goes silent randomly and it seems like it happens mostly on Chrome and when starting a Youtube movie so far. Just when the video starts its goes silent on right and i need to reboot or deactivate the card and reactivate to get it working normal again. And sometimes like today i have also that full volume white noise problem which also occured a few times on Win 7 but not often. Im using the latest firmware on the card aswell tried Asus and urs Win 10 beta driver with same problem. Any suggestions would be nice altho i know there hasnt been any real answers to these problems what i have found. When the card works its 100% perfect just very annoying with this bugs and would be pity to go back to onboard soundcard instead.

    Reply

  2. Jasper02 Oct 2015 @ 21:50

    Hi.. I'm using a Xonar DG on windows 10 64bit with driver v1.80a r2, Everything is working perfectly except for the microphone. It doesn't record voice input, so i'm unable make skype calls.. any fix for that?

    Reply

    • CarvedInside02 Oct 2015 @ 22:01

      Hi,
      Is you microphone connected to the front panel of the case or directly to the card?
      Make sure you have it selected the microphone for the Xonar DG as "Default device" and "Default communication device" in Windows Volume->Recording Devices.
      If it is set as default and it still does not work try unchecking and checking the "front panel microphone" option from the Audio Panel or from Windows->Volume->Recording devices-> “Microphone Asus Xonar DG(…)” Proprieties-> Custom.

      Let us know if the tips above worked and which one.

      Reply

      • Jasper02 Oct 2015 @ 23:14

        1. It’s connected via the front panel.
        2. In Recording devices Microphone (Xonar DG) is set to “Default device” and “Default communication device”
        3. Tried switching between Font Mic and Microphone, didn’t worked..
        When switched to front mic and enable monitoring it keeps outputting a high-pitched static noise and when switched to microphone it produces a low static noise.

        Reply

        • CarvedInside03 Oct 2015 @ 01:22

          I don't know what it could be. Try your microphone in the onboard audio card and see if it works there. Of course you will need to set that as default.

          Reply

          • Jasper16 Oct 2015 @ 20:47

            It was an issue with the microphone itself. got a new razer kraken and the drivers are working perfectly, no issues whatsoever.

            Reply

  3. Tuoni02 Oct 2015 @ 22:50

    Endpoint protection doesn't like the new installer and files at all.
    Main executable is blocked and after installation Endpoint is also not happy with a handful of dll's in the windows/system folder. For now i reverted back to 1.75b r2 as that version installed and worked just fine on my system.

    Reply

    • CarvedInside03 Oct 2015 @ 01:28

      I've received feedback from another STX II owner and for him 1.80b r2 installed with all settings properly set up and with ASUS Audio Center autostarting at Windows startup.
      Now that you mention Endpoint protection not liking the 1.80b r2 drivers, that might explain the partial install and maybe some files and actions where blocked.
      You are perfectly fine with 1.75b r2 but if in he future you will like to install a new xonar driver you might need to pause the protection and add those files to the antivirus exception list.
      Regarding the paranoid protection of some security suits I'm not sure what I can do.

      Reply

      • Tuoni03 Oct 2015 @ 01:46

        I read your comment about partial installation and that made me think about a possible issue with Endpoint.
        I will try to install 1.80b r2 with Endpoint disabled and see if that will result into a full complete installation. It's weird that Endpoint doesn't give any notifications during installation but as soon as you try to run the program after Endpoint starts to be difficult about multiple files in multiple folders which makes it harder to make a(n) exception(s) for.

        Reply

        • Tuoni03 Oct 2015 @ 02:20

          Hmm.. cant edit my own post.
          Anyway. I installed 1.80b r2 with Endpoint completely disabled (as in log only mode, don't delete or block anything). That seems to help as it installed without problems and the control panel is auto starting with windows now. Also have the UNi Xonar driver entry in the software panel now which helps if i ever want to uninstall it again. Driver still installed with GX enabled, samplerate set to 96Khz and S/PDIF out enabled though.
          Endpoint doesn't go nuts over the dll files which was most likely caused by the incomplete and therefor mismatching installation of those files.

          In short everything seems to be back to normal now except for the weird default settings after installation.

          PS Why is it called "Oxygen HD Audio" in the control panel now? I liked the old "UNi Xonar Driver" name and the corresponding icon better. 🙂

          LE:Another small update
          I did a full scan to see which files are a problem for Endpoint or other antivirus programs. The scan shows that only the “cmicnfgp.dll” file in the windows syswow64 folder is causing a problem and Endpoint wants to quarantine it. I made an exception for that .dll file.. i totally trust you on this one ;-P and Endpoint is “happy” with the Xonar drivers now.
          Maybe it worth looking into how to avoid the “cmicnfgp.dll” file being seen as a possible threat by antivirus software with future driver package releases.

          Reply

          • CarvedInside05 Oct 2015 @ 03:07

            Thank you for the feedback so far.
            It's showed as “Oxygen HD Audio” because the configuration file where it is labeled as "UNi Xonar Driver" wasn't properly installed.
            The “cmicnfgp.dll” file is C-Media Panel and its also used to launch Asus Audio Center. I take the file from the original driver files and replace icons and some images.

            If you still got 1.80b r2 drivers installed I would like to know some things. Can you tell me if you got "cmudaxp.ini" and "cmudaxp_STXII.ini" in "C:\Windows". If you don't have them, do a search for them in the Windows directory and see if they are other directory. If its possible I would like for you to send me these cmudaxp.ini and cmudaxp_STXII.ini files and any cmcnfg*.ini files that are stored in "C:\Windows\System\". You can e-mail them to me. These are Xonar driver configuration files generated by the installer and might be of help in figuring what is going wrong.

            Reply

            • Mopral05 Oct 2015 @ 15:45

              On my computer, it's also showed as "Oxygen HD Audio" in the control panel with 1.80b r2 and STXII card.
              I search for those .ini files and they are exactly in the directory you give
              Just give me your mail if you want me to send them to you

              Reply

  4. Kwakiz03 Oct 2015 @ 22:03

    Hello i have also Asus xonar D2X sound card i installed windows 10 recently and i got all sound drivers working but when i have this on max sound everything sounds really low even thou i got everything on 100/Procent sound you know whats wrong?

    Reply

  5. Tuoni04 Oct 2015 @ 20:13

    Do you have the driver cleaner tool also available as a standalone application?
    I ask this because once 1.80b r2 is installed there's no way to properly uninstall it. When i go to the programs and features window in the control panel UNI Xonar is listed but get an ''program not found. Probably already uninstalled. Do you want to remove the entry from the list?'' error. So i can manually uninstall in the device manger window but that will leave about everything still on my system. There's something going on with the way the installer works (or rather say not works) with driver package 1.80b r2. I also tested 1.80b r2 on the system of my GF who is running Windows 8.1 Pro and the exact same issues on her system.
    I did not have any issues whatsoever with the installer of driver 1.75b r2. Why did the installer change, what do i gain from the new installer if it would work properly? Right now i feel like i would like to see all the driver improvements of 1.80 packaged in a 1.75 type installer.

    Reply

    • CarvedInside05 Oct 2015 @ 03:21

      Here is the driver clear tool as a standalone application. Before you cleanup, read the comment I've made to you in the other discussion thread.

      What Xonar card has your GF PC?

      I believe that the problems that you've been experiencing with 1.80b drivers are related to the updated driver+components installer (from C-Media) and updated C-Media Panel and are not related with the UNI Xonar installer which launches the driver+components installer.

      Reply

      • Tuoni05 Oct 2015 @ 20:23

        I did read it and send you an email couple seconds ago. Please let me know if you need any additional and/or extra information.

        My GF system had my STX II because at that time i did not had a different Xonar card to test it with. Sadly couldn't convince my GF not to go for the Phoebus.
        But today i borrowed a Xonar DX and tested that card in my GF system with Windows 8.1 and the 1.80a r2 drivers. Everything installed and functioned fine (after disabling anti virus) with that combination. Control Panel auto loads without any weird default settings and in the control panel it is listed as UNi Xonar Audio something... don't remember the exact name 🙂 It's nothing like Oxygen HD Audio or something like that at least.

        So with my limited testing it seems that it is an issue with the Xonar STX II and the 1.80b r2 STX II driver version. As i can't get that driver to instal properly under Windows 8.1 Pro x64 or Windows 10 Pro x64 no matter what i try or do while the DX with 1.80a r2 driver installed correctly the first try.

        Reply

  6. Wulfgar05 Oct 2015 @ 18:21

    Hey Carved, the reported version of the "cmudaxp.sys" file under the Device Manager > Driver > Driver Details section of my Essence ST is 7.12.8.1794. Shouldn't it be .1823? I'm using UNi 1823 1.80a (not r2).

    Reply

    • CarvedInside05 Oct 2015 @ 20:19

      No. Its like that because the C-media guys doing the audio drivers are to lazy to update the version field of the file when doing a new build.

      Reply

  7. Marco05 Oct 2015 @ 21:04

    After a while my microphone doesn't works anymore. It get's recognized but it's like it is muted somehow, but it's not. It just doesn't work. Always have to re-install the uni xonar driver.
    Using win 10 x64 home. Asus xonar dx.

    Reply

  8. Al Curtis06 Oct 2015 @ 00:59

    Problem with Xonar Essence ST; No matter what version drivers i install..any of the UNI Xonar or ASUS oem, cannot select other than 2 speakers or headphones in analog out no matter what setting source input is at on either the C-Media panel or Xonar audio center. I have the Xonar H6 output card installed that has the side, rear and center/sub rca outs. Have had the same problem with a HDAV1.3 Deluxe card that was replaced by the Essence ST in hopes of solving this. OS is windows 7 Ult 64 bit, Asrock FM2 FM2A85X Extreme 6 mobo, AMD FM2 A8-5600 apu

    Reply

    • Al Curtis06 Oct 2015 @ 05:42

      Removed Essence ST card, put HDAV1.3 Deluxe card back in system. Removed drivers i had in and used cleaning tool. Installed Uni Xonar 1.80a drivers and on the C-Media panel i could now get 7.1 speakers to display. Reinstalled Essence ST(had to install 1.80a again), no 7.1 on either control panel. Tried 1.80b drivers..nothing. Uninstalled drivers yet again (driver clean tool used again), put in HDAV1.3 Deluxe yet again, istalled 1.80a drivers again...now no 5.1 or 7.1 anymore...about ready to go to a creative soundcard.....

      Reply

      • Tuoni06 Oct 2015 @ 11:58

        Can't be of much help other then to say that i have no issues with 7.1 output through the H6 board on my STX II with the 1.80b r 2 drivers.
        Good luck with Creative.. they also have their fair share of software and driver issues.

        Reply

  9. Keith Robinson06 Oct 2015 @ 17:17

    Hi
    I Have the Xonar D2 and it is just not working with Windows 10 Pro, and ideas.

    Thanks

    Keith

    Reply

    • Tuoni07 Oct 2015 @ 22:27

      I'm working on a build with a Xonar D2X on Windows 10 Pro x64 right now and the card works perfectly.
      Think we need a bit more information then "just not working" to try to help you.

      Reply

      • Keith Robinson08 Oct 2015 @ 21:18

        I was just hoping that someone knew about a driver that would work with Windows Pro 10.

        It started when I installed Windows 10 Pro the day it was released. I notice that my Xonar D2 sound card wasn't working at all, not only that, but as far as Windows 10 Pro 64bit was concerned the soundcard wasn't there. I shut down the computer, remove the card, and inserted the card into a different PCI slot, making sure that the cables were in correctly. I then re-booted the PC again, hoping that the computer would now recognise the card, but it didn't. I have tried all the different drivers that people have been suggested, but none work with my card.

        Reply

        • CarvedInside08 Oct 2015 @ 22:19

          What error message you get when trying to install 1.80a drivers? Have you tried the possible solutions from this guide?

          Reply

  10. Mike00k706 Oct 2015 @ 20:05

    Thanks for making my STX running smooth on Win 8.1 pro x64! Keep up the good work, u are great!!

    Reply

  11. Kostas06 Oct 2015 @ 20:42

    Hello
    I have the D2/PM and under windows 10 i have run into an issue with ASIO. When i use Asio with a 192khz file and thus with a sample rate of 192/24 or 192/32 i get noice and clicking like it is in complete distortion. Everything else works perfect. Even 96/24 or 96/32 formats. Has anyone had this problem?

    Reply

  12. avcrnjkeec07 Oct 2015 @ 02:05

    Is it possible to create a script (batch file or otherwise) to enable/disable SVN?

    Reply

  13. Tuoni07 Oct 2015 @ 10:28

    Something else..
    I'm working on a system with a Xonar D2X and now I'm wondering if it's possible to completely disable analog output when using the S/PDIF output?
    I'm asking because in this setup he wants to connect his 5.1 Kave headset to the analog output of the D2X and use the S/PDIF output of the D2X for his 2.0 monitors. Now he doesn't want any sound coming from his headset when he's using the S/PDIF output when listening to his monitors.
    I've been poking around in the control panel but it seems you can enable/disable optical output but can't disable analog output when optical output is enabled.. or am i missing something?

    Reply

    • CarvedInside07 Oct 2015 @ 17:21

      I don't know of such a setting. You may try and see if you can configure the "S/PDIF Pass-trough Device". This way he could set Speakers or "S/PDIF Pass-trough Device" as the default playback device in Windows->Volume->Playback devices. I don't have any experience with "S/PDIF Pass-trough" as output and if it would actually work in this case cause I've seen people asking me how to make it work.
      Another way would be to connect the 2.0 monitors to the onboard audio S/PDIF output as in this case it would not make any difference in terms of sound quality (with S/PDIF the digital to analog conversion is done in the speakers/receiver and not the card). Again switching between the Xonar Speakers and onboard S/PDIF in "Playback devices" depending on the need.

      Reply

  14. larry09 Oct 2015 @ 08:59

    these work great on Windows 10 Pro latest insider build. excellent

    Reply

Legend:AdminAuthorFeaturedLinkedOff-topic

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
  • Don't post questions without doing a search beforehand
  • For replies to individuals regarding the SAME discussion, use Reply to write to that individual. For a NEW issue write a new comment.
  • Make your comment easly readable. Write the product names how they are originally written or at least capitalize their first letter. Write "i" as "I". Add a space after end of a sentence and beginning of another (e.g. ".I" -> ". I").

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.

Close