Logos 5 Rebooting Windows 7

I can start it, run it for a while and there isn't anything really consistent about it, but eventually the mouse stops responding and a few seconds later it reboots.

Logos 5 doesn't contain any code that will reboot the computer (except perhaps in the initial setup application if the .NET Framework needs to be installed, but even that may just be delegated to the .NET Framework installer).

This sounds like a driver or hardware problem. Is a blue screen displayed when the computer reboots, or does it just shutdown and reboot normally (as if you had chosen that from the Start menu)?

https://community.logos.com/discussion/comment/546426#Comment_546426

Bradley,

Thanks for the quick response. There is no blue screen. It goes black and then my computer reboots. On start up it knows it was an abnormal shutdown.

https://community.logos.com/discussion/comment/546435#Comment_546435

What does the Windows Event Log show --> see http://wiki.logos.com/Windows_Troubleshooting#Logos_.28or_the_Logos_Indexer.29_crashes.

https://community.logos.com/discussion/comment/546543#Comment_546543

Since we had the holiday and i'm finally able to get back to this, I had a difficult pinpointing the exact entry in the Windows event log. I will run it again collect the Logos log file, note the time of crash and then try to get the Windows event for you.

https://community.logos.com/discussion/comment/548186#Comment_548186

3603.WindowEvent.txtHere is the log and Windows event record from a crash at 10.25 today. The Windows event was the last event logged before the crash. It was the only event that had a warning symbol. The events leading up to it were informational only.0652.Logos Log Files.zip

https://community.logos.com/discussion/comment/548221#Comment_548221

3603.WindowEvent.txtHere is the log and Windows event record from a crash at 10.25 today. The Windows event was the last event logged before the crash. It was the only event that had a warning symbol. The events leading up to it were informational only.0652.Logos Log Files.zip

My suspicion is that you've got indexing going on (the log shows that), and the heavy indexing done by Logos is overheating your computer. Most computers have built-in safeguards to prevent damage to the computer. This may explain the shut-downs. A bad or marginal power-supply can also do this (happened to me on my Dell desktop), since the extra hard drive tasks can overtax a bad or marginal power-supply.

The remedies for this issue vary with the type of computer your using. For a desktop, make sure that the power supply is more than adequate for all you're doing with your computer (some higher end video cards require quite a bit, e.g.). You will also want to remove any dust that accumulates. Take your desktop outside and blow out the dust (there are a number of ways to do this, you can research this on-line if you need specifics).

For a laptop, make sure that there is adequate ventilation on all sides of the laptop. Some laptop fans are poorly placed and you have to make sure that there is nothing obstructing the airflow (both in and out). Some CPU's are known to be problematic in laptops, including the i7 - they can get very, very hot.

There are freeware heat monitoring devices that might help pinpoint an overheating issue. As for the power supply problem - that's harder to diagnose (at least it was for me). The easiest way I know to diagnose that problem is to replace the power supply, and see if the problem persists. I was able to do that by borrowing one from a computer that wasn't being used very much. Note that your power supply should always exceed your anticipated needs (if you need 350watts, get at least a 400W power supply, e.g.)

NB.Mick

https://community.logos.com/discussion/comment/548227#Comment_548227

For a laptop, make sure that there is adequate ventilation on all sides of the laptop.

One can't stress this enough. I once had a laptop that used to shut-off when doing something more graphics oriented (like playing a youtube video). It tried to suck air from below - i.e. a sure way to kill it was running it on a carpet, the couch or on a table covered with tablecloth. There are inexpensive, USB-powered ventilation stands - once I had that, the problem was away.

https://community.logos.com/discussion/comment/548227#Comment_548227

Thank you for your advice. I will give the power supply a shot. Today I had a utility running that measured core temp. I'm not sure if that is what you mean, but there was no indexing going on. At least it didn't display it in the top status area. The core temp wasn't the highest it was average 102 when it rebooted. Maybe you don't mean CPU temp, but temp within the chassis. Thanks again.

https://community.logos.com/discussion/comment/548721#Comment_548721

Thank you for your advice. I will give the power supply a shot. Today I had a utility running that measured core temp. I'm not sure if that is what you mean, but there was no indexing going on. At least it didn't display it in the top status area. The core temp wasn't the highest it was average 102 when it rebooted. Maybe you don't mean CPU temp, but temp within the chassis. Thanks again.

Is that 102F or 102C? In my experience most prog's measure in Celsius, not Farenheit. 102F would be very, very cool for most core temps (in my limited experience).

Power supply issues are significant for desktops only. Assuming you have a desktop, did you clear out the dust from inside as I suggested?

https://community.logos.com/discussion/comment/548727#Comment_548727

That temperature was 102F. I have a tower chassis and didn't clean it out.

https://community.logos.com/discussion/comment/548730#Comment_548730

That temperature was 102F. I have a tower chassis and didn't clean it out.

Well, if it's 102F, then you have a pretty efficient cooling system. It's not likely a heat issue. One freeware prog I used was called Speedfan (I think), it showed temps of all the CPU's and a few other things. Is that what you're seeing? If so, I would suspect a hardware issue, and because of my experience with a power supply going bad, that would be one of the things I'd check, if I could. (There's also a chance that this could be a malware issue, but that would probably also produce other problems with your system.)

https://community.logos.com/discussion/comment/548803#Comment_548803

There are ways to test your computer without physically messing with the hardware for now.

Google "CPU stress" and also google "memtest".

Mark Barnes

https://community.logos.com/discussion/comment/546435#Comment_546435

Thanks for the quick response. There is no blue screen. It goes black and then my computer reboots. On start up it knows it was an abnormal shutdown.

If there's no entry in the event log, and it's not CPU overheating, then it's almost certainly going to be a hardware or drive issue. Not having an entry in the event log is going to make diagnosis very difficult, so check and double-check you don't have anything else that may be relevant (for example other errors that started about the time this problem began).

I would certainly test your RAM, and I would also look at the Windows Update History (Control Panel ->System and Security -> Windows Update -> View update history) to see what updates were installed at that time. If any of them were drivers, then I would try uninstalling it (Control Panel -> Programs -> Programs and Features -> Installed Updates).

https://community.logos.com/discussion/comment/548816#Comment_548816

I ran a few CPU stress tests and maxed out the CPUs in addition to getting the temperature to about 130F and it was fine. I also ran 2 memory tests. One online in addition to the Windows version and there were no problems found. My reboot yesterday was around 10.45 AM. However I remember when I first started Logos, it began to download resources then began indexing. The indexer crashed at about 9.07 and I restarted Logos. I didn't think much of it since it was a full 1.5hrs prior to the shutdown. Anyway, I went back and found those Windows events and saved them to send them in this reply.2055.IndexerEvents.txt

https://community.logos.com/discussion/comment/548995#Comment_548995

Well, it looks like your hardware is basically sound. Perhaps a disk scan would be prudent.

This from a google search:

[quote user=""]

Hit start and search for "cmd"

Right click it and select "Run as administrator"
This will give you an old fashioned command prompt window.
In that window you can just type it as you see "chkdsk c: /f"

If you have more then one drive or partition, you will need to tell it the disk(chkdsk d: /f).

If it is the primary windows disk is c:\ it will ask you to schedule it for next boot. When you restart, it will do a chkdsk for you before even getting to the login screen.

In the end, though, you may want to try Logos customer service.

Mark Barnes

https://community.logos.com/discussion/comment/548995#Comment_548995

The indexer crashed at about 9.07 and I restarted Logos. I didn't think much of it since it was a full 1.5hrs prior to the shutdown. Anyway, I went back and found those Windows events and saved them to send them in this reply.

Great! Indexer crashes are easier to diagnose than restarts (but the two may not necessarily be related). I don't suppose you have the crash and indexer logs from the Logos Log Files folder in Documents, do you?

https://community.logos.com/discussion/comment/549009#Comment_549009

I ran a check disk and none of the 3 phases reported any errors or repairs. Unfortunately I don't have any log for when that indexer crashed. I didn't have it logging at that time.

https://community.logos.com/discussion/comment/549015#Comment_549015

FWIW, I had some strange behaviour a couple of months back, and after REBUILD INDEX the problems went away. (It will take a while to finish.)

I never had Logos 5 cause a reboot before, not even a BSOD.

See if you could also update your graphics driver?

https://community.logos.com/discussion/comment/549120#Comment_549120

Thanks. I looked back at updates (as instructed earlier) and saw that one on my updates was a graphics driver. We updated that driver again. Also my mouse was acting strange so we replaced the mouse. Logos ran fine for quite a while. Then I read what Lee wrote. I typed Rebuild Index and the indexer crashed and the machine rebooted. Here is the LogosIndexer.log file.2844.LogosIndexer.log

https://community.logos.com/discussion/comment/549140#Comment_549140

Thanks. I looked back at updates (as instructed earlier) and saw that one on my updates was a graphics driver. We updated that driver again. Also my mouse was acting strange so we replaced the mouse. Logos ran fine for quite a while. Then I read what Lee wrote. I typed Rebuild Index and the indexer crashed and the machine rebooted. Here is the LogosIndexer.log file.2844.LogosIndexer.log

No errors or warnings in the log file. This suggests that it is not likely the indexer that crashed the machine directly, though indirectly (points to another problem). Is there anything in the Windows event log about this time?

I continue to suspect a hardware issue. Doing a little searching for "spontaneous reboot" on the internet turns up RAM as a likely culprit. In my limited experience the power supply can also do it. There could be other possibilities (I'm not a computer tech).

You could try to figure this out on your own, or find a reputable computer repair place and see if they can determine anything. If I were you, that's what I'd be doing at this point. It might take a few days, but it could take longer to figure it out here in these forums. If a hardware issue can be ruled out, then I'd suggest letting one of the Logos techs take a look at it (they can do that remotely - this usually requires a phone call to tech support). But I would rule out the hardware issue first, since it is the most likely culprit (IMHO).

Scott E. Mahle

https://community.logos.com/discussion/comment/549184#Comment_549184

No errors or warnings in the log file.

I don’t read logs so I probably shouldn’t even say anything but I can’t help myself [:)]

Don’t the following lines from his log suggest a corrupt index or two? Did Logos correct the corruptions found?

2013-12-05 14:47:24.6295 7 Info BibleIndex Re-indexing because the existing index seems to have been corrupted.

2013-12-05 14:47:25.5690 7 Info LibraryIndex Re-indexing because the existing index seems to have been corrupted.

https://community.logos.com/discussion/comment/549203#Comment_549203

No errors or warnings in the log file.

I don’t read logs so I probably shouldn’t even say anything but I can’t help myself

Don’t the following lines from his log suggest a corrupt index or two? Did Logos correct the corruptions found?

2013-12-05 14:47:24.6295 7 Info BibleIndex Re-indexing because the existing index seems to have been corrupted.

2013-12-05 14:47:25.5690 7 Info LibraryIndex Re-indexing because the existing index seems to have been corrupted.

Good question. The log is noting that re-indexing is required, there there is an error in the index. However, this is not an error in the program (it, presumably correctly diagnosed a problem). The "Info" part of the line tells us that this is information. We sometimes see "Warn" or "Error" there. The latter may cause a crash.

Obviously the user needs to rebuild the indexes. For some reason attempting to do so reboots his computer. Indexing shouldn't do that, and as far as I know, there's no code in the indexer, or in the main Logos program that can reboot the computer. Something else is doing so, though indexing could indirectly cause a reboot if there is some marginal hardware issue that the indexer stresses. At least that's my theory.

https://community.logos.com/discussion/comment/549203#Comment_549203

Don’t the following lines from his log suggest a corrupt index or two? Did Logos correct the corruptions found?

2013-12-05 14:47:24.6295 7 Info BibleIndex Re-indexing because the existing index seems to have been corrupted.

2013-12-05 14:47:25.5690 7 Info LibraryIndex Re-indexing because the existing index seems to have been corrupted.

The Info part correctly suggests what is currently happening, but the "corrupted" part is misleading as it should state that Logos initiated the user rebuild command by destroying the current index!

As the log finished unexpectedly, we are back to hardware as being the culprit, unless there are current crash logs.

https://community.logos.com/discussion/comment/549245#Comment_549245

It could be anything. So Scott, could you contact Logos customer service? They may be able to troubleshoot your problem more closely. They may also need to mine specific information about your computer setup.

https://community.logos.com/discussion/comment/549247#Comment_549247

It could be anything.

Yes but the most likely culprit is not related to Logos at all. (Hardware or malware, with a driver issue coming in a distant 3rd - IMHO). I recommend a reputable computer repair shop.

https://community.logos.com/discussion/comment/549245#Comment_549245

but the "corrupted" part is misleading

Yes; this line will be logged if there is no existing index at all. I can add " (or was deleted)" or something like that to the end to make it a little less misleading for log readers.

https://community.logos.com/discussion/comment/549310#Comment_549310

I can add " (or was deleted)" or something like that to the end to make it a little less misleading for log readers.

Yes please!

https://community.logos.com/discussion/comment/549333#Comment_549333

It will now say "Re-indexing because the existing index is corrupt or missing." (which matches the logic in the code).

https://community.logos.com/discussion/comment/549309#Comment_549309

It could be anything.

Yes but the most likely culprit is not related to Logos at all.

If Logos consistently causes the problem to surface, then that's the best lead to go on for now. It would be different if the rebooting occurred intermittently, or if the OP managed to provoke a reboot using a stress test program.

Of course, that's not saying that it's a problem with Logos code at all.

https://community.logos.com/discussion/comment/549140#Comment_549140

I typed Rebuild Index and the indexer crashed and the machine rebooted. Here is the LogosIndexer.log file.2844.LogosIndexer.log

This log shows the last messages to be:-

2013-12-05 14:47:28.2603 10 Info BibleIndex (Timed) Indexing LLS:1.0.196
2013-12-05 14:47:28.2813 11 Info BibleIndex (Timed) Indexing LLS:1.0.60
2013-12-05 14:47:28.3043 12 Info BibleIndex (Timed) Indexing LLS:AV1873
2013-12-05 14:47:28.3313 13 Info BibleIndex (Timed) Indexing LLS:BRENTONLXXEN

and a fix for this crash will be available in the next (beta) release. As noted above, though, it does not cause the machine to reboot.

https://community.logos.com/discussion/comment/549882#Comment_549882

I am so appreciative for the response. I'm a bit confused since there are a number of people responding and I can't afford to continue in this direction on a daily basis. I've asked our sys admin to get a new drive and install a fresh Windows 8. My question is, Logos will look at this as a new device, will you allow me to install Logos new on this Hard drive? I assume so, but want to be sure. Thanks again. Maranatha!

https://community.logos.com/discussion/comment/550278#Comment_550278

I am so appreciative for the response. I'm a bit confused since there are a number of people responding and I can't afford to continue in this direction on a daily basis. I've asked our sys admin to get a new drive and install a fresh Windows 8. My question is, Logos will look at this as a new device, will you allow me to install Logos new on this Hard drive? I assume so, but want to be sure. Thanks again. Maranatha!

Logos license is attached to you, not a device. In fact you can install on as many devices as you want simultaneously. So no problem.

I agree that you shouldn't be trying to diagnose and solve this here. You need tech help-my thought is for hardware, though a software issue isn't completely impossible. A hard drive and a fresh install may help, or may rule out one more possible culprit.

https://community.logos.com/discussion/comment/550294#Comment_550294

@Scott Gallatin:

As an aside, you may want to have your sysadmin put in Windows 8.1, but please note the potential pitfalls (e.g. some hardware are not well supported under Win 8.1).

https://community.logos.com/discussion/comment/549140#Comment_549140

Is there a particular Anti Virus software that Logos recommends?

https://community.logos.com/discussion/comment/551323#Comment_551323

There's a couple I know Logos would not recommend[:D], but the company does not endorse specific brands of Anti Virus software. I use MalwareBytes Pro.

https://community.logos.com/discussion/comment/551333#Comment_551333

Can you tell me the ones they would NOT recommend. We are building a new desktop with Windows 8.1 and installing other software before I download Logos 5 on it Monday.

https://community.logos.com/discussion/comment/551335#Comment_551335

Can you tell me the ones they would NOT recommend

There have been some well known brands that thought Logos was malware and caused it to crash, but I was not serious in stating that Logos would not recommend them! Suffice to say that the brand I recommended was not one of them.

https://community.logos.com/discussion/comment/551335#Comment_551335

"Included in Windows 8.1 and Windows RT 8.1, Windows Defender helps guard your PC against viruses and other malware." (http://windows.microsoft.com/en-us/windows/security-essentials-download)

You can choose to install another virus scanner if you want, but the built-in one is good and free. I never had any incompatibilities with Microsoft Security Essentials (the previous version) and Logos on Windows 7.

https://community.logos.com/discussion/comment/549140#Comment_549140

Ok, I'm back. I have a new system new motherboard, power supply, Windows 8.1. When this problem started I had Logos 4. I upgraded to version 5 and the problem continued. So my question is, now that I have my new machine is it possible to start with Logos 5, or am I required to download 4 first? Because I'm trying to install 4 and it tells me it can't install .net framework 3.5. Win 8.1 already has .net framework 4.5.