You are viewing comment page 153 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.
Thank you! Much appreciated!
I got random BSOD on startup, just before windows 8.1 logon screen appears. It happens once a week.
Windows 8.1 x64 with Essence STX.
I did a clean install (running that bat file and driver sweeper) and it still happens.
May I ask, how do you know the BSOD's are related to the Xonar card and its drivers?
Regarding drivers BSOD's, these are usually caused by GX, if you've enable it then disable it. You may want to try installing the drivers with Low DPC Latency or C-media panel configuration options and see if things are better.
I saw this report here by chance and have to report the same issue with my Essence ST! Unfortunately I can't remember exactly when the problem started, but since a few months I'm getting this occasional BSOD when the logon screen appears (~ once in a month). I'm using Windows 8.1 x64 as well. If it's happening, the computer freezes right before the logon screen appears when you have to swipe away the lock screen image.
I analyzed the BSODs using the tool "BlueScreenView" and it identifies an error in "cmudaxp.sys" as the cause for the BSOD. I was using the UniXonar 1.72 (low DPC latency version) together with XonarSwitch when I encountered the problem for the first time.
I then tried uninstalling UniXonar using your recommandation for a clean uninstall with DriverSweeper. After that I installed the latest version of UniXonar 1.75, again in low latency mode.
But yesterday I had the same BSOD again, related to cmudaxp.sys. Strange thing is that I'm using UniXonar+XonarSwitch for over a year now (since January 2014) and I never had a problem. So it has to be related to a change in my system (Windows update, driver updates etc.) or a hardware failure.
Next thing I will try is disabling the “Fast startup”-feature of Windows 8.1 because this feature already caused several problems for me in the past… As far as I remember, the BSOD never happened when I did a restart. It just happened after a shutdown when the fast startup feature is relevant, so maybe it’s related to an incompatibility with the way Windows 8.1 handles the hardware initialization when fast startup is turned on?
Besides Windows updates that where applied recently, faulty ram, these BSOD's could be caused by the antivirus software. You could temporary uninstall the antivirus software and check to see if you still get the BSOD’s. I’ve had some crazy issues and even random BSOD’s from buggy antivirus programs. Let us know if you figure it out from what the BSOD's are coming from.
I'm sure is related to that fastboot feature too.
Mine too crashes with cmudap.sys
I'm now trying older drives, i have GX disabled and have tried both Low Latency and normal modes.
@David
All my random blue screens of the past have been ram related. You might want to make sure first your memory is alright. Because even the established brands in the business shipping a lot of faulty memory kits these days.
I doubt it's ram related, i've never had a single BSOD in Windows 7 nor Windows 8.1 with my Geil kits. This is the first time and only happens after a cold boot.
I'm using latest Low DPC Latency with Xonar DX on Win 10 10130. From time to time (but rather othen) sound starts to stutter in Chrome, MPC and other apps (haven't noticed it in IE though). Has anyone else come across this one? This issue was with every Win 10 build.
I'm having the same trouble in any blink based browser, Win 10 - sound is distorted and stuttery.
Will there be a driver compatible with the soon to be released Windows 10 ?
Read the note about Windows 10 Technical Preview in the post above.
Sorry, I just check it.
Have a nice day
Hai
I'm using the newest driver from this Webside... everything is working for maybe the first min. and then i haven't Sound
Xonar D1
Win 7 64Bit
When it is not working check the Asus Xonar D1 entry in Device Manager. If it shows with a exclamation point check to see the description for the problems.
Check also the device status Windows Volume->Playback Devices, does the Speakers Asus Xonar D1 show the playback visualization ?
How are the original drivers behaving in this regard?
The Original was worster then this Option, i tried it frist. but it won't work with my PC, then i have search in the internet, and found this side. and worked better. the D1 was in the Device Manager OK, on the newest Update and with no problem marked. Then in the Option in that you can choose where have to go out the sound. Again i had sound on the Screen over DP and the System Sound worked.... but the D1 again not... with PC newstarting worked the Software for an Minute but not more....
Sry for the English, i am german 🙂
LE: i tryed probably everything but without achivment… in a Time of 5hours….
Wie geht's. I took 2 years of Deutsch in college and I know how difficult it is speak a foreign language fluently. I will try to help. Your English is better than my Deutsch.
"The original [except for names, nouns are not capped in English] was worse [ no general rule, you need to know the verb - bad, worse, worst] than this option. I [most always capped] tried it first, but it won't [ok, but 'didn't' might be better] work with my PC. Then I searched the internet and found this site and its driver worked better. The D1 was in the Device Manager ok [Your cap is ok, too]. on the newest update and with no problem marked. And, in the options, you can choose the output port [I think this is what you meant]. Again I had sound over DP, the system sound worked, but still D1 did not work. When rebooting, [I generally offset temporal phrases with a coma] the software worked briefly, but no more than a minute,
I spent 5 hours and tried probably [American tech guys usually say 'prolly' - not sure why, but we do] everything but without success.
+++++
Wish I spoke German as well as you speak English. Hope this helped. If you ever need someone to critique your technical English, I would be glad to help out. Bill
Was facing problems with HsMgr 32 bit vs 64 bit and gave this a try... worked like a peach!
Donation deserved!
I'm happy to hear that these drivers helped you. Thank you for your donation!
If you can please share more details about the "HsMgr 32 bit vs 64 bit" problem you had and which driver version you previously used.
I am on Windows 7 64x and have an Asus Xonar DX. Previously I was using Asus drivers and the first time I had issues I could only control the column of the left speaker in a stereo configuration. After some annoying trial and error I found out the issue was related to having both HsMgr.exe and HsMgr64. exe running at the same time. The work around was to install the drivers and delete HsMgr.exe under SysWOW64 folder and make sure it was not running on startup. But recently I went to update the official drivers, fearful that the same thing would happen... well this time no matter what I would try... both files would be in SysWOW64/ and both would be running from startup. Maybe there was yet another workaround but I read about the unified drivers in multiple minimally trustful places (like headfi forum) and gave it a try. It worked immediately, so that says something. Cheers!
Will Upgrading driver change/improve sound quality? im using ASUS drivers for my essence STX currently.
Read this answer.
having a xonar essence stx, which driver is recommended for me to install: the a or b driver?
do the b driver have any advantages (perhaps better sound quality?) over the a drivers for me?
I would recommend 1.75a. 1.75b are just newer drivers but they lack a valid driver signature for STX cards so they may require additional steps to install.
Has there been any way to fix the recurring screeching problem with the STX? It seems to happen no matter what driver version is installed. I really fear for my headphones...
What problem is that?
Never had it.
This one: http://www.head-fi.org/t/585158/asus-xonar-essence-stx-bugs-problems
http://www.head-fi.org/t/494565/xonar-essense-stx-random-loud-high-pitched-ringing-noise
http://forums.overclockers.com.au/showthread.php?t=954153
Place your card in another pci slot, the farther from your gpu the better.
what drivers would i need for a xonar dsx?
1.75a
-Modified AsusAudioCenter to actually close.
-Fixed: "Could not find kernel driver for %s" error with 64bit ASIO: 64Bit ASIO works now, yay!
-Removed excess ASIO Params GUID: Both 32 and 64bit ASIO now share settings.
-Disabled STXII64 driver from locking timer resolution to 2000µs.
Notes:
Modified STXII64 driver needs to be test signed, use “Driver Signature Enforcement Overrider” to do that.
You may need re-reg cmasioSTXII|cmasioSTXII64 using regsvr32 if you decide to just override files on existing driver installation.
Feel free to incorporate these into future Uni Xonar drivers.
Left original files in so those with know-how could compare and learn what was modified.
Apologies if these links cause trouble! Could have shared these through proper loops but I'm lazy..
http://www33.zippyshare.com/v/AUzBeBvY/file.html
http://www.uploadable.ch/file/pHVBXEAA5qHE/STXII.zip
Hi. Thanks for sharing these fixes and changes with us.
The STXII64.sys file is not working, when I've tried to use it I got "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)" error in Device Manager. I've checked it with Windows in Test Mode and also with Disable Driver Signature Enforcement option.
The 64 bit ASIO did not work when I tried it separately. The 64 bit ASIO fix is tied to the STXII64.sys file that you modified?
For my information, you've changed the assembly code for the fixes right? Can you share which program(s) you've used to do this.
I have some basics in assembly language so if I won't be able to replicate some of your fixes in future driver versions could I ask you to do them? If that's ok with you, can I contact you by e-mail?
TL;DR Warning!
Human error, I'm running my own ”modified” drivers based of the original STXII drivers so some assumptions lead to problems, sorry about that.
ASIO fix is not tied to the driver modification.
Are you using 64bit Vista, by any chance?
Vista and earlier used general error (code 39) to indicate signature verification failure, newer version use a specific (Code 52).
For clarification setting: “bcdedit -set testsigning on” and restarting is not enough, the driver itself needs be signed like I mentioned.
However, I think its possible that a code loop that is not used on x64 Windows 8|8.1 versions depends on the timer resolution lock to a fault, after all, that lock is used as a workaround for inputs not initializing correctly, why its not released after initialization is beyond stupid.
I've used this for a year now and only had to disable/re-enable the soundcard once to get microphone input working again.
Having control over timer resolution is critical to me and while most people won't notice, many time sensitive applications and games on their system would be more than happy to have that control back.
The problem with 64Bit ASIO was that I didn't include cmasioSTXII64.ini as I assumed there'd be one.
INI with a same name is needed for correct registration of the asio.dll, even tho it appears to be successful without it.
Anyway, made a repack with a batch that should deal with ASIO and a readme where I try to be more clear on driver signing aspect...
http://www75.zippyshare.com/v/gCujOxzi/file.html
http://www.uploadable.ch/file/MFQNqwkumCAp/STXIIv2.zip
..I warned you..
Yes, some peeking of the assembly was done. In this case just perving through IDA.
Kept it simple, byte flipped here and there, no code caves etc. should be real easy to replicate.
Hints: Google, ExSetTimerResolution, SendMessageA and CLSID|GUID.
If a new Win10 driver for STXII appears, I'll try to remember to come by and see if you or someone else managed it.
Back to lolcatz from once I came from, Farewell!
Thanks for these drivers!
I'm having a strange issue, that I'm not entirely sure how to describe. Any time I open the control panel (whether it's Xonar Audio Center or C-Media Audio Panel), the sound becomes very distorted. It's as though the volume is constantly fluctuating from high to low, but distorted at the same time. It's very hard to explain. However, if I just install the drivers without ever opening the control panel, everything works/sounds fine. Once I open the control panel, no amount of restarting seems to fix the problem. I'm at a loss here. Any help would be much appreciated!
Strange issue. This is the first I heard about such an issue. After seeing your comment I've ran some RMAA audio tests comparing the system with no audio panel launched after driver install and with panel launched and those tests reveal no changes between them.
Your audio card and OS is? Have you tried launching XonarSwitch instead? Are you familiar with the dynamic volume issue and what your saying is something else right?
Launching the audio panels adds some registry settings that will be applied to the audio drivers each time you restart even if you would not run any of the panels in that session. Maybe one of those settings is responsible. Here is the list of registry keys that are added by the audio panels: VSpeakerPos, XearDist0dB, Pl2xParam , DHEnable, DHRoom. To find out if one of these is the cause of the issue you are describing you need to do the following: find the Xonar registry settings (see FAQ Q&A5), delete the first key from the list above, disable and re-enable the Xonar card in Device Manager, see if the issue is still there, if it is then repeat the previous steps with the next registry key. Let us know of any of your findings.
Thank you for these drivers. Much appreciated.
I have Xonar D2X card and currently using LAV Audio decoder for decoding DTS/Dolby HD streams to PCM for output via the Xonar analog out. Can this driver support DTS-HD MA and Dolby TrueHD decoding so I do not have to use LAV software decoder?
I don't know if it's possible to enable DTS-HD and Dolby TrueHD on cards that do not originally support them.
Would greatly appreciate if you could consider giving this a try (decoding of HD audio formats). Cheaper on-board sound chips from Realtek support the HD formats so I am wondering if this superior hardware has the capability but not enabled for some reason.
Thank you for all your hard work on these Xonar drivers! I am just about to install 1.75a Rev2 on a brand new (no audio driver and in fact, no sound!) Windows 8.1 Pro x64 installation. I am using an Asus Xonar Xense (connected to 2.0 speakers via analog, plus headphones/mic via the dedicated headphone/mic amp/jacks) and I am wondering about the best install settings to use.
I notice that if I choose "Xonar Xense" under the card type, it informs me I'll probably need Windows Test Mode enabled. However, if I leave it on "default card settings / card not listed", the Windows Test Mode warnings do not arise. What differences will there be between choosing Xonar Xense and just leaving it as Default Card Settings? Is it worth the additional steps of Test Mode / Disable Driver Signing to select Xonar Xense?
Thank you again.
I've checked and that warning is shown by mistake on your card. You do not need Test Mode in order to install the drivers for your card.
The card selection serves two purposes: 1) To make some customization based on that specific card the way original drivers do. Drivers remain the same, only configuration changes. 2) To show warning if a specific driver requires test mode if installed on a specific Xonar card. This is informative.
Choosing a card over "default card settings / card not listed" does not change anything that would cause the drivers to require Test Mode or Disabling Driver signing.
Hi,
the latest 2 versions of the drivers are preventing my PC form shutdown.
I had similar issue with the original Asus drivers.
When I use shutdown, pop-up message appears about some memory error related to skype.exe
OS: Windows 8.1 64bit
I'll upload screenshot and post the link here asap.
The problem is described here:
http://community.skype.com/t5/Modern-Windows-from-Windows/Skype-crashing-when-shutting-down-windows-8/td-p/1364459/page/2
Well,
I resolved my issue with disabling the skype startup, and creating scheduled task to run skype on system startup with high privileges.
Thanks for sharing. Interesting fix. I was not aware of the issue. Besides not running Windows 8 and neither Skype always on, I have disabled UAC so any program launched has administrator rights. Based on your fix, I don't know where to put this issue Skype or Xonar drivers.
Genius. Thx