More > JRiver Media Center 22 for Windows

MC22 Crash with Tidal

<< < (3/6) > >>

Trumpetguy:
On both my work computers the 24/88.2 option is missing. Have no clue why, need to do some research.

Trumpetguy:
I have been blaming Tidal for these BSoDs. Now I'm thinking it must be related to JRiver wdm driver. Tidal never crashes when playing to any other audio output than the wdm, but BSoDs instantly when playing certain content to the wdm. This happens on three different computers. Two Win7 enterprise and one Win10pro, tested with a few different physical DACs with exactly the same and reproducible result. This makes me think that the issue with the missing 24/88.2 option on two of these machines may not have any relevance, or at best is part of the problem.

Any chance you could try and reproduce this? Or point me in the direction how to troubleshoot further?

kktan:
Mine does not have the 88.2/24 option either  :(

Luckbad:
I'm getting the same issue. Blue screen of death caused by the JRiver WDM driver.

It reproduces at 100% (instantly) if I try to play the Master version of "Bach Trios" with Yo-Yo Ma, Chris Thile, and Edgar Meyer going to JRiver. On the JRiver side, I'm using ASIO drivers to go to a Schiit Eitr.

P.S. This also happens with MC23.

On Thu 7/27/2017 11:58:21 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: jriverwdmdriver.sys (JRiverWDMDriver+0x1EEF)
Bugcheck code: 0xBE (0xFFFFB208621F3000, 0x8A0000037D8EC121, 0xFFFFDA810EB16160, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\drivers\jriverwdmdriver.sys
product: JRiver WDM Driver
company: JRiver, Inc.
description: JRiver WDM Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jriverwdmdriver.sys (JRiver WDM Driver, JRiver, Inc.).
Google query: JRiver, Inc. ATTEMPTED_WRITE_TO_READONLY_MEMORY

On Tue 7/25/2017 7:36:05 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\072517-10625-01.dmp
This was probably caused by the following module: jriverwdmdriver.sys (JRiverWDMDriver+0x2090)
Bugcheck code: 0xD1 (0xFFFFDB8A6E41BB70, 0x2, 0x1, 0xFFFFF8069DBF2090)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\jriverwdmdriver.sys
product: JRiver WDM Driver
company: JRiver, Inc.
description: JRiver WDM Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: jriverwdmdriver.sys (JRiver WDM Driver, JRiver, Inc.).
Google query: JRiver, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

winterwolf:
+1 WDM driver crashes when switching to Masters and BSODs machine

Navigation

[0] Message Index

[#] Next page

[*] Previous page