INTERACT FORUM
More => Old Versions => Media Center 16 (Development Ended) => Topic started by: james_smith1976 on March 03, 2011, 09:20:42 am
-
I've been using MC16 to sync with a micro SD card on my Blackberry Bold (principally to do a FLAC -> WMA encode).
It works 'ok' - it seems a lot more stable than MC14 anyway, which used to crash all over the shop during a device sync.
However, after @2-3 hours of snycing (I have ~30 GB to transfer so it takes a while) MC throws up a C++ Runtime error...
'Runtime Error!
Program: ...Files (x86)\J River\Media Center 16\Media Center.exe
This application has requested the Runtime to terminate in an unusual way...' blah blah blah, you know the drill.
This has happened a few times now. Any ideas what’s causing the issue? I’ve initiated a log now, so if/when it happens again I could potentially submit it…
Another question on syncing - if I try and run all 4 cores at the same time, MC quickly crashes. Is there a fundamental problem trying to use 4 cores for processing or should this work? It would greatly reduce my sync time if it worked...
-
I've been using MC16 to sync with a micro SD card on my Blackberry Bold (principally to do a FLAC -> WMA encode).
... if I try and run all 4 cores at the same time, MC quickly crashes. Is there a fundamental problem trying to use 4 cores for processing or should this work?
Using 4 cores should work unless the encoder has a problem. But the sync speed is probably limited by the connection, so try using just one process at a time.
-
Hi Jim. Setting 4 simultaneous processes *usually* leads to a crash ("MC has stopped working...") as soon as the format conversion/transfer process starts (i.e. immediately ater the file check). If it manages to start the format conversion process without a crash, it seems to be ok (aside from the inevitable C++ error after an hour or so). I think I get various different crash records, but for example:
Problem signature:
Problem Event Name: BEX
Application Name: Media Center 16.exe
Application Version: 16.0.42.0
Application Timestamp: 4d6ed220
Fault Module Name: enc_main.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4d6eb1d1
Exception Offset: 0942fd81
Exception Code: c000001d
Exception Data: badc0de1
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: d41d
Additional Information 2: d41d8cd98f00b204e9800998ecf8427e
Additional Information 3: b3fb
Additional Information 4: b3fb93f3e62b3dd9ff114e4c2630e98a
I continued to get C++ errors every couple of hours on my sync. I checked the log file immediately after a crash, but there's nothing suspicious in there.