Logos crashing every five minutes or at startup

Cannot work with Logos today. Very frustrating. Logos 5.2a SR-1 (5.2.1.0081) keeps crashing about every five minutes now, as well as a few times at startup.

I've also found strange problems with the Library in between these crashes. One was that no filters would work except basic filters on resource titles. But a few crashes later and it now works on filtering using mytags which didn't work before. Also, I had a 'Rank' column displayed for some time to the far left, which could not be selected/removed.

If anyone can help me get Logos back to working order again (I use it every day, but it has only started playing up today), that would be great. Log files attached (with permanent logging already enabled).

50371.Logos.zip

Thanks

Find more posts tagged with

Comments

Dave Hooton

You have problems with a corrupt catalog index database at C:\Users\John\AppData\Local\Logos4\Data\aytx5cbw.n5q\LibraryCatalog. I recommend you delete all its files EXCEPT for the two catalog.db files.These should be rebuilt when Logos is restarted.

One of the crashes is related to your resource collections and I noticed some very long author: rules which create a lot of inefficient searches in the catalog. Look to simplifying these with rules based on other metadata like title, subject, type.

Bradley Grainger (Logos)

Based on the number and variety of the different crashes you've encountered today (some that I've never seen before as a .NET developer), I would strongly recommend running a hardware check on your system.

I've never used Windows Memory Diagnostic before, but it's built into Windows and easy-to-use: http://windows.microsoft.com/en-us/windows7/diagnosing-memory-problems-on-your-computer

Alternatively, memtest86+ is a great tool to run overnight for an extended stress test: http://www.memtest.org/

John Duffy

https://community.logos.com/discussion/comment/587871#Comment_587871

You have problems with a corrupt catalog index database at C:\Users\John\AppData\Local\Logos4\Data\aytx5cbw.n5q\LibraryCatalog. I recommend you delete all its files EXCEPT for the two catalog.db files.These should be rebuilt when Logos is restarted.

Thanks Dave - I tried that, and it lasted about 10-15 minutes before crashing, which was helpful but not a fix.

One of the crashes is related to your resource collections and I noticed some very long author: rules which create a lot of inefficient searches in the catalog. Look to simplifying these with rules based on other metadata like title, subject, type.

I looked into those, and found that they were the collections I imported from a Faithlife group (denom. streams, denominations, etc). I've them all, and so far it seems to be working fine. The fact that I was using the library pane a lot today (which I don't normally do), might have had something to do with it. I'll see how it goes tomorrow, but hopefully it'll work better than today.

Thanks again.

John Duffy

https://community.logos.com/discussion/comment/587896#Comment_587896

Based on the number and variety of the different crashes you've encountered today (some that I've never seen before as a .NET developer), I would strongly recommend running a hardware check on your system.

Hi Bradley, thanks for looking at the logs. I did some fairly extensive checking on the system a few months ago, including those which you've mentioned, and a lot more, and all was fine after I replaced the PSU (supplied by the PC manufacturer and which turned out to be a cheap and unreliable model, not the one I expected) for a top quality model. With everything else checking out fine on high stress tests, I would not expect them to be the root cause now, although they could well have gone suspect in the meantime.

I'll wait until I see the results of having deleted the collections which Dave noted, and report back on whether it is working more reliably.

Thanks for the pointers, though.

John Duffy

https://community.logos.com/discussion/comment/587913#Comment_587913

All was fine today, working with different resources, on and off all day. Then, to open a new resource, I pressed Ctrl+L to open the library pane. After about a second the computer crashed with a BSOD. The only thing, though, was that I immediately tried to move the library pane using the mouse, before it had properly loaded. That was just over an hour and a half ago. I've since loaded L5 and waited for the library pane to load, and it's fine. But it's been fine in the last few minutes (I was away from the PC for a good while in between).

Yesterday I was working extensively with the library when I experienced crashes too.

I've attached the log files if that helps.

5353.Logos (2).zip

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/588109#Comment_588109

the computer crashed with a BSOD

This indicates you almost certainly have faulty hardware (or possibly bad drivers); it's basically impossible for a "user mode" application (like Logos 5) to take down the entire system with a BSOD.

As stated before, I think bad RAM is the most likely culprit.

Dave Hooton

https://community.logos.com/discussion/comment/588109#Comment_588109

Then, to open a new resource, I pressed Ctrl+L to open the library pane. After about a second the computer crashed with a BSOD.

The error log shows that the earlier "corrupt" Catalog index issue has not repeated (because you deleted the imported author: collections?). But there are still crashes related to collections and the catalog index, an unexpected crash + the BSOD which point to hardware issues. Here's another comment from Bradley.

EDIT: I just saw that I didn't have to quote Bradley!

John Duffy

https://community.logos.com/discussion/comment/588171#Comment_588171

Bradley, Dave, that makes sense. I'll chase up hardware issues and see what I can do.

Many thanks for your analysis