sprite

8368 Comments

  1. Michael03 Feb 2019 @ 19:20

    I recently ugraded my old Windows 7 system to a Ryzen-based x470 system running Windows 10 (latest version).

    Everything seems to run perfectly fine, however, I noticed that when changing to a different output the internal relay actually clicks 3 times in a row.
    With my former system it was just one click.

    Just wanted to make sure this is standard behaviour now with UniXonar. Tested the latest version aswell as 1.71. Same behaviour.

    But thanks a lot for still supporting this card. I would have a hard time finding an alternative soundcard.

    Reply

    • CarvedInside03 Feb 2019 @ 20:00

      Please clarify what exactly are you changing and from what to what. Which Xonar card do you have? Which motherboard do you have?
      I wouldn’t say 3 internal relay clicks are normal. I will have to check how it behaves for me.
      The relay click behavior could have changed if you’re using different drivers than previously, because of some issue within Windows 10 or the Ryzen platform.

      Reply

      • Michael03 Feb 2019 @ 20:26

        I’m using a Xonar Essence STX running on an Asus X470 Prime. So, no victim of the incompatibility between Ryzen & STX II here.
        When changing the ouput, it’s like 2 fast clicks, then about 400ms pause followed by the third click. And it happens every time, no matter if I change to speakers or headphone.

        . .. and if it helps: The card is seated in a PCIx1 slot with it’s own dedicated power cable running to a BeQuiet Dark Power Pro 550W power supply.
        Installed the latest version, followed by an uninstall and then 1.71 again. Same behaviour. Onboard sound is disabled in BIOS.

        Reply

        • CarvedInside03 Feb 2019 @ 21:00

          Your comment above was written as a new comment instead of a reply to the discussion and I moved it. When replying to an existing discussion use the “Reply” button floating on the right of the comment you are replying to.

          Which panel are you using to change the output? The speakers are set to multiple channels/speakers?

          Reply

          • Michael03 Feb 2019 @ 21:53

            I tried both panels. Speakers are set to 2 channel stereo.

            As long it’s working well, I don’t really care. But I’m curious how many clicks other users with an Essence STX get 🙂

            Reply

            • Michael03 Feb 2019 @ 23:05

              Just installed ‘UNi Xonar 1814/1815 v1.64 r3’ and there are just two clicks, like it used to be on Windows 7.

              As long as there aren’t any negative side effects and no bugs which are fixed in later versions, I consider this one as a keeper!

              Reply

              • CarvedInside04 Feb 2019 @ 16:59

                Which driver version did you had installed when you where on Windows 7?
                I have tested with my system Intel Core 2 Duo platform, Windows 10 1809, Xonar DX, tested with both UNi Xonar v1.71.1 and v1.81a and I only get 1 click.
                STX cards might behave differently, we would only know if someone else with a STX card would report back.

                Reply

                • Michael06 Feb 2019 @ 00:43

                  I used the offical 7.12.8.1793 driver. 2 clicks and worked perfectly, so no reason to update.

                  I tried the official Asus driver for Windows 10. Apart from not working (no sound at all), I got 3 clicks aswell here. So the driver changed the click behaviour somewhere. So it looks like all UniXonar drivers > 1.71 are adding an additonal click when changing relays.

                  Reply

  2. Moravid03 Feb 2019 @ 21:35

    After updating to 1809 my STX II on latest W10 drivers BSOD whenever I used the standalone apps to switch rate or gain, earlier version refused to install and system freezes.googling BSOD stop code “DRIVER IRQL NOT LESS….” cmudaxp.sys shows issues with cmedia controller so I resetted BIOS then disabled the integrated sound as well as AMD HDMI sound under device manager and restarted making sure integrated sound is once again disabled in BIOS. Happy to report standalone apps now work without issue!

    Reply

  3. David04 Feb 2019 @ 16:50

    These drivers somehow conflict with my Realtek wireless network device(s), i found a correlation between random connectivity problems and the ‘cmudaxp.sys’ driver, I am a developer myself and I know how hard it will be to convince you of this relation but I will try to do my best:
    – I’ve been having random loss of network (total drop of bandwidth/total loss, or heavy interference) while the wifi network remains connected, often in IE at those times it will say “INET_E_RESOURCE_NOT_FOUND”.
    – The problem happened more often with 1 of my 2 available wifi networks, so I mostly used the other (i considered more reliable) one. The ‘unreliable’ one is with a repeater.
    – Yesterday, the situation worsened as also my ‘reliable’ network started having these cuts. I decided to reset winsock and perform network resets, like I would usually try.
    I then rebooted and cleaned my temp files both with CCleaner and Wise Cleaner 365, the latter crashed my PC with a BSOD on cmudaxp.sys when it reached a certain cleaning stage. It clearly hit some critical driver temp files.
    My microphone’s hardware toggle button was switched on at this time.

    – I was done with it, so after a few more tries to fix my network (it would cut out every time in just minutes or less) I went to bed and ready to give it a go today.
    – Today, the same problem appeared with my internet connection. I decided to switch network, and when I clicked the “connect” button on another network, I got a BSOD on cmudaxp.sys.
    * Note: this is the most recent minidump I will attach

    The event of that BSOD happening in the very millisecond I tried switching to another network (the first one having loss of internet connectivity..), on the audio driver, made me confirm in my head Xonar drivers were related,
    to the months-long, random, internet problems I had encountered. I also feel that the rate of random connection cuts increased when I started using my microphone, as I have been playing a game requiring this for the past 2 days, I got it more often than normal.

    Ok, so with my internet hampering almost permanently (even with the mic button switched off, so no voice input.. didnt try disconnecting cable though) and my suspicion about the Xonar uni drivers interfering,
    and without success for hours since last night, I uninstalled the audio drivers (using Xonar uni uninstaller/cleaner) and suddenly, my network problems were gone.

    So, now, this also isn’t coincidence, after all these hours a simple uninstall of your driver fixed my network so it would stay connected indefinitely and not seconds to minutes.
    As I said, this solved the raised rate of ‘random’ connection problems I had encountered for months, now making my life almost impossible. I don’t expect the random (less oftenly occuring) drops to return, now that I uninstalled the sound driver, as they were equal in nature.

    The random stability issue has been pestering me for months, and now that I laid these links, I also seem to memorize it all started around the time I first installed Uni Xonar drivers.
    I started assuming something in my OS was messed up and that some day I’d need a re-install to make sure, because the routers behind both networks had a very solid DSL line and throughput even when it occured.

    Now, I feel the unlikely event of the sound card (when running these drivers) interfering with my network devices, is true (chipsets: Realtek 8812BU, 8188GU, RT3572 – tried multiple to solve it, even most recent one).
    I am delighted that I finally found the problem, I can miss these network interruptions like toothpain, but I want to report this issue so that you may investigate or fix it if confirmed.

    I uploaded my minidumps here:
    https://1drv.ms/u/s!AumAu7ACCRzIcF1khp713GsB8b0

    The BSODs may be a side effect of the root problem, but can help you narrow down where to look for specifically.

    Side notes (unlikely to have played a role):
    – I touched and may have adjusted the sound card a few days ago, around the onset of the more heavy problems (when I also increased my use of microphone as explained earlier), by reaching the mainboard battery underneath I had to bend it over a bit.
    – There has always been a slight current spanned over my computer’s case; you can feel it being under weak power with a finger. The source is unknown, it could be my PSU.

    The first is unlikely to play a role because I memorize increased network problems whenever I started to increase my mic usage in the past. But never such an increase as rendering my network so crippled like it did last night.
    The second is unlikely to play a role because I memorize the network problems started around the time I started using Uni Xonar drivers.

    I don’t think either have created a predisposition, but I just want to be 100% transparent so you can investigate it properly.
    Also to note that I am a very advanced user (working in IT but haven’t lost touch with the basics while at uni) so I am 100% certain that my OS is in top shape, I am not the type of user that will nuke their Windows.
    Unlike many others, I don’t need to re-install Windows every now and then because of slowing/nuking/dooming/infecting it.

    I just mean, that if a symptom of something (software) occurs on my PC, I can be sure it’s the fault of that software, and often tell support desks I cannot be Tier-1’d or helped with troubleshooting. I always turn out to be right that it’s not a problem on my side.

    I hope this detailed issue report helps. Interference of an sound card (due to drivers) with Wifi equipment sounds unlikely, but as you can see I got factors pointing in that direction. Also please note that I re-installed Uni Xonar drivers (after complete clean-ups) several times, for unrelated reasons in the months I ran it, and I always experienced the described network issues during that time.

    Reply

    • CarvedInside13 Feb 2019 @ 20:59

      First, I want to clarify some things. These are modded drivers and if the problem was indeed from the Xonar driver, I would not be able to fix it as I do not have the access to the source code. Another thing is that the problem is not specific to UNi Xonar drivers, if you would install ASUS original drivers with the same audio drivers(1816, 1818, 1823, etc.) as the UNi Xonar drivers you would have the same issue.

      Things you could try:
      1. Try different Xonar driver versions and install them with “Low DPC Latency” configuration. Try especially with v1.71.1. Do not run ASUS Audio Center to change the settings, use C-Media Panel or XonarSwitch instead.
      2. Try different Realtek wireless driver versions.
      3. Check if the Realtek wireless card shares the same IRQ with the Xonar card. If it does, you could change the interrupt mode to MSI mode for the Realtek wireless card with MSI Utility. Do not change the Xonar card to MSI mode as it will not work and Windows will crash at boot.

      There is the possibility that there are 2 problems going on. The BSOD problem or some of the BSOD being caused by something else. The BSOD could also be from:
      1. System memory errors, check with Memtest86+ or Windows Memory Diagnostics.
      2. The security suite you are using might interfere with the drivers or memory allocation, try running with it uninstalled.
      3. Xonar card has a hardware malfunction. If you can, try the Xonar card in another PC.

      Let me know if any of those helped.

      Reply

      • David20 Feb 2019 @ 07:09

        Oh man, thank you so much. Turns out that the Xonar DGX card shared the same IRQ value as the USB host controller in which I plug my Realtek wifi USB’s.
        One of my “Standard OpenHCD USB Host Controller” (PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00) entries. I had always gotten the feeling it was somehow connected to the USB itself.. sometimes also the “device disconnection” beep would sound when I got sudden network issues.

        Image of the ‘conflict’: https://i.imgur.com/tEkDiG2.png

        I will run some tests such as with altered IRQ using the method you gave me, and let know of the results.

        Note: the issues returned after my initial confidence in downgrading to the original Asus drivers. It’s not the fault of Uni modded drivers (you).. glad I seem to have figured it out now thanks to you!
        Any idea why they would share the same IRQ? (sound card and USB host controller.. wtf)

        Reply

        • CarvedInside21 Feb 2019 @ 19:12

          The USB controller may not be the one that’s being used by the Realtek Wireless. To check, plug the wireless card, go to Device Manager, View->”Devices by connection”, now you can expand that specific “Standard OpenHCD USB Host Controller” to see if the Realtek Wireless is connected to it.

          Since you are using a USB network card I don’t think you can change the card to MSI mode. But you could try changing the USB controller. If that does not work, try plugging the network card in different different USB ports.

          Since the “Standard OpenHCD USB Host Controller” is using the MS generic drivers, you should install for the drivers from the manufacturer.

          The IRQ ports are limited, so devices have to share the IRQs, normally this isn’t a problem but if more demanding devices end up sharing the same IRQ then that could turn into a problem.

          Reply

          • David09 Mar 2019 @ 21:31

            I actually discovered that setting IRQ to MSI mode didn’t (completely) solve the problem, MSI_util_v2 to do that also said that USB controller didn’t support MSI mode. So i assumed that these conflicts (giving me network trouble) were thanks to Asus for bad coding of their kernel sound drivers. I don’t understand why I have to be the victim of this.. you have a sound card and USB controllers, they should be able to function properly together. But shit happens.

            So now that I got rid of my WiFi connection, and started to use LAN cable to my router instead, it’s completely solved. No more random network fallouts and instability, No more BSODs (irql_not_less_or_equal) or actually extremely rare now, so I am fine and it was certainly the culprit.

            If i find time soon, ill roll back to using WiFi once more, to try checking out what you said, and trying to find a driver for OpenHCD. I will let you know in that case.. thanks.

            Update 1:
            OpenHCD drivers cannot be found on the web, and my motherboard (Sabertooth 990FX R2.0) page offers only Asmedia USB controller drivers. So it’s not available, I think everyone uses those W10 drivers for OpenHCD. I actually tried updating Asmedia USB to ones provided by a driver modding community, at an earlier stage in a bid to improve the problem, but to no avail. That was from https://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html so im now using ver from 2018 on Asmedia.

            Also i believe Asmedia is USB3.0 ports, the problems occured independently if I plugged Wifi USB’s into USB2.0 or USB3.0 ports. Although it seems the issues had a preference for certain ports.. or switching could make a crash & net loss streak recover.

            Reply

          • David11 Mar 2019 @ 02:54

            I also forgot to say that the problem seems to have been tied to a few more odd things:

            – Hardware switch on my standing desktop microphone: turning it off means higher chance of net loss or BSOD (that feeling i get, idk) but that’s no software switch or sound panel one.
            – Transmission of voice in certain application(s) like Discord, seems to induce it to become blurry and my network to get loss. Discord uses certain codecs for voice (Opus), idk.
            – Opening certain applications (mostly while another relevant soft is open that deals with microphone input) creates a risk of problems
            – Cleaning temp files (with cleaner application) has suddenly caused a bsod when it reached a certain folder, idk
            All bsod on cmudaxp.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL

            Everything is connected to eachother.

            Maybe this helps others with same issue to minimize the risk.
            After all, yes, it seems mostly tied to the amount of network load, (voice) transmissions, etc.

            Reply

            • David20 Aug 2019 @ 12:47

              Actually my posts above were really outdated, the issue came back hard after any of those moments.

              Now, i can provide more meaningful information (it can help whoever has the same in future);

              I found out that the problem can start (or get exacerbated) when you remove HsMgr.exe and HsMgr64.exe from Windows autostart or your PC (in C:\Windows\System and SYSWOW64 folders). They are “HookSupport Manager” processes that (thus) apparently are vital for the stability of Xonar drivers on your PC, and even though because Asus just coded the cmudaxp kernel driver badly you may (always) get BSOD on shutting down your PC, when you stop these HsMgr processes you can also start facing the NETWORK ISSUES like INET_E_RESOURCE_NOT_FOUND and connectivity drops.

              In my case, I started having it directly on my LAN after disabling them (and idk if matters, doing some config things like setting BASS profile in audio center equalizer), so it’s clearly not limited to interfering with USB wifi devices.

              The fact that I continued to (unavoidable) get BSOD’s occasionally on PC shutdown even after clean Windows 1903 install (but there, as long HsMgr processes are autostarted, no network issues) and the fact that these “Hook manager” processes, part of the official Xonar drivers as well, are apparently needed to ensure stability, says a lot about Asus and how bad they did things. I would never again buy a Xonar or Asus sound card, they clearly never dug into it or released an update, so their kernel driver keeps interfering with other hardware, crashing, bsod, and messing network stability of people. Basically, installing this sound card is an attack on your PC’s health. I will replace it soon..

              Please note that all issues in the whole topic are received with the official Asus Xonar driver as well.. maybe the “custom drivers” from UNi even reduced their frequency a little (thus is better than official when you’re affected by the described problems).

              Anyways, moral of the story is: NEVER remove HsMgr and HsMgr64.exe from Windows autorun or your PC.. i can imagine a lot of people that try to clean and speed up their PC made this mistake. Then, these Asus drivers will come crashing down hard, and things like I struggled with happen. If you have it and its removed, then fully uninstall the drivers and clean-install it, so the entries in autostart get restored.

              Entries arent simple to configure manually, here is how the correct configuration (default by installer) looks like:
              https://i.imgur.com/eUT5EgA.png

              I’m afraid you will have to never touch it at all, I mean even if your PC is either 32 or 64 bit, keep both processes in there.

              Reply

              • CarvedInside21 Aug 2019 @ 17:05

                Thank you for posting the update, might come handy to someone.

                As far I know, those HsMgr processes hook into specific applications, most prominently they would do this in order to provide EAX emulation when the GX option is enabled. I also found that they would hook into older versions of RMAA(Right Mark Audio Analyzer) in order to reduce or make it report a lower input latency. I have not seen this lower input latency in other applications I’ve tested like for example Audacity.

                I don’t know why you would have these problems if HsMgr processes would not be running. I can tell you that I am not running those processes since close to 10 years and I never had any problems and through all the various tests I ran I never really found a use except what I’ve written above. Also, there are a lot of people who use the UNi Xonar drivers in “Low DPC latency” or “C-Media Panel” install configuration (both disable HsMgr from starting) and, as far as I know, there isn’t one that reported having problems that where not present if with Normal install configuration or if they installed Asus original drivers with the same audio driver version. Maybe the problems you had are caused in conjunction with a specific application you have running or those Realtek wireless drivers. Now given your experience I will try to have another look into those HsMgr processes.

                Reply

  4. Alex06 Feb 2019 @ 14:53

    Hello, I have the Asus Xonar D2X and i’m trying to get Sound working on Windows 10 Pro 1803.
    It doesn’t matter what driver (Asus or UNI Xonar), or what GUI I use, I get only 2.0 sound (left speaker and right speaker).
    But let’s start from the beginning:
    The computer was running with this soundcard on WinXP for years without problems.
    Well, I wanted to change to SSD… so Win10 makes sense. For the soundcard there are even win10 drivers available from asus by now, but in beta state.
    So i installed that Asus Driver, did the 5.1 Setup (In the Asus Utility and in Win10 Sound settings) and everything was fine.
    When i click on a speaker, in speaker setup, i get a sound signal, from each of the 5.1 speakers.
    But when i start to play an audio file, Youtube or a simple Windows sound i get only 2.0 Sound (front left and front right).
    With the UNI Xonar driver i have exactly the same problem, I tested UNi Xonar 1816/1823 v1.80a r3 and UNi Xonar W10 1825 v1.81a r2 , tried all options and all GUI’s, always erasing the old Driver files.
    I also tried to setup as 7.1 System and excluded the ‘side speakers’ to make it 5.1 again, i read that somewhere as workarround, but didn’t solve the problem.

    I read on several sites that the D2X is working with this Driver on Win10 with 5.1 Speakers…
    I don’t know what to do now. I think i’ve tested all possible settings. But maybe someone can help me here 🙂

    Reply

    • CarvedInside08 Feb 2019 @ 02:14

      FYI the content in YouTube is 2.0 (stereo), there is no 5.1 audio content.
      Basically, you want the stereo content be played to 5.1 speakers, this is called stereo upmixing to 5.1.
      On Windows XP, the original Xonar drivers did have stereo upmix enabled by default. Check the FAQ Q&A 4 for how to enable stereo upmix on Windows 10.

      Reply

      • Alex09 Feb 2019 @ 16:16

        Thank you, the sound is now perfect. It’s a bit uncomfortable for me that the solution was so simple and so close. But i’m glad that it solved the problem now. Good work 🙂

        Reply

  5. Farewell07 Feb 2019 @ 00:09

    dont know if someone can help me with my problem but i post it anyways

    I use a Xonar HDAV 1.3 have it looped with my vga card via hdmi, then to my reciever then my TV
    now the problem is that when i turn my TV off for a while and then back on, it seems that the Xonar HDAV wont
    pickup the signal again and i get black screen

    what i did was check if my video card was the problem but when i connected directly to my VGA card there was signal again

    anyone have any ideas about what can cause it?

    Friendly Regards

    Reply

  6. Mauricio08 Feb 2019 @ 09:47

    Hi. I installed the 1823 – v1.80a with Driver enforcement mode, but now i’m in Test Mode even if I not installed in that way. When I try to /testsigning off it just don’t work, and I really need to stay without Test mode for Battleye anticheat and some stuff like that. What can I do?

    Thanks

    Reply

    • CarvedInside08 Feb 2019 @ 18:01

      Hi. Do you have the Test Mode watermark on desktop?
      Have you followed the instructions from here with running the “disable testmode.bat” file with “Run as administrator”? If that does not work, try removing the drivers that you installed with “Disable driver signature enforcement”. If the Test Mode is disabled after that, install drivers that have a valid signature for your card.
      Let me know how it goes.

      Reply

  7. Mintrel12 Feb 2019 @ 22:03

    Windows 10 1809 *clean install*, using UNi Xonar W10 1825 v1.81a r2.
    I got a BSOD when waking computer from sleep (after 1 hour of sleeping).
    0x000000d1 DRIVER_IRQL_NOT_LESS_OR_EQUAL cmudaxp.sys

    Note: It doesn’t always happen, but the same driver never gave me a BSOD when I was on windows 10 1803 in the same computer.
    Any suggestions to fix this?

    LE: I forgot to say that I’m using Windows 10 Pro x64 version build 1809

    Reply

  8. Scaffold13 Feb 2019 @ 20:17

    Hello! I’m using Win 10 1803 with Xonar Essense STX II and UNi Xonar W10 1825 v1.81a r2 installed. I cannot change to headphones from the speakers using the Xonar Audio Center – regardless of the setting it continues to sound through the speakers. Has anything like this been reported before?

    Reply

    • CarvedInside13 Feb 2019 @ 20:53

      Are you switching to front panel headphones or headphones (rear of the card). I suggest you try switching with XonarSwitch and see if it works.
      This might be an issue with 1.81a or with all “a” drivers. Before switching to 1.80b, you may want to try with 1.80a.
      With 1.80a drivers and STX II cards, for Asus Audio Center to work you need to download this patched version and copy paste it over “C:\Program Files\UNi Xonar Audio\Customapp\”.

      Let me know of the results.

      Reply

      • Scaffold13 Feb 2019 @ 20:59

        Thanks for the response! What is XonarSwitch? I somehow don’t know it.
        Regarding your question – yes, I’m switching to the rear panel headphones as I always used to do with my old STX.

        Just tried overwriting the file with your version and it still does not switch over to headphones.

        An Update. I figured out what is XonarSwitch, and installed it. But it reports the following: “A Xonar HDAV 1.3 has been detected, but the card model is currently not supported by XonarSwitch”.

        Reply

        • Scaffold13 Feb 2019 @ 21:49

          I just realized that you’re suggesting switching over to 1.80a or 1.80b? Well, I didn’t try this yet. Probably that’s why XonarSwitch isn’t working. I will try these versions, but a bit later.

          Reply

          • CarvedInside13 Feb 2019 @ 22:36

            For XonarSwitch, I was also interested if it worked with 1.81a drivers. When you have time try XonarSwitch and the patched ASUS Audio Center on v1.80a drivers.
            If switching to headphones still does not work, try with 1.80b drivers.
            Another thing to check, is your card detected as a STX II when you run the UNi Xonar installer?

            Reply

            • Scaffold16 Feb 2019 @ 11:33

              Curious enough, the card is detected as Xonar HDAV / HDAV Slim.
              When I tried to install 1.80a having manually switched over to STX II, I got a very heavy BSOD.
              After that I tried to instatll 1.80b also having manually switched over to STX II, I got a freeze after the card switch-on click.
              I disabled the network connection and retried installation of 1.80b, this time successfully. But the sound is still not switched over to headphones.
              You think it might be a good idea to try installing drivers for whatever it auto-detects?

              Reply

              • CarvedInside16 Feb 2019 @ 14:59

                Your cards EEPROM has been overwritten and as a result the card is detected as a HDAV. This is most likely why you can’t switch to headphones.
                To restore the cards original EEPROM you need follow the instructions from this page. After that install the drivers again and you could try with v1.81 again.

                Reply

                • Scaffold16 Feb 2019 @ 18:40

                  Thanks for the suggestion! Can’t try it right now, but will do in few days when I have time.

                  Reply

  9. TechnoRush28 Feb 2019 @ 18:27

    Is the issue with setting volume to 100% still prevalent? http://maxedtech.com/useful-tips-suggestions-known-issues-workarounds/

    And would you recommend 1825 or 1823 for Windows 10 1803 and 1809?

    Currently on Windows 10 1803 and 1825 drivers.

    Reply

    • CarvedInside01 Mar 2019 @ 00:06

      The dynamic volume issue is a Windows issue. I haven’t tested but I believe it affects even the latest version of Windows 10.

      If you don’t have any issues with 1825 drivers then you should keep them.

      Reply

  10. Mauricio01 Mar 2019 @ 13:32

    I’m getting cracking sounds, already disabled HD Nvidia audio. What can be the cause? I didn’t disabled the MB sound tho, maybe it’s something about that?

    EDIT: I disabled MB sound (realtek) from BIOS, uninstalled the drivers and rebooted PC and I have sound wtf! Why can i listen sound if the dispositive isn’t detected?

    Reply

    • CarvedInside03 Mar 2019 @ 22:35

      The sound playback will only work if the driver is installed. The audio driver was either reinstalled by Windows from driver backups or was not uninstalled.
      If you want to uninstall them completely you should check UNi Xonar Driver Cleaner.

      Are you using ASIO playback? If you are still having the cracking sounds maybe you should check the playback with the onboard card and see if you have the same problem.

      Reply

  11. Lucas02 Mar 2019 @ 19:11

    Windows 10 Professional x64: if i restart my pc the microphone reset to 100% volume…any fix out there???

    Reply

    • CarvedInside03 Mar 2019 @ 22:43

      Tell me your Windows version and build number. If you have version 1809, did this problem started recently or did you had this prior to October 2018?
      Which audio panel are you using (Asus, C-media or XonarSwitch)?

      Reply

      • Lucas04 Mar 2019 @ 15:17

        hey thank you for your answer.

        build 1809
        exactly: 180914-1434

        i use the UNi Xonar 1816/1823 v1.80a r3 and the xonar switch 0.9.661 beta.

        Reply

        • CarvedInside05 Mar 2019 @ 00:52

          Did this problem started recently or did you had this prior to October 2018 (or when the update to version 1809 was applied)?

          Reply

          • Lucas05 Mar 2019 @ 01:23

            the problem started recently after the update from 1803 to 1809

            Reply

            • CarvedInside07 Mar 2019 @ 23:52

              I have investigated this on my Windows 10 1809 and this does not happen to me. I think the issue could be from:
              1. XonarSwitch.
              1a. You’ve set up a profile which sets microphone to 100% and this profile is set to autoload at startup. To check this right click on XonarSwitch tray-> Profiles -> “Default Profile…”->Startup-> Audio -> When Xonarswitch is started-> Load this profile.
              1b. You manually change between profiles and one profile has microphone set to 100%.

              2. Some other audio application that starts at Windows startup and sets the microphone to 100%.

              3. Your system is affected by Windows 10 1809 bug that manifests under certain conditions.

              Reply

              • Lucas08 Mar 2019 @ 16:11

                thank you very much for youre time my friend:)

                with your infos i set my profiles with my mic volume settings. because i switch between two profiles.

                again, thanks you a lot!

                Reply

  12. Juli04 Mar 2019 @ 15:39

    tried installing the new windows update and while restarting for the update, i got a BSOD: https://paste.pics/619b25ae93e05c861d775e2a3d1aba6d

    I use W10 1825 driver.

    Would be nice if u could check this out!

    Reply

  13. Kalimoff05 Mar 2019 @ 06:33

    If your have freezes in Metro Exodus. Set sample rate to 44.1 KHZ.
    I have s*x all week, with it )))

    Reply

  14. Junni07 Mar 2019 @ 13:33

    Hi!

    I just installed my Xonar Essence STX II yesterday. The sound worked just fine for a couple of hours until the problems started. I have my headset plugged in to the soundcard via the 6,5mm.

    I have two problems here for now:

    1. I can’t hear others nor use the mic in apps like Discord (I have allowed the microphone to be used in the Windows settings and looked trough Discord settings)
    2. I have random crashes (BSOD) that I think must be related to the new soundcard since they didnt occur before yesterday.

    I have the newest ASUS drivers. But those are from 2015 soooo… What should I do? Any help?

    Thanks!

    Reply

    • Junni07 Mar 2019 @ 22:18

      Edit!

      Seems like I got rid of the BSOD crashes. Still can’t make the mic work in the headset though.

      Reply

    • CarvedInside08 Mar 2019 @ 00:16

      How did you solve the BSOD crashes?

      Does your microphone work with the onboard card?
      On the Xonar STX II card where have you connected the microphone, front panel or back of the card? Try the other way as it might be problem with the port. If you connect it to the front panel, you need to enable it the audio panel. For Asus Audio Center go to Mixer->Recording-> press the Tool button close to Mic label-> check Front Panel Microphone.

      Reply

      • Junni08 Mar 2019 @ 00:33

        Hello!

        I uninstalled all the other sound devices and their drivers. Then I set all STX II settings to default for now and haven’t had a single crash since. Also disabled the motherboard HD audio device (Realtek) from BIOS.

        I have a Astro A40 headset which has only one 3.5mm connector. I attach it to the 6.5mm adapter and then put it in the ‘Headphone’ slot in the soundcard. Asus manual says this is the slot where you should put it for headsets… So yes I have it connected to back panel. I don’t even have front panel audio slots. I don’t have separate cables for sound + mic. Just one 3.5mm auxiliary cable.

        Reply

        • Junni08 Mar 2019 @ 11:35

          Edit 2!

          Hi again!

          Now I feel like a complete moron! So my Astros have been connected to PC with the MixAmp before. Now that I want to connect it straightly in to the soundcard I’d need a cable for mic + sound…? Right?

          https://www.astrogaming.com/accessories/cables-and-adapters/PC-Splitter-Cable.html

          Guess I need this splitter cable then? And btw I DO have a place for mic + sound on my front panel. Ugh I’m so embarassed!

          Reply

          • CarvedInside09 Mar 2019 @ 06:08

            Yeah, you need to split the signal. The STX card has separate connections for speakers and microphone.

            Reply

            • Junni10 Mar 2019 @ 11:01

              Hello!

              Update here! So I got rid of all the problems except that I can’t make the audio work with chat applications like Discord when changing ‘Audio Channel’. For example, I can hear others only if I make it put the sound out in ‘2 channel’ -mode. But it recommends to play games with 8 channels (7.1). If I put ‘8 channel’ mode on, I can play games but my chat mates get muted instantly and I haven’t found a way to enable their voice in 8 channel mode yet. In the other hand if I use 2 channel mode to play games and hear my friends, my game sounds suffer greatly…

              Is there any way to make it work? Thanks in advance!

              Reply

              • Case11 Mar 2019 @ 03:40

                Since you seem to be using headphones…do you have virtual surround turned on when you’re set to 8 channel audio? Because if you don’t, you will only be hearing the front left and front right channels in your headset, which might also explain why you don’t hear the voicechat when set to 7.1, since I guess Discord might be placing the audio into different channels (center, possibly?) in 7.1 mode…

                Reply

                • Junni11 Mar 2019 @ 18:45

                  Hi!

                  Im not sure. Where can I check if I have it on or off? So many audio options in the software, in windows etc…

                  Reply

                  • Case11 Mar 2019 @ 19:03

                    In your sound card’s control panel. I have no idea how it looks on your card or even which one you are using. Look for Dolby Headphone or virtual headphone or something like that.

                    Reply

                    • Junni11 Mar 2019 @ 19:53

                      Hi!

                      Oh yeah. I’ve tried turning it on and off before. Doesn’t change anything for me, sadly. Any other ideas…?

                    • Junni11 Mar 2019 @ 23:00

                      Update!

                      Okay now I got the channel thing to work but my friends say my voice sounds super weird when talking through the soundcard. They say it sounds like im talking inside a bottle or something and my volume is low. I have the mic boost turned on since they can’t hear me at all if I have it turned off. They say there are also random crackles in my voice/sound.

                      If I use my mic through MixAmp system or in Playstation 4 or in any else layout they say my mic sounds normal. So it shouldn’t be the mics problem here for now.

                      Any ideas how to fix this? Thank you guys in advance!

                    • Junni11 Mar 2019 @ 23:42

                      Update!

                      Tried connecting the 3,5mm auxiliary to different spots in my PC to try if my mic voice would sound any better. Front panel and motherboard back panel. Couldn’t make the mic work at all.

                      But when I tried connecting my headset through the green labeled 3,5mm headphone thingy in front and back panel, I could hear others.

                      I’ve really got zero ideas with this… Any help or ideas would be totally welcome! I know I might be an idiot here but I’m desperate for help with this since I really gotta RMA this if I can’t make it work. I think I’m so close on figuring this whole thing out and make it work that I wouldn’t like to give up. But I’m no tech expert with these so I’m super grateful with the help I’ve gotten so far from this site!

  15. Mark19 Mar 2019 @ 21:17

    Have there been any out of sync audio issues with Xonar DS? What’s the latest driver update for Xonar DS with Windows 7 64 Bit?

    Reply

AdminAuthorFeaturedBuried

Leave a Comment

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.

Close