Logos crashes after upgrade to version 6

After the automatic upgrade from version 5 to 6, Logos crashes every time I try to open it.

It shows the splash screen and than starts to synchronise my documents and settings before crashing with the message "Logos Bible software has stopped working". The only option I have is to close it.

I have un-installed and re-installed Logos 6 with the installer, but still gets the same issue.

I cannot open Logos at all.

I have attached the log files as instructed.

Kind regards

Werner

4503.Logos Log Files.zip

Find more posts tagged with

Comments

Mike Binks

Hi Werner

Welcome to the forum.

I am no expert in reading logs but just to check!

Does your system meet these requirements?

Werner Peens

https://community.logos.com/discussion/comment/694013#Comment_694013

I am running Windows 8.1, 4GB RAM, HD Display, and still 51GB free on my SSD drive.

NB.Mick

https://community.logos.com/discussion/comment/694013#Comment_694013

Mike,

the Logs show Werner is running Win 8.1 with 4GB RAM and 75 GB free disk space.

The only error listed under Logos 6 was

Program Version: 6.0b SR-2 (6.0.2.0075)
Time: 2015-02-03 20:12:55 +08:00 (2015-02-03T12:12:55Z)
SQLite Error 539: recovered 6 pages from C:\Users\Werner\AppData\Local\Logos5\Documents\mekg15co.px5\UserPreferences2\PreferencesManager.db-journal

no crash in the logs and no crash log either.

Werner,

maybe restarting your computer may help, otherwise I see no reason for a crash (maybe someone can tell if it's an idea to delete the file referenced in the error.)

Mike Binks

https://community.logos.com/discussion/comment/694022#Comment_694022

Thanks NB and Werner

I shouldn't step above my pay grade?

But for my edification - why do the logs refer to Windows NT?

NB.Mick

https://community.logos.com/discussion/comment/694043#Comment_694043

why do the logs refer to Windows NT?

Ever since MS invented NT they kept this designation for thos OS versions based on it.

See http://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions

Bradley Grainger (Logos)

There's not a crash in the logs, so we'll need to see details from Windows Event Viewer. Or you can contact our Technical Support department for assistance.