APPCRASH, Logos.exe - fault module clr.dll... ugh!

Earl Stuller

It's really wearying how unreliable this program is proving.  Used Logos 3 for a long time with no trouble, but Logos 4 presented persistent problems with crash on start up - Logos 5 worked once and now has the same persistent problem.

Every time I start Logos it reports:

Problem signature:

  Problem Event Name:                        APPCRASH

  Application Name:                             Logos.exe

  Application Version:                           5.2.0.121

  Application Timestamp:                     52ec12c9

  Fault Module Name:                          clr.dll

  Fault Module Version:                        4.0.30319.17929

  Fault Module Timestamp:                  4ffa5753

  Exception Code:                                  c0000005

  Exception Offset:                                001774fe

  OS Version:                                          6.1.7601.2.1.0.768.3

  Locale ID:                                             1033

  Additional Information 1:                  ca2b

  Additional Information 2:                  ca2b9f795dce50ba910ac0c7dc9dc141

  Additional Information 3:                  a0ca

  Additional Information 4:                  a0ca1d6f275ba831378bce488a650a2e

I recognize this is a MS .NET DLL but why is it Logos is the only application that blows up trying to access it.

 

I'm running Windows 7, Home Premium 6.1.7601, SP 1, Build 7601.

Anyone else having this trouble?  Even better, anyone that had this problem that found a solution?

JT (alabama24)

Please enable and post logs as per the wiki: http://wiki.logos.com/Diagnostic_Logging 

Rich DeRuiter

Earl Stuller said:

It's really wearying how unreliable this program is proving.  Used Logos 3 for a long time with no trouble, but Logos 4 presented persistent problems with crash on start up - Logos 5 worked once and now has the same persistent proble

First the good news: most people don't have this problem, so it should be solvable. I run Logos5 on a Win7 machine and have only had crashes very infrequently, and usually when running a beta.

Enable diagnostic Logging, as already suggested. That way we can look under the hood to see what might be solvable. Typically, errors like this require a call or email to Logos tech support, but you never know.

There are a couple of things you might try as well:

• In Control Panel > Programs and Features, find Logos Prerequisites, right click and choose "repair." This is the most likely way to fix this issue, short of calling Logos tech support.
• You could also read this article and see if it applies to you: http://support.microsoft.com/kb/2640103 (Note: there are numerous kinds of errors with clr.dll as it interacts with many programs--see here for example, so make sure that solution applies to your case. A number of diagnostics are included in the article.)

Dave Hooton

Earl Stuller said:

Fault Module Name:                          clr.dll

  Fault Module Version:                        4.0.30319.17929

The KB reference given above refers to version 4.0.30319.526 of clr.dll that is older than yours. I have version 4.0.30319.18408 on the same OS as yours, and have just received a Security Update for NET 4.5.1 (KB 2898869) with version 4.0.30319.18444. I suggest you install this latest update.