Multiple Crashes during indexing (HIGH TEMPS!!!)

David Paul · March 1

I was typing a reply in the forum a few minutes ago when my system suddenly shut down without warning. At the time it happened, my fans were spinning up in the way that only occurs when I am indexing Logos. I complained a year or two ago about stupid high temps during indexing, and at that time I was only hitting about 90 degrees +/- 2 degrees. Since then, I've seen far worse, and just now when my system crashed, my cpu cooler logged 108 degrees!!!

This is UTTERLY RIDICULOUS. My system almost never verges into the 70s, and only occasionally into the 60s. Just now, my system crashed 4 TIMES IN A ROW, and it was due to the Logos index 100%. The reason I'm able to type this and send it is because I turned off the index as soon as it kicked in. I assume my system is simply protecting itself with these shutdowns. THIS HAS TO BE FIXED.

David Paul · March 1

For comparison, this is what my temps are as I'm typing this.

Kevin A · March 1

It would seem to me that your cooling is the issue, Logos cant use more than 100% of your CPU, but clearly your cooling is insufficient for that usage over extended periods. First thing I would check would be my thermal paste, it may have dried out a bit.

David Paul · March 1

Yeah, seriously doubt my system is the problem. I installed a new cpu using liquid metal less than 2 years ago. The ONLY thing that has ever caused my system to strain is Logos during an index. Also, this isn't an "extended period" issue either. The spin up lasts about 10-15 seconds and then cools down. The program appears to force the whole index through the pipe at one time…it's asking the system to do too much in too short a time.

After my second post above, I turned on the index and after about 20-30 seconds, the spin up happened, and before I could pause it, the system crashed again.

MJ. Smith · March 1

The program appears to force the whole index through the pipe at one time…it's asking the system to do too much in too short a time.

I suspect you are referring to the merge portion of the sort/index process. If so, this is simply the normal processing of a multi-thread process which your system should be prepared to handle. It is curious problem that the intensive I/O causes overheating.

John · March 1

Check all your cooling fans, especially the one on the processor.

Don Awalt · March 1

you never said- what is your system? Specs? Windows I assume?

David Paul · March 1

Win11

Bradley Grainger (Logos) · March 1

Yeah, seriously doubt my system is the problem.

I'm sorry, but if a program running at 100% CPU for 15 seconds causes your CPU to overheat and shut down, then your hardware is absolutely the problem (not the software).

Logos is a resource-intensive program that is designed to use all available CPU resources (when necessary) to speed up its tasks.

One thing you could try is right-clicking LogosIndexer in Details view of Task Manager and changing its Priority:

That might not help, because it will still use all available CPUs even at Low priority; that just gives other processes more of a change to use the CPU. (And LogosIndexer already lowers its own priority in the first place.)

So the other thing you could try is "Set affinity", then uncheck some of the CPUs that it's allowed to run on:

Note that this only takes effect for the current run of the process; you'll need to Set Affinity again the next time LogosIndexer starts.

Joey Midgett · March 1

Have you tried running cpu stress tests? If not I would do that to see what happens during that.

Don Awalt · March 1

@David Paul you didn't mention system specs - CPU? Disk type and model? Amount of memory? Graphics card?

Also - I assume when you show your system is at 108 degrees, that's Celsius?

If it overheats and shuts down, that could be a hardware failure - they happen. Just some of the likely failures it could be, from what I have seen in forums:

thermal paste degradation as someone mentioned here;
fan failure (I have had them go up myself!);
dust buildup în heat sinks, vents, or fans (it can be BAD inside a chassis/around the vents! Have you opened up your chassis and checked/cleaned it and the vents lately?);
A failing power supply can cause voltage instability leading to excess heat in the chassis

Less likely, but certainly possible, would be a thermal sensor malfunction.

Here's a good benchmark utility to try - run Cinebench (link below) - you can read about it, many use it to test their system's speed and to stress test. It basically renders an image on your screen, but it's pretty intensive. I have a MacBook Pro M4, its specs say it can run up to 212 degrees F., although it can go over that with no concerns for short periods of time. It normally runs around 105 degrees F., I think when the Logos Indexer runs it briefly gets to around 140 degrees.

I just ran Cinebench, and the laptop happened to be doing a backup also at the same time. The laptop also had around 10 windows open including Verbum - and the highest temperature I saw was 188.

However, this test is not just to see if the unit completes the Cinebench test without shutting down. If your computer is functioning properly, I think you should see the temps ramp up quickly when it is running, then the fans should kick in and the temps moderate. On my laptop, as I said it got to about 188 degrees pretty quickly, but then it dropped back to around 165 degrees for the rest of the test. It then quickly dropped back to 120 when the test ended (within 30 seconds or so). Yours should do something similar; if the temps ramp up high and stay there, you have a cooling problem due to one of the issues I mentioned above.

https://www.maxon.net/en/downloads/cinebench-2024-downloads

Multiple Crashes during indexing (HIGH TEMPS!!!)

Comments

Categories