Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[justsomeguy]

I've been getting random crashes since updating to 22.0.41. They seem to happen during periods of inactivity when MC and the computer aren't being used as I haven't had it happen while using it. Nothing new has been installed since 22.0.41. No AV running on the computer, Defender is disabled.

I captured a log of the crash... https://drive.google.com/open?id=0B8STIzDFNsyob3R1dU5nOUhVeHc

[Matt]

The crash is from the ATSC EPG retriever.  I called in our TV expert to have him take a look.

[JimH]

Do you use MC for TV?  Is there a tuner present?  Is it set up?

[Yaobing]

Hopefully the following will fix the problem.

Fixed: MC would crash when scanning for ATSC EPG data if a rating region contained in a content advisory descscriptor does not have text description.

The change will be in an upcoming new build (build 45 or higher).

[justsomeguy]

wow thanks for the quick replies and possible fix in upcoming builds.

Yes I am using a SiliconDust HDHomeRun on the network. MC has been setup and working with it for a while now and is configured to retrieve programming info.

[HedgeHog]

Hi,

Not sure if I should just add to this thread or start a new one.  Please move it if I erred.

Recently, MC22 22.0.41 keeps crashing on my PC (i7 6700K, 16GB, Win10 Ultimate, Win Defender).  MC22 and several JRiver files were excluded from Defender.  It crashed halfway through a new SACD ISO rip so I thought the file had issue so I rebooted and played a FLAC CD rip.  Same problem after a while playing.

My next steps were what's recommended, backed up library, uninstall MC22 and registries, reboot, reinistalled MC2 (.41), and restored library.  Random crashing again.  I then tried going back to .34.  Now it randomly crashes even not playing anything.

I've attached the program crash pop-up but it's probably just a generic Windows error message.

Also, here's the Event Viewer listing.

Code: [Select]

Faulting application name: Media Center 22.exe, version: 22.0.34.0, time stamp: 0x57ffaaf8
Faulting module name: Media Center 22.exe, version: 22.0.34.0, time stamp: 0x57ffaaf8
Exception code: 0xc0000409
Fault offset: 0x00a9ba16
Faulting process id: 0x3570
Faulting application start time: 0x01d24bf51a89ac5e
Faulting application path: C:\Program Files (x86)\J River\Media Center 22\Media Center 22.exe
Faulting module path: C:\Program Files (x86)\J River\Media Center 22\Media Center 22.exe
Report Id: ad741721-6a93-4426-acdc-26a05bc07878
Faulting package full name:
Faulting package-relative application ID:
and

Code: [Select]

Fault bucket 116254701318, type 5
Event Name: BEX
Response: Not available
Cab Id: 116230807158

Problem signature:
P1: Media Center 22.exe
P2: 22.0.34.0
P3: 57ffaaf8
P4: Media Center 22.exe
P5: 22.0.34.0
P6: 57ffaaf8
P7: 00a9ba16
P8: c0000409
P9: 00000007
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C8A.tmp.WERInternalMetadata.xml
\\?\C:\Users\Hedwig Poon\AppData\Local\Temp\WER9881.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9AD4.tmp.dmp
\\?\C:\Users\Hedwig Poon\AppData\Local\Temp\WER9B13.tmp.WERDataCollectionFailure.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Media Center 22._9f7ac1d67b23a896dd416cec98f5309ca668ae72_3c1f7f65_cab_3f04da7b

Analysis symbol:
Rechecking for solution: 0
Report Id: ad741721-6a93-4426-acdc-26a05bc07878
Report Status: 8
Hashed bucket: 1097964ac45dfd4efbc3a2d6aa22f55e

What steps should I take to rectify this?

Thanks in advance.

PS.  No new apps were installed and malware scan results were clean.

-Hedwig

[JimH]

You might look at this thread for ideas:

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

[HedgeHog]

You might look at this thread for ideas:

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

Thanks, JimH.

I had a look through the threads and, sadly, they don't  seem to be applicable.  Weird that it was working fine last week.  I think on Defender definitions got updated since but, as mentioned, MC22 has been excluded from active scan.

It just crashed again with it up but not playing.  Really not sure what's up with it.  No other apps are causing problem.  I can use other player (Foobar) with no problems.

 ?

-H

[JimH]

Take a look here:
http://wiki.jriver.com/index.php/Taming_Windows_Defender

[HedgeHog]

Take a look here:
http://wiki.jriver.com/index.php/Taming_Windows_Defender

Jim,

Love the product and really do appreciate the support but it's like a broken record with the "anti-virus breaks the app" thing.  Pretty sure I mentioned in both my posts that MC has been excluded from scans.  So it's probably not Defender (per that link above).  Also, iTunes and Foobar plays fine and neither have been excluded.  It's just weird that everything's been fine until a couple of days ago.  Not sure if it coincided with some MS Updates (don't think any was downloaded) or moving to 22.0.41.

Anyway, will use the other apps until MS releases another update to see it makes any diff.

-H

[JimH]

If you can do your own trouble shooting, have at it.

If you want to be sure you have the broken record thing fixed, please read the topic carefully.

Let us know what you find.

You could read a little of this thread to see why antivirus is often raised as a possible cause of crashes:
http://yabb.jriver.com/interact/index.php/topic,86096.msg588759.html#msg588759

[CountryBumkin]

Hi,

Not sure if I should just add to this thread or start a new one.  Please move it if I erred.

Recently, MC22 22.0.41 keeps crashing on my PC (i7 6700K, 16GB, Win10 Ultimate, Win Defender).  MC22 and several JRiver files were excluded from Defender.  It crashed halfway through a new SACD ISO rip so I thought the file had issue so I rebooted and played a FLAC CD rip.  Same problem after a while playing.

My next steps were what's recommended, backed up library, uninstall MC22 and registries, reboot, reinistalled MC2 (.41), and restored library.  Random crashing again.  I then tried going back to .34.  Now it randomly crashes even not playing anything.

I've attached the program crash pop-up but it's probably just a generic Windows error message.

Also, here's the Event Viewer listing.

-Hedwig

You should attach a copy of the MC log (Help>Logging>Report Problem) to this thread.
Actually, IMO, you should probably start your own/new thread. Since this a different problem from the OP's post.
Since the log can get real big, it's best if you reset the log first, then wait for the crash, restart MC and then capture the log.

[KingSparta]

the only time I get a crash is when messing with the TV Tuner.

[HedgeHog]

Thx for the urging...so I did pursue this further via the log.  Looking at the last bit of the LOG.TXT shows:

Code: [Select]

0110516: 2536: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0110516: 2536: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using specified output format
0110516: 2536: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 352.8 kHz 64bit 2ch
0110516: 2536: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
0110516: 2536: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0110516: 2536: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using specified output format
0110516: 2536: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 44.1 kHz 64bit 2ch
0110516: 2536: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
0110516: 2536: Playback: CWaveOutBin::CreateBin: Finish (0 ms)
0110516: 2536: Playback: CMJWaveFeeder::Thread: Preparing to feed data
0110516: 3068: Playback: CWaveOutBinPlayThread::Thread: Start
0110516: 2536: Playback: CMJWaveFeeder::Thread: Memory playback: 0; Maximum play buffer bytes: 1073741824; Grow by bytes: 268435456; System available bytes: 4294967295
0110516: 2536: Playback: CMJWaveFeeder::Thread: Running feeder loop
[color=red]0110516: 2536: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
0110516: 2536: General: TopLevelExceptionFilter: Message: 275, wParam: 6001, lParam: 0[/color]
0110516: 2536: General: RunProgram: Start
0110516: 2536: General: RunProgram: Filename: C:\Program Files (x86)\J River\Media Center 22\JRCrashHandler.exe / Parameters: JRCrashInfo15232
0325641: 14180: Sharing Plugins: CUDPSocketReader::Accept: Finish (215735 ms)
0325641: 10088: Sharing Plugins: CUDPSocketReader::Accept: Canceled: socket=CListenerBase::CListenerBase [UDP], cancel event number=1
0325641: 10088: Sharing Plugins: CUDPSocketReader::Accept: Deleting socket
0325641: 10088: Sharing Plugins: CUDPSocketReader::Accept: Finish (239360 ms)
And from the PREVIOUS LOG.TXT:

Code: [Select]

0095890: 14812: Playback: CMJWaveFeeder::Thread: Preparing to feed data
0095890: 9840: Playback: CWaveOutBinPlayThread::Thread: Start
0095890: 14812: Playback: CMJWaveFeeder::Thread: Memory playback: 0; Maximum play buffer bytes: 1073741824; Grow by bytes: 268435456; System available bytes: 4294967295
[color=red]0095890: 14812: Playback: CMJWaveFeeder::Thread: Running feeder loop
0095906: 14812: General: TopLevelExceptionFilter: Unhandled exception -- program crashing[/color]
0095906: 14812: General: TopLevelExceptionFilter: Message: 275, wParam: 6001, lParam: 0
0095906: 14812: General: RunProgram: Start
0095906: 14812: General: RunProgram: Filename: C:\Program Files (x86)\J River\Media Center 22\JRCrashHandler.exe / Parameters: JRCrashInfo11984
0095906: 14812: General: RunProgram: Performing ShellExecute...

Not sure what that implied so I just uninstalled MC 22.0.41 and purged all folders relevant to JRiver.  I backed up the Library Backup folder and the logs but, in my haste, neglected to backup cover art.  Anyway, rebooted, reinstalled MC 22.0.41  and it behaved as a new install.  Restored the library and settings, now everything is working fine.  So, no antivirus was harm during this diagoistic. 

Sadly, a lot of my downloaded cover art are gone but, alas, whatever got messed up from in-place upgrades back from MC 18 to 22 seems to have been the culprit.  Still miffed at having to find/fix cover art though. 

-H

[HedgeHog]

Nevermind, spoke too soon.  I had left MC running for a couple of hours without issue.  Then played a whole SACD ISO without problem.  Now 3/4 into another ISO, it crashed.

Code: [Select]

6099906: 18404: Playback: CMJWaveFeeder::Thread: Preparing to feed data
6099906: 18380: Playback: CWaveOutBinPlayThread::Thread: Start
6099906: 18404: Playback: CMJWaveFeeder::Thread: Memory playback: 0; Maximum play buffer bytes: 1073741824; Grow by bytes: 268435456; System available bytes: 4294967295
6099906: 18404: Playback: CMJWaveFeeder::Thread: Running feeder loop
6099906: 18404: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
6099906: 18404: General: TopLevelExceptionFilter: Message: 15, wParam: 0, lParam: 0
6099906: 18404: General: RunProgram: Start
6099906: 18404: General: RunProgram: Filename: C:\Program Files (x86)\J River\Media Center 22\JRCrashHandler.exe / Parameters: JRCrashInfo6076
6099906: 18404: General: RunProgram: Performing ShellExecute...
6099969: 18404: General: RunProgram: Running process...
6099969: 18404: General: RunProgram: Waiting for completion
0000000: 18348: General: JRCrashHandlerApp::Run: Start
0000000: 18348: General: JRCrashHandlerApp::Run: Opening Shared Memory: JRCrashInfo6076
0000000: 18348: General: JRCrashHandlerApp::CreateMiniDump: Start
0000000: 18348: General: JRCrashHandlerApp::CreateMiniDump: Trying to set dump privileges
0000000: 18348: General: JRCrashHandlerApp::CreateMiniDump: Creating dump output file at C:\Users\Hedwig Poon\AppData\Roaming\J River\Media Center 22\Crash.dmp
0000219: 18348: General: JRCrashHandlerApp::CreateMiniDump: Finish (result: 1) (219 ms)
0000219: 18348: General: JRCrashHandlerApp::Run: Finish (219 ms)
0000219: 18348: General: JRCrashHandlerApp::ExitInstance: Start
0000219: 18348: General: JRCrashHandlerApp::ExitInstance: Finishing
6100235: 18404: General: RunProgram: Finished
6100235: 18404: General: RunProgram: Done waiting
6100235: 18404: General: RunProgram: Finish (329 ms)
6109078: 12828: Sharing Plugins: CUDPSocketReader::Accept: Finish (12328 ms)
6109078: 18564: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
6109078: 18564: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.100: NOTIFY: http://239.255.255.250:1900*
6109078: 18564: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:alive: uuid:fdfe61e1-98f4-adae-4172-2034e2988e1e::urn:schemas-cyberlink-com:service:RemoteControl:1
6109078: 18564: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
6109078: 12828: Sharing Plugins: CUDPSocketReader::Accept: Start
6109078: 12828: Sharing Plugins: CUDPSocketReader::Accept: Description: CListenerBase::CListenerBase [UDP]
6109078: 12828: Sharing Plugins: CUDPSocketReader::Accept: Finish (0 ms)
6109078: 18568: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
6109078: 18568: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.100: NOTIFY: http://239.255.255.250:1900*
6109078: 18568: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:alive: uuid:fdfe61e1-98f4-adae-4172-2034e2988e1e::urn:schemas-cyberlink-com:service:RemoteControl:1
6109078: 18568: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
6109078: 12828: Sharing Plugins: CUDPSocketReader::Accept: Start
6109078: 12828: Sharing Plugins: CUDPSocketReader::Accept: Description: CListenerBase::CListenerBase [UDP]
6109078: 12828: Sharing Plugins: CUDPSocketReader::Accept: Finish (0 ms)
6109078: 18572: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
6109078: 18572: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.100: NOTIFY: http://239.255.255.250:1900*
6109078: 18572: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:alive: uuid:fdfe61e1-98f4-adae-4172-2034e2988e1e::urn:schemas-cyberlink-com:service:RemoteControl:1
6109078: 18572: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
6109078: 12828: Sharing Plugins: CUDPSocketReader::Accept: Start
Event Viewer Application Log:

Fault bucket 108563271494, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Media Center 22.exe
P2: 22.0.41.0
P3: 582a04c9
P4: JRReader.dll
P5: 22.0.41.0
P6: 582a03cc
P7: c0000005
P8: 000e901e
P9:
P10:

and

Code: [Select]

Faulting application name: Media Center 22.exe, version: 22.0.41.0, time stamp: 0x582a04c9
Faulting module name: JRReader.dll, version: 22.0.41.0, time stamp: 0x582a03cc
Exception code: 0xc0000005
Fault offset: 0x000e901e
Faulting process id: 0x17bc
Faulting application start time: 0x01d24dac4331e104
Faulting application path: C:\Program Files (x86)\J River\Media Center 22\Media Center 22.exe
Faulting module path: C:\Program Files (x86)\J River\Media Center 22\JRReader.dll
Report Id: 0d3c8565-c04a-41d2-9646-da09ddf46144
Faulting package full name:
Faulting package-relative application ID:

[Hendrik]

Please attach a full log package, or mail it to logs at jriver dot com (with a reference to this thread), it includes more information then just the one crash line.
You can generate the full package by restarting MC after a crash, and immediately going to "Help -> Logging -> Report problem...". It'll generate a zip file for you which you can submit (ideally without any modification).

[HedgeHog]

Last update (sorry for thread-jacking):  While searching the web for similar problems, I found a link to my own post from 22.0.1x. https://yabb.jriver.com/interact/index.php?topic=106265.0  Matt had suggested disabling the memory playback, so I tried it this time and, voila, it worked like a charm!  Did an Extended Windows Memory Diagnostic test (2-passes), found no problems.

Oh well, it's fixed and everything's been playing fine for a couple of days.  Guess it's fixed.

[justsomeguy]

Hopefully the following will fix the problem.

Fixed: MC would crash when scanning for ATSC EPG data if a rating region contained in a content advisory descscriptor does not have text description.

The change will be in an upcoming new build (build 45 or higher).

So I haven't had a crash now for a week. I'm guessing that means whatever the EPG data that was being downloaded and missing a text description now isn't missing it. Appreciate the upcoming fix though as I could see the problem happening again down the road.