INTERACT FORUM
More => Old Versions => JRiver Media Center 23 for Windows => Topic started by: Grga-Ri on August 01, 2017, 12:06:48 am
-
Hi,
I waited with Win 10 - 64 Pro Creators Update, and yesterday decided let's update, and in Microsoft usual way more problems generated than solved,
I can start JRiver 22 and playback on the PC is working fine, but as soon I switch to S/PDIF converter (M2Tech HiFace EVO) blues screen appears, with
stop code, and what failed: vadspdif64.sys. Up to this update worked fine with different versions of JRiver.
JRiver 22.0.108
Windows Edition 10 Pro / Version 1703 / Build 15063.483
Please for help.
Rgds,
Damir
-
It's vadspdif64.sys is causing the issue, the issue is likely with the M2Tech HiFace EVO drivers for S/PDIF. I'd contact them about it - maybe they have newer drivers for Windows 10 Creators Update?
-
They have this driver from 2011., and worked fine up till now, with various Windows versions (7,8,10) and MC from 17 to 22. I can contact them but the problem is in Microsoft update!
-
From 2011, no updates since then? There's been changes in regards to audio in the Windows 10 Creators Update (e.g. native USB Audio Class 2.0 support) which could of broke the driver. Hopefully the manufacturer has some sort of updated driver - Windows Update just serves the third-party drivers directly from the vendor regardless if they're buggy or not (which in this case, it seems like it is).
-
I've sent the mail to M2Tech, but I don't think they plan to update this driver :-X will see what the answer will be!
-
It's a long shot, but try reducing the buffer size in device settings.
The Creative WDM drivers will BSOD 100% of the time if the buffer is any larger than 100ms for example. (reported it years ago, they don't care)
On Windows 10, I'd recommend 10ms.
-
It's a long shot, but try reducing the buffer size in device settings.
The Creative WDM drivers will BSOD 100% of the time if the buffer is any larger than 100ms for example. (reported it years ago, they don't care)
Creative?
-
Creative?
http://www.creative.com
-
What does that have to do with M2Tech? Are you just guessing that the problem is the same?
-
Creative is notorious for having terrible drivers. If I recall correctly some years ago a third-party user tried to fix issues with their drivers via modded drivers, only to be sued by Creative. ASUS is also notorious for having terrible drivers. Example being the third-party Unified drivers for the Xonar cards existing to help alleviate issues with their drivers.
Sounds like M2Tech is no different. IMO, I'd replace the DAC with another one from a manufacturer that actually actively develops/updates drivers for Windows.
-
Received the info from M2Tech:
at the moment, the only way to have your Evo working with Creators Update is disabling exclusive access. Alas, this will prevent JRiver using any sampling frequency different from the one set by Windows.
So for now I can listen only to 16/44 files, they are now closed for vacation, allegedly they will make new driver when they return.
-
I couldn't listen to direct sound driver, because soundwise cannot be compared to WASAPI, so I made roll back to previous Windows build.
-
Kernel Streaming did not work for you?