Aray
New Head-Fier
- Joined
- Feb 6, 2016
- Posts
- 23
- Likes
- 0
Did anybody try the fix?
i applied it, ill let you guys know if it happens again
Did anybody try the fix?
Essence STX here too. And I think, I know the Problem very well. Unsuspectingly you're clicking through Videos, as you suddenly get raped by a Krrrrrrrrrk EEEEEEEEE!!!!!!
The solution for me is to unregister the asio drivers. This is how to do that:
- Press the Windows-Key
- Type: cmd
- Hold CTRL+SHIFT and press ENTER
------------ 64bit ------------
- Type: regsvr32 /u "%SystemRoot%\System32\cmasiopx.dll"
- Type: regsvr32 /u "%SystemRoot%\SysWOW64\cmasiop.dll"
- Press Enter.
------------ 32bit ------------
- Type: regsvr32 /u "%SystemRoot%\System32\cmasiop.dll"
- Press Enter
I created a small batch file as a one-click solution, but the Forum don't want me to attach it to this post. Not even zipped.
@echo off & whoami /groups /nh | find "S-1-16-12288" > nul ||(
echo createObject("shell.application"^).shellExecute"%~s0",,,"runas"^&createObject("scripting.filesystemObject"^).getFile("%tmp%\.vbs"^).delete > "%tmp%\.vbs"
start "" "%tmp%\.vbs" & exit
)
wmic cpu get addresswidth | find "64" &&(
regsvr32 /u "%SystemRoot%\System32\cmasiopx.dll"
regsvr32 /u "%SystemRoot%\SysWOW64\cmasiop.dll"
)||(
regsvr32 /u "%SystemRoot%\System32\cmasiop.dll"
)
timeout 5 > nul
Create the file: STX_Eeeek-Fix.txt and paste the code into it. Save, close and rename it to: STX_Eeeek-Fix.cmd then execute the file.
Hope it works for you guys as well.
I recommend to remove the GX-Feature also. You will find it in Windows autorun and it can disabled by using tools like CCleaner or Autoruns. Or the Windows-Taskmanager, if you run Windows 10. The relevant entry should be named: Cmaudio8788GX(64). And should link to: HsMgr(64).exe. It's not related with the Problem described here for me. But I've experienced trouble with some programs, even if the GX-button is not marked in the Xonar-Center. And practicaly, it's useless anyways.
welp, i've witnessed it happening in directsound now, in addition to wasapi. So it's not as api specific as I thought it was.
At any rate, spdif output is safe. Still seems to only affect asus cards that use the asus processors; the ones with official cmedia processors are also safe for some reason.
So there is a fix in the sense that you can use an external spdif dac in conjunction with the xonar, but using digital output sorta defeats the purpose of an expensive sound card.
Another thought I had is that the driver seems to have more trouble installing on windows 7 sp1 than windows 7. Maybe that is also a factor somehow?
welp, i've witnessed it happening in directsound now, in addition to wasapi. So it's not as api specific as I thought it was.
At any rate, spdif output is safe. Still seems to only affect asus cards that use the asus processors; the ones with official cmedia processors are also safe for some reason.
So there is a fix in the sense that you can use an external spdif dac in conjunction with the xonar, but using digital output sorta defeats the purpose of an expensive sound card.
Another thought I had is that the driver seems to have more trouble installing on windows 7 sp1 than windows 7. Maybe that is also a factor somehow?
i contacted ASUS and they said they can't do much about it because they can't recreate it. if you guys have any idea how to get it to happen more consistently let me know and let ASUS know
I can make it happen very quickly by madly skipping through youtube videos (win10x64 - firefox x64 - html5). But as I said before, i disabled html5 and had no issue since then. I can also confirm that the passive studio monitor I installed between the sound card and the speakers works and give volume control on the issue.
I can make it happen very quickly by madly skipping through youtube videos (win10x64 - firefox x64 - html5). But as I said before, i disabled html5 and had no issue since then. I can also confirm that the passive studio monitor I installed between the sound card and the speakers works and give volume control on the issue.
i encourage you to submit this to asus. i dont think we should let up.