L4 Indexing stops working or crashes

I have been trying to get L4 to complete the initial indexing for almost a month now. The indexer crashes or stops working before even getting halfway through the process. This install was originally an upgrade from L3 which tech support could not get running after I upgraded from Windows XP SP2 (also about a month ago). My system config is

ASUS M2N-E Motherboard, AMD Athlon 64 X2 processor, 8GB RAM, Windows 7 professional with all updates installed, .NET 4.0 with all updates installed (recommended by Logos Tech Support), Norton Internet Security 2011, Office Home 2010 etc.

The indexer hangs on certain resources which are removed and indexing restarted, replaced and indexing restarted, etc. In addition, I have been instructed by logos technical support to remove directories and restart the application, update resources, and rebuild the index...all without success. The last thing I was asked to do was to reinstall L4.

Ever since I reinstalled I have had some BSODs with Memory Management and page fault in non-paged area, etc. When I look at the crashdumps in appcrashview, this is what I see (these are the last 5):

Logos4Indexer.exe Stopped working 10/14/2010 8:35:39 AM jjohnson 0xc0000417 0x0006c955 MSVCR90.dll 9.0.30729.4926 C:\Users\jjohnson\AppData\Local\Logos4\System\Logos4Indexer.exe 20,788 C:\Users\jjohnson\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Logos4Indexer.ex_8ac7cbb4e0f046b6914ba9b6bff74c78f9e4a9_10eded6a\Report.wer

Logos4Indexer.exe APPCRASH 10/14/2010 7:58:02 AM jjohnson 0xc0000005 0x00062374 mscorwks.dll 2.0.50727.4952 C:\Users\jjohnson\AppData\Local\Logos4\System\Logos4Indexer.exe 20,218 C:\Users\jjohnson\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Logos4Indexer.ex_d334b1e38433ac2b369130667c90c5366a762ad_07aa7b85\Report.wer

Logos4Indexer.exe APPCRASH 10/14/2010 6:09:24 AM jjohnson 0xc0000005 0x0002e1fe ntdll.dll 6.1.7600.16559 C:\Users\jjohnson\AppData\Local\Logos4\System\Logos4Indexer.exe 20,376 C:\Users\jjohnson\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Logos4Indexer.ex_8a181d29256f3176b92d17aba408ca2a81392fe_08198dbe\Report.wer

Logos4Indexer.exe Stopped working 10/13/2010 10:04:16 PM jjohnson 0xc0000417 0x0006c955 MSVCR90.dll 9.0.30729.4926 C:\Users\jjohnson\AppData\Local\Logos4\System\Logos4Indexer.exe 20,966 C:\Users\jjohnson\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Logos4Indexer.ex_8ac7cbb4e0f046b6914ba9b6bff74c78f9e4a9_0d357994\Report.wer

Logos4Indexer.exe Stopped working 10/13/2010 9:33:15 PM jjohnson 0xc0000417 0x0006c955 MSVCR90.dll 9.0.30729.4926 C:\Users\jjohnson\AppData\Local\Logos4\System\Logos4Indexer.exe 20,966 C:\Users\jjohnson\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Logos4Indexer.ex_8ac7cbb4e0f046b6914ba9b6bff74c78f9e4a9_0ec11dcd\Report.wer

As you can see, the problems are with Win 7 components. The last words I got were that if it happened again I needed to take it up with Microsoft. With the variety of conflicts with L4 and native windows DLLs it is not an OS problem since the rest of my applications play nice with them. I have attached the last indexer log...I'm waiting for another crash.

Anyone have any ideas?

JP

Find more posts tagged with

Comments

Bradley Grainger (Logos)

Ever since I reinstalled I have had some BSODs with Memory Management and page fault in non-paged area, etc. When I look at the crashdumps in appcrashview, this is what I see (these are the last 5):

It's impossible for a "user mode" application (like Logos 4) to have a bug that directly causes a BSOD (since it's the OS's job to prevent that), so this points to an underlying hardware or driver problem. The Logos 4 indexer is a very RAM and CPU intensive application, and the extra load it puts on the computer can possibly cause problems that don't show up under light usage. (See also http://community.logos.com/forums/t/17747.aspx.)

I recommend running a stress test on your computer to rule out (or confirm) the possibility of hardware issues. Please download Prime95 from http://mersenneforum.org/gimps/p95v2511.zip (assuming you are running 32-bit Windows; see http://www.mersenne.org/freesoft/ for other versions of the software). This program is commonly used for stress testing hardware (http://en.wikipedia.org/wiki/Prime95#Use_for_stress_testing).

After you unzip it and run prime95.exe, it should ask you if you want to join PrimeNet or just run a Stress Test. Choose the Stress Test option, then the "Blend" option (the default) and let it run. It will be best to start this at the end of the day and let it run overnight. If it's still running with no errors in the morning, then your system has a clean bill of health. If, however, your computer has blue-screened, rebooted, turned off, or Prime95 is reporting an error, then it's likely that there's an underlying hardware problem that is causing the crashes in Logos 4.