HELP! Crash: "Logos Bible Software 5 has stopped working"

Help!!

For no accountable reason Logos5 has started crashing.

This has happened every time I have opened the program (5 times now) in the past 20 mins, and occurs whether idle or in use. The screen mists over and a system dialog box opens telling me to close the program.

Anyone able to help me diagnose/fix the problem - with Sunday coming up I really need my resources today.

Thanks,

Stephen.

Find more posts tagged with

Comments

Fred Chapman

Help!!

For no accountable reason Logos5 has started crashing.

This has happened every time I have opened the program (5 times now) in the past 20 mins, and occurs whether idle or in use. The screen mists over and a system dialog box opens telling me to close the program.

Anyone able to help me diagnose/fix the problem - with Sunday coming up I really need my resources today.

Thanks,

Stephen.

The only way to try and diagnose the problem is with logs. http://wiki.logos.com/Diagnostic_Logging

Stephen Harper

https://community.logos.com/discussion/comment/426535#Comment_426535

Thanks - I knew how to start with a blank layout that way, but didn't realise it automatically started logging.

Just crashed another twice since posting my first message

Fred Chapman

https://community.logos.com/discussion/comment/426539#Comment_426539

Thanks - I knew how to start with a blank layout that way, but didn't realise it automatically started logging.

Just crashed another twice since posting my first message

Please post the logs when you can

Stephen Harper

https://community.logos.com/discussion/comment/426539#Comment_426539

So here is my error log. It means nothing to me. Can anyone shed any light on the problem?

Thanks,

Stephen8562.Logos4Crash.zip

Fred Chapman

https://community.logos.com/discussion/comment/426546#Comment_426546

So here is my error log. It means nothing to me. Can anyone shed any light on the problem?

Thanks,

Stephen8562.Logos4Crash.zip

This crash log is over a year old and is for L4.3 Please review the wiki page I provided a link for above and enable logging for your current installation.

Stephen Harper

https://community.logos.com/discussion/comment/426550#Comment_426550

Sorry - I couldn't figure out what happened, but then I realised that "My Documents" is on a separate partition but Logos creates the folder in the system directory, so I was thrown by the fact that there was an old folder from an earlier installation .

The correct og is now attached. Sorry, again.7801.LogosCrash.zip

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/426568#Comment_426568

This looks to be the same problem as one reported yesterday that was caused by a minor corruption in notes; we're investigating further.

In the meantime, I have been able to push out a fix to you via sync; the next time your computer syncs, you should get updated data that prevents the crash.

Stephen Harper

https://community.logos.com/discussion/comment/426592#Comment_426592

Thanks for your prompt attention. I'll see how that goes.

Stephen.

Fred Chapman

https://community.logos.com/discussion/comment/426592#Comment_426592

This looks to be the same problem as one reported yesterday that was caused by a minor corruption in notes; we're investigating further.

In the meantime, I have been able to push out a fix to you via sync; the next time your computer syncs, you should get updated data that prevents the crash.

Thanks Bradley

Joseph Palermo

https://community.logos.com/discussion/comment/426676#Comment_426676

6283.LogosCrash.zip

Getting the same error; logs attached, please advise.

Joseph Palermo

https://community.logos.com/discussion/comment/470528#Comment_470528

Problem solved - I'm currently in Afghanistan and the net connection is too slow (causing a crash). Disabling "go online" solved the crash. I'll simply start using the online feature once I'm back in the US.

fgh

https://community.logos.com/discussion/comment/470565#Comment_470565

Disabling "go online" solved the crash. I'll simply start using the online feature once I'm back in the US.

Then you need to think through your backup strategy, or you'll lose all your notes and stuff if something happens to your computer.

Joseph Palermo

https://community.logos.com/discussion/comment/470576#Comment_470576

No issues - I don't use those features. I simply use the program as a glorified Adobe reader or Kindle to access my commentaries.

Michel D. Mahler

I had the same problem happen to me today. Here is what worked for me (I am running Windows 7 on a PC so your computer may be slightly different if using a Mac or a different operating software):

1. Go to your list of programs and find your Logos icon (might also work if you have the Logos icon on your desktop).

2. Right-click and click on "Open file location".

3. Look for the folder named "Documents".

4. Right-click and click "Rename" (there should now be a box around the name of the file).

5. Place a "1" after "Documents" so your new file name will be "Documents1"

6. Close the window.

7. Try to restart Logos.

In my case, Logos started synchronizing (took several minutes) and then Logos opened with no issues.

I home this helps someone else in the future. The tech on the phone said several have had this problem but they aren't quite sure what is causing it yet.

Dave Hooton

https://community.logos.com/discussion/comment/475103#Comment_475103

I had the same problem happen to me today. Here is what worked for me

Michael

Please don't publish fixes unless you are sure you had exactly the same problem. "Crashing" or "Crashing at start" can happen for a variety of different reasons and renaming the Documents folder is a brute force approach as it affects ALL your documents, forcing them to be re-downloaded (Sync'd) from the Logos server and it may fix nothing.

Anthony U

https://community.logos.com/discussion/comment/475152#Comment_475152

I had the same issue and did a system restore to a prior date. That worked perfectly without having to do anything else. I hope this will help you. Blessings.

Dave Hooton

https://community.logos.com/discussion/comment/475220#Comment_475220

I had the same issue and did a system restore to a prior date. That worked perfectly without having to do anything else. I hope this will help you. Blessings.

[*-)]

Fred Chapman

https://community.logos.com/discussion/comment/475225#Comment_475225

I had the same issue and did a system restore to a prior date. That worked perfectly without having to do anything else. I hope this will help you. Blessings.

[:)]

Michel D. Mahler

https://community.logos.com/discussion/comment/475152#Comment_475152

Dave,

Thanks. Understood. I won't post anymore. Should someone do this I would hope that if it didn't work they would simply go back in and remove the "1" from the end of the file they added it to and things would be no worse than before.

To be fair, are any of us posting in this forum absolutely sure we have exactly the same problem ? I am new here, but I thought that was what the forum was for...suggesting possible fixes for problems. There are a lot of other people suggesting "fixes" in this forum and many people post that they've tried them and they didn't work. I'm just not sure why you are singling me out to say I shouldn't post. I'm just trying to be helpful and listed (very carefully) the same steps that the customer support instructed me to follow.

Dave Hooton

https://community.logos.com/discussion/comment/475378#Comment_475378

I'm just not sure why you are singling me out to say I shouldn't post. I'm just trying to be helpful and listed (very carefully) the same steps that the customer support instructed me to follow.

Fred had asked Stephen for logs on two occasions, stating that they were necessary to diagnose the "crash". Then Bradley (Logos) had stated what the problem was and had initiated a fix for some Notes. So my "singling" was connected with this chain of events and the fact that a specific solution had already been offered.

One user had applied two fixes that I had suggested for two other crashes without success, until I suggested that a reboot would fix their crash (and it did!).

To reiterate then, a "crash" is not a specific problem and each one has to be diagnosed from logs, as was your crash, and a specific fix is recommended.

There are a lot of other people suggesting "fixes" in this forum and many people post that they've tried them and they didn't work.

Both Bradley and I have posted about "generic" fixes like re-indexing which do no harm except take a long time for no result! Unless the suggestion comes from an analysis of the logs it is always going to be a guess e.g. I didn't know the cause of one crash but I remembered a "similar" crash and wondered if it was the "same". The two logs were the same and I was able to suggest the same fix (successfully!).