Logos 6 crashing
PC running Win 10 Home
AMD A10-8700P Radeon R6, 10 Core 4C + 6G 1.80GHZ
RAM 16 GB
64 bit OS
Logos 6 crashes when I enter a passage to search. Windows searches for a solution but then just closes the App.
I tried running log files and it dutifully tells me Logos 4 log files running. I then hit CTRL while opening Logos and follow the instructions to find the log files in my documents folder. But the only Log files I find there date back to 26th Sept 2016 - none for today.
My Logos 6 is running fine on my old laptop so I'll use that for the time being but would like to get it running on this one as it's much faster.
Any ideas?
Comments
-
Welcome [:D]
Ideas is support article => What to do if Logos Crashes that includes link => Report a Problem with how to enable diagnostic logging.
Also curious if System Event viewer in Windows has any relevant crash information ?
Keep Smiling [:)]
0 -
Thanks "Keep smiling". I've worked through those two links, which is why my comments re. the log files are critical in this context. Since I can't get the log files I can't give any more info. I haven't been using Logos 6 offline,
0 -
Have you tried Step 4 to Enable Logging => Report a Problem ?
Report a Problem said:Step 4: "Setup" Logging (Installation Problems)
If you experience an error running the Logos Setup you will have to enable logging for Logos5Setup.exe.
- Save the EnableLogging.js script found here, to your Desktop.
- If you get a page of "code" when clicking the link, try right-clicking and use the "Save-as" option.
- Navigate to the Desktop and open the EnableLogging.js file you saved.
- Once you've enabled logging, retry the installation, then continue from Steps 2-3.
Noted Step 4 has a sentence that dates back to Logos 5. Running the EnableLogging.js => https://www.logos.com/media/tech/4xLogging/EnableLogging.js turns on Diagnostic Logging
After Logging is enabled, then launch Logos normally. If crash repeats, then look in "Logos Log Files" folder:
for files with today's date. Please compress then use paper clip to attach zip files to forum reply.
FYI: personally have logging enabled all the time (since do not know when a beta version will have an issue).
After crash is resolved, can turn logging off by running DisableLogging.js => https://www.logos.com/media/tech/4xLogging/DisableLogging.js
Other option is contacting Faithlife technical support tomorrow => https://www.logos.com/contact With your permission, Faithlife can remotely connect to your computer for troubleshooting crash.
Keep Smiling [:)]
0 - Save the EnableLogging.js script found here, to your Desktop.
-
Windows Event Viewer has nothing.
0 -
Thanks again for your patience. That method #4 also gives me no log files in the Logos Log Files folder. I still have the files from September last year and no new ones.
0 -
Ray Wilson said:
That method #4 also gives me no log files in the Logos Log Files folder.
Puzzling, suggest checking "Logos Log Files" folder permissions => Error Writing to File
Also would check folder and files with Logos.exe (if permissions have become read only, then Logos does not work because many files need to be opened with write access so file contents can be changed).
FYI: when logging is enabled, the first line of Logos.log file has date and time along with application version.
Keep Smiling [:)]
0
