Logos Bible Software has stopped working (Logos 6 on Windows 8.1)

Windows error message: Bible Software has stopped working (Logos 6 on Windows 8.1)

Logos 6 crashes (log files attached). I tried uninstalling and downgrading to Logos 5 but when I do it tells me an upgrade is required.

8030.Logos Log Files.zip

Find more posts tagged with

Comments

JT (alabama24)

Welcome! sorry for your troubles. [:s]

I am not near a computer to look at your logs now... Hopefully a techie will be by soon. I did want to clarify: deleting the software is generally pointless unless you also delete all of the user files. The warning that an update is required" indicates that you just deleted the software engine rarher than a complete uninstall. I Don't think you should do that, by the way.

one quick suggestion: did you try loading to a blank layout? i believe the windows procedure is to press and hold the control key immediately upon startup.

Bradley Grainger (Logos)

I don't see an error in the logs; this may mean we need more information from Windows Event Viewer. Or you can call technical support for assistance when they open tomorrow.

In case it helps, I've recently seen crashes caused by incompatibilities with FL Studio, Lavasoft Web Companion, and PicColor Utility or ColorMedia64 (malware). If you have one of those programs, you may need to uninstall or disable it.

Ted Dang

I don't have any of those programs. Windows Event Viewer showsa .NET Runtime unhandled exception:

Log Name:      Application
Source:        .NET Runtime
Date:          2/11/2015 6:27:18 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DANGER-X1-C
Description:
Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 000000EF18737E70
Stack:

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-12T02:27:18.000000000Z" />
    <EventRecordID>4510</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DANGER-X1-C</Computer>
    <Security />
</System>
<EventData>
    <Data>Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 000000EF18737E70
Stack:
</Data>
</EventData>
</Event>

Ted Dang

I think it has something to do with resources that have been converted to Logos 6? When I uninstall 6, and delete C:\Users\[user name]\AppData\Local\Logos5, I then reinstall Logos 5 but my library is empty: "You don't have a license to view this resource" (and this is for my preferred Bible, NASB...I've had Logos/Libronix NASB for 15 years). There's a hyperlink to the NASB product page but I can't "Add to cart" because, as the mouse-over says: "You already own this product"

Graham Criddle

In your reinstalled Logos 5 what happens if you type "update resources" in the command box?

Ted Dang

"Checking for updates" (which would upgrade me to Logos 6)

Dave Hooton

I think it has something to do with resources that have been converted to Logos 6?

Logos 5 wouldn't necessarily resolve the problem and we need to see detailed logs to establish what is happening. So enable logging and release the download which will install Logos6 and get all your resources. Upload the log files folder if it crashes.

Ted Dang

Crashes

2112.Logos Log Files.zip

Bradley Grainger (Logos)

Windows Event Viewer showsa .NET Runtime unhandled exception

Can you paste in the other "Error" from Event Viewer? (They usually come in pairs, and the other one has more details.)

Ted Dang

Log Name:      Application
Source:        Application Error
Date:          2/12/2015 5:31:25 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DANGER-X1-C
Description:
Faulting application name: Logos.exe, version: 6.0.2.79, time stamp: 0x54d9127a
Faulting module name: ASProxy64.dll, version: 2.3.0.7, time stamp: 0x5469088c
Exception code: 0xc0000005
Fault offset: 0x0000000000007e70
Faulting process id: 0x634
Faulting application start time: 0x01d046c80b34167d
Faulting application path: C:\Users\Ted Dang\AppData\Local\Logos5\System\Logos.exe
Faulting module path: C:\WINDOWS\system32\ASProxy64.dll
Report Id: 708dd09b-b2bb-11e4-825f-28b2bd06c308
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-12T13:31:25.000000000Z" />
    <EventRecordID>4704</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DANGER-X1-C</Computer>
    <Security />
</System>
<EventData>
    <Data>Logos.exe</Data>
    <Data>6.0.2.79</Data>
    <Data>54d9127a</Data>
    <Data>ASProxy64.dll</Data>
    <Data>2.3.0.7</Data>
    <Data>5469088c</Data>
    <Data>c0000005</Data>
    <Data>0000000000007e70</Data>
    <Data>634</Data>
    <Data>01d046c80b34167d</Data>
    <Data>C:\Users\Ted Dang\AppData\Local\Logos5\System\Logos.exe</Data>
    <Data>C:\WINDOWS\system32\ASProxy64.dll</Data>
    <Data>708dd09b-b2bb-11e4-825f-28b2bd06c308</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>