Topic: JR22 has become unstable lately; crashes changing channels [Solved] (Read 10621 times)

DeaneG · « **on:** December 29, 2016, 06:57:41 pm »

My JR setup has become unstable over the last few releases (or versions of my Nvidia driver?) for TV. I'm currently running 22.0.54, Win 10, Nvidia GTX970 using their current driver 21.21.13.7633. It seems to crash when the stream to madVR starts up or is reinitialized.

To reproduce the problem, I set JR to Theater mode, select Guide on my IR remote, and press Play to start watching a channel. Then I press the Channel Up button periodically, waiting a second or so between presses for the video to stabilize. Within several button presses, I get a pop-up saying that mc22.exe has crashed. If I click "continue", I then get a pop up saying that madVR has crashed. I always get the mc22 popup first.

Thanks for any ideas for clearing this up.

JimH · « **Reply #1 on:** December 30, 2016, 02:06:00 am »

It's probably this problem:
http://yabb.jriver.com/interact/index.php/topic,24031.msg748298.html#msg748298

There is another similar thread here.

tzr916 · « **Reply #2 on:** December 30, 2016, 11:23:42 am »

http://yabb.jriver.com/interact/index.php/topic,108587.0.html

http://yabb.jriver.com/interact/index.php/topic,108362.0.html

JimH · « **Reply #3 on:** December 30, 2016, 11:47:20 am »

Quote from: tzr916 on December 30, 2016, 11:23:42 am

http://yabb.jriver.com/interact/index.php/topic,108587.0.html

http://yabb.jriver.com/interact/index.php/topic,108362.0.html

http://yabb.jriver.com/interact/index.php/topic,108587.msg752500.html#msg752500

DeaneG · « **Reply #4 on:** December 30, 2016, 12:20:45 pm »

With RO standard, I get a video hang instead of the MC22 crashes I get with ROHQ.

I suspect it is related to the NVIDIA driver. I'll try rolling back to a driver from a few months ago to see if the problem goes away.

DeaneG · « **Reply #5 on:** December 30, 2016, 02:21:40 pm »

Looks like it isn't the NVIDIA driver. I rolled back to 372.54 from Aug 15 of this year, and found the same crash in about five or six channel changes.

DeaneG · « **Reply #6 on:** December 30, 2016, 03:25:37 pm »

I switched from the GTX970 to Intel's build in "HD graphics 4000". MC22 crashes very similarly on ROHQ but seems stable so far on RO standard. I'll leave it there for now, until I have a chance to backup MC22 and do an uninstall/reinstall.

Or should I switch back to the GTX970 and check my Directshow filters first? If I do, what should I see?

JimH · « **Reply #7 on:** December 30, 2016, 03:33:41 pm »

This is probably a madVR problem that can be solved with a setting change. Please read a little.

Here, for example:
https://yabb.jriver.com/interact/index.php/topic,107814.msg748208.html#msg748208

DeaneG · « **Reply #8 on:** December 30, 2016, 06:08:44 pm »

Thanks, I had read that thread but didn't have much hope for it making a difference, as RO Std also fails on the Nvidia graphics system and I assume RO Std has some fairly safe rendering setup.

Rendering to a DirectX11 surface using the advanced setting didn't help - same crash under the same circumstance, reproducible within a minute or so of testing.

DeaneG · « **Reply #9 on:** December 30, 2016, 07:20:29 pm »

It seems to be working again. The solution was to uninstall uninstall MC22, reboot, reinstall, and restore the library but not the settings. If I restore the settings, it's back to broken. Everything seems OK now using current versions of MC22 and Nvidia's driver with RO HQ.

It would be very nice if there were a "restore default settings for this page" button on each page of the Options, which only affects the settings on that page. In particular this would be helpful for the RO HQ settings pages.

I imagine I changed some setting a month or two ago which made my setup unreliable, even in RO standard mode, and I have no idea what it might have been.

DeaneG · « **Reply #10 on:** December 30, 2016, 07:32:46 pm »

Spoke too soon, still broken. I'll try a complete uninstall (deleting everything) and reinstall.

JimH · « **Reply #11 on:** December 31, 2016, 02:32:22 am »

Try setting it to RO Std, and then power down everything and power it up again, including the TV tuner, network, and computers.

Test with RO Std a while.

brett · « **Reply #12 on:** December 31, 2016, 09:41:32 am »

I'm struggling with this as well (see other thread under Television) under a fresh Win 10 install on a new MSI Cubi2. I was experiencing the same channel changing issue with an Intel NUC6i5SYH. So either it is a MC22 problem or an Intel driver problem, or a combination of both.

I have to believe a MSI Cubi2 with Kaby Lake Core i7-7500U with Intel HD620 graphics would have enough horsepower to run ROHQ? However, If I switch to ROHQ, the picture becomes all jerky and is unwatchable. Not sure what to try next.

brett · « **Reply #13 on:** December 31, 2016, 10:27:51 am »

I restarted everything, changed the channels about a dozen times and bam, computer completely froze up. Totally unresponsive. Like in the past, I had to hit the power button to get it to restart.

I've attached the logs for your review. Looks like it gets caught in some sort of a loop. Hopefully this get us somewhere.

0621969: 5804: TV: CTSFileReader::ReadSampleHeader: Index Limit(796), Current(796).
0622000: 5804: TV: CTSFileReader::ReadSampleHeader: Caught up with writer (A) while in normal speed. Limit(1288067682), Current(-0)
0622000: 5804: TV: CTSFileReader::ReadSampleHeader: Index Limit(796), Current(796).
0622031: 5804: TV: CTSFileReader::ReadSampleHeader: Caught up with writer (A) while in normal speed. Limit(1288067682), Current(-0)
0622031: 5804: TV: CTSFileReader::ReadSampleHeader: Index Limit(796), Current(796).
0622063: 5804: TV: CTSFileReader::ReadSampleHeader: Caught up with writer (A) while in normal speed. Limit(1288067682), Current(-0)
0622063: 5804: TV: CTSFileReader::ReadSampleHeader: Index Limit(796), Current(796).

Over and over and over...

JimH · « **Reply #14 on:** December 31, 2016, 10:44:23 am »

Can you duplicate the problem with video set to Red October Standard?

DeaneG · « **Reply #15 on:** December 31, 2016, 10:56:16 am »

My wife has occasionally seen a similar mc22.exe crash box on another TV, operating on a NUC D54250WYK at RO standard. It hasn't happened enough to become a problem though.

brett · « **Reply #16 on:** December 31, 2016, 10:59:37 am »

Quote from: JimH on December 31, 2016, 10:44:23 am

Can you duplicate the problem with video set to Red October Standard?

I think you are responding to me? Red October is set to standard. As I stated before, ROHQ is unwatchable (though I don't understand why).

Thanks

JimH · « **Reply #17 on:** December 31, 2016, 11:00:29 am »

Please test RO on the machine you're using now. It will help identify where the problem is.

brett · « **Reply #18 on:** December 31, 2016, 11:03:34 am »

Jim - Should I start a new thread with my troubleshooting logs since I'm not sure as to who you are responding to? Thanks.

JimH · « **Reply #19 on:** December 31, 2016, 12:01:05 pm »

If anyone is having this problem with 22.0.54, please try Red October Standard as your video setting.

JimH · « **Reply #20 on:** December 31, 2016, 12:02:52 pm »

Quote from: brett on December 31, 2016, 10:59:37 am

Red October is set to standard. As I stated before, ROHQ is unwatchable (though I don't understand why).

If you're seeing a crash, there could be several causes. What antivirus are you using? Where are the files stored?

DeaneG · « **Reply #21 on:** December 31, 2016, 12:03:34 pm »

My setup appears stable now on RO std. after rebooting the PC, tuners, and ethernet switch that connects the two. I had rebooted the PC many times before without improvement, even on RO std (though that worked much more reliably than RO HQ, with an occasional freeze upon changing channels rather than a frequent crash box), so maybe the difference is in the reboot of the switch or the tuners.

FYI, I also at one point dropped back to 22.0.32 (which has a previous version of madVR) without improvement.

I'll leave it at that for now. Thanks for your help!

brett · « **Reply #22 on:** December 31, 2016, 12:31:00 pm »

Quote from: JimH on December 31, 2016, 12:02:52 pm

If you're seeing a crash, there could be several causes. What antivirus are you using? Where are the files stored?

MSI Cubi2 with Kaby Lake Core i7-7500U with Intel HD 620 graphics. Clean Windows 10 64 bit install.

Windows Defender, but I've excluded the JRIver folders and processes

This is strictly a Live TV viewing, channel changing issue. The O/S and JRiver files are on the same SSD. Using RO STD at 4096 × 2160 @ 60Hz through the Displayport -> Displayport to HDMI adapter -> Onkyo Receiver -> LG OLED OLED65B6P. I can't get ROHQ to work at 4096 x 2160. Computer totally unresponsive after crash I have to do a hard reboot by holding down the power button.

It did some more messing around and found that I could get ROHQ to work if I dropped the resolution on the PC to 1920x1080. However, making the rendering DX11 change in madVR makes display picture while in the guide all jerky.

Using RO STD results in the same computer freeze/crash while changing channels at 1920 x 1080 through the HDMI port and the Displayport.

I will try to reboot the switches as well. Please take a look at the logs and tell me if they mean anything.

Thanks

JimH · « **Reply #23 on:** December 31, 2016, 12:42:40 pm »

Make sure Windows Defender is excluding all of MC's directories for recording, etc. Temp directory....

What is the TV Tuner? Are you using a driver that the manufacturer recommends for Win10?

What happens if you record TV, or even just pause it and resume?

Don't try ROHQ until RO STD is working.

brett · « **Reply #24 on:** December 31, 2016, 01:08:02 pm »

Quote from: JimH on December 31, 2016, 12:42:40 pm

Make sure Windows Defender is excluding all of MC's directories for recording, etc. Temp directory....

What is the TV Tuner? Are you using a driver that the manufacturer recommends for Win10?

What happens if you record TV, or even just pause it and resume?

Don't try ROHQ until RO STD is working.

JRiver folders and processes are all excluded from Windows Defender as described in the Wiki

SD HDHomerun Extend tuners. Latest firmware and drivers.

No issues with recording, pausing, rewinding, of FF live TV.

Hilton · « **Reply #25 on:** January 01, 2017, 07:16:23 am »

I've got Black screen with audio then hang with 22.0.54 + MadVR 90.20 + ROHQ - If I use RO standard its fine and if I use MC21 its also fine. (Nvidia 376.48 Windows 10 64bit w/ GTX1080 SLI)

Also tested madVR 91.4 and still have same problem. MC21 works fine full screen with madVR 91.4.

Noticed that windowed mode in MC22 works fine with ROHQ as soon as you go full screen it goes black and eventually crashes.

Also tried clean install of MC22 (no joy) and restoring library from MC21 to MC22 (no joy)
Back to MC21 for now.

JimH · « **Reply #26 on:** January 01, 2017, 07:57:19 am »

There have been one or two threads on this in the last week. See the last few posts in the Weird Problems thread.

Hilton · « **Reply #27 on:** January 03, 2017, 03:33:29 am »

Thanks Jim none of those options worked. Add a new one to the list...

I rolled back to 22.0.32 and older Nvidia drivers, older madVR and older LAV (2015 vintage) and none of that worked.

However - rolling back from Windows 10 64bit anniversary update has fixed it without changing anything else.. ie it wasn't working on w10 build 1607 anniversary build - rolling back to 1511 and it worked without changing any of the current versions of JRiver/madVR/LAV/Nvidia that were there prior to the roll back.

JimH · « **Reply #28 on:** January 03, 2017, 04:23:59 am »

Oh brother... thanks for that. One for Weird and Wonderful.

Hilton · « **Reply #29 on:** January 03, 2017, 04:25:01 am »

Also still working with everything running latest versions - MC 22.0.54 w/ madVR 90.24 and LAV 69.0 on Nvidia 376.33.

brett · « **Reply #30 on:** January 03, 2017, 07:04:38 am »

I gave up. Nothing worked. The computer continued to hard crash when changing channels. Really frustrating.

I guess I will try the Windows roll back if I have time...

DeaneG · « **Reply #31 on:** January 03, 2017, 08:44:06 am »

It's possible that my issue started with the anniversary update. The timing would be about right. Or I suppose it could have been one of the windows updates around then or somewhat after.

INTERACT FORUM

Author Topic: JR22 has become unstable lately; crashes changing channels [Solved] (Read 10621 times)