1. Ihy17 Oct 2017 @ 17:58

    I've been struggling with those crazy loud screeches with my Xonar Essence ST every single week for the past 2 years since upgrading to windows 10 in 2015, but I can safely now say that after upgrading my power supply (from Super Flower Golden King 550W Platinum to Corsair RM750x) has fixed the issue for me. It's now been 4 months without a single screech and that was the only part I changed on my system.


    • CarvedInside18 Oct 2017 @ 22:23

      While it's possible that the PSU had something to do with the loud screech issues, I am thinking it's more likely that a Windows update or browser update (if you had them in youtube) fixed the issue. Here is another report stating that the loud screech issues were fixed recently. Thank you for sharing the information.


  2. Paul Rossi18 Oct 2017 @ 03:43

    On the Windows 10 1709 settings reset issue I can tell you that the sound setting reset is not limited to just c-media chip cards. My realtek card is doing it too. fyi


    • CarvedInside18 Oct 2017 @ 22:16

      I thought it would be so. Thanks for the information.


    • Paul Rossi02 Nov 2017 @ 16:02

      I have been working with Microsoft 3rd tier support about this sound setting reset issue.
      They took all the logs and information remotely and were able to see and duplicate the problem on my PC. He said expect to get back to me on Sunday with more info or a solution(I hope). I will report back.


  3. Spamhead21 Oct 2017 @ 05:54

    Just wanted to report my experience: My Xonar DX on the new Windows 10 Fall Creators Update is working great with the "UNi Xonar 1816/1823 v1.80a r3" Low DPC drivers. Haven't noticed any issues so far. No settings being reset on my end like reported.

    Thank you CarvedInside!


    • CarvedInside21 Oct 2017 @ 07:34

      It may not happen on every restart but from time to time. Or maybe the issue was fixed in the meantime.
      Thank you for the feedback so far.


  4. smagjus21 Oct 2017 @ 10:58

    I have major problems with the UNi Xonar W10 1825 v1.81a r2 release on Windows 10 x64 Edu Fall Creators Update. Completely fresh install.

    I have a Xonar DGX and installed the C-Media Panel for a change. Front panel audio did not work so I tried to uninstall the driver. But every time I try I get an irql_not_less_or_equal BSOD. And every time I try to install using the other options (low DPC and such) I get the same BSOD.

    How should I proceed from here?


    • CarvedInside21 Oct 2017 @ 11:39

      Unfortunately front panel does not work in C-Media Panel.
      I think you missed the instructions on how to uninstall v1.81, they are written in v1.81 release notes and on the first page of the uninstaller. You will need to play an audio file before proceeding with the uninstall process. Restart system after the uninstall process is done.
      If you want to keep v1.81 but switch to Asus Audio Center you should overwrite(reinstall) v1.81 drivers again while playing some audio file, and then restart.


  5. Crim22 Oct 2017 @ 04:49

    I just built a new gaming PC and it won't shut down, I think it's because of the ASUS Xonar Xense. I get an error PCH Initialization Before Microcode Loading. When I shut down my PC from Windows, the OS logs out, and screens go black, like Windows is closed, but my fans, lights, PC etc.. all remain on.. I have to hold the power button. I thought it was my motherboard, so I exchanged and bought a different brand and model board.. but the problem persisted.. I thought it was something else, so I exchanged the CPU, RAM, GPU, and PSU. Leaving the only thing the same being my Xonar Xense card. But the problem still existed. I took the Xonar out, and now the problem is gone.. I was wondering if this is a driver issue, should I revert back to an older version of the driver? Or do you think it's a hardware issue as in my card finally going bad after 6.5 years? BTW, thank you for supporting the Xense for so long.


    • CarvedInside23 Oct 2017 @ 16:44

      I think it's unlikely that this is a driver issue. You could try installing any driver below 1.81 and disable the card in device manager before shut down and see if your system will shutdown properly or not.
      Maybe it has to do with a compatibility issue between your motherboard and the Xonar card. Which motherboard do you have? Ryzen motherboards seem to have all sorts of issues.
      To know if it's the card you would need to test if your Xonar Xense card behave this way with your old PC or a similar PC?

      I'm not sure if you are familiar with Standby (S3). It's a very practical way to keep your system turned off instead of completely shutting it off and this way you would avoid these shut down issues as much as possible. You can read more about Standby S3 in FAQ 26.1


      • Crim23 Oct 2017 @ 17:03

        Thanks for the reply. I will test some more with older driver package. Currently running 7700k on ASrock z270 fatal1ty gaming k6. I had it in a pcie bridge slot previously which is where I had it on my maximus vi formula with my 4770k which had no issues. I put it in the pcie under my GPU now and havent had an issue. This problem happened with my 1st mobo that I exchanged to, which was an ASUS maximus ix code.


  6. resync500022 Oct 2017 @ 16:09

    does the UNi Xonar W10 1825 v1.81a r2 work with w10 1709? (i got an stx2)

    or should i wait to patch my windows?


  7. Chris Polhill24 Oct 2017 @ 18:00

    Hello folks,
    I have a windows 10 4gig i7and my soundcard is an envy 32bit. I don't do much in the way of fiddling or tweaking, I just play movies and music via my jriver media centre.
    I have been given a brand new boxed Xonar D2X and having read up a bit about driver issues with win 10, I'm not sure if I want to use it, and if I do, should I use the Asus beta driver or the Uni driver?
    Any advice or help much appreciated.


  8. Nisse24 Oct 2017 @ 22:40

    So I had a very weird thing happen today with my Xonar DX.Today when I booted my machine like any other day, I had high volume in my left ear and very low in my right. At first I thought my headphones where broken, so I connected them to my phone and there they seemed to work fine. So I restarted my pc instead, it didn't fix it, instead the channels got flipped so that the right speaker became high and the left low. Rebooted again and same issue was there. So I tried reinstalling the driver I have been using the last 3 months without problem, v1.71 r2 (Newer versions gave me BSOD, I'm running Windows 10 Creators update (not fall yet)) this didn't help either. So I plugged my headphones into the built in sound card on the motherboard for now which works fine. Any ideas?


    • CarvedInside25 Oct 2017 @ 01:29

      Try switching between rear and front panel headphones a couple of times and see if the issue is still there.
      If you are using the front panel connection also check the front panel cable that goes in the card.
      Check if both rear and front panel have the same issue.
      There is a strong possibility that your card might be defective.


  9. Patrick26 Oct 2017 @ 13:49

    I am using windows 10 creator edition. For some reason the loud clicky noise glitch when changing song resolved each time I have visited this page.


    • CarvedInside26 Oct 2017 @ 18:41

      I don't understand what your are saying. Please clarify.


      • Patrick27 Oct 2017 @ 15:30

        I have the Xonar STX 2 running the unixonar driver 1.81a. When changing song from the play list under Foobar, there is a sharp brief click. I have discovered that this clicky noise had resolved when I opened this webpage in my Firefox. After a few restart, the same glitch resurfaced. I have tried to go into other webpages including youtube as a test but the glitch remained. However, when I entered this website, the clitchy noise resolved. This is weird.


        • CarvedInside27 Oct 2017 @ 19:17

          Weird indeed. I have done nothing to the website that would offer such functionality.
          The clicky noise comes from the speakers/headphones or from inside your computer, presumably the sound card?
          You may want to try previous drivers and see if any of those don't have the issue.
          Let me know if you notice anything else or have any new information.


  10. Paul26 Oct 2017 @ 14:56

    I have had my pc freezing with a loud buzzing sound in my headphone/speaker whenever I was playing games. This completely locks out the computer, the system does not respond to any mouse movement or key presses. This happens randomly and it is possible that it does not occur for several days and after that it appears again. And the only way to get out of the freeze is to hard reset the computer. I am using a Xonar DGX, having speakers connected to the speakers output and headphones using the S/PDIF port. think it has something to do with conflicts between the two playback devices (speakers and S/PDIF passthrough device). It seems that the freezing and loud buzzing stopped when I manually disabled the speaker playback device and only use the S/PDIF passthrough device whenever I was gaming and enable it back on afterwards when done with gaming. I am also not sure which driver package I was using, but I assume it was UNi Xonar 1816/1823 v1.80a r3 or UNi Xonar W10 1825 v1.81a r2. Anyway, I decided to test another driver, and installed the UNi Xonar 1816/1821 v1.71 drivers. So far, I have not had a single crash and have not disabled any of the playback devices while I am gaming. I am not sure if this is luck or this driver has really fixed the problem. Maybe you might have an idea what is going on here? Hopefully this will get fixed if there is a new release ever coming out 🙂


    • CarvedInside26 Oct 2017 @ 18:48

      I don't know about this issue and why it happens. It could or could not be a Xonar driver issue. After some time you can let us know if v1.71 fixed the issue for certain or not. If the issue will still happen I recommend that you disable the Xonar card and use the onboard card and see if you the issue happens with the onboard card as well.


  11. Seth03 Nov 2017 @ 02:42

    Hi, I recall reading on one of the threads here that I should set the bitdepth from whatever source I'm using to 24 bit for my Essence STX - is this correct? According to https://yabb.jriver.com/interact/index.php?topic=68703.0 it should be set to 32 bit (not 24 or 24 padded to 32). I thought you might have a more authoritative answer. I have my card going to a set of Adam A7X monitors FWIW. Now time to do some speakercompensation testing... Thanks.


    • CarvedInside04 Nov 2017 @ 03:15

      Hi. Definitely 24 bit-depth is the best setting for ASIO playback on Xonar cards. I've ran some tests with RMAA and they show that 24 bit-depth is the best setting, while the 32 bit-depth ASIO behaves like 16 bit-depth. Here you have the tests with the playback file being 16bit. For 24bit playback file the results show no improvement for 32 bit-depth ASIO compared to 24 bit-depth.
      This probably has to do with the fact that the Xonar cards DAC maximum bit-depth is 24 bit. Cards with 32 bit-depth DACs could perform better but only for 24bit audio files.


      • Seth07 Nov 2017 @ 00:59

        Thanks. I feel like I can hear the difference between different output formats and 24 vs 32 bit depth but I realize it's highly unlikely.


        • Seth09 Nov 2017 @ 21:42

          I've done some sighted testing of the various output modes, asio4all seems to sound a bit different (with the caveat that it may all be in my head).


          • Seth29 Nov 2017 @ 06:28

            As an update, with my active speaker setup, I've found I need to feed a very 'hot' signal to my speakers (playback speaker setting in the Asus control panel between 94-100 volume levels). I've been using WASAPI instead of the built-in ASIO drivers (have had too much choppy playback with ASIO and directsound). I tried using Peace API with Directsound for playback with the same speaker volume levels to be sure that there's no digital clipping - none observed even with loud volume levels! I'm not sure where this orthodoxy about setting the volume @ 76 in the speaker volume levels started but I think you can safely push it louder than that.


  12. William08 Nov 2017 @ 02:53

    The latest 1825 works great on falls creators update for me, but i just noticed it starts lowering the sound quality from 24bit 192000hz to 16bit for no reason. Its at random.
    All other sound sources are disabled/uninstalled and the motherboard soundcard is turned off in bios.

    Gonna reinstall now and see if it works.
    Thx for the great drivers you guys are providing, cheers!


    • CarvedInside08 Nov 2017 @ 20:03

      How do you know it lowers the bit depth to 16bit? With previous Windows 10 build you didn't have this problem?
      Beside reinstalling the v1.81 drivers I suggest you try previous drivers.


      • William12 Nov 2017 @ 11:32

        On random or after a restart it either has dropped to 16bit in playback devices or changed to two channel from eight in the xonar hdav center.
        If you enable 24bit in playback devices again it changes to 2 channel in the xonar hdav center so you have to change to 8 there again and its fine.

        I never had this problem before the falls creators update and can now confirm its the same with all your HDAV supported drivers for win 10.
        Its not the whole world to change back now and again, just trying to provide some feedback. The issue seem to lie in windows for the moment.


  13. Bryce08 Nov 2017 @ 10:07

    Hi there,
    Using W10-1825-v1.81a-r2 on a completely fresh Windows 10 install, it switches my Audio Channel from 8 Channels to 2 as soon as I right click the windows speaker icon in the system tray. 100% reproducible every time I reboot my computer.

    Thanks for any input you might have!


    • CarvedInside08 Nov 2017 @ 20:10

      Hi. Your Windows 10 is Fall Creators (1709) build or some other build? This is probably a Windows issue but I suggest you try installing the previous UNI Xonar drivers.


      • Bryce14 Nov 2017 @ 01:55

        1709, yep. I tried v1.81a r2 and 1816/1823 v1.80a r3 with the same issue. Not a big deal as i don't click the speaker icon often, but if you had a quick fix I'm all ears.

        Thanks again!


        • Steph14 Nov 2017 @ 21:23

          I just have the same issue with the right click today. It reset to default values (stereo 16bits 48khz). windows 10 pro v1709 and drivers UNi Xonar W10 1825 v1.81a r2.
          I had also the random reset since the spring creator update with the asus driver v8.1.8.1823
          The card is an essence stx.


  14. B-CHe09 Nov 2017 @ 21:39

    The asus driver causes a high khz tone when playing sound, I swapped to this driver and it gets rid of it. Ever since the recent windows fall creator update the high khz tone is back.

    windows 10 1709
    Asus dgx sound card


    • Kizaki20 Nov 2017 @ 05:03

      I am having the same problem. It's been happening randomly while watching YouTube videos.


      • Dee15 Jan 2018 @ 20:07

        +1 the same.
        shit bricks on this moment


        • Jeff30 Mar 2018 @ 00:37

          I'm glad to find out this is an issue with the Asus cards. I can add that this is rare with Asus Xonar STX Essense on W10 1709. I have only ever had this happen with YouTube as well.

          So incredibly loud, and I've "debugged" this issue by unplugging the cable from my headphones. The system appears to be generating no sound at all, but plugging them back in you can hear the noise. It is easily fixable to stopping and starting the video, but it still makes me shit brick as Dee would say 🙂


  15. Roman13 Nov 2017 @ 21:20

    Guys, I always hear some sort of "cave" or "echo" effect while using 7.1 Virtual option in C-Media pannel.
    Is it a driver \ headphones \ audiocard issue?
    Can this "effect" be completely removed somehow? I really want to enjoy virtual 7.1 but this cave\echo effect is killing me.
    I'm mostly playing Word of Warcraft.

    My spec:
    Windows 10, Xonar DX with Sennheiser HD518
    UNi Xonar 1816/1823 v1.80a r3 (Low DPC latency version) with 7.1 virtual speaker shifter enhanced profile v1.0



    • Roman17 Nov 2017 @ 09:35

      Update: I've tried Razer Surround software, and it sounds much better than 7.1 Virtualization from the driver.
      When I use Razer Surround software - there is no echo or cave effect.
      Could it be an issue with driver build in 7.1 virtualization logic?
      I just want to understand if I should spend more time to solve driver 7.1 virtualization issue or just switch to another softwsre.


      • Case17 Nov 2017 @ 18:06

        I'm not sure if it's the "cave effect" you're talking about, but the Dolby Headphone technology does include a slight reverb which some people describe in a similar way. If it is what you're talking about, then that's indeed part of the technology, it simulates the room you're in and helps the sound to be more natural (you might disagree with that) and less sterile. There are three listening rooms included, so try switching to a different one - each one includes the reverb, but each one is different. Personally, I think it's just something you get used to and that is worth getting used to.

        And yeah, Razer Surround does not include this effect (or not to this extent), but it has other issues, including (but not limited to) a much worse sound directionality, especially when it comes to front/back sound cues. YMMV.



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.