You are viewing comment page 198 of the post. View the post contents here.
Tip: Press Ctrl+F to search for a specific keyword or keyword combination.
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.
TuN14 Nov 2017 @ 18:46
Getting high DPC latency / stuttering in games with "UNi-Xonar-W10-1825-v1.81a-r2".
Highest reported DPC routing execution time ( 2000+ µs): ( cmudaxp.sys - C-Media Audio WDM Driver, C-Media Inc)
Using latest Win10 ( 1709 ) and Xonar DX, installed using Low DPC latency as well.
CarvedInside16 Nov 2017 @ 21:06
Try installing some of the previous drivers. If you still have this high DPC latency I think it may be a newly introduced issue with Windows 10 build 1709.
Skyler16 Nov 2017 @ 12:10
HI. I just want to remove the uni xonar drivers entirely from my computer and then reinstall the basic asus xonar drivers. I understand that your drivers are superior, but I want to go back for my own reasons. However, when I uninstall the uni program from my computer (windows 10), and then install the xonar drivers from the asus site, the program still seems to be using the uni drivers. How do I go about removing the uni drivers from my computer entirely, so I can do a fresh install of the basic asus drivers? Thank you so much for all that you do!!
CarvedInside16 Nov 2017 @ 20:53
Hi. Where does it say it's still using the UNi drivers?
The problem is probably just a customization file that's been left behind. Have you tried using UNi Xonar driver cleaner?
If that does not fix do FAQ Q&A 1 Extended driver cleaning step 3.
Let me know if you managed to fix this or not.
Skyler16 Nov 2017 @ 22:33
pretty sure I figured it out. I used Revo uninstaller to uninstall the program, ran CCcleaner, then did your driver cleaner. Reinstalled the asus drivers from their website, and it seems to be running normally now. Thanks!!
Hiivasieni16 Nov 2017 @ 22:46
I'm currently using Xonar DGX with UNi v.1.80a r3 drivers. I have Windows 7 but I'm building a new PC soon and probably upgrading to a Windows 10. From what I've read around the forum, Windows 10 compatibility is problematic. I listen to a lot of music, play some games and watch movies. I have Philips Fidelio X2 headphones. Just wondering which drivers would be the best bet for Win 10 and Xonar DGX? I've had no issues in Win 7 with UNi but didn't work at all with the Asus factory drivers. Is the DGX okay for Win 10 or should I go for something else?
CarvedInside24 Nov 2017 @ 01:36
Hi. I personally suggest you avoid the Windows 10 mess and try to install Windows 7 on your new PC. You may be required to slipstream some drivers to your Windows 7 install DVD/USB. If you decide to go with Windows 10, I don't know maybe start with v1.71 drivers.
James22 Nov 2017 @ 16:07
With my HT Omega eClaro, UNi Xonar 1816/1821 v1.71 is the only driver that doesn't give me Windows 10 BSODs during or after sleep. I've tried everything else including the most recent Xonar drivers as well as HT Omega's 1825 drivers. All lead to BSODs except 1816/1821 v1.71 drivers. Am I losing any real features or benefits from using almost 5 year old drivers? Are there enhancements and features in the 1825 drivers that outweigh the BSOD issues?
CarvedInside22 Nov 2017 @ 22:52
I don't think you are missing anything in terms of features. Each driver has different issues I've noted some of them in the release notes, choose the one that works best for you, in this case clearly go with the drivers that do not give you BSOD.
James25 Nov 2017 @ 15:36
Thank you. I did a fresh install with the HT Omega's 1825 drivers attempting to change different settings in BIOS and Sleep power state for the PCI - trying to remove all power loss during the sleep phase - with no luck. I can practically reproduce the BSOD on demand. Forcing a sleep and waking the PC up within a few seconds won't do it. It needs to sleep for at least, I think, 20 minutes? I'm still attempting to find a "settings" workaround, but i'm close to just going back to v1.71 drivers since it's the only one that works. Do you know if its maybe a specific tweak you did to 1.71 that makes it work? Or it's just whatever C-Media did in that version?
CarvedInside26 Nov 2017 @ 04:45
Thanks for sharing the details of the issue.
I think the issue is because of the changes C-Media did to the audio drivers after 1821 version. Curious enough most of the people don't have this BSOD issues with newer drivers. It might be tide to other drivers or other system hardware.
James03 Dec 2017 @ 14:32
No problem, and what you said is interesting.. I was actually going to ask if you had any insight since you've collectively seen all the issues. Have you noticed anyone with Z270 chipset motherboards complaining of BSODs? My current board is Z97 based. I don't want to force a system upgrade if I'm going to have the same issue again. 3-4 times out of 5 I can put the PC sleep and when I return it already experienced a BSOD and restarted, or, right as I wake the PC it BSODs. The other 1-2 times out of 5 it doesn't. I can't figure out why. All the same apps are running in the background in every scenario. Right now it didn't BSOD and the only thing I noticed different was YouTube wasn't open in a Chrome tab. However, I'm 99% sure I've closed everything in the past (including Chrome) and it still had a BSOD. I'll have to test more.
CarvedInside03 Dec 2017 @ 16:08
The others that reported BSODs didn't specified their motherboard. When I said that most people didn't have these BSODs after wake-up issues, that was based on reports prior to Windows 10 build 1709. With the new reports on build 1709 it seems that many more are affected.
The issue might be related memory read or write that's been done by the Xonar driver after sleep resume. But the problem could because of a Windows 10 bug and not a driver bug.
Your Windows 10 is build 1709?
James03 Dec 2017 @ 16:40
Ah ok. Would choice of ram be an issue? Or its still an issue completely on the card/drivers you think? Yes, I'm on Windows 10 Pro 1709 16299.64. I had the BSODs in earlier versions of Windows 10. I've had the BSOD issues for every build of Windows this year as well as part of 2016.
CarvedInside03 Dec 2017 @ 18:36
By memory read or write I was referring to memory operations that are managed by the OS.
But of course problematic RAM or RAM and motherboard compatibility issues can give BSODs. Just to be sure you could this with something like memtest86, Windows memory test or Prime95 overnight.
Another thing to do is check that you have the latest BIOS installed for your motherboard.
James03 Dec 2017 @ 20:09
Ah got it. I actually went through memtest86 without issue with my ram. Also, my motherboard has the latest bios - which I believe is from 10/2015. I guess it simply boils down to hardware used.. however it's interesting how the vast majority of users all claim 1.71 has no BSODs. If 1821 seems to be the most solid, I wonder what changed so dramatically in future versions?
White17 Dec 2017 @ 11:21
Hi I have the same issue as you I'm also using Z97 I've tried everythings just like you anythings won't work and this is so annoying I'll try 1.71 just like you said.
James21 Dec 2017 @ 17:21
I moved up to the latest drivers and the crashes resumed. So far, the 1.71 are the only ones that don't cause a crash.
Discussion continued here.
Richard Johnson28 Nov 2017 @ 21:54
Can anyone verify that Dolby Headphone works correctly on Windows 10 with the latest Creator's Update?
Case29 Nov 2017 @ 13:16
I don't seem to have any problems using Dolby Headphone on an up-to-date Win 10 install with my Xonar DX.
Richard Johnson02 Dec 2017 @ 21:49
You don't have the dolby headphone audio balance issue you used to have?
Case02 Dec 2017 @ 23:03
OK, maybe saying I don't have "any problems" was not technically correct. I do actually still have the issue where in Raceroom Racing Experience, my in-game audio is much louder than my menu audio if I'm using anything else than stereo in the game options. So yeah, that's one issue I still have and I'm not sure if it's something on my side or some rare in-game bug. Nobody seems to be having this problem with the game except me, though.
And as for the other games having slightly different audio balance...well, I either got used to that or it's gone. I can't hear that anymore.
One thing worth mentioning is that I'm actually using older drivers, not the latest ones. 1.64 if I remember correctly. The reason for this is mostly because it seems to me like they do have better directionality for Dolby Headphone. Maybe it's placebo, but I do seem to be able to hear a difference if I test them back to back with newer drivers.
Frank30 Nov 2017 @ 07:25
I was using 1825 v1.81a r2 without issue until the 1709 update. Now there will always be a BSOD after waking up from sleep. Crash dump files indicate the culprit be cmudaxp.exe, I am rolling back to 1.71 as suggested by others to see if that solves the issue.
CarvedInside30 Nov 2017 @ 15:32
Let us know if v1.71 works fine or not.
Frank30 Nov 2017 @ 18:24
Turns out that move sets me on a longer journey... After removing v1.81a I found myself unable to install any versions of driver, for earlier version (1.64, 1.71) it's "Please plug-in audio device", and for older (1.80, 1.81) it's "installation failed". Have tried everything from safe mode to disable signature enforcement to verifying EEPROM, even did a keep files and apps Win 10 refresh, but was slapped with another cmudaxp BSOD in the end. Probably will try a fresh Win 10 install later today.
CarvedInside30 Nov 2017 @ 18:53
Have you tried manually installing the audio driver like it's described in Possible Solution 1 from this page?
Frank30 Nov 2017 @ 19:06
Yes, get a generic "Windows encountered a problem installing your driver" error.
Frank01 Dec 2017 @ 22:01
Before I reinstall Win 10 a new update came out (KB4051963), after which all my troubles went away (I am also having difficulties with display driver after uninstalling sound driver). Not sure why though, my guess is the problems have something to do with the Windows update mechanism.
CarvedInside02 Dec 2017 @ 01:23
Which Xonar drivers did you end up installing after applying KB4051963 update? Do you still get the BSOD after waking up from sleep issue?
Frank02 Dec 2017 @ 03:04
1.71, so far have about 4 sleep / wake and no BSOD. One thing though, after installing the driver waking up take considerably longer time, screen will be unresponsive for a short while, same with 1.81a except that leads to BSOD usually. This is not the case pre-1709.
Jacob25 Dec 2017 @ 23:07
You need to restart your computer before the device will be detectable after removing it. I had this exact problem too.
Matteo02 Dec 2017 @ 16:54
I have a Xonar Essence STX II and I'm running Windows 10 Enterprise version 1703. I postponed the update to 1709 until today, hoping that it could go smoothly.
It didn't.... After installing the update and restarting, I got BSOD and "system thread exception not handled" and nothing else.
Windows restored its previous version, so I can use my computer.
Did anybody else have this error?
CarvedInside02 Dec 2017 @ 18:50
Hi. I want to point out that your BSOD issue might not be related Xonar drivers. You could uninstall the Xonar drivers before installing the 1709 build update and see if you still get the BSOD.
Matteo02 Dec 2017 @ 19:01
Thank you for the advice. Do you think I also have to remove the card from my PC or just uninstalling the drivers should help?
CarvedInside02 Dec 2017 @ 21:25
Uninstalling the drivers is enough. If you still get the BSOD you could then remove the Xonar card just so could rule out if it's Xonar card related.
Matteo03 Dec 2017 @ 15:07
Thank you, you're really there to help!
CarvedInside03 Dec 2017 @ 15:46
You're welcome. Let us know of the result.
Jason03 Dec 2017 @ 00:58
Just chiming in to say that v1.71 worked for my on Windows 10. I was using the official Asus 1823 version before and was getting BSODs on waking.
CarvedInside03 Dec 2017 @ 15:15
Thank you for the feedback. Is this on Windows 10 build 1709 or is it happening on a previous Windows build?
Jason04 Dec 2017 @ 04:11
Yes. Windows 10 Pro. Version 1709. Build 16299.98.
CarvedInside04 Dec 2017 @ 14:02
Was this happening with the previous Windows 10 build or it only started with the 1709 update?
Jason14 Dec 2017 @ 04:07
Sorry for the delayed response.
The BSODs only started happening with an update (official drivers). I am not sure if it was the 1709 update specifically as I went from 1511 (no issues with official drivers) to 1709 (BSODs with official drivers) in one update session, as it was a fresh installation of Windows 10.
I'm still having no issues with your v1.71.
CarvedInside15 Dec 2017 @ 20:08
No problem. Thank you for the information.
Benjamin04 Dec 2017 @ 12:38
After installing Win10 1709, at first I was logged in with my Microsoft account ([email protected]) before I later switched to local account ("Benny"). I think I installed the Uni Xonar drivers before that change, but I am not sure.
Sadly MS left me with a user folder named "benja" instead of "Benny", so I renamed my user profile folder to "Benny" and changed the profile path in the registry.
Problem is, that Uni Xonar (no matter how I uninstall/clean and reinstall) creates that old/wrong path c:\users\benja\Asus\Xonar..... where there is just one DLL file and the ini file with my Settings.
I can't find any registry key or ini file that tells Uni Xonar software to create that path. Maybe it has something to do with the Software installing/running with that UAC-virtualization flag in Taskmanager?
Is there a workaround for that? I just want those folders/config files in my normal user profile path.
CarvedInside04 Dec 2017 @ 14:18
Isn't the path "C:\Users\benja\AppData\Roaming\ASUS\Xonar (..) Audio Center"?
The path with Xonar Audio Center in the name is the path for settings from the ASUS Audio Center and is automatically generated by the AsusAudioCenter.exe using system variables. There is not setting to change that from the AsusAudioCenter perspective.
Your problem seems to be with the profile path change which didn't changed all user profile variables. You may want to try something like reversing the benja->benny changes and use User Profile Wizard or some other tool to move the profile to another name.
Benjamin04 Dec 2017 @ 14:51
Thanks for the tip. Yes you're right, the path goes down into appdata\roaming\ASUS etc. I'm not on my computer right now, so I forgot about the appdata subfolders.
If it's a system variable that the Audiocenter is using, I might find out, how to change that variable .
Fábio11 Dec 2017 @ 16:28
I've one issue with Windows 10 FCU with v1.81a r2 or 1823 v1.80a r3.
Right clicking the windows tray speaker will reset my XonarSwitch from 7.1 Dolby Headphones/24 Bits/41.100 to Stereo/16 Bits.
CarvedInside11 Dec 2017 @ 16:57
I've already written about this in "Notes about Windows 10 compatibility" section.
Vin01 Jan 2018 @ 22:41
It does it for me too. I'm pulling my hair out as I click my speaker icon in the task bar tray frequently. Is there any fix for it?
rej11 Dec 2017 @ 22:00
I must be tone deaf because I don't hear any differences between the UNI drivers and the asus drivers. I've tried many times but I always go back to asus driver. Certainly that being 64 years old makes for less than perfect hearing but If someone here could describe why they like these drivers more than the original, please do so. Also, I never had any problems of any kind with the asus driver.. what problems am I supposed to have ...or what make you guys change for the unified drivers? there must be something since so many people are using the UNI driver which work very well also....
John12 Dec 2017 @ 04:39
Its not a major change but asus has not spend much time on their drivers in a long time so for some people this driver may fix a major bug preventing them from even running the soundcard in the right setting. There are only a few changes really related directly to audio, but especially for games and such where perfomance can cause skips and such these drivers can be installed in low latency mode and behave much better performance wise than the stock asus drivers, which may or may not improve the audio and/or performance of the rest of the system.
Dima17 Dec 2017 @ 14:01
Hi, I faced with an issue as switched to Windows 10 - sometimes relay on my Xonar D2/PM switches for few times with no reason like I've opened some page on browser(sometimes it switches even more than few times). What could cause this?
CarvedInside20 Dec 2017 @ 01:28
This could happen when an application scans the recording devices causing the card to switch from microphone to line-in and to microphone again. Also some sites scan the recording devices, someone said it's a form of bot detection.
You could try something like this to see if it reduces the occurrence: right click the Windows Volume, select Recording devices, select Microphone (Asus Xonar...) an set it as default.
Ofcourse the issue you are having can be related to a Windows bug.
Dima23 Dec 2017 @ 14:52
The thing is, it happens only with Mozilla Firefox for some reason, tested on Edge and Chrome no cracking so far. Btw, I've installed your drivers and hope microphone will work properly, sometimes it wasn't able to work on firm ASUS drivers - I had to restart Windows 10 or click in Xonar Audio Center on microphone boost to remove the mark, press OK, then re-open the window and return the mark on microphone boost. And afterall it was quite silent, on MB card everything is smooth.
CarvedInside24 Dec 2017 @ 15:59
It seems it's a bug or feature within Firefox.
I've come up with workaround fix for this issue. If you don't need the Line In input being available at all times do the following: 1) Right click Windows Volume and select Recording Devices. 2) Right click on Line In (Asus Xonar...) and select disable 3) Right click one of the other items in recording devices and select "Show disabled devices" so that you can re-enable Line In when needed.
Dima05 Jan 2018 @ 01:01
Thanks a lot, it helped. But what about issue with microphone itself? Its way too quiet sometimes, time to time remove/add microphone boost helps, but in 70% of time i should to restart PC to make microphone work as should. Problem remains on newest drivers(downloaded here).
CarvedInside05 Jan 2018 @ 23:40
I'm pleased to hear it worked.
Please write the microphone boost issue as a new comment. Mention OS version and build number, card, driver versions that have you tried, if it happened with previous Windows 10 builds.
James21 Dec 2017 @ 17:26
Just a quick update: I moved off the 1.71 drivers to test the latest (which crash) to continue my own tests. The crashes still always happen during or when resuming sleep - so I've been able to catch it live - but I still wasn't sure what triggered it. Sleep states and lower power states for the PCI didn't change anything. However, during the testing, at one point I didn't crash at all (first two weeks of December). The only thing different, I think, was I closed all YouTube links that I leave open in Chrome before allowing the PC to go to sleep. Also, I think any website or app (Spotify) that could play music was closed. I think there might be a connection. I left YouTube open again, it crashed.
Anton22 Dec 2017 @ 05:20
Hello, found (bug or feature): If you use latest firefox browser, soundcard (my card Xonar d2) and try to visit some sites ( http://www.vk.com for example) it will click relay (not realy sure for right translation). Im not sure that its sound card trouble or drivers, or its browser (didn't found issue on FF forums)...
CarvedInside22 Dec 2017 @ 05:46
Hello. See this answer.
CarvedInside24 Dec 2017 @ 16:04
In case you are interested I've posted a workaround fix in the previously linked discussion thread.
Nelson24 Dec 2017 @ 11:53
I've encountered one peculiar glitch with the 1.80b r3 driver before I reinstalled it where lowering the volume would not affect the right channel's volume (it would stay at 100% while the left channel's volume can be changed normally). Even at 0% volume (using a volume wheel to go down to zero until it mutes and unmuting via the mute button) the right channel was at full blast, while the left channel was inaudible. 50% volume made left channel 50% and right channel 100%, etc. As of now, I'm not able to reproduce the glitch, but it was an interesting observation and thought I should share. I am using Windows 10 Fall Creators, version 1709, build 16299.125.
CarvedInside24 Dec 2017 @ 15:47
Thanks for sharing. Let us know if you ran into the issue again.