getmusicbee.com
Support => Questions => Topic started by: Zodler on June 10, 2017, 11:23:19 PM
-
I have MusicBee 3.0.6335. A Chord Mojo is connected and in the player I have Output: WASAPI and Sound Device: Chord Mojo.
If I play any file I get a real bad Windows 10 blue screen of death and windows crashes and restarts. Just one week ago this worked fine. Any ideas? What should I do?
If I connect another amp like FIIO E17K in the same way, it works, no crash.
-
You might try the latest 3.1 patch. See my sig.
And please report back whether or not the issue was resolved.
-
If I play any file I get a real bad Windows 10 blue screen of death and windows crashes and restarts. Just one week ago this worked fine. Any ideas? What should I do?
What error message do you get on the BSOD?
Have you checked the Chord site for an updated driver?
If you recently updated to Windows 10 Creators version than some drivers can be blocked or deleted.
-
I used v3.1 patch and the same crash. This does not happen outside of musicbee in windows 10.
It happens inside music bee and only when I use WASAPI. If I use DirectSound inside MusicBee, it works, no crash.
Stop code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
failed: cdh76864.sys
I have the latest chord mojo driver 1.0.58 from their site.
Also what is ASIO? That does not work but no crash.
-
i cant help you with your issue, but blue screen with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED exception seems to be very frequent in win10 creators update.
-
I recommend reinstalling your Chord driver and then engaging their support team if you still have the issue. It might be a known issue with a known solution. If not, they may need to tweak their drivers. cdh76864.sys is a Chord file.
-
I have reinstalled the driver and still the same. Do you know any other free music player that supports direct digital out so I can rule out that it is not MusicBee.
-
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED exception is kernel space exception and mb is definitely a user space program, so its something about your environment even if other players works fine.
-
It's a reasonable test. Anyone knows of a free player that uses WASAPI?
-
suggest trying AIMP, though i never used it.
-
I just tried AIMP. It has 3 modes
WASAPI
WASAPI Exclusive (Event)
WASAPI Exclusive (Push)
The first works. The other 2 crashes windows 10. The first one that works does not send the original stream.
It seems it converts before sending. The Mojo input color does not change.
-
Is "event mode" checked in your MB preferences? If so, uncheck it and try again. It's on the player tab just under where you choose WASAPI output.
-
I just tried AIMP. It has 3 modes
WASAPI
WASAPI Exclusive (Event)
WASAPI Exclusive (Push)
WASAPI non exclusive is the same as Direct Sound ie. Direct Sound uses WASAPI in shared mode
-
Is "event mode" checked in your MB preferences? If so, uncheck it and try again. It's on the player tab just under where you choose WASAPI output.
I do not find "event mode" in MusicBee.
-
update to v3.1 from the first forum topic. However event mode hasnt worked well for several users but it works fine for me
-
However event mode hasnt worked well for several users but it works fine for me
Just to add to this;
Any problems I had concerning wasapi (with and without event mode), and may have reported here have been resolved when replacing my previous dac with a new one.
(The Tascam is gone, good riddance. My new Audio-GD is absolutely fantastic. My best audio purchase in years!)
-
It's motherf***ing Microsoft. Their updates are interfering with the Chord Mojo driver and I haven't had a response from Chord at all either. It's the cumulative security updates for Windows. First one I managed to uninstall it was KB4034674 and it fixed it for 1 month or so. Now it's back but I can't even see the update that is causing the issue so I'm stuck.
Later Edit: Chord seems to have released a new Windows 10 Creators Update specific driver for the Mojo and you can find it on the official Chord Mojo website page downloads.
-
i also have driver problems with my Wyred4sound Dac2 all of a sudden WASAPI didnt work anymore the Dac was useless emailed the company and they said that there was no plan to update the driver because they said that it was discontinued i was mad i had only bought this dac 2 years ago so in order to get a working dac i had to upgrade to dac2 dsd when i received it i used WASAPI as usual and it still didnt work but the driver file also came with ASIO drivers tried that and it worked emailed the company again to tell them about the WASAPI driver and they said they were worknig on a new driver .Gear gets obsolete so fast these days .
-
I h
i also have driver problems with my Wyred4sound Dac2 all of a sudden WASAPI didnt work anymore the Dac was useless emailed the company and they said that there was no plan to update the driver because they said that it was discontinued i was mad i had only bought this dac 2 years ago so in order to get a working dac i had to upgrade to dac2 dsd when i received it i used WASAPI as usual and it still didnt work but the driver file also came with ASIO drivers tried that and it worked emailed the company again to tell them about the WASAPI driver and they said they were worknig on a new driver .Gear gets obsolete so fast these days .
I have EXACTLY the same problem with a CHORD QBD HDSD 76 DAC... their Top-Of-The-Line DAC . A Shame considering the Huge Price and product abandon by CHORD...
Anyways, shift to Kernnel Streaming, and do not use WASAPI .... Worked for me