More > JRiver Media Center 22 for Windows

WASAPI Problem - W4S64.sys crash (wyred for sound DAC-2) [Solved]

(1/2) > >>

mramsden:
I’ve had my DAC-2 since 2011, using MC since then.

Was working just fine yesterday … but today, when I tried running JRiver, I get a blue screen crash, which says there is a problem with the W4S64.sys file.

I found mention of this on the JRiver wiki, re: the driver from 2012.

I switched from the WASAPI to kernel streaming for the driver, and it doesn’t crash.

I upgraded to version 22 JRiver: still crashes with WASAPI.

I tried downloading new drivers from the W4S website … seems the newest listed for the DAC-2 are from 2010. (I downloaded and installed the drivers labeled 10th Anniv DSD USB drivers, which seems to have a newer W4S64.sys driver, but if I select WASAPI it still crashes.)

I’m running this on Windows 10, latest version (non-beta) which worked fine up until yesterday.  Haven't added anything new recently, although there was a windows update Tuesday night ... but yesterday had no trouble with it, post-update.

Any ideas?  I have sent much the same msg to W4S as well ...

Thanks for any advice.

..Mike

mramsden:
.. Also .. with the "kernel streaming" mode, sound is locked to MC after running: ie it doesn't relinquish sound after closing. Trying to run anything else produces a message that the output is in use. Other sound sources work fine until MC is run, then no sound from others.

No obvious component of MC is running in Task Manager to lock everything else out. Have to reboot to get sound to other software after running Media Center.

JimH:
Can you try rolling back the Windows update?

gdrichardson:
Exactly the same thing has happened to me. I have had my DAC-2 since 2012, my last Windows 10 update was 6/14/2017 (2017-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4022725)).

mramsden:

--- Quote from: JimH on June 30, 2017, 06:02:56 pm ---Can you try rolling back the Windows update?

--- End quote ---

 ;D ;D ;D

Brilliant: that did it! Back to normal. Seems the latest Windows update: KB4022716, 2017/06/27, broke it. Rolled back that single update, and it's back to normal.

Will let W4S know; perhaps they can troubleshoot with MS to figure out why.

But: happy it's back to working properly!

Navigation

[0] Message Index

[#] Next page