I was working and got a "not responding message" then a faded screen. When I clicked to close and restart I received a "Logos has stopped working message". It did not generate a Crash log or an Error log.
5280.Logos.zip
Post the text from Windows Event Viewer
There are two errors associated with this event:
The first is an Application Error
Faulting application name: LogosCEF.exe, version: 1.2.1.6, time stamp: 0x5550ff9c
Faulting module name: libcef.dll, version: 3.2272.2077.1, time stamp: 0x5526e6e8
Exception code: 0xc0000005
Fault offset: 0x00000000004e9d92
Faulting process id: 0x1b40
Faulting application start time: 0x01d09e29759e47c8
Faulting application path: C:\Users\Fred\AppData\Local\Logos\6.4.0.0021\LogosCEF.exe
Faulting module path: C:\Users\Fred\AppData\Local\Logos\6.4.0.0021\libcef.dll
Report Id: dd797954-0b18-11e5-8278-f8a9637b8339
Faulting package full name:
Faulting package-relative application ID:
The second is identified as an Application Hang
The program Logos.exe version 6.4.0.21 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 240
Start Time: 01d09e2794ba7586
Termination Time: 58
Application Path: C:\Users\Fred\AppData\Local\Logos\6.4.0.0021\Logos.exe
Report Id: da34c0f9-0b18-11e5-8278-f8a9637b8339
If this is reproducible, we'd like to collect a Hang Dump (see https://wiki.logos.com/ProcDump). If not, then unfortunately neither the log nor Windows Event Viewer contain enough information to know why it was hanging.
Unfortunately I have not been able to reproduce it. If it happens again I will take note of everything that was open and exactly what I did when it occurred.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
