Discussion Locked

Word 97 Error - Painful Error

0 helpful
18 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have spent sooooo much time trying different things, I can not figure this one out....Ill have you try it....

We are on a NT Network, this particular computer is getting Dr. Watson Errors at different areas of the application. Sometimes we would be working under the page setup, other times would would be pasting information. It comes up saying

That a Application Error had occured with WINWORD.exe
access violation (0xc0000005), Address 0x3070aeac.

ACK! I have tried everything. Reinstalling, New profile for the user, new install of windows...the users files are opening and she can use them for a while...a then BAAAM! Error.

I would seriously consider sending whoever fixes this for me a fat check....(if that was possible)...:)
Help.

18 replies

by skitzizzy

Hello,

Access violation tends to indicate some component is trying to access a resource it can't, be it in the file system or in memory, which causes Winword.exe to crash.

I'll assume you've installed the SR-2 patch for Office 97 and that you are using SPack 5 or higher for WinNT. Now a few q's...

Does it work on another users profile or the admin profile? Does the system crash if the user is a power user or an admin rather than a normal user?

Office/Word also relies on the printer drivers to grab it's fonts, page settings etc, so try reinstalling the printer driver with an updated driver, it could be crashing when interfacing with the print driver.

Is Office installed on the C: and is the pagefile located on C:? Check that you have enough pagefile space and if office is running on another drive than C:, give that drive some pagefile space as well.

If the documents are using macros, try turning them off when (if) prompted and testing the documents without the macros running, something in their may be causing a problem as well.

Do you protect part of the documents?

Good luck,

Andy

by dklippert

Delete all TMP files. Word leaves a lot of them around where ever the document was stored. Delete any files starting with a tilde (~).
Locate and Rename/Delete any Normal.dot files. There should be only one.
Start Word on the Start>Run line with:
Winword.exe /a

Check on any odd add-ins and the contents of the Startup folder.
In the original Word 7.0 the suggestion was disable automatic spell checking in the Grammer Check.
I think it was fixed in 7.0a

by gperrie

Does this only happen with certain files? Try noting what files she has problems with and opening them on another PC.

I've had problems with really old files that were converted from WordPerfect and the solution was to open them in a newer version of Office(2000 in this cause - no idea why it didn't have problems!) then copy the doc into a completely new doc.

Gavin

by steve-the-helpdesk

I've had similar Dr Watson errors on NT boxes around my shop. Usually they occur during periods of high disc activity. I seem to have settled them all down by moving as many of the data files off the C: drive and on to a networked fileserver. Then Icreated as big a swap file as I can on the existing C: drive or by adding another small drive and creating extra swap file space on that one. Then comes the hard part - training the user to save their work on the networked drive and leaving the C: drive alone

It worked for me, many times

Good luck, buddy.

Steve

by hjs

Afterlooking at what you have done I would say you have a harware problem. Have you tried this user on another machine? If you have then the problem is the user. Here is why: If you have one user, two different machines and the problem follows then the user is doing something.

by skitzizzy

Hi,

Do the files close after the same amount of time?

Check the duration between auto-saves (Tools --> Options --> Save Tab) and either stretch out the duration or disable it, then test.

Maybe the folder Word is trying to auto-save to is marked Read-only on the network and that is generating the error.

by lphilly2000

Try to unregister & reregister the EXE after cleaning up the system. Delete all of the temp files & reboot first. Then do a Start-run and type in "C:\Program Files\Microsoft Office\Office\Winword.exe" /unregserver (or wherever you have it installed) & click on OK. Then do another Start-run and type in "C:\Program Files\Microsoft Office\Office\Excel.exe" /regserver click OK. You may only see a flash after each OK, but I've had it work with Excel as well. I used to get a lot of Low resource errors before the access violations. Also make sure your Normal.dot is not corrupt.

This discussion is closed to new replies.