Print

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

[jackolynn]

I have been using MC since MC13 and was using the beta of MC16 on the trial.  As this has now expired I paid for the upgrade, but now it crashes every time after a minute or so when trying to play a file.  I have uninstalled, cleared the registry, turned the machine on and off again and reinstalled all with the same result.  Help please!

Thanks

The problem details are:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   Media Center 16.exe
  Application Version:   16.0.111.0
  Application Timestamp:   4df7df5e
  Fault Module Name:   ntdll.dll
  Fault Module Version:   6.1.7601.17514
  Fault Module Timestamp:   4ce7ba58
  Exception Code:   c0000005
  Exception Offset:   000222c2
  OS Version:   6.1.7601.2.1.0.768.3
  Locale ID:   2057
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

[JimH]

Uninstall any versions that didn't come from our site.

What kind of file are you trying to play when it happens? 

MC has logging under Help. 

My signature has a link on "Stability".

[jackolynn]

I have MC15 & MC16 loaded, both of which are direct from your site.

I don'y often get far enough to select a file before it crashes.  (My library is a DNLA media server on my NAS box).  I have disabled everything I can, but still it crashes.  I have been using MC16 in exactly the same way for over a month, so not sure what has changed that is causing this other than I have paid for the licence and loaded the most recent program file.

I have set the logging going, what do you want me to do with the logs?

Regards,

[JimH]

You could read the bottom of the log to see why it is crashing.

Take DLNA (not DNLA) out of the picture until you have things working.

[jackolynn]

Sorry yes DLNA. Bottom of the log means nothing to me:

0577297: 5948: Reader: CInternetReader::DownloadFromHTTPURL: Success
0577297: 5948: Reader: CInternetReader::DownloadFromHTTPURL: Finish (1373 ms)
0577297: 5948: Reader: CInternetReader::Thread: Finish (1388 ms)
0577297: 3712: Reader: CInternetReader::Open: Finish (1388 ms)
0577375: 5708: Reader: CInternetReader::Open: Start
0577375: 5708: Reader: CInternetReader::Open: Opening http://192.168.1.116:9000/ContentDirectory.xml
0577375: 2656: Reader: CInternetReader::Thread: Start
0577375: 2656: Reader: CInternetReader::Connect: Start
0577375: 2656: Reader: CInternetReader::Connect: Finish (0 ms)
0577375: 2656: Reader: CInternetReader::DownloadFromHTTPURL: Start
0577375: 2656: Reader: CInternetReader::DownloadFromHTTPURL: Success
0577391: 2656: Reader: CInternetReader::DownloadFromHTTPURL: Finish (16 ms)
0577391: 2656: Reader: CInternetReader::Thread: Finish (16 ms)
0577391: 5708: Reader: CInternetReader::Open: Finish (16 ms)
0577391: 5708: Reader: CInternetReader::Close: Start
0577391: 5708: Reader: CInternetReader::Close: Finish (0 ms)
0577391: 5708: Reader: CInternetReader::Open: Start
0577391: 5708: Reader: CInternetReader::Open: Opening http://192.168.1.116:9000/ContentDirectory/Control
0577391: 592: Reader: CInternetReader::Thread: Start
0577391: 592: Reader: CInternetReader::Connect: Start
0577391: 592: Reader: CInternetReader::Connect: Finish (0 ms)
0577391: 592: Reader: CInternetReader::DownloadFromHTTPURL: Start
0587453: 592: Reader: CInternetReader::DownloadFromHTTPURL: Success
0587453: 592: Reader: CInternetReader::DownloadFromHTTPURL: Finish (10062 ms)
0587468: 592: Reader: CInternetReader::Thread: Finish (10077 ms)
0587468: 5708: Reader: CInternetReader::Open: Finish (10077 ms)
0587733: 5708: Reader: CInternetReader::Close: Start
0587733: 5708: Reader: CInternetReader::Close: Finish (0 ms)
0587827: 5708: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
0587827: 5708: General: TopLevelExceptionFilter: Message: 0, wParam: 0, lParam: 0, Window class:

[JimH]

Try a local library, without using DLNA.

[jackolynn]

That seems to keep the software going.  But how do I get it to work again with the DLNA server as that is the main purpose I have bought MC and it's been working fine for ages in 15 and until recently in 16?

[JimH]

I would try powering everything down and back up.  Including any network equipment.

Does MC15 still work?  If so, what's different?  Settings?

Did the NAS firmware get updated?  If not, have you tried that?  What device is it?

[jackolynn]

I have completely uninstalled MC15 & MC16 and reinstalled both.  I have powered the PC and all network equipment down and rebooted.  The NAS is a WD MyBookWorld  Edition II, with the most up to date firmware.  It runs Twonkymedia server 5.1.9.

MC15 connects to my DLNA library fine, MC16 crashes as soon as it starts to load the DLNA library.  As far as I can tell there are no differences in settings as the only thing I have done in both the new install of 15 & 16 is turn on the DLNA server (MC15 Tools/Options/Media Network/ tick "DLNA server"; & MC16 Tools/Options/Media Network/ tick use media network to share this library and enable DLNA) and load the library.

Any ideas?

[bob]

I have completely uninstalled MC15 & MC16 and reinstalled both.  I have powered the PC and all network equipment down and rebooted.  The NAS is a WD MyBookWorld  Edition II, with the most up to date firmware.  It runs Twonkymedia server 5.1.9.

MC15 connects to my DLNA library fine, MC16 crashes as soon as it starts to load the DLNA library.  As far as I can tell there are no differences in settings as the only thing I have done in both the new install of 15 & 16 is turn on the DLNA server (MC15 Tools/Options/Media Network/ tick "DLNA server"; & MC16 Tools/Options/Media Network/ tick use media network to share this library and enable DLNA) and load the library.

Any ideas?

Am I getting it straight that it works in 15 and not 16?

[jackolynn]

Yes MC15 loads the DLNA library fine and plays no problem.  Try to do the same with MC16 and the program crashes.

[bob]

Could you do a wireshark dump from the PC while loading trying to load the library from the NAS?
http://www.wireshark.org/download.html
When you get it installed, start it up, do capture->options, make sure the interface is your ethernet card and in the filter box type
host 1.2.3.4 and host 5.6.7.8
where 1.2.3.4 is changed to the ip of your PC and 5.6.7.8 is changed to the ip of your NAS.
Click start
go back to MC
try to load the NAS library
wait a couple of seconds after the crash
go back to wireshark
hit the stop button (fourth in from the left)
do file->save as
put in somename. It will be saved as somename.pcap
email the file to bob (at) jriver (dot) com.

Thanks..

[DSKO]

I have the same problem in MC v16.0.111, together with Twonky Server v6.0.32 for Windows, installed on my Windows Home Server.

And this bug is definitively introduced in MC v16.0.111.

On version 16.0.111, MC crashes a minute or two after startup, when the Twonky DLNA library is loaded.
This pattern started only after updating to v16.0.111 (from v16.0.110),
and this is consistent on 3 PC-s running v16.0.111.

On all these 3 PC-s; If I'm quick and unload the Twonky DLNA library right after startup,
MC continues to run without crashing.

On my 4th PC, I still have MC v16.0.110 (Twonky DLNA library loaded),
and this instance is running OK without crashes.

Espen

[bob]

Can you guys try 16.0.115 and see if that solves the problem??

[Matt]

Bump.  We're hoping for feedback on whether this problem still exists in the latest build.

Thanks.

[DSKO]

Thanks, it seems it doesn't crash in build 16.0.116.

Espen

[jackolynn]

Just managed to load the DLNA library and no crashes yet!

Thanks,

[MrC]

Bump.  We're hoping for feedback on whether this problem still exists in the latest build.

Thanks.

In case this problem, and this crash, were the same or related, no crashes either since .112.