Topic: Crash on pressing stop (Read 8384 times)

kstuart · « **on:** July 04, 2013, 04:12:52 pm »

I updated from 188 to 205, and immediately, MC18 would exit upon pressing the STOP button. Not every time, but frequently - it happens several times a day.

(I have yet to update to 206, because nothing listed was relevant, and this problem was not listed in 206's notes.)

JimH · « **Reply #1 on:** July 04, 2013, 06:30:47 pm »

Try 206, but I don't think that's a known problem.

kstuart · « **Reply #2 on:** July 06, 2013, 08:52:30 pm »

I tried 201 and then 188 and the problem persists, so it seems not to be a regression.

The only other recent change is to hookup MC18 to a TV tuner. The crash-upon-stop-button happens both with TV shows and with music files.

6233638 · « **Reply #3 on:** July 06, 2013, 10:17:56 pm »

Do you have it set to stop immediately or fade out?

Windows sometimes thinks MC has frozen for me when I have it set to fade out.

kstuart · « **Reply #4 on:** July 07, 2013, 02:51:49 pm »

It just did it with 206, btw.

I have it set to "Fade (fast)". I just changed it to "Immediate" to test that theory.

But I have seen it happen with stop of Video...

kstuart · « **Reply #5 on:** July 08, 2013, 10:03:58 pm »

Problem occurs with 206 and with "Immediate"...

Matt · « **Reply #6 on:** July 09, 2013, 10:19:26 am »

Please try a different audio output mode.

Because if a driver misbehaves, it can cause this.

gtgray · « **Reply #7 on:** July 10, 2013, 12:20:40 pm »

I have experienced this with video hardware acceleration turned on. I can work around it with madVR if I use custom instead of ROHQ and use LAV and madVR. This has been this way for quite a view versions. I don't know what the difference is in the preconfigured ROHQ and my custom.

6233638 · « **Reply #8 on:** July 10, 2013, 01:07:08 pm »

Quote from: gtgray on July 10, 2013, 12:20:40 pm

I have experienced this with video hardware acceleration turned on. I can work around it with madVR if I use custom instead of ROHQ and use LAV and madVR. This has been this way for quite a view versions. I don't know what the difference is in the preconfigured ROHQ and my custom.

Does disabling hardware acceleration in Media Center with ROHQ fix this? (rather than custom)

kstuart · « **Reply #9 on:** July 10, 2013, 10:59:36 pm »

Aha ! The other thing I did recently is increase the hardware acceleration on MC18 GUI rendering (in other words, Tools->Options->General->Video Card, NOT to be confused with the hardware acceleration in Tools->Options->Video, which I have always had checked). I had forgotten about that until someone mentioned it in this thread (hurrah for threads).

I just changed to Low, which turns off all three accelerations, and so far, no crashes.

Update - Crashes still occurring, so that is not the answer.

kstuart · « **Reply #10 on:** July 12, 2013, 06:24:06 pm »

Hmmm.... I'm trying to migrate my TV recording to a different dedicated PC (it is currently on my main audio and video PC).

I just pressed stop on MC18 on that other PC and bang - it crashed.

Three things in common between the two PCs:

* TV card being used (note that pressing stop on an audio-only music file can also produce the crash)

* Media Server running

* Windows Vista 32-bit (just to be rigorous, but seems unlikely to be related)

The second PC has build 188 and the first PC has build 206 btw.

====

So, I moved the TV cards from the first PC to the second PC... if the first PC stops crashing, we will know that it is a TV related problem. If it does not stop crashing, then it is likely a Media Server related problem. I'll let you know...

kstuart · « **Reply #11 on:** July 13, 2013, 11:00:03 pm »

So far, no crashes since I removed the TV tuner card from the first PC (and it is still running a Media Server). So, it seems related to Television support in MC18.

There was also this post:

Quote from: Jack Fate 318 on July 13, 2013, 08:10:41 pm

but MC worked great until I added a tv tuner then mc stopped working almost every time I stop a recording. Did all was told to do finally gave up. I just restart & move on

If you want to move this thread to the TV Forum, that would make sense...

kstuart · « **Reply #12 on:** July 15, 2013, 01:32:54 pm »

Still no crashes since TV card was removed.

So, change my request to "Please move this thread to TV Forum, thanks !"

JimH · « **Reply #13 on:** July 15, 2013, 01:38:36 pm »

What TV card?

Did you try updating the driver for it?

Yaobing · « **Reply #14 on:** July 15, 2013, 02:12:31 pm »

So, your PC1 that no longer has a TV device is not crashing anymore. But PC2 with TV device still crashes. In the beginning you said playing audio files also caused crash. Is that still the case on PC2?

kstuart · « **Reply #15 on:** July 15, 2013, 02:51:46 pm »

Hauppauge 125 PCI-E card.

I have had crashes since the card was installed - only a few weeks in total - and only when I removed the TV card, did I discover that it was the source of the crashes. I did not update the driver, since presumably it was using the most recent driver at the time it was installed a few weeks ago.

The driver is whatever Vista installed...

kstuart · « **Reply #16 on:** July 15, 2013, 02:55:36 pm »

Quote from: Yaobing on July 15, 2013, 02:12:31 pm

So, your PC1 that no longer has a TV device is not crashing anymore. But PC2 with TV device still crashes. In the beginning you said playing audio files also caused crash. Is that still the case on PC2?

Hi Yaobing,

PC2 does not currently have audio output hooked up. The idea is to use it as a DVR only. I just was playing TV shows on PC2 in order to test that the TV cards were working (and that's how I noticed that it would also crash on stop).

If you like, I can try playing an audio file on it just as a test...

Yaobing · « **Reply #17 on:** July 15, 2013, 03:43:12 pm »

Just email me a log. yaobing at jriver dot com

kstuart · « **Reply #18 on:** July 15, 2013, 05:04:36 pm »

I checked Hauppauge web site, and their drivers have a much higher version number than what Microsoft Windows installs, so I updated the TV tuners drivers to the 2013 ones on the Hauppauge site.

I will see if I can get PC2 to crash with the updated drivers - if not, we can then assume that the problem is that Hauppauge needs to submit new drivers to Microsoft.

Meanwhile, I did email you the log for other problem I am having, which is actually a bigger problem...

BradC · « **Reply #19 on:** July 16, 2013, 04:24:51 am »

I have had MC crash on press stop when playing TV too. It does it very frequently

It only started with ver 206 (I think it went from 195 - set to stable updates)

TV playback is generally quite unstable, and not ready for general use. It has been a lot worse in MC 18 than 17

I am using a leadtek usb DVB-T tuner

JimH · « **Reply #20 on:** July 16, 2013, 06:55:08 am »

Experiment with Red October Std and with the hardware acceleration setting for video.

mkloharry · « **Reply #21 on:** July 16, 2013, 09:34:56 am »

I also have problem with live tv video. Records in background OK, but when I view live hit stop JRiver crashes and or closes completly. I tried latest stable and latest beta. Attached logs stable and beta. I tried changing settings video accleration on off, made no difference.
Thanks for any help.

kstuart · « **Reply #22 on:** July 16, 2013, 03:24:17 pm »

Quote from: JimH on July 16, 2013, 06:55:08 am

Experiment with Red October Std and with the hardware acceleration setting for video.

I have only ever used Red October Std.

I tried turning off hardware acceleration for video files.

The next experiment is "NextPVR", frankly.

JimH · « **Reply #23 on:** July 16, 2013, 04:02:27 pm »

Quote from: kstuart on July 15, 2013, 02:51:46 pm

Hauppauge 125 PCI-E card.

I have had crashes since the card was installed - only a few weeks in total - and only when I removed the TV card, did I discover that it was the source of the crashes. I did not update the driver, since presumably it was using the most recent driver at the time it was installed a few weeks ago.

The driver is whatever Vista installed...

Check with the manufacturer for an updated driver or do a Google search for similar problem with that device.

kstuart · « **Reply #24 on:** July 16, 2013, 09:58:29 pm »

Quote from: JimH on July 16, 2013, 04:02:27 pm

Check with the manufacturer for an updated driver or do a Google search for similar problem with that device.

I mentioned in:

http://yabb.jriver.com/interact/index.php?topic=81789.msg558918#msg558918

that I had updated the driver, and it did not fix the problem.

I don't think that the other people with the problem have the same TV tuner card.

BradC · « **Reply #25 on:** July 17, 2013, 03:46:35 am »

My crashing only started after upgrading to ver 206.

I did not have this crash before that.

No drivers or hardware changed

Yaobing · « **Reply #26 on:** July 17, 2013, 07:14:13 am »

Quote from: BradC on July 17, 2013, 03:46:35 am

My crashing only started after upgrading to ver 206.

I did not have this crash before that.

No drivers or hardware changed

Do you use TV in Theater view? If so, can you try it in Standard view and see if there is a difference?

Yaobing · « **Reply #27 on:** July 17, 2013, 01:08:00 pm »

Quote from: kstuart on July 16, 2013, 09:58:29 pm

I mentioned in:

http://yabb.jriver.com/interact/index.php?topic=81789.msg558918#msg558918

that I had updated the driver, and it did not fix the problem.

I don't think that the other people with the problem have the same TV tuner card.

mkloharry's log suggested that the crash occurred in Theater view. I would like you guys to confirm that this is a common thread (i.e. you all had crash while stopping TV playback in Theater view, and whether MC also crashes in Standard view).

Please provide a log, including the crash dump file if available.

Matt · « **Reply #28 on:** July 17, 2013, 04:34:13 pm »

I got a log from BradC.

It ended like this:

Code: [Select]

0505412: 6920: TV: CGenericHDTV::PreTeardownTSReaderGraph: Finish (0 ms)
0505412: 6920: TV: CTimeShifting::TearDownPlayerGraph: Releasing objects
0505412: 6920: TV: CTimeShifting::TearDownPlayerGraph: Releasing bitrate monitor
0505412: 6920: TV: CTimeShifting::TearDownPlayerGraph: Releasing graph
0505412: 4596: Playback: CVideoRefreshRateThread::Thread: Finish (21263 ms)
0505443: 6280: Playback: CASIOPlugin::~CASIOPlugin: Start
0505443: 6280: Playback: CASIOPlugin::~CASIOPlugin: Stopping ASIO
0505458: 6280: Playback: CASIOPlugin::~CASIOPlugin: Disposing buffers
0505458: 6280: Playback: CASIOPlugin::~CASIOPlugin: Exiting ASIO
0505458: 6280: Playback: CASIOPlugin::~CASIOPlugin: Deleting ASIO wrapper
0505458: 6280: Playback: CASIOPlugin::~CASIOPlugin: Updating plugins
0505458: 6280: Playback: CASIOPlugin::~CASIOPlugin: Deleting buffers
0505458: 6280: Playback: CASIOPlugin::~CASIOPlugin: Finish (15 ms)

MC doesn't log the crash and the only thing that happens after is some Media Network chatter.

The madVR crash log showed:

Code: [Select]

exception message : Access violation at address $6fb51c35 in module 'dxva2.dll'. Read of address $0.

CFrameQueue::DxvaProcessThread ($df8):
6fb51c35 +0000 dxva2.dll
4a423ad9 +1749 madvr.ax     framequeue.cpp 5577 +233 CFrameQueue.DxvaProcessFrame
4a4241d1 +0321 madvr.ax     framequeue.cpp 5719  +63 CFrameQueue.DxvaProcess
4a424330 +00d0 madvr.ax     framequeue.cpp 5747   +9 CFrameQueue.DxvaProcessThread
4a410216 +0006 madvr.ax     framequeue.cpp  163   +0 Queue_DxvaProcessThread
7621ed6a +0010 kernel32.dll

So that sounds like a NULL pointer access in dxva2.dll.

In this case, switching to Red October Standard might be a good thing to try for a while.

BradC · « **Reply #29 on:** July 18, 2013, 04:37:39 am »

Matt

The log I sent was from some madVR crashes that are new.

I tried, but could not cause a crash on stop. I have recently updated the graphics driver to 13.4 (AMD). Maybe this fixed it. I will wait and see.
So maybe the new driver has some problems with madVR

Brad

CountryBumkin · « **Reply #30 on:** July 18, 2013, 09:30:53 am »

Quote from: BradC on July 18, 2013, 04:37:39 am

Matt

The log I sent was from some madVR crashes that are new.

I tried, but could not cause a crash on stop. I have recently updated the graphics driver to 13.4 (AMD). Maybe this fixed it. I will wait and see.
So maybe the new driver has some problems with madVR

Brad

This may be the same problem I posted about a while back http://yabb.jriver.com/interact/index.php?topic=80826.0

I belive the latest madVR update fixes the (my) problem (at least that's what I've been told). Hopefully JRiver will have time to include the latest madVR with MC version 210. If not, you could do a manual install. I just set up my TV playback to use EVR for now (and only use madVR for movies). I have had no more crashes since I stopped using madVR for Live TV playback.

Yaobing · « **Reply #31 on:** July 18, 2013, 01:36:45 pm »

kstuart's TV recording playback on client problem is split to a new topic.

http://yabb.jriver.com/interact/index.php?topic=82049.0

BradC · « **Reply #32 on:** July 22, 2013, 04:47:08 am »

I have sent a log of the crash on stop to Matt.

I don't have an issue with freezing when changing channel. This issue seems to be after watching TV for a while, then press stop, it sometimes crashes.

I also have an issue switching between HD and SD channels. Going from HD -> SD -> HD, the deinterlacing is broken when switching back to HD. Pressing stop and reselecting the channel, or right click and restart player fixes the deinterlacing.

I am using AMD driver 13.4

mkloharry · « **Reply #33 on:** July 23, 2013, 08:18:37 am »

Quote from: Yaobing on July 17, 2013, 01:08:00 pm

mkloharry's log suggested that the crash occurred in Theater view. I would like you guys to confirm that this is a common thread (i.e. you all had crash while stopping TV playback in Theater view, and whether MC also crashes in Standard view).

Please provide a log, including the crash dump file if available.

I can confirm that live TV also crashes in standard view, with or without hardware acceleration on or off.

Yaobing · « **Reply #34 on:** July 23, 2013, 08:52:15 am »

Can you provide another log for crashing in standard view? I hope without the complication of the Theater view I can get more info. Thanks.

mkloharry · « **Reply #35 on:** July 24, 2013, 09:46:53 am »

Quote from: Yaobing on July 23, 2013, 08:52:15 am

Can you provide another log for crashing in standard view? I hope without the complication of the Theater view I can get more info. Thanks.

Hope this helps.
Thanks for any help

Matt · « **Reply #36 on:** July 24, 2013, 01:05:26 pm »

When it crashes, what is the faulting module listed on the Windows crash dialog?

mkloharry · « **Reply #37 on:** July 25, 2013, 08:35:39 am »

Quote from: Matt on July 24, 2013, 01:05:26 pm

When it crashes, what is the faulting module listed on the Windows crash dialog?

ntdll.dll

JimH · « **Reply #38 on:** July 25, 2013, 09:17:49 am »

Please try this build:
http://yabb.jriver.com/interact/index.php?topic=82271.0

mkloharry · « **Reply #39 on:** July 25, 2013, 12:01:15 pm »

Quote from: JimH on July 25, 2013, 09:17:49 am

Please try this build:
http://yabb.jriver.com/interact/index.php?topic=82271.0

Unfortunately I still get the same crash, with windows reporting the same error module ntdll.dll

I can play Bluray, DVD, music any video file, youtube, Netflix, record Tv in background all no problems at all, until I hit stop when watching live TV

BradC · « **Reply #40 on:** July 28, 2013, 08:32:29 pm »

Hi

I still had the same crash on ver 211.

It crashed in theaterview, but I haven't been able to make it crash in standard view yet.

I also seem to only get the deinterlacing problem in theaterview too. Using rewind on live tv, or changing channels in theaterview, breaks deinterlacing, requiring the use of stop (and a crash).

Lenm · « **Reply #41 on:** August 28, 2013, 05:53:57 pm »

Hi,

Was this issue resolved and if so, what was the problem and what fixed it?

I'm having a similar problem, it was suggested that the problem was my Hauppauge Tv card/driver but I'm having no issue with either WMC, XBMC or MediaPortal.

mkloharry · « **Reply #42 on:** October 06, 2013, 12:08:35 pm »

I am happy to report that since build 19.0.45 live TV no longer crashes on stop. Thank you.

INTERACT FORUM

Author Topic: Crash on pressing stop (Read 8384 times)