[resolved] logos 6 crashes on startup on microsoft surface

My surface 3 installation crashes on logos startup.

I uninstalled logos 6 completely and then reinstalled in an attempt to clear out the problem. After reinstallation logos 6 still crashes on startup.

When I hold down the control button and start logos it does not crash so the attached log files may not be helpful.

Thank you for your help.

Find more posts tagged with

Comments

Mark Barnes

I uninstalled logos 6 completely and then reinstalled in an attempt to clear out the problem. After reinstallation logos 6 still crashes on startup.

When I hold down the control button and start logos it does not crash so the attached log files may not be helpful.

Looking at the error log, the last error was a sign-in problem. It looks like you are running a local proxy that refused the connection. (I can't know for certain that this is the error causing the crash. To be certain of that, I'd need to see a logos.log file for the crash. To get that you will need to turn logging on permanently: https://wiki.logos.com/diagnostic_logging)

Randall Fairman

https://community.logos.com/discussion/comment/724435#Comment_724435

I turned on the diagnostic logging and again started without using the control key and the program crashed as before.

I have attached the log files.

Logos Log Files.zip

Bradley Grainger (Logos)

Are you running Astrill VPN?

It causes crashes in Logos 6. You will need to disable or uninstall it.

Randall Fairman

https://community.logos.com/discussion/comment/724467#Comment_724467

I live abroad and cannot access bible stuff without vpn. Your response does not seem like a reasonable answer to me.

Randall Fairman

https://community.logos.com/discussion/comment/724467#Comment_724467

I tried to "disable" but did not see a way to do that. I actually exited Astril and tried again and logos 6 still crashed.

Randy

Dave Hooton

https://community.logos.com/discussion/comment/724481#Comment_724481

We need to see the Windows Event log for the time of the "crash".

Randall Fairman

https://community.logos.com/discussion/comment/724513#Comment_724513

There are 3 logs:

Here is #1 ...

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Logos Bible Software because of this error.

Program: Logos Bible Software

File:

The error value is listed in the Additional Data section.

User Action

1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.

2. If the file still cannot be accessed and

- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.

- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.

3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.

4. If the problem persists, restore the file from a backup copy.

5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data

Error value: 00000000

Disk type: 0

Here is #2

Faulting application name: Logos.exe, version: 6.2.0.43, time stamp: 0x55411a54

Faulting module name: ASProxy64.dll, version: 2.3.3.10, time stamp: 0x55141783

Exception code: 0xc000001d

Fault offset: 0x000000000000835b

Faulting process id: 0x2cb8

Faulting application start time: 0x01d08a30ae6ee84c

Faulting application path: C:\Users\Randall\AppData\Local\Logos\System\Logos.exe

Faulting module path: C:\windows\system32\ASProxy64.dll

Report Id: f5a7539a-f623-11e4-8264-c0335e12caea

Faulting package full name:

Faulting package-relative application ID:

Here is #3

Application: Logos.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c000001d, exception address 0000003F7F6A835B

Stack:

Dave Hooton

https://community.logos.com/discussion/comment/724515#Comment_724515

The Faulting module ASProxy64.dll belongs to Astrill, so I'm afraid you will have to face Bradley's conclusion and uninstall it. Find another VPN software.

Randall Fairman

https://community.logos.com/discussion/comment/724519#Comment_724519

is this something that astral needs to fix or you need to fix?

I need to get a refund from one of you or else get them working together.

Mark Barnes

https://community.logos.com/discussion/comment/724523#Comment_724523

is this something that astral needs to fix or you need to fix?

This thread suggests its likely to be an Astrill problem: https://community.logos.com/forums/t/100740.aspx

And given that there's a lot more choice of VPNs than there are of Bible software, I would advise switching VPN provider or using their router-based solution. You'll probably be better off using a solution that doesn't require additional software. Something like this: https://www.tigervpn.com/

Randall Fairman

https://community.logos.com/discussion/comment/724526#Comment_724526

Fair enough.

I downloaded their portable version of the astril software and it works now.

Thank you for helping me solve my problem.

Randy

Mark Barnes

https://community.logos.com/discussion/comment/724528#Comment_724528

I downloaded their portable version of the astril software and it works now.

Great! It's good to know the portable version works.