Computer crashing--appears to come from indexer
Over the last several weeks I have had problems with my computer crashing. At first I thought it was problems with Windows upgrades, but now I have reason to believe that Logos 4 is causing the problem. It seems that whenever the indexer tries to start, the entire system locks up. I can move the mouse, but nothing else. System restore points have been getting me around this problem so far, but now that I suspect the problem is coming from Logos, I wanted to ask the Logos community if anyone else has experienced this or knows of a solution. I did a search of forum topics, but they all seemed to relate to only the program/indexer itself crashing, not the entire system. Any help would be greatly appreciated. I currently have 4.6b SR-1(4.62.0.2675)
Comments
-
Karl Flentje said:
Over the last several weeks I have had problems with my computer crashing. At first I thought it was problems with Windows upgrades, but now I have reason to believe that Logos 4 is causing the problem. It seems that whenever the indexer tries to start, the entire system locks up. I can move the mouse, but nothing else. System restore points have been getting me around this problem so far, but now that I suspect the problem is coming from Logos, I wanted to ask the Logos community if anyone else has experienced this or knows of a solution. I did a search of forum topics, but they all seemed to relate to only the program/indexer itself crashing, not the entire system. Any help would be greatly appreciated. I currently have 4.6b SR-1(4.62.0.2675)
Please enable logging by following all the instructions in the link below. Run Logos and let the indexer run until it crashes. Do not restart Logos before posting all logs here for review (see link below for how to upload logs). We'll see if there's anything we can do to help.
Here are the URLs to enable logging and post your logs here:Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Here are the log files. It took a while to get them uploaded, because the indexer started automatically when I restarted my computer and it ended up crashing a couple more times!
Thanks for your help!
0 -
Karl Flentje said:
Here are the log files. It took a while to get them uploaded, because the indexer started automatically when I restarted my computer and it ended up crashing a couple more times!
Thanks for your help!
The indexer did not appear to crash, according to the logs, or it crashed without providing a notification after it was paused for 4 hours (about 2 minutes into the indexing process). The indexer continued in 'Paused mode' for another 23 minutes before the logging data simply ends.
There are two interesting lines during the pause that refer to updating your Library and Personal Book indexes. But this did not crash the program (at least the program continued for another 11 minutes after that event).
Not sure what to suggest. If you didn't pause indexing, then something strange is going on. If you did, try to let it run next time without indexing (when you have the time), and let's see what it does.
The Logos4 log files show some problems with possibly some personal book milestones and the NIV reverse interlinear. If the NIV is your preferred Bible, temporarily choose another Bible as your preferred, restart Logos and type update resources in the Logos4 command bar. If this downloads a new NIV, this may solve your problem. I'm not aware that this is an issue outside of Logos5, but it could parallel an intermittent problem in L5 in updating the default Bible (which is to say, I'm guessing on this one).
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Karl Flentje said:
Here are the log files. It took a while to get them uploaded, because the indexer started automatically when I restarted my computer and it ended up crashing a couple more times!
I'd like to see those two logs related to each other in time, so begin with nothing running/paused, start Logos and let it crash. BEFORE you do anything else Zip the Logos Log files folder (as per the wiki) and upload that.
Dave
===Windows 11 & Android 13
0 -
Hi, sorry it's taken me so long to get anything else posted, but I've just had to pause the indexing every time (it starts automatically when I start my computer) to be able to get some work done. It is becoming more and more evident though--if the indexing is running, it is just a matter of time before the computer freezes up completely. If I pause indexing then the computer does not crash. Dave, I don't know if the attached log file is going to have what you wanted. I've turned indexing on permanently, so I can't get an error log and the regular log from the same start up, because I have no way of saving the regular log when the computer crashes. I'm beginning to wonder if this is a case where I should just uninstall Logos completely and reinstall. 03113.Logos4Indexer.zip
0 -
The operating system's job is to prevent regular programs from crashing/freezing the computer, so when it does happen, it's often indicative of an underlying hardware error. The multi-core indexing of Logos 4 can sometimes stress inadequately-cooled hardware to breaking point.
One way to try to work around this is to force Logos 4 to only use a single indexing thread. This will dramatically slow it down, but may improve stability. (You could also blow out any dust from a desktop computer, or try using a laptop cooling stand for a notebook.)
To do this, copy the following line to the clipboard, then open a command prompt. Click the icon in the top left, then select Edit > Paste. (If necessary, press Enter.) It should say "The operation completed successfully."
reg add HKCU\Software\Logos4 /v MaxIndexingThreads /t REG_DWORD /d 1 /f
Try launching Logos 4 again. You should see much lower CPU usage in Task Manager, and hopefully it will finish indexing without error. (It will probably also pay to type "rebuild index" into your Logos 4 Command Box, to force the existing indexes to be recreated from scratch.)
0 -
If you’ve had no luck and your computer keeps shutting off, I learned a new
trick from Microsoft.
o Open up your Task Manager (ctrl‐alt‐del)
o Go to the details tab
o Look for the logosindexer. Right click it when you find it. Scroll down
until you see Affinity (usually the 4th option.). Left click on affinity.
There you will see how many cores are working on the index. If all
are checked, you are probably overheating the cpu and killing the
computer. Try unchecking half of the boxes; indexing “might” be
slower, but it will get the job done!0
