BUG: L5 crashes when opening NT221 videos

Description

Since the Logos/Faithlife server/database crashes I have not been able to open the NT221 video resource without Logos 5 crashing. The text resource for NT221 opens and is function until I click on an embedded link to the video resource.

Steps to reproduce

I have attempted to open NT221 video resource through click the library icon, by opening a saved layout, and by using the command box with "open NT221" and clicking the video resource.

Actual Result
Each time I get this error:

Expected Result
Instead of crashing I expected Logos to play the video segment. For clarification, I had played these videos prior to the server meltdown at Logos.

System Specs
Dell 1747 laptop. 6GB RAM, 256GB Samsung SDD, 30GB Patriot SDD, ATI Mobility Radeon HD 4650 display adapter

Comments
I removed the two resources from "C:\Users\Mark\AppData\Local\Logos5\Data\tixglsbe.e4v\ResourceManager\Resources", and downloaded them again with the command "update resources", with the same crashing lack of success. I also shut down and restarted (lots and lots of times). I'm attaching log file.

1537.Logos.log

Find more posts tagged with

Comments

Graham Criddle

Since the Logos/Faithlife server/database crashes I have not been able to open the NT221 video resource without Logos 5 crashing. The text resource for NT221 opens and is function until I click on an embedded link to the video resource.

Strange - I've just tried it on 6.0a (I no longer have a V5 installation) and it works fine there.

I can't see any indication of an error in the log - was there anything in the Windows event viewer at the time?

Brother Mark

https://community.logos.com/discussion/comment/668586#Comment_668586

Strange - I've just tried it on 6.0a (I no longer have a V5 installation) and it works fine there.

I can't see any indication of an error in the log - was there anything in the Windows event viewer at the time?

Nope. The usual Windows conclusion:

and a fresh log for comparison: 3414.Logos.log

Bradley Grainger (Logos)

There's no error in the log files, which usually means it's only recorded in Event Viewer. Pasting the crash details from the event log might help us diagnose the problem.

(If you don't know what that means, you can contact CS, ask them to capture a crash dump, and reference this thread.)

Brother Mark

https://community.logos.com/discussion/comment/668688#Comment_668688

There's no error in the log files, which usually means it's only recorded in Event Viewer. Pasting the crash details from the event log might help us diagnose the problem.

(If you don't know what that means, you can contact CS, ask them to capture a crash dump, and reference this thread.)

Thanks for your response Bradley, here's a capture of the relevant event error:

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/668951#Comment_668951

The "faulting modules" is mfmp4srcsnk.dll; this is a Microsoft component (that we use for playing media) so we may not be able to fix or work around this issue. (I did notice a lot of hits about crashes when I googled for mfmp4srcsnk so it seems like this may not be an uncommon problem, although I don't know how reliable the suggested fixes on the Internet would be; there's often a lot of misinformation out there.)

Did you install any Windows Updates or other software before this crash started happening? Perhaps there's a recent update that introduced the problem that could be uninstalled?