4.0d Beta 4 started crashing as soon as it was opened this morning
Attaching log file. It runs to the point where all the panels are finally displayed, then crashes.
Comments
-
The log file doesn't have the crash exception data. Was a Logos4Crash.txt file created? Are you able to open to a blank layout?
0 -
There was an old one from April there, so I didn't post it. Opening a blank layout does seemt to work. Let me go delete all the old log files and open up the session that was causing the problem and see what happens....
Yep, it crashes when I load the session "Sermon" but only Logos4.log is left behind. This time there's an Logos4Indexer.log too, but that's because some resources got downloaded when I opened an empty session....
Here's the exact crash message:
"Logos Bible Software 4 has encountered a problem and needs to close. We are sorry for the inconvenience."Error signature:
AppName: logos4.exe AppVer: 4.4.4.839 AppStamp:4c17eec4
ModName: mscorwks.dll ModVer: 2.0.50727.3053 ModStamp:4889dc18
fDebug: 0 Offset: 0001d8deUnfortunately, Windows doesn't support copy/paste from the Error Report Contents window. I'll type a few things here that look interesting:
Exception Information
Code: 0xc0000005 Flags: 0x00000000
Record: 0x0000000000000000 Address=0x0000000079e8d8deModule 1
Logos4.exeModule 2
ntdll.dllModule 3
mscores.dll174 modules total
Thread 1
Thread ID: 0x00001318
Context
EDI: 0x00000000 ESI: 0x000000c0 EAX: 0x17f764a0
EBX: 0x00171430 ECX: 0x00000002 EDX: 0x0000005a
EIP: 0x7c90e4f4 EBP: 0x0013e078 SegCs: 0x0000001b
EFlags: 0x00000246 ESP: 0x0013e014 SegSs: 0x000000023Ug, too much more stuff to type.
0 -
Jeffrey, its usually more helpful to simply attached the logs rather than trying to put their content into the message. If you're having trouble with attaching them, let us know.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
That wasn't the Logos4 log. That was the Microsoft stuff (which I give some snippets from since it appears I'm not getting the Logos4 crash log). Sorry for the confusion. Unfortunately, there doesn't seem to be any way for the user to get the Microsoft stuff into a file as the dialog doesn't even support selection and copying.
0 -
Got it. Thanks for the clarification
Have you considered capturing a screen image? That might prove to be easier than retyping.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Jeffrey Glen Jackson said:
That wasn't the Logos4 log. That was the Microsoft stuff (which I give some snippets from since it appears I'm not getting the Logos4 crash log). Sorry for the confusion. Unfortunately, there doesn't seem to be any way for the user to get the Microsoft stuff into a file as the dialog doesn't even support selection and copying.
This may be a problem with .NET. What version of Windows is installed?
0 -
Windows XP SP 3. It's a rather old laptop I use for running the betas and as a server so I can access Logos via remote desktop from other computers and my Windows Mobile devices.
0 -
Jeffrey Glen Jackson said:
Windows XP SP 3. It's a rather old laptop I use for running the betas and as a server so I can access Logos via remote desktop from other computers and my Windows Mobile devices.
It may have been affected by a recent Windows Update, SP2 for .NET 3.5. A workaround is to uninstall the update, KB976769v2. A possible solution is to uninstall the .NET Framework, reinstall 3.5, and redownload updates. See the last post here for the steps: http://forums.techguy.org/windows-xp/928680-latest-windows-xp-updates.html.
0 -
Looks like I don't have SP2 installed. All I show in Add or Remove Programs is:
Microsoft .NET Framework 3.5 SP1 and
Hotfix for Microsoft .NET Framework 3.5 SP1 (KB953595).
0 -
Looks like I am way behind in Windows Update. This will take a few reboots before I'm done.
0 -
Jeffrey Glen Jackson said:
Looks like I am way behind in Windows Update. This will take a few reboots before I'm done.
Microsoft may have pulled SP2 for XP systems. If it continues to crash, you may want to repair/reinstall .NET 3.5.
0 -
I'm still bringing that computer up-to-date. I was way behind and I'm only looking in on the computer the kick off the next reboot (I've lost count how many so far) only every few hours.
0 -
Bringing everything up-to-date, including .NET 3.5, seems to have resolved the issue. At least, it's not dieing immediately now. Thank you.
0
