Logos 4 Crash Report "Logos Bible Software has Stopped Working"
I am running the current version of Logos 4 in Windows 7 using parallels on my iMac. With 12 Gig of Ram, there is no ram problems. I have had no crash problems until the last update. Now, after I do a "passage guide" query, or if the program just sits open for longer than 2 minutes - the program turns a few shades of white and I get the message "Logos Bible Software has Stopped Working."
This has been happening for a few days now. I did get one error message report when it closed down a few minutes ago that read verbatim:
"The exception unknown software exception (0xe0434f4d) occurred in the application at the location 0x75x69617."
Any ideas?
Comments
-
Please enable Diagnostic Logging and then upload your logs. Some of us will take a look at them and we might be able to determine what is going on.
Even if some of us can't figure it out, the Devs will be able to use the logs as well, so they're useful.
Sarcasm is my love language. Obviously I love you. 0 -
Alright - here is my posted crash report:
0 -
Seems to be connected with reading your Notes so I'm hesitant to recommend deleting databases. Please contact Technical Support.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Seems to be connected with reading your Notes so I'm hesitant to recommend deleting databases. Please contact Technical Support.
To further explain, it looks like your notes database has become corrupted. The usual fix for corrupted databases is to delete the file, and allow Logos to re-create it (in this case by re-syncing with the Logos servers). However, notes are very important to most people, and Dave (nor I) want to take the responsibility of you possibly losing some or all of your notes! Hence the suggestion of contacting Tech Support.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0
