DescriptionLogos crashes upon startup
Steps to reproduce
Actual ResultIt crashed
Expected ResultInstead of crashing, i expected it to open the passage guide to those verses
System SpecsLaptop | Windows Experience Index: 3.4 | Intel Core Duo 2 L9400 @1.86 GHz | 3GB RAM | 12" monitor at 1280 x 800 | Mobile Intel RMA 4500MHD | 128 GB SSD | Windows 7 Ultimate 32bit - all patches. | Microsoft Security Essentials– up to date
Comments7673.Logos4Crash.zipWhen it crashed the first time, it apparently had not yet saved the layout, so I could open it and I tried reproducing the problem by going to each of the verses in the passage guide (Luke 8:4, Luke8:5, etc) and no particular verse caused the crash. I then tried various ranges (Luke 8:4-8, Luke 8:8-15 etc) and those also did not cause the crash. I then tried specifically Luke 8:4-15 and it crashed again and this time it saved the layout so now it crashes upon opening.
You can bypass the crash on opening by holding down the Ctrl key which forces you to log in again and on the login screen you can choose to start up with no layout. Do this. Then see if you can reproduce the initial crash by going to Luke 8:4-15 again. I'm able to do it without crashing.
The error message in your log file is "No imaging component suitable to complete this operation was found." This has been attributed to video driver problems causing a crash in WPF, the platform Logos is built upon. You could try updating to the latest video driver or rolling back to a previous version. There's more info in this thread: http://community.logos.com/forums/t/10428.aspx
If you have no luck with that, I think it's time to call Customer Service.
How to Ask for Help | Logos Wiki | My Machine Specs | My Blog
Is the problem still occurring?