BUG: Continual Crashing WIndows 10
Logos has been crashing at random today. I have not been able to pinpoint any similarities. It's usually though while I am not even doing anything just reading. I have attached logs.
Comments
-
Have you changed your Faithlife.com account password recently?
Try holding down Ctrl at startup to display the sign in dialog, then signing in again. This may clear out bad cached credentials that may be causing the problem.
If that doesn't work, you may have to hold down Ctrl at startup then click “Work offline” to disable all Internet features (including the one that is causing the crash).
0 -
Have you changed your Faithlife.com account password recently?
Try holding down Ctrl at startup to display the sign in dialog, then signing in again. This may clear out bad cached credentials that may be causing the problem.
If that doesn't work, you may have to hold down Ctrl at startup then click “Work offline” to disable all Internet features (including the one that is causing the crash).
Yes I recently had to change my password and have support do a global sign out because Logos was asking me to login at every open. I noticed this behavior started happening again today as well. Oddly enough, it just crashed again as I opened your response. Logs attached.
0 -
If signing in again didn't help, then you'll probably need to work offline for now. I apologise for the inconvenience.
We'll have a fix available soon (by 8.0 SR-2 or 8.1 Beta 2, possibly sooner).
0 -
If signing in again didn't help, then you'll probably need to work offline for now. I apologise for the inconvenience.
We'll have a fix available soon (by 8.0 SR-2 or 8.1 Beta 2, possibly sooner).
I did as you suggested and worked offline for about 10 minutes then signed back in. So far (praying) it has not crashed again. Glad to know a fix will be available.
0 -
David Taylor Jr said:
Logos has been crashing at random today. I have not been able to pinpoint any similarities. It's usually though while I am not even doing anything just reading. I have attached logs.
This has been fixed in 8.0 SR-1.
0
