Crash
Logos crashes enough that I thought I'd enable logging, and start posting some of the various log files that show up in the directory. What's attached is my third crash for the night.
I was reading a journal entry, and decided to leave it for the night--so I minimized Logos to the tray. Just before going up to read, I checked my mail (Thunderbird, latest rev); in the middle of the mail download, the Logos crash screen popped up. When I reopen Logos, it's always at an older version of the desktop (IE, I've now lost where I was in my reading, and it's actually going to be pretty hard to find again).
My machine is a Dell Studio XPS 8000, Intel i7 2.8G quad core, 8GB of memory, latest update of Win 7, 700GB hard drive, about 500GB free. I have Logos on auto update, so it's on the latest version.
Russ
Comments
-
RussWhite said:
My machine is a Dell Studio XPS 8000, Intel i7 2.8G quad core, 8GB of memory, latest update of Win 7, 700GB hard drive, about 500GB free. I have Logos on auto update, so it's on the latest version.
WoW Russ, I'm trying not to be envious here.
With hardware & Operating System specs like that you have ruled out my first 10 suspicions. I can only wonder if you've uncovered a driver conflict. I'll be interested in what is causing it since you're running a setup I am seriously considering.
btw: I'm running Vista w 4GB and AMD 64Live and L4 never crashes.
Logos 7 Collectors Edition
0 -
RussWhite said:
Logos crashes enough that I thought I'd enable logging, and start posting some of the various log files that show up in the directory. What's attached is my third crash for the night.
I was reading a journal entry, and decided to leave it for the night--so I minimized Logos to the tray. Just before going up to read, I checked my mail (Thunderbird, latest rev); in the middle of the mail download, the Logos crash screen popped up. When I reopen Logos, it's always at an older version of the desktop (IE, I've now lost where I was in my reading, and it's actually going to be pretty hard to find again).
My machine is a Dell Studio XPS 8000, Intel i7 2.8G quad core, 8GB of memory, latest update of Win 7, 700GB hard drive, about 500GB free. I have Logos on auto update, so it's on the latest version.
Russ
Sorry for the inconvenience - I have submitted your logs to development.
0 -
It looks like you installed Logos 4 to a custom path (C:\data\Logos4). For some reason, the program can't access "C:\data\Logos4\Documents\d2vvnzpb.sup\Documents\documents.idx.bak". There are a lot of very important files you don't want to delete in that folder, but try deleting every file whose name begins with "documents" in "C:\data\Logos4\Documents\d2vvnzpb.sup\Documents\". Windows will probably give you a security prompt when you try to delete some of them, which is the cause of the problem.
0 -
Okay--deleted them... No security warnings, though. It might be the anti-virus software, Trend Micro. I know that for some reason I have problems with being able to save Powerpoint files, too, which seems to be related to it. I'll try excluding the logos folder from PCCillan and see if that fixes it.
I'll let you know if it crashes again...
:-)
Russ
0 -
Well, I have a theory about computers... I can never get enough processing power or memory (especially). I actually bought this one through the Dell refurb page, and then "boosted it up" a little in some places (memory and hard drive). The problem I always run in to is I tend to open a lot of applications at once--for instance, yesterday, while I was working on something for work, I have CorelDRAW (with four or five network diagrams open), Word (with three docs I was copying and pasting between), Visio (for reference to a network diagram), Powerpoint (two presentations), Firefox with a few tabs, Thunderbird, Webex Connect, Outlook (just for calendar), and then, in the background, Logos, of course... I just can't seem to get enough memory, for some reason! I can't imagine why that would be... :-)
:-)
Russ
0 -
24 hours and no crashes... I was getting three or four crashes a day, so I would guess what's happening is PCCillan is locking the files for something, and then Logos tries to write them, eventually times out, and crashes.
Anyone using PCillan should note to add Logos to the exception list.
:-)
Russ
0 -
RussWhite said:
24 hours and no crashes... I was getting three or four crashes a day, so I would guess what's happening is PCCillan is locking the files for something, and then Logos tries to write them, eventually times out, and crashes.
Anyone using PCillan should note to add Logos to the exception list.
:-)
Russ
Thanks Russ I'm glad its working.
0
