Logos 4 Crashes when Launched

Bill,

We'll need logs. You should have some from the Ctrl key event. They are in your My Documents\Logos Log File folder.

See http://wiki.logos.com/Diagnostic_Logging for how to enable permanganate diagnostic logging and how to attach these logs to a follow-up message.

https://community.logos.com/discussion/comment/336728#Comment_336728

8780.Logos4Error.log 3426.Logos4.log 6237.Logos4Error-2.log 51473.Logos4Crash.txt 4812.Logos4IndexerCrash.txt

Here are the logs...

https://community.logos.com/discussion/comment/336734#Comment_336734

Bill, two of those files (Logos4Error-2 and Logos4IndexerCrash) are from long ago.

The other logs show the crash was due to:

"Error OurApp Unhandled exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

It seems to be trying to get resource info off your disc as it loads the program. I think it would be good if Logos looked at this. Perhaps someone will look in tonight. if not call Tech Support tomorrow. In the past, solutions to this problem were not straightforward. Sometimes corrupt resources caused it, sometimes processor overheating during indexing. You didn't submit an indexer log but it doesn't look like Logos was indexing when this crash occurred.

Someone else may remember a consistent cause and fix for this issue, I do not and in searching the forums cannot find one.

https://community.logos.com/discussion/comment/336734#Comment_336734

Here are the logs...

There is no consistent fix for this. A couple of suggestions:-

go to Control Panel >> Programs and Features, right click Logos 4 Bible Software and select Repair
if you have another working installation reinstall using Method 2 NB. remove the \Logos4 folder after uninstalling

Otherwise let Logos Support investigate on your computer.

https://community.logos.com/discussion/comment/336782#Comment_336782

Hey Mark,

Thanks. That actually makes sense. I restarted my box was was able to bring it up. I started a reindex build and boom an hour in it crashed.

https://community.logos.com/discussion/comment/336876#Comment_336876

Hey Mark,

Thanks. That actually makes sense. I restarted my box was was able to bring it up. I started a reindex build and boom an hour in it crashed.

Logs?

Did you consider either of my suggestions or have you contacted Logos Support?

https://community.logos.com/discussion/comment/337005#Comment_337005

I am working with support. I have too many notes and such to lose by a reinstallation.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/336876#Comment_336876

I restarted my box was was able to bring it up. I started a reindex build and boom an hour in it crashed.

The bug looks like an error in WPF itself, based on the call stack. Unfortunately, searching the Internet (to see if anyone else has run into this) turns up no results, so I have no suggestions for a workaround or a fix. I doubt that uninstalling and reinstalling will help.

Since it happened while rebuilding an index, there's a small possibility that your system is overheating (under load) and becoming destabilised. Tools like memtest86+ and Prime95 (see http://community.logos.com/forums/p/16836/128062.aspx#128062) can be used to try to detect hardware failures.

https://community.logos.com/discussion/comment/337138#Comment_337138

Since it happened while rebuilding an index, there's a small possibility that your system is overheating (under load) and becoming destabilised.

A few of the problems reported on the forum earlier with this error were traced back to processor overheating during indexing. I didn't catch that going on in Bill's log.

Bill, what are your computer specs? I had this problem on my former computer but it didn't happen the first time I used L4. It appeared after many months, perhaps because of the aging of the computer.

If you follow the instructions that Dave Hooten pointed to on the wiki, you will not lose your data by reinstalling. That procedure calls for backing the files up and then putting them back after reinstalling. Your data is also on Logos' servers and would be replaced after you reinstall. I'd prefer to use the method Dave pointed you to so nothing can go wrong.

I hope support can help you.

https://community.logos.com/discussion/comment/337138#Comment_337138

Thanks for your suggestion Bradley.

I check the temp on my processor...104(f)...it is a water cooled processor and stays pretty cool. I do not game or anything so it is over kill i know...but I thought it would be fun to build it that way. Also, various versions of Logos has been running for a few years on this computer without this issues.

Bill

https://community.logos.com/discussion/comment/337184#Comment_337184

Mark,

See my reply to Bradly about the specs...the processor is an i7 task manager reports 8 cores. But this machine stays pretty cool.

I think i will take your suggestion and reinstall...sigh

I hope that works. I will keep you posted...

Thanks, Bill

https://community.logos.com/discussion/comment/337233#Comment_337233

.the processor is an i7 task manager reports 8 cores

I don't think overheating is the problem. My i7 only uses about 50% of its CPU cycles under the toughest indexing.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/337284#Comment_337284

I don't think overheating is the problem.

That was a wild guess based on the problem being reported as happening intermittently. It could well be a red herring.

https://community.logos.com/discussion/comment/337303#Comment_337303

well...reinstalled and during indexing BOOM. CPU was at around 4%...this is a tech support thing for sure...

https://community.logos.com/discussion/comment/337323#Comment_337323

well...reinstalled and during indexing BOOM.

Sorry you are having so much trouble. I hope the techs can figure something out for you.

Peter Banks

I am seeing the same symptoms. I had some type of update yesterday I wonder if it is related?

https://community.logos.com/discussion/comment/337535#Comment_337535

I wonder if it is related?

Peter, please upload your logs. (See the instructions given earlier in this thread).

https://community.logos.com/discussion/comment/337564#Comment_337564

Just a thought...I started using the new IPAD notes feature this weekend. I wonder if it is related.

Graham Criddle

https://community.logos.com/discussion/comment/337693#Comment_337693

Hi Bill

Just a thought...I started using the new IPAD notes feature this weekend. I wonder if it is related.

With Bradley's post that this is a WPF-related issue I would think it very unlikely that it relates to the use of the iPad notes capabilities.

Graham

https://community.logos.com/discussion/comment/337696#Comment_337696

yea, just trying to think of everything that changed prior to the problem...

Peter Banks

https://community.logos.com/discussion/comment/337564#Comment_337564

I tried build blowing everything away and reinstalling.

A miniscule better but still crashes. I am not sure how to upload the files I do have some from last night.

https://community.logos.com/discussion/comment/338009#Comment_338009

I tried build blowing everything away and reinstalling.

A miniscule better but still crashes. I am not sure how to upload the files I do have some from last night.

Please study this article (for enabling and uploading) http://wiki.logos.com/Diagnostic_Logging

enable permanent logging
run L4 and wait until it crashes
upload logos4.log, logos4indexer.log (if there) and any crash/error logs

Peter Banks

https://community.logos.com/discussion/comment/338012#Comment_338012

0647.Logos Log Files.zip

Here is the zip sure glad I am not preaching on Sunday!

https://community.logos.com/discussion/comment/338024#Comment_338024

Peter,

Neither of those logs shows a crash. Logos and the Indexer seem to have been working just fine when those were produced (yesterday, by the way).

https://community.logos.com/discussion/comment/338042#Comment_338042

Just to complete the thread...this is the solution from Tech Support...from Steve Workman

Thank you for the logs. According to the logs it seems like you have a bad index file and a corrupt Library Catalog.

To remedy this first close Logos 4 then please right click on the Logos 4 icon and click properties. In Vista and Win 7 you should see a button listed as Open File Location, in XP you should see an option to Open Target Location. Please click that button. Please double click the Data folder. Open the next folder it's title is randomly generated. Delete the LibraryIndex, LibraryCatalog and BibleIndex folders.

Restart the program and it will recreate the folders without the issues. Let us know if you have any further concerns.

Thank you all for your help

Bill

https://community.logos.com/discussion/comment/338838#Comment_338838

Thanks for the feedback Bill.

https://community.logos.com/discussion/comment/338838#Comment_338838

Bill,

That was quite an ordeal. I'm sure you'll let us know if things go bad again.