sprite

8704 Comments

  1. HSM0631 May 2020 @ 22:14

    ASUS ROG MAXIMUS XII HERO (Z490)+ ASUS Essence STX II, install driver (STXII 11.5 v1.80b r3) BSOD, Error: DRIVER_VERFIER_DMA_VIOLATION

    Reply

    • CarvedInside01 Jun 2020 @ 01:40

      I presume you have Windows 10, but which version? Did this start as soon as you've upgraded to the Z490 motherboard? Did you migrated the OS from the previous system or did a new install?

      Reply

      • HSM0601 Jun 2020 @ 07:05

        Windows 10 1909 & 2004 Have tried ,That's right, there was a problem after upgrading to z490 , Are new installations , The situation is the same bsod .

        Reply

        • CarvedInside01 Jun 2020 @ 15:34

          Have you tried installing the drivers with Windows in safe mode? What about manually installing the driver according to Possible Solution 1 this page? You should also try a different driver version like v1.80a, see if that works by any chance.

          Reply

          • HSM0601 Jun 2020 @ 16:52

            I tried the installation again after trying BSOD.The driver has a Code 52 driver error.
            I try to enter Disable driver signing mode. The result is bsod before loading the desktop, BSOD : DRIVER_VERFIER_DMA_VIOLATION

            I just tried to install in safe mode. Restart the device, Code52 appears, I try to enter the "disable driver signature" mode, still BSOD DRIVER_VERIFIER_DMA_VIOLATION.

            I tried to install the original ASUS driver, and it was still BSOD: DRIVER_VERIFIER_DMA_VIOLATION.
            I have feedback related questions to ASUS official customer service, but I don't think there will be any response...

            Reply

            • CarvedInside02 Jun 2020 @ 12:19

              I think the BSOD issue you have is because of the motherboard. ASUS might be able to fix it with BIOS update but whether they care or not to investigate and fix it remains to be seen.

              There are some other things you could try, maybe get it working but if I am to spend more of my time on this I need to receive a money compensation from you. If you are interested let me know. If you've previously sent me a donation, send me an e-mail from that e-mail address you used for payment.

              Reply

    • Kimthesax10 Jun 2020 @ 19:37

      Found a possible workaround for Asus Essence STX 2 and AM4 reboot/BSOD. For those who are f***** with BSOD. For my X570 it works if I pre install http://www.asio4all.org/ before you install the Essence driver it seems to work well for me. For now stable!!!

      Reply

  2. BF08 Jun 2020 @ 07:58

    Hey there! Got a Xonar DX, but since upgrading to Win10 2004 the drivers seem to have been replaced with Microsoft Audio Endpoint drivers 10.0.19041.1. When run the installer for Xonar it installs fine, but nothing changes when looking at the devices in device manager. If I select the INF manually, it says it doesn't contain compatible software driver for your device. Anyone having this issue? Tried 1.80 and 1.81.

    Reply

    • CarvedInside08 Jun 2020 @ 14:38

      1. In Device Manager, does the card show up as ASUS Xonar DX or as Microsoft Audio Endpoint?
      2. In Device Manager, double click on ASUS Xonar DX or Microsoft Audio Endpoint device, go to Details tab, select "Hardware Ids" in the Propriety field, copy the top hardware id and provide it here.
      3. Is the card properly detected as a Xonar DX in the UNi Xonar installer?
      4. So just prior to upgrading to Windows 10 version 2004 the card worked properly?
      5. Just to clarify, this was an upgrade for a prior Windows 10 version and not a new installation?

      Reply

      • BF11 Jun 2020 @ 00:48

        Thanks for your response. The card does show up as ASUS Xonar DX. I guess I was just thrown off by the fact that in the driver section of the properties it lists the Microsoft Audio Endpoint rather than saying something like ASUS or UNi Xonar etc. I was under the impression that the UNi Xonar driver version reflected there in the past. It was definitely weird because I had some audio issues following the upgrade - not a new installation - went from 1909 to 2004. I kept having cracking sounds and random other stuff happening that I didn't experience before. However, after running the driver cleaner and reinstalling and reapplying my settings it does now seem to work properly. Sorry for the rushed call for help!

        Reply

    • ravdo10 Jun 2020 @ 23:01

      I have Xonar DX and it works fine on Win10 2004. Didn't need to re-install the driver after updated from 1903 to 2004. I'm using v1.71.1, never tried any other version.

      Reply

  3. Shion14 Jun 2020 @ 10:25

    Hello! I am running into a rather annoying issue with my Xonar Essence STX II. I tried finding information on it, but was only able to find one article that describes this issue: https://www.stereophile.com/content/asus-xonar-essence-ststx-soundcards-follow-september-2010
    Basically, when outputting through coax (selected through the tick-box in the asus driver panel), whenever audio playback is interrupted when the signal is not 0, there will be a persistent DC offset at the value the last played audio sample was at volume wise and channel-independent, and it persists until another audio source is started (aka, simple pausing and resuming playback of music, skipping through the playback bar, closing a browser while a video is playing and starting playback of music or a game etc., you get what I mean, it is happening ALL the time) and will cause potentially heavy popping sounds depending on where playback was interrupted. Despite the article saying that the problem is not pathological and does not seem to translate to the analog outputs of whatever external DACs they were using, it is very well an issue on my end. I am using a Schiit Modi Multibit and a Magni 3+ as my DAC/AMP combo, OS is Windows 10.
    My question is, is this something that can even be fixed by using a different driver like the UNi Xonar drivers? Is this a known issue or has it been addressed by the UNi drivers already? Is there anything I can do to prevent this aside from not using the coax output or using a different DAC (which I do not have)?
    I appreciate any input!

    Reply

  4. Sprite19 Jun 2020 @ 18:52

    Hey there!

    I just installed the STX II in my Ryzen System. Disabled onboard Sound,Uninstalled Nvidia Audio Drivers. Installation went fine but I have some serious Audio Issues.
    I'm using a Beyerdynamic DT 770 Pro 250 Ohm. If I set the Gain to 64-300 Ohms i get cracking which sounds like "overdrive". Like upping the Volume to max and all the sounds get distorted. I hope you know what i mean.
    But if i set the Gain to 16 Ohms that Problem is gone. But then I'm getting a High pitched Sound all the time like coil whine.
    Any Idea whats causing that? I'm almost at the point of sending it back and using my Onboard Sound.

    Reply

    • CarvedInside22 Jun 2020 @ 04:40

      Hi. If I am to get involved and help you figure things out I ask that you make a donation of $7 or more. If you wish to do so, donate following this link and mention in the donation notes the e-mail used here followed by "for STX II and Ryzen with headphones gain distortion".
      Then write a comment reply with your system (motherboard, CPU, video card, Windows version) and which Xonar drivers have you tried.

      Reply

  5. Michael20 Jun 2020 @ 10:25

    Hi,

    Since the 2004 install these have not worked for me. Everything was fine on 1806. I did an in-place upgrade to 2004 and things seemed to function OK. I got some new RAM and installed and started encountering errors in games, new Edge trying to play YouTube would crash even when not using headphones through my STX II, and even had some completely random BSODs seemingly coming from either NVidia or wdf01000.sys. After scrutinizing the hell my new RAM, the system was generally unreliable so I formatted. Upon a fresh install, this time 2004, the system was fine up until I tried to install these drivers. The system would quickly become extremely slow and eventually lock up. Forcing a reboot wouldn't even work. Each time I had to rely on Windows to kick me to the advanced options screen, and I had restore back to a restore point.

    I tried versions v1.81a r2, v1.80a r3, v1.75a r3, and v1.71.1. I'm willing to be a limited guinea pig of sorts so let me know if you want any particular logs. I would be willing to send them to an email but don't want to make anything available here in a thread.

    Reply

    • CarvedInside22 Jun 2020 @ 04:31

      Hi.
      1. You mistyped or misremembered the previous Windows version where it worked fine. If you can clarify which version was it.
      2. Have you tested your new memory with Windows Memory test or with some other memory testing program?
      3. What system do you have (motherboard, CPU and video card)?
      4. Have you tried installing the UNi Xonar drivers with "Low DPC Latency" configuration? What about with "Normal" configuration?

      BTW Thank you for the donation. If you wouldn't have done so, I would be asking that you do, because I'm increasingly tired of offering my services completely for free.

      Reply

      • Michael24 Jun 2020 @ 16:37

        1. Correct. That should have been 1809.
        2. I used the Windows Memory Diagnostic utility on basic first then the enhanced/extended configuration.
        3. I have a Taichi X370 mobo, Ryzen 2700X CPU, and an RTX 2070 GPU. I understand the official support for X370 isn't there but like I said it was working great before. I hope Microsoft didn't kill whatever method you have of giving broader support.
        4. No, I didn't as the DPC tool I used reported ready for real-time apps so I didn't see a pressing need for it. I will try that. I tried normal install and the C-Media version.

        As for the donation, for sure. I'm more about the annoyance of ads than not paying for software I use, but I get they're a reality and more often a relenting than something webmasters actually want on their sites. Best of luck.

        LE: I used the DSP DPC option with the v1.80b r3 version since it comes with a signed driver. Works great, thank you! Question though: the other media controlling app let me change the gain group since I have high impedance headphones. I don't see a similar option in the DSP DPC install with C-Media. Is there a way I can change this option? The sound coming through is a bit muted so I have to turn it up more than usual.

        Reply

        • CarvedInside25 Jun 2020 @ 00:43

          Hmm... The thing is, "C-Media Panel" configuration that you've previously tried should have behaved the same as "Low DPC Latency" configuration in this regard as they both lack HsMgr(GX) processes which could cause some conflicts with other software. Let's see if it continues to work or something else is or was going on.

          Regarding the compatibility between your ASRock Taichi X370 motherboard and the STX II card, did you had to do anything to make it work initially, like changing PCIe Gen speed or the PCIe slot? In which PCIe slot the STX II is plugged? Regarding the issues you had, have you updated the motherboard BIOS when you've upgraded the RAM and the issues started?

          For setting headphones gain, either launch ASUS Audio Center and set it there or what I would recommend is to use XonarSwitch.

          Reply

          • Michael25 Jun 2020 @ 01:33

            The only oddity I noticed on my initial install was that the installer didn't like that it was running in a Hyper-V environment. Windows automatically creates one when you use things like the Virtual Machine Platform or Application Guard. I had to use bcedit to force disable it, do the install with driver signature checking disabled, and then I could reboot and turn it back on and everything was normal. The only intermittent oddity from there out was that sometimes my headphones would squelch at max volume (really f-ing loud, btw) and my machine would lock up. It happened maybe a couple times and didn't seem to follow a pattern.

            I flashed my BIOS to latest several months ago so there hasn't been a correlation between new RAM or whatnot. Almost as a rule I don't do major upgrades in tandem. Do you think it'd be worth while to try the normal install with the signed driver?

            Reply

            • CarvedInside25 Jun 2020 @ 21:36

              In which PCIe slot the STX II is plugged?

              For now I would keep the drivers with "Low DPC Latency" configuration, see how it goes for a week or so, then you could try the "Normal" configuration again.
              Because you mention you had that loud noise and system lock issues, it means it was not exactly fine before. These issues might have the same cause, whether it's because of running in the Hyper-V environment or because of the Ryzen AM4 platform. Let me know how it goes now and if you find anything else.

              Reply

  6. Niraj20 Jun 2020 @ 18:05

    Is the Xonar DX discontinued in India ?

    Reply

    • CarvedInside22 Jun 2020 @ 06:31

      If you can't find one then they most likely don't make them anymore. Honestly, this isn't a question for this page and instead you should have contacted ASUS support.

      Reply

      • Niraj22 Jun 2020 @ 14:41

        Sadly it is not available anywhere...
        Sorry for going off topic again..
        What about Xonar AE .. Have you tried it.. Do we have any modified drivers for the same?

        Reply

        • CarvedInside24 Jun 2020 @ 03:13

          Maybe you can find one on the second hand market.
          I have not tried the Xonar AE. I would not buy it. I don't think there are any modified drivers for Xonar AE and I will not make any.

          Reply

  7. Tonico21 Jun 2020 @ 13:06

    Using Essence STX and W10 2004 broke digital out/SPDIF for me. With 1909 I could output equalized sound from Essence control panel to my BT transmitter with TOSLINK, but now only pass-through works, which means no EQ settings for optical digital out.

    Reply

    • CarvedInside22 Jun 2020 @ 03:31

      Which drivers have your tried? I suggest trying with different driver version see if with any of them it works (1.71.1, 1.75a, 1.80b, 1.81a).

      Reply

      • Tonico23 Jun 2020 @ 11:20

        This was with 1.81A, but I got around the EQ problem by using APO Equalizer which seems to only use 0.2% of CPU. There seems to be a lot of problems with S/PDIF being broken on version 2004 in general, not just with these sound cards.
        https://answers.microsoft.com/en-us/windows/forum/all/windows-10-version-2004-audio-bug-latest/5f1e54bf-2031-478d-a903-6cd3037236f3

        Reply

        • CarvedInside24 Jun 2020 @ 03:43

          Thank you for sharing the link.

          When you said "only pass-through works" did you meant that only "S/PDIF Pass-through Device (ASUS Xonar...)" output device is working or you meant that the standard S/PDIF output that you enable in the Xonar audio panel works but the sound does not have the EQ settings applied?

          Reply

          • Tonico24 Jun 2020 @ 11:31

            I only get optical audio out of the when ticking SPDIF Out and selecting PCM in the Xonar Audio Center, but that does not result in EQ or other settings in the control panel to affect the output. From what I recall in 1909, there were also PCM options in the Windows sound control panel for SPDIF which gave me equalized audio from the Xonar control panel, but that Windows setting does not seem to exist in version 2004.

            Reply

  8. theriverlethe21 Jun 2020 @ 19:23

    I recently put this card in my current PC and installed latest UNi drivers on Windows 10 2004. I installed UNi driver with low DPC latency, but I'm surprised to find that setting WASAPI exclusive latency lower than 10ms in Jriver output results in garbled audio. I have a USB ODAC working fine at 5ms, so it's not my PC. Is this normal? Are there some firmware PCI settings I should look into?

    Reply

    • CarvedInside22 Jun 2020 @ 04:44

      1. Which card?
      2. If you try with the onboard audio card, how that goes?
      3. What USB DAC do you have?
      4. When you say the USB DAC working fine at 5ms, is if you try it now with the current Windows version and other configuration?
      5. What motherboard and CPU do you have?

      I don't know if this is normal, I have never tried this.

      Reply

  9. 18000rpm23 Jun 2020 @ 07:29

    I will be replacing my Xonar D2X with an Essence STX II 7.1.

    Should I use my existing Unified driver (1.81a r2) or uninstall that and use the official Asus driver which is dated December 2019? My #1 priority is audio quality. I don't use any of the Dolby/surround features etc.

    Reply

    • CarvedInside24 Jun 2020 @ 03:42

      You will have to install the drivers again even if you chose v1.81a drivers. I think you should probably go with 1.80b, if you have any problems try the other ones.
      About those ASUS drivers, ASUS just removed the beta tag from previous STX II 2015 driver package. Those have the same audio driver as UNi Xonar 1.80b drivers.

      Reply

  10. Retromann28 Jun 2020 @ 21:36

    Did anyone of you tried a Xonar soundcard on linux?

    Reply

    • CarvedInside29 Jun 2020 @ 03:36

      For a more efficient communication, you should mention what exactly do you want to know.

      Reply

      • Retromann30 Jun 2020 @ 00:18

        I want to play with Linux. Is switching FP Headphones and speakers possible?

        Reply

        • zentoo04 Jul 2020 @ 22:01

          Yes it's working perfectly, better than with windows 10 IMHO.
          IT can work directly with pulse audio or you can use it with pure alsa setup with a .asoundrc configured with dmix/dnoop.
          You can choose impedance level and switch speaker/headset/frontpanel too.
          I personnaly use qasmixer to access all features.

          Reply

  11. fantom29 Jun 2020 @ 14:00

    Hi.
    Firstly i give you my specs:
    Windows 10 home x64, os version: 1909, os compilation: 18363.900
    Sound card: ASUS Xonar D2/PM/A, sound card driver: UNi Xonar W10 1825 v1.81a r2, main board: MSI Z270 pc mate

    Additionally i have software platform by Waves (Waves SoundGrid). It's related to its famous VST plugins bundle pack. Waves software never causes problems in my case, probably it's another cause.

    I want to connect turntable in a simpliest way (only through mixer and 2-cinch-mini jack cable).

    2 months ago I've installed above-mentioned windows 10 and now my Line In source via sound card doesn't work.:( In my win sound preferences appears "In Line input is currently unavaliable". My sound card setup contains only two sources:
    - speakers: Asus Xonar D2 Audio Device
    - line in: Asus Xonar D2 Audio Device

    I've tried reinstall original drivers and obviously it didn't work.
    What's interesting, previously, on original ASUS drivers, at least i can hear sound from turntable (but i can't record it).
    After installation Your drivers, everything just shut (but i think pc sound is slightly better :).

    Does anyone has it and can help? I guess you have some advice.
    Best regards.

    Reply

  12. Mounter06 Jul 2020 @ 07:53

    Hello!
    I'm all new to these Uni version drivers, only used the official ones for my Xonar DS with Windows 7 so far. But now I've got a fresh installation of Windows 10 on my machine (with all the possible updates) and I'm a bit confused regarding that trying with these Uni drivers would do any good and worth it over the official ones. There are lost of possible issues listed here with Windows 10 and also stated that "You will have the same issues with corresponding versions of ASUS drivers". So if I'm getting this right (just to be 100% clear) no matter if I install an official version, they won't be any better regarding the possible issues than these Uni Xonar versions? So all the issues listed here with Windows 10 are also apply to all the corresponding official Asus drivers as well? So no matter if I want an issue-less driver and operation from my soundcard as possible, it's absolutely equal if I choose the Uni Xonar or the official driver regarding? I would want the benefits of the modded Uni drivers, but not with the cost of possible more issues on Windows 10, than the official ones would have. So please make this a bit more unequivocal for me.

    Thanks for the replies!

    Reply

    • CarvedInside06 Jul 2020 @ 09:56

      Yes, all the issues listed here with Windows 10 also apply to all the corresponding official ASUS drivers as well. You won't have more issues with corresponding version of UNi Xonar Drivers.

      Reply

      • Mounter06 Jul 2020 @ 15:42

        Ok, thanks, so I guess I will than give a run for these Uni drivers. For Xonar DS and Win10 combination what would you suggest more preferably, the latest v1.81a r2 or the earlier v1.80a r3?
        And so, anyone here who's reading these and have an experience with these drivers on Windows 10 and have a Xonar DS card? Any experience, negative or positive, or any issue reporting would be welcome!

        Reply

          • Mounter07 Jul 2020 @ 20:13

            Forget to mention that I have Win10 X64 version 2004. Have tried both v.180a and v.181a and also the very latest official from ASUS website, but every time It freezes the whole system during in the middle of the installation while hearing a "clicking" sound from the back of the computer (only the reset button helps), so it's a fail so far.

            Have tried in safe mode but the result is the same. Have tried with manually the "drivers only" version (not in safe mode) with 1.80a and it seemed to install but the device manager still shows it has trouble with driver signature and the card is not working, After this installing the corresponding full UNI driver with your setup file also seem to success, but still no change in device manager, the sound card still not working at all.

            I have an ASUS P5QSE2 motherboard with some onboard Realtek soundcard, which is working fine, with Windows own drivers and beside this I have 2 High Def Audio devices listed as HDMI and SPDIF (the first might be related to my Nvidia card).
            The next I guess I will try is to install in "Driver signature not needed" mode as in your suggestions list.
            Anything else you could advice in this case to give a try first (or after)?

            Reply

            • CarvedInside08 Jul 2020 @ 08:10

              When you launch the UNi Xonar installer is your card properly detected? Copy paste the exact message you get in cards proprieties from Device Manager. I am not sure what you mean by "install in "Driver signature not needed" mode as in your suggestions list." LE: I guess you are to referring to installing the drivers in Test Mode or with Disable Driver Signature Verification, which yes at this point you should try, but I don't know where exactly I am suggesting that.
              Do you still also have Windows 7 on that machine to try the card again there?

              Reply

              • Mounter08 Jul 2020 @ 11:32

                Success!!!, that sounds trivial, but I couldn't think of doing it at first place: I have take out the card, wipe off some dust, pushing the OPA chip a bit down in it's socket (tho' it didn't looked and felt loose, but I've remembered it was real sticky job to reinsert the original chip after a disappointing exchange to some other), put and screw the card back to it's place. After Win10 startup I've installed the 1.80a full Uni driver fluidly (I've choose the "Low Latency only" option with driver cleaning) and the card begin to work immediately like charm.
                I could have started it with this, but I didn't suspected that this could be a resolution as it was working before under Win7 and since I din't touch the card, but it was like years ago I've last checked it really. (And that many issue descriptions with Win10 versions made me think that one of those could be the problem). Maybe it was just a little bit of loosening in the PCI socket... But at least it woks now, thanks and cheers!

                Reply

  13. Balrog06 Jul 2020 @ 13:24

    Not a driver issue, and I apologize for the distraction. I have an Asus Xonar Essence STX II. Over the years I've been getting more frequent bouts of the popup dialogue, and now it won't clear.
    The Internal Power for Xonar Essence STX is not detected. The audio card may not work. Please power off your PC and then connect the power cable onto the card.
    Has anyone found a fix for this? Barring that, what's your favorite replacement hardware?

    Reply

    • CarvedInside07 Jul 2020 @ 09:42

      Other than that the message, the card works perfectly fine?
      You could try installing the UNi Xonar drivers with "Low DPC Latency" or "C-Media Panel" configuration and only use C-Media Audio Panel or XonarSwitch to control the cards settings or if you have use ASUS Audio Center make sure you close it from the tray icon. Let me know if this prevents the message from showing.

      Reply

  14. mguar508 Jul 2020 @ 18:33

    Hi,

    I have Xonar ST on windows 10 PRO 32 Bits and installed 1.72r2 but i still have BSOD after sleep, there is a driver version that solves this problem?

    Thanks

    Reply

    • CarvedInside08 Jul 2020 @ 19:29

      First, uninstall the Xonar drivers and see if you still get the BSOD. If you still get it, try installing other drivers, start with v1.71a and choose "Low DPC Latency" configuration.
      Tell me the complete Windows 10 version and your motherboard.

      Reply

  15. Eyre10 Jul 2020 @ 14:34

    I'm using the 1.80b drivers with an STXII. Since the latest windows updates is there a known issue with bleed of output audio into the microphone input? I am having issues where apps like discord are unusable unless I'm on push to talk because as soon as anyone speaks it creates a feedback loop.

    Reply

Legend:AdminAuthorFeaturedOff-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

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