Word 2002 Problem

[DS]

PC is running Works 2003 which includes Word 2002 on Wondows 2000 OS SP4.
Word starts fine and seems to function ok, but will randomly close,
sometimes without even hitting a key or button within the app. The Event
Log shows two errors when this occurs:

1) Source = Microsoft Office 10
Category = None
Event ID = 1001

Description: Fault bucket 20257966


2) Source = Microsoft Office 10
Category = None
Event ID= 1000

Description: Faulting application winword.exe, version 10.0.4219.0,
faulting module
unknown, version 0.0.0.0, fault address 0x00000000.


I have already tried recreating printers, renaming normal.dot, detect &
repair, uninstall/reinstall, disabling any extraneous startup
items/screensavers/power mang. Today I suggested that the user try and run
the app from the run line "winword /a" to see if the problem still occurs.

If anybody has any additional ideas to resolve this problem they would be
appreciated.

Kind Regards,
Dave

 

[Rob Schneider]

1. Check for computer viruses.
2. go back to previous restore points.


Hope this is useful to you. Let us know.

rms

 

[Rob]

I am also having the same problems on about 12 computer terminals.

I have installed the latest office updates and still it is not working.

 

[Rob Schneider]

1. Check for computer viruses.
2. go back to previous restore points.
Hope this is useful to you. Let us know.

rms

 

[DS]

The PC doesn't have any viruses, and it's running Win2K so going back to a
previous restore point isn't an option. I'm going to follow up with the
user after today to see if running winword with the /a flag seemed to help
or not. If it did, it is a rather sloppy resolve. I would like to get to
the bottom of the problem.

Thanks,
Dave

 

[DS]

Well... running winword /a didn't work either.

The PC doesn't have any viruses, and it's running Win2K so going back to a
previous restore point isn't an option. I'm going to follow up with the
user after today to see if running winword with the /a flag seemed to help
or not. If it did, it is a rather sloppy resolve. I would like to get to
the bottom of the problem.

Thanks,
Dave

 

[DS]

Although I rarely have problems with Kingston memory, I swapped the memory
out anyway because of the 'fault bucket' error in the event log. The user
hasn't had the problem occur again as of yet.

-Dave

 

[Rob Schneider]

good news. I initially asked myself, though, why was this problem solved
this way when affecting 12 machines, but then I realized we had two
discussion threads here... well done.

Hope this is useful to you. Let us know.

rms