Windows 10 Crash

Logos 6 has starting having significant problems under Windows 10. This problem only began to manifest itself late last week after a Windows 10 update....... it had functioned well under Win10 for several weeks before.
Logos 6 launches and operates for 10min or so and then a small window pops-up saying that LOGOS has stopped responding and asks to shut down the program.

Find more posts tagged with

Comments

Lynden O. Williams

Welcome to the forums Karl. Please follow the steps outlined here after a crash and upload logos.

https://wiki.logos.com/Diagnostic_Logging

Graham Criddle

https://community.logos.com/discussion/comment/759863#Comment_759863

Karl

Just to clarify something - you need to enable logging before a crash and upload logs afterwards.

Graham

Karl Heckart

7128.LogosError.logCrash log attached0268.LogosCrash.txt

Graham Criddle

https://community.logos.com/discussion/comment/759872#Comment_759872

Hi Karl

The log shows a disk I/O error. I would check the disk for errors and run disk diagnostics if you can

Graham

Karl Heckart

https://community.logos.com/discussion/comment/759875#Comment_759875

It's an SDxc card and scan says it has no errors.

Graham Criddle

https://community.logos.com/discussion/comment/759882#Comment_759882

It's an SDxc card and scan says it has no errors.

Please provide some more details of the specs of your system - it sounds like it is a tablet device. Is that correct?

And was there a Logos.log file as well? If so, please upload it.

Karl Heckart

https://community.logos.com/discussion/comment/759886#Comment_759886

I am running a Surface Pro3 Logos files are on a 64gb SDXC card.

3716.Logos.log

Dave Hooton

https://community.logos.com/discussion/comment/759882#Comment_759882

It's an SDxc card and scan says it has no errors.

Delete the \Logos5\Data\fsze0pj4.or1\UserEventManager folder and restart Logos.

Karl Heckart

https://community.logos.com/discussion/comment/759891#Comment_759891

0574.LogosCrash.txtLogs attached.

5367.Logos.log

7080.LogosError.log

Deleted the UserEventManager folder and restarted. Logos crashed after a resource was opened.

Thanks for the help

Dave Hooton

https://community.logos.com/discussion/comment/759897#Comment_759897

The log shows that UserEventManager was recreated and then crashed as a result of errors on the same file. Please contact Tech Support to resolve the issue (refer them to this thread).

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/759900#Comment_759900

Logos 6 requires an internal HDD/SSD (https://www.logos.com/system-requirements#requirements); we don't support running on SD cards or external drives (because they're unfortunately prone to these kind of problems).

Karl Heckart

https://community.logos.com/discussion/comment/759941#Comment_759941

So is that your final answer? ;-)

If you can't tell me what may have gotten corrupted, can you at least provide options on migrating the files (in a way that will get Logos running) onto the internal drive?

Dave Hooton

https://community.logos.com/discussion/comment/760050#Comment_760050

can you at least provide options on migrating the files (in a way that will get Logos running) onto the internal drive?

The file I mentioned has been marked as corrupt by Logos and it will be re-created and then crash again with each restart. You could try a check for bad sectors i.e start a Command (CMD) Prompt with Admin privilege and type:

chkdsk E: /R

(replace E with your drive letter)

To migrate safely it is best to only copy resources from SD card, as follows

rename the Logos folder on SD card e.g. Logos5 ---> old-Logos5 (this will preserve your Resources)
uninstall Logos from Control Panel >> Programs and Features
install Logos using Method 3 with resources from SD card
delete the Logos folder on SD card.

Dave Hooton

https://community.logos.com/discussion/comment/760189#Comment_760189

EDIT: Another factor with SD cards is they usually come formatted with FAT32 file system. If possible (some don't allow it) format as NTFS, the same file system used by Windows 7 and newer. This is much more reliable than FAT32, but still ensure there are no bad sectors!

Karl Heckart

https://community.logos.com/discussion/comment/760189#Comment_760189

Ran the chkdsk and found no errors. I will likely migrate to the internal drive over the weekend.

I find it puzzling that LOGOS appears to have little interest in supporting expanded storage in our mobile age. Perhaps it is related to a bigger move to get people onto the new cloud service.

Dave Hooton

https://community.logos.com/discussion/comment/760956#Comment_760956

I find it puzzling that LOGOS appears to have little interest in supporting expanded storage in our mobile age.

There are a number of issues with (micro) SD cards for an app like Logos/Verbum:-

they are SLOW --> it can take days to index your library
they are not designed for computer apps --> hence the default FAT or FAT32 system
when removed they can lose their drive letter to another peripheral/removable drive
MS software has had problems maintaining connection with microSD cards

Removable hard drives/SSD's would suffer #3 mainly, UNLESS you change the drive letter in Disk Management e.g. from the default or E: to R:

Karl Heckart

https://community.logos.com/discussion/comment/761140#Comment_761140

To wrap this up:

Before migrating back to an internal drive, I rebooted my Surface and was notified of a firmware update.
I applied the update and restarted the computer.
I started Logos and ran it thru its paces.
It is rock solid once again.

I will leave well enough alone for now. Should it go south I will follow your instructions to migrate to the surfaces internal SSD.

Thanks for your assistance.

Karl

Dave Hooton

https://community.logos.com/discussion/comment/761990#Comment_761990

If it's no longer broke....

I'm glad it's working!