crashes immediately after start-up
When I start-up logos, I get the start-up page unpopulated and the message"program has stopped responding."
Comments
-
I think the problem is in your updates.db If that is the problem, it can be deleted and then when you start the next time that database will be rebuilt. HOWEVER, I AM NOT a log expert so I would not try that until someone with more knowledge of how to identify problems in the log has a chance to review.
0 -
I don't see a updates.db file.
0 -
Here is the path to its location
C:\Users\username\AppData\Local\Logos\Data\random\UpdateManager\Updates.db-journal
0 -
If FredC's instructions don't fix the problem please include Event Viewer logs immediately after the crash.
After Logos crashes open the Event Viewer (http://windows.microsoft.com/en-us/windows/open-event-viewer#1TC=windows-7) and navigate to Windows Logs>Application. It might take a while for the window on the right to populate.
Once it does, look for error messages. Please select the error messages and any adjacent messages together, select the “Action” menu and select “Save selected events.” Then attach the files to a reply post. Please also send me the text from any adjacent messages where they source is Windows error Reporting.
I'm not sure if our forums support this file type to be uploaded so if it doesn't please copy and paste the text from each message to individual text files and post those instead.
0 -
FredC's instructions did not fix the problem. I am attaching what I hope is the information you requested.5658.Logos Log Files.txt
0 -
It appears that you have Lavasoft Ad-Aware Web Companion installed. This program is not compatible with Logos 6 and will cause it to crash at startup. Uninstalling it should fix the problem.
0 -
Same problem, but I just updated Logos.
Is this what you need for a diagnosis (below)?
Thanks!
John
0 -
Hi John - and welcome to the forums.
Looks like a different problem.
Please start a new thread, enable diagnostic logging as per https://www.logos.com/support/logos6/windows/report-problem and post logs to that thread after a crash
Graham
0 -
Ok. Thanks.
0
