Logos 4.2 indexing crashes my computer?
This is a strange problem, but I thought I would mention it. Sunday night I downloaded and installed 4.2 and then downloaded all the resource updates. When it was finished, I turned off the computer and went to bed (before indexing). In the morning I turned on the PC and indexing automatically started. I walked away from the computer for about ten minutes - I come back and my computer is off. (Not ON with Logos crashed/not working, but the computer physically was off.) I never thought this might be related to Logos at this point. I started the computer again and had the same results. This happened three times before I left for work. My family had the same problem several times during the evening. Everytime it happened, no one was at the computer to see it. My daughter said she saw the computer out of the corner of her eye and it just shut off, she thinks, with no warning. (When the computer is restarted, it says that Windows was not shut down properly and asks about starting up in Safe Mode / Normally.)
I still thought this was not related to Logos. My wife logs onto her account in Windows Vista - indexing did not start because it was only indexing in my account. The computer stayed on for about fours hours with no problems. I get home from work and switch to my account. Indexing starts and the computer shuts off after about ten minutes. I restart the computer, log on and stop indexing immediately. I killed my antivirus program and other non essentials, started resource monitor, restarted indexing and watched the resource monitor to see what Logos was doing. (It was accessing 100+ resource files at once while indexing.) Indexing finally completed. Since then the computer has not shut off again.
I work on electronics/computers for a living, so I have plenty of experience with PCs. My computer is a self-built PC:
Intel 2.4 Ghz Quad Core CPU, 4gig Memory, 500gb hard drive, GeForce GTX 260 video, Sound Blaster X-Fi sound card, 650 Watt Antec power supply. This PC plays hardware-intesive games with no problems at all.
I have experienced failed motherboards, hard drives, CPUs, video and memory and dealt with numerous Windows/software issues, but I have never had software cause a PC to shut off. (Which is why I am still skeptical that Logos caused it, even though it seems to be cause.) Even the dreaded Blue Screen of Death keeps the computer on... Anyone with any more smarts than me have any ideas?
"It seems our problems solve themselves when we look beyond us to those truly in hell." - Beyond Our Suffering - AILD
Comments
-
If your PC is overheating, it will shut itself down. Some computers don't handle 100% CPU loads very well (insufficient heat handling) Try opening the case and turning a external fan on it to see if that changes things.
MacBook Pro (2019), ThinkPad E540
0 -
This PC has a high performance case with an intake fan in the front, an exhaust fan in the back and fan blowing directly onto the CPU and video card area. (In addition to the fan in the power supply, on the video card and the CPU fan...) That was my first guess too, but all fans appear to be working properly. (But I will try your suggestion, just in case...)
"It seems our problems solve themselves when we look beyond us to those truly in hell." - Beyond Our Suffering - AILD
0 -
Check for dust build-up, too, while you've got it open, or just take a can of compressed air to the whole thing.
Overheating is the only fault I know of that causes a shutdown (or stand-by, as my Thinkpad does when it overheats).
MacBook Pro (2019), ThinkPad E540
0 -
Todd Phillips said:
Check for dust build-up, too, while you've got it open, or just take a can of compressed air to the whole thing.
Tip, do that outside, or at least in the garage. A particle mask is nice to have too.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I truly think that version 4.2 update has a problem with indexing. Like yourself, I my laptop automatically installed the update last Sunday. Since then, my pc feels a bit sluggish and I can tell that the CPU is working harder as I got the turbo boost software. My laptop has only got core i5 (duo) and Windows 64. I read somewhere that someone is having the same issue with certain resource. I am waiting for another small update to fix this issue.
0 -
I have installed 4.2 and now the LogosIndexer crashes when attempting to index. Sometimes the indexer just crashes and sometimes I get the blue screen of death.
I would agree 4.2 seems to be so kind in indexing.
0 -
Jesse Craycraft said:
I would agree 4.2 seems to be so kind in indexing.
Jesse, if you want help then please start a new thread with details of the problem. We will need logs, though, so please read this article very carefully.
Dave
===Windows 11 & Android 13
0 -
Tom Geswein said:
This PC has a high performance case with an intake fan in the front, an exhaust fan in the back and fan blowing directly onto the CPU and video card area. (In addition to the fan in the power supply, on the video card and the CPU fan...) That was my first guess too, but all fans appear to be working properly. (But I will try your suggestion, just in case...)
Perhaps you should run some monitoring software that logs CPU and HDD temps.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I have the same problem and have been having it for a while with Logos 4.2. Today I decided I ought to contact Logos about it and saw this thread. I was thinking maybe it was because I was using the Beta version, but maybe not. Logos will start indexing and my computer after some time (10 minutes does seem about right) will just turn off, simply "snap" and its off, no blue screen or nothing. When it restarts it doesn't say windows is recovering from a crash. At first I wasn't sure what was causing it, but soon figured out it was Logos. If I pause the indexing for 4 hours, it's fine, but as soon as I let it go again it crashes. It seem to eventually get the indexing done (after several repeated crashes) and is fine until it needs to index again.
To me this is a SERIOUS PROBLEM that needs to be addressed. I don't think its simply my CPU overheating as some have theorized, but I'm not sure what it could be. However, even if it is the CPU overheating that should be addressed by Logos to make the process run in the back ground and use less CPU power. Again, I think the problem is something else, but as stated in the original post, have also never experienced software being able to do this to a PC.
0 -
John Barber said:
To me this is a SERIOUS PROBLEM that needs to be addressed. I don't think its simply my CPU overheating as some have theorized, but I'm not sure what it could be.
Pragmatically, get additional cooling air directed at the computer (incl. hard drives). I use a household fan with my laptop (see below) which otherwise will switch OFF as you describe after 10 minutes!
Full indexing will use all the cores (2 or 4 with Intel) on your processor very intensively. You can elect to lower the priority of Logos4Indexer.exe in Task Manager but I doubt that will affect things if you index unattended (no other tasks running). Indexing is run in the background.
Dave
===Windows 11 & Android 13
0 -
UPDATE: I rolled back off the Beta updates (i.e had to reinstall Logos from scratch) but that didn't seem to help, first time indexing crashed as stated above. Then i decided to go with the CPU overheating idea that has been mentioned several times in this thread. Before going out to buy a cooling pad for my laptop, I decided I would check the BIOS to make sure it was up to date, figuring an out of date BIOS might not be managing the fan/colling functions as well. I did find a Windows 7 update to my BIOS (originally a Vista PC but now running 7). I updated it and it just finished indexing my new LOGOS install, about 2.5 hours with NO CRASH (YEAH!!). So far so good. So, if you are having a similar problem maybe checking your BIOS is one way to go.
0 -
John Barber said:
I did find a Windows 7 update to my BIOS (originally a Vista PC but now running 7). I updated it and it just finished indexing my new LOGOS install, about 2.5 hours with NO CRASH (YEAH!!). So far so good. So, if you are having a similar problem maybe checking your BIOS is one way to go.
A BIOS update is usually a good idea when switching OS like that.
Let us know the end result.
Dave
===Windows 11 & Android 13
0 -
Update. I thoroughly cleaned out the computer - it was quite dusty. Haven't had any problems since indexing finally finished. All was fine until today when I upgraded from Silver to Platinum and bought a bunch of resources in the Christmas special.
Indexing started and the computer shut off again. Logos is the only program that I have experienced this with and my guess is that the indexing is just causing too much heat in the CPU. When time allows, I will try to open up the case and put a fan on it and start indexing again to see if it helps. Thanks for all your responses. I will let you know what happens...
"It seems our problems solve themselves when we look beyond us to those truly in hell." - Beyond Our Suffering - AILD
0 -
I'm battling the same problem myself. In my case, I know I have an overheating problem as I've had the laptop crashing when viewing videos or anything else that is cpu intensive. Last night I decided to install some temp monitoring software. Could very easily see the temps of the cpu cores rising as Logos was running the indexer. As soon as I shutdown/paused the indexing, the temp would start to fall (along with the cpu usage). I'm trying to figure out some strategy now to get the indexing done with some manual intervention to better control the cpu cycles and give the cores a rest (as I don't think my wife is going to agree the purchase of new laptop is a better solution [:^)] ).
0 -
Jeff Causey said:
as I don't think my wife is going to agree the purchase of new laptop is a better solution
Buy a household fan instead!
Dave
===Windows 11 & Android 13
0 -
CPU is overheating. I removed the cover and put a fan on the CPU/MB and temps dropped 20 degrees F right away. (CPU was around 130 and the motherboard was around 95.) Started indexing and all four cores of the CPU went to about 90% with the CPU temperature peaking around 200. The cores are fluctuating from time to time from about 40% and then back to nearly 100% as it is working. Next step is to remove/remount the CPU fan - not sure what has changed - this computer has been together for over two years with no problems.
Thanks for your help and suggestions
"It seems our problems solve themselves when we look beyond us to those truly in hell." - Beyond Our Suffering - AILD
0
