I got this error a few minutes ago. I walked away from my computer to grab lunch and came back to a crash:
Logs attached.
Note so sure as to what's pure about that lot [*-)]
I haven't had such an error yet, hopefully these issues you are having will be resolved soon.
Thomas,
Do you remember what you were doing or what resources you might have had open before you left for lunch? The Logos logs don't appear to show anything about a crash.
Kevin,
I'm not in front of that computer to double check; but all day I've had the Westminster catechism's, confession and Hodges commentaries on the confessions open. Doubtless the NASB95 was open as well.
This one just hit me again in the middle of a class.
Log attached.
http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/78/3808.Logos4.log
I'll attach the new logs to the existing case. Thanks!
And it's back!
I was reading the NAC Luke commentary at 9:2 and center clicked on a link to 4:43, the familiar dialog box above arrived.
Sadly the only log with a timestamp matching is the Logos4.log which shows nothing to my eyes.
The procdump, running behind Logos did not even record a dump file.
I was not able to reproduce the crash just now using the same procedure.
I've updated the existing case for this issue with the new logs.
Sadly this one continues. just got another one.
Please download ListDLLs from http://technet.microsoft.com/en-us/sysinternals/bb896656.aspx, unzip it, and run the following at a command prompt:
listdlls -v logos4 > %temp%\listdlls.txt
Then reply and attach the %temp%\listdlls.txt file.
Here you go sir.
http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/78/7215.listdlls.txt
