Could Logos 5 be making Word 97 unhappy?

Lately I've been experiencing frequent crashes of Word 97. I've updated, repaired, reinstalled Word multiple times. I thought it was fixed for a couple of days but now it is back to crashing, usually when I am moving a window (sometimes a Word window, sometimes a Logos 5 window) by grabbing the top blue bar with the mouse. Now I'm wondering if the issue is something going on between Logos and Word. Are the attached Logos log files (which are from the time of my last Word crash and recovery) enlightening to anyone?

Many thanks!

4606.Logos.log

2620.LogosIndexer.log

Find more posts tagged with

Comments

DMB

Until someone intelligent answers, your Logos.log looks like a clean exit.

Running Word97 (97?!), Vista, and Logos5 seems like an invitation.

But that said, I'm on Windows7/64, and run some of the latest art packages, and Logos5 crashes. Of course it's ONLY Logos5 that crashes.

And it's random, so when I see a crash, I automatically reach for the Logos icon. Libby (Libronix) NEVER crashes; she's kind to me.

Mary-Ellen

https://community.logos.com/discussion/comment/526724#Comment_526724

(97?!)

Yep, the ol' Toshiba is still kicking. I anticipate that could end any minute, however, so I back-up often. [:D]

Thanks for taking a look.

Dave Hooton

I thought it was fixed for a couple of days but now it is back to crashing, usually when I am moving a window (sometimes a Word window, sometimes a Logos 5 window) by grabbing the top blue bar with the mouse.

Go to Control Panel > System, click Advanced system settings, click Advanced, Performance Settings then Visual Effects tab and uncheck show window contents while dragging. See if that makes a difference

Now I'm wondering if the issue is something going on between Logos and Word. Are the attached Logos log files (which are from the time of my last Word crash and recovery) enlightening to anyone?

Nothing untoward in the logs. You need to look at the Window Event Viewer for Word 97:-

Go to the Start Menu and type Event Viewer in the search box. When you see the link for event viewer appear in the search results, click it.
When the event viewer opens, expand the Windows Logs folder, and then click on Application.
Scroll through the list until you come to the time and date when Word crashed.
Click once on the row to display the error details in the lower part of the window.

Bradley Grainger (Logos)

Now I'm wondering if the issue is something going on between Logos and Word.

The only interaction between Logos and Word is the Office Smart Tag (which is off by default, and to the best of my knowledge is only supported by Office 2003 and later). It seems unlikely to me that the problem is caused by Logos.

If it's caused by moving a window, it could be due to having a Windows "enhancement" or "skinning" product or multi-monitor utility installed, such as WindowBlinds, UltraMon, etc. Do you use anything like that?

Mary-Ellen

https://community.logos.com/discussion/comment/526790#Comment_526790

error details in the lower part of the window.

Excellent instructions! I intrepidly clicked away. Here's what I find there from the crash contemporaneous with the log files. Does this convey anything useful?

Log Name:      Application
Source:        Application Error
Date:          9/16/2013 11:11:38 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Mom-Tablet
Description:
Faulting application WINWORD.EXE, version 12.0.6683.5001, time stamp 0x51fd43eb, faulting module gdiplus.dll_unloaded, version 0.0.0.0, time stamp 0x515ba857, exception code 0xc0000005, fault offset 0x690c74b2, process id 0x1520, application start time 0x01ceb2eddcbda3c7.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-09-16T15:11:38.000Z" />
    <EventRecordID>306666</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Mom-Tablet</Computer>
    <Security />
</System>
<EventData>
    <Data>WINWORD.EXE</Data>
    <Data>12.0.6683.5001</Data>
    <Data>51fd43eb</Data>
    <Data>gdiplus.dll_unloaded</Data>
    <Data>0.0.0.0</Data>
    <Data>515ba857</Data>
    <Data>c0000005</Data>
    <Data>690c74b2</Data>
    <Data>1520</Data>
    <Data>01ceb2eddcbda3c7</Data>
</EventData>
</Event>

Mary-Ellen

https://community.logos.com/discussion/comment/526797#Comment_526797

Windows "enhancement" or "skinning" product or multi-monitor utility installed, such as WindowBlinds, UltraMon, etc. Do you use anything like that?

Nothing that I added. I do use a second monitor, with the Intel Graphics Media Accelerator Driver that came with the laptop. Come to think of it, when I open floating windows in Logos, more often than not they open on the "wrong" screen. I usually maximize Logos on the larger secondary monitor, and floating windows often pop up partly off-screen on the smaller laptop screen. It looks like they think they are opening on a larger size screen.

Dave Hooton

https://community.logos.com/discussion/comment/526816#Comment_526816

faulting module gdiplus.dll_unloaded

I Google'd for gdiplus.dll_unloaded word crash and a fix is elusive. It affects newer versions of Word as well. Here are some suggestions:-

Mary-Ellen

https://community.logos.com/discussion/comment/526842#Comment_526842

Dave, thank you so much for your research! You are a gentleman and a scholar! I'll work my way through the ideas on those pages . . . It's some comfort to know I'm not the only one with this mysterious problem.