Print

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

[StuckMojo]

I am testing MC 17.0.95 now.

I've two librarys.Main and Secondary.
When try to switch,MC 17 crashes with following Error Message:

"Problemsignatur:
  Problemereignisname:   APPCRASH
  Anwendungsname:   Media Center 17.exe
  Anwendungsversion:   17.0.95.0
  Anwendungszeitstempel:   4f481fc6
  Fehlermodulname:   clr.dll
  Fehlermodulversion:   4.0.30319.261
  Fehlermodulzeitstempel:   4ec9f6ff
  Ausnahmecode:   c00000fd
  Ausnahmeoffset:   00001ac6
  Betriebsystemversion:   6.1.7601.2.1.0.256.1
  Gebietsschema-ID:   3079
  Zusatzinformation 1:   7457
  Zusatzinformation 2:   74573db6db5e394a25cb5dc08e98dd77
  Zusatzinformation 3:   f35b
  Zusatzinformation 4:   f35b09278557879a20dc8ce19b7e8e8a"

Anyone else with this Problem?

Main Library:
Firts I added 3 HDD's with only Movies on them. No Problem.
When I added the 4 HDD with lots of different Filetypes,the Problem started.
On this HDD there are many Music Files(FLAC,MP3,SACD Rips,DVD Audio,...) and
many different Video Files (BluRay ISO,mkv,DVD,mp4,and many more).
So it's difficult for me to see,what causes the problem.

On the secondary library there are only Video Files.

MC is crashing in both directions.
Main to Secondary library.
Secondary to Main library.

It's driving me crazy! ?

With MC 16 I'm having this problem too.
It has been working for a while with MC16 without Problems.
Tried MC 17->Same Problem.
Now i made a clean Win 7 x64 install.
Installed MC 17.Without extra Direct Show Filters.
Adding HDD's,Creating Librarys again.
Same Problem again.

Can someone help.

Edit:
Could it be that waking up the HDD's when switching library is causing the problem?

[Alex B]

Is the crash always reproducible or does it happen only sometimes. Does it happen if you don't do anything before the crash (i.e. if you just start MC and try to switch the library)?

Perhaps MC's internal logging could tell something. Enabled logging in Help > Logging... After the crash open the previous log. It will contain all events that MC was able to log before the crash occurred. You could post the tail of the log here (or logs if the "Main to Secondary" log seems different from the "Secondary to Main" log).

You could also create a new empty library (perhaps import a file or two to it) and check if switching to/from it causes a crash as well.

[Alex B]

Edit:
Could it be that waking up the HDD's when switching library is causing the problem?

That should be easy to test. Can you reproduce the crash when the HDDs are running?

[StuckMojo]

So,changed Power save options for hdd ->No Change,still crashing.

When i play a video file,then stop and switch to secondary->Crash.
Restart MC17 Switch immediatly to secondary-> Ok.
Switching back to main->always crashing.

The difference is:
Main to Secondary->Crash->Restart->Main Library active->Switch to secondary->OK!
Secondary to Main->Crash->Restart->Main Library active (No more switching required)!

MC Logging seems to be ok.Shows no error.

I think it must be one of the files on the fourth HDD.But which one ?
Before importing this HDD nothing crashed.

Seems like will have to unload all files from this HDD and re-import Files "Bit by Bit".
Ufff Plenty of work to do!

[Matt]

Could you share the end of the previous log (Help > Logging) after a crash?  It should have the word 'crashing' in it.

[StuckMojo]

Searched for "crashing" in both Log Files but nothing found.

This is the end of the Log File after crashing:

_{0048485: 5772: Sharing Plugins: CTCPSocketReader::Read: Read failed: 10060 (socket: 3324)
0048485: 5772: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
0048485: 5988: Reader: CInternetReader::Open: ConnectToURL failed, timed out (2500 ms), URL=http://1.1.1.2:2869/upnphost/udhisapi.dll?content=uuid:08dcd026-454f-45f3-bfd6-d5cd625e84ab
0048485: 5932: Sharing Plugins: CTCPSocketReader::Read: Read failed: 10060 (socket: 3780)
0048485: 5932: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
0048485: 5932: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (14336 ms)
0048485: 668: Reader: CInternetReader::DownloadFromHTTPURL: HttpSendRequest error: 12002
0048485: 668: Reader: CInternetReader::DownloadFromHTTPURL: Failed (header status code: -1)
0048485: 668: Reader: CInternetReader::DownloadFromHTTPURL: Finish (14820 ms)
0048485: 668: Reader: CInternetReader::Thread: Finish (14820 ms)
0048485: 5772: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (16021 ms)
0048485: 548: Sharing Plugins: CTCPSocketReader::Read: Read failed: 10060 (socket: 3232)
0048485: 5988: Reader: CInternetReader::Close: Start
0048485: 4820: Sharing Plugins: CTCPSocketReader::Read: Read failed: 10060 (socket: 2644)
0048485: 4820: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
0048485: 4820: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (15475 ms)
0048485: 4164: Handheld: CWMDMThread::Thread: Enumeration succeeded -- processing results
0048485: 548: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
0048485: 4100: Sharing Plugins: CTCPSocketReader::Read: Read failed: 10060 (socket: 2492)
0048485: 4100: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
0048485: 4100: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (16115 ms)
0048485: 548: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (15678 ms)
0048485: 1876: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0048485: 1540: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0048485: 1876: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 1.1.1.2: GET: http://1.1.1.1:52100/DeviceDescription.xml
0048485: 2652: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0048485: 2652: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 1.1.1.4: SUBSCRIBE: http://1.1.1.1:52100/ContentDirectory/event
0048485: 2652: Sharing Plugins: VHTTPMessage::Write: Wrote 215 bytes
0048485: 2652: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
0048485: 1540: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 1.1.1.4: SUBSCRIBE: http://1.1.1.1:52101/ContentDirectory/event
0048485: 1540: Sharing Plugins: VHTTPMessage::Write: Wrote 215 bytes
0048485: 1540: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)}

[Matt]

If you turn off Media Network (Options > Media Network), does it fix the crashes when switching libraries?

[StuckMojo]

Sorry for the late answer.

I turned off Media Network->Crashing like before.
Tested with 17.0.155

[Matt]

Sorry for the late answer.

I turned off Media Network->Crashing like before.
Tested with 17.0.155

Please use 'Report a Problem' in Help > Logging, and email the zip file to logs at jriver dot com.

Thanks.

[glynor]

If you turn off Media Network (Options > Media Network), does it fix the crashes when switching libraries?

I haven't tested this in a while, but I have a bit of time to kill.

Want another log from me as well, while you're at it?

[Matt]

I haven't tested this in a while, but I have a bit of time to kill.

Want another log from me as well, while you're at it?

If it's a crash with a dump file in the log, yes please.

[glynor]

If it's a crash with a dump file in the log, yes please.

Minutes were, unfortunately, decidedly not had as I'd expected.

Tomorrow, tomorrow, I love ya, tomorrow.  It should be easy to reproduce, unless it is magically fixed.

If you turn off Media Network (Options > Media Network), does it fix the crashes when switching libraries?

For StuckMojo:  Matt asked this because I've had the same, or a similar, problem that was "cured" by disabling the Media Network server on the machines in question.

I have two machines at the office that exhibit the problem, and another two that are fine.  I haven't figured it out, but yes, it has been a long-standing problem (I saw it with MC16 for sure).  Even wiping out the Windows install entirely on one of them didn't solve anything.

I've wondered if it is something specific to the network infrastructure, or network quirks specific to the machines in question.  But, if disabling the Media Network server doesn't solve your issue, perhaps they're two similar (related) but not identical issues.