Crashes while opening

Running Windows 10 and just updated the Office 365 and now I'm getting the error that is Logos Bible Software has stopped Working and will close. I've tried holding down the CTRL and running it as Administrator, but still get the crash each time. I've tried several times and rebooted. Still no luck. Opening screen shows then get the crash message.

1440.Logos Log Files.zip

Find more posts tagged with

Comments

Graham Criddle

Hi David - and welcome to the forums

Sorry to hear you are having problems.

There is nothing in the Logos logfile that I can see indicating a problem. Please check if there is any relevant information in the Windows Event Viewer - details at https://community.logos.com/forums/t/124126.aspx

and running it as Administrator

Logos is designed to run in User mode so running as Administrator rarely helps and can cause issues

Graham

Dr. David E. Graves

https://community.logos.com/discussion/comment/820563#Comment_820563

Hi Graham,

Here is the event log.

Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at Libronix.DigitalLibrary.Resources.Logos.NativeMethods.TitleLoader_LoadTitle(Libronix.DigitalLibrary.Resources.Logos.SafeTitleLoaderHandle, System.String, IntPtr, System.String, Libronix.DigitalLibrary.Resources.Logos.TitleLoadHint)
   at Libronix.DigitalLibrary.Resources.Logos.LogosResourceCore.Create(Libronix.DigitalLibrary.Resources.Logos.LogosResourceDriver, Libronix.DigitalLibrary.LicenseManager, System.String, System.String, System.String, Libronix.Utility.Threading.IWorkState)
   at Libronix.DigitalLibrary.Resources.Logos.LogosResourceDriver.CreateResourceCore(System.String, System.String, System.String, Libronix.Utility.Threading.IWorkState)
   at Libronix.DigitalLibrary.Resources.Logos.LogosResourceDriver.DiscoverResource(System.String, Libronix.Utility.Threading.IWorkState, Libronix.DigitalLibrary.Resource ByRef)
   at Libronix.DigitalLibrary.Resources.Core.LocalFileResourceDiscoverer+<DiscoverResourcesCore>d__1.MoveNext()
   at Libronix.DigitalLibrary.ResourceManager.DiscoverResources(Libronix.DigitalLibrary.ResourceDriver, System.Collections.Generic.HashSet`1<Libronix.DigitalLibrary.DiscoveredResourceInfo>, System.Collections.Generic.IReadOnlyCollection`1<Libronix.DigitalLibrary.ResourceFileInfo>, System.Collections.Generic.HashSet`1<System.String>, Libronix.Utility.Threading.IPausableWorkState)
   at Libronix.DigitalLibrary.ResourceManager.DiscoverResources(Libronix.Utility.Threading.IPausableWorkState, System.Collections.Generic.Dictionary`2<Int64,System.Collections.Generic.HashSet`1<Libronix.DigitalLibrary.DiscoveredResourceInfo>>, System.Collections.Generic.HashSet`1<System.String>, System.Collections.Generic.IEnumerable`1<ResourceDriverInfo>)
   at Libronix.DigitalLibrary.ResourceManager.DiscoverResourcesThread(Libronix.Utility.Threading.IPausableWorkState, DiscoveryData)
   at Libronix.Utility.Threading.WorkStateThreadOwner`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ThreadProc(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart(System.Object)

PS I have to run it as administrator or it won't update my books.

regards,

Dr. Graves

JT (alabama24)

https://community.logos.com/discussion/comment/820615#Comment_820615

PS I have to run it as administrator or it won't update my books.

I am not a windows user, so haven't dealt with this issue (thankfully). It is frustrating to me as someone who helps out in the forums... I am sure it must be even more frustrating to you! [:s]

The "official" word from FL is that you should not run as "administrator." I know there are certain issues which can pop up if you do run in that mode. It might be good to try to fix the other issue (when you have time), else it is like driving your car with the door duck taped on. [:P]

Dr. David E. Graves

https://community.logos.com/discussion/comment/820623#Comment_820623

I was told to run it in admin to get the books to update. Something to do with one of the files needing admin rights to update properly. I didn't get the impression this was a flaw just a permissions issue.

JT (alabama24)

https://community.logos.com/discussion/comment/820625#Comment_820625

I was told to run it in admin to get the books to update.

You were told this by Faithlife? If so, that would be good to know... but goes against what I have read before.

Dr. David E. Graves

https://community.logos.com/discussion/comment/820637#Comment_820637

Yes Faithlife tech support when I was having difficulty installing and uploading my books. It is not a good practice to run any program as administrator, (from a past life as an IT administrator :-). But it is necessary, on occasion, to do an install as you must have access to certain files that only admin can access.

Dr. David E. Graves

https://community.logos.com/discussion/comment/820625#Comment_820625

I just opened my books and it is stable and has not crashed so far. I did not restart my computer last night but only put it to sleep disconnected from the internet. It appears to have been something on Logos server synchronization. I will keep you posted. thanks

Dr. David E. Graves

https://community.logos.com/discussion/comment/820563#Comment_820563

Fault bucket 120468853286, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Logos.exe
P2: 6.11.0.41
P3: 5728fbde
P4: VCRUNTIME140.dll
P5: 14.0.23506.0
P6: 563c45c0
P7: c0000005
P8: 000000000000c901
P9:
P10:

Attached files:
C:\Users\David\AppData\Local\Temp\WERD045.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Logos.exe_7cd8d5faa5c1f2b41b6597aa260586fcaa77671_942830b6_0c95e506

Analysis symbol:
Rechecking for solution: 0
Report Id: a9044774-3f7a-4251-bbc3-edd1921e0725
Report Status: 0

ERROR

Dr. David E. Graves

https://community.logos.com/discussion/comment/820690#Comment_820690

I reinstalled the Logos 6 Core Engine and it runs and opens but then after a few minutes it crashes. I wonder if the synchronization of Athanasius: On the Incarnation of the Word of God (with audio) is crashing it as there is still one syn showing? Just a thought.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/820704#Comment_820704

I wonder if the synchronization of Athanasius: On the Incarnation of the Word of God (with audio) is crashing it as there is still one syn showing? Just a thought.

Please attach zip file with Logos diagnostic logs.

Is Windows up to date ? (just restarted Windows 10 to install an update)

Is network stable ? (or changing)

Keep Smiling [:)]

Dr. David E. Graves

https://community.logos.com/discussion/comment/820740#Comment_820740

Zip file is attached to first post.

Windows has been restarted several times and up to date.

My network is stable (Rogers in Toronto).

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/820704#Comment_820704

I reinstalled the Logos 6 Core Engine and it runs and opens but then after a few minutes it crashes. I wonder if the synchronization of Athanasius: On the Incarnation of the Word of God (with audio) is crashing it as there is still one syn showing? Just a thought.

After reinstall of Logos 6 core engine and subsequent crash, would like to look at Logos Diagnostic Log files that correspond with Event Viewer crash. Likewise would to see if LogosError.log has more entries to consider.

Keep Smiling [:)]

Dr. David E. Graves

https://community.logos.com/discussion/comment/820754#Comment_820754

Did a complete reinstall and reindex of my library and thing seem to be back to normal. Will see once everything is loaded back on but so far so good. Seemed to be a corrupt book collection that crashed the system when loaded.