|
|
|
Faulting application winword.exe, version 10.0.262 |
Post a Reply |
From: Geordie on 12/12/2002
I have received on numerous occations the following error whilst using Office XP........anyone know what the problem is????Faulting application winword.exe, version 10.0.2627.0, faulting module ntdll.dll, version 5.1.2600.0, fault address 0x000032bb.
| |
Votes:
Rating: 0
Delete: 0
|
|
--- Replies to this Problem ---
From: Tony on 06/03/2011
Hi,Same problem with word 2003; in my case were and Live Addon from Microsoft office ... uninstalled, renamed Normal.dot as Normal.old and now works fine. Hope it will help someone !!
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Harrison on 02/19/2009
Superb sharing of info! Normal.dot was my problem, too. Yes, renaming to .old was the exact fix.Thanks all for your continued interests in sharing information. Take care!
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Dane on 03/04/2008
I also had the corrupt normal.dot file. ProcessMonitor was very handy. Thanks for the posts.
Followed Jims steps from post on 01\01\08. Thank you Jim!!
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Jim on 01/01/2008
In my case, problem was a corrupt template (Normal.dot) file.
I was running Word 2000 on a Windows XP machine.
Diagnosis and solution came from
http://word.mvps.org/FAQs/AppErrors/ProbsOpeningWord.htmBriefly put:
run winword.exe /a
to bypass loading template. If it works, then rename Normal.dot to Normal.old, and try running word.
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Andrewakl on 06/10/2007
Hi there,Thought I should mention I got the same error with Windows Vista and Office 2007.
Word was causing the same problem and would not start.
Resolve mentioned here says about Xerox printer.
So I deleted the Fuji Xerox Docuprint C525A printer and then Word started no problems. The printer was installed by connecting to a network printer \\machine\printer and it installed the print driver that way. I presume the printer driver installed automatically using a windows XP driver instead of Windows Vista. Who knows! IT does seem related to Fuji Xerox printer drivers though as it works all good now. Regards Andrew.
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Sam on 04/28/2007
I had the same problem but it turned out to be a newly added printer.
I remove the printer and now everything works fine. I hope this helps.
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Andrew on 04/12/2007
Hi,My Solutions was as follows. Download ProcessMonitor from Microsoft (was from Sysinternals) and run it on you PC. Create a filter in process monitor to ONLY show you system activity for WinWord.exe
Now open Word and at the point where it crashes have a look at ProcessMonitor and you will see the file that it was trying to access when it crashed. If Work gives you an message that it can't start DON'T click on OK until after you have looked at ProcessMonitor. For me the problem ended up being a file in C:\Windows\System32\spool\drivers\w32x86\3. It was a file related to a Xerox Printer. After deleting the printer and that file Work worked fine. Good Luck.
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Jan on 03/21/2004
I am getting a similiar error closing Publisher 2002 xp.
Faulting application mspub.exe version 10.0.2621.0, faulting module ntdll.dll, version 5.1.2600.0, fault address 0x0000215e
I have gone as far as wiping hard drive and doing a clean install - now I only have winxp loaded and publisher and still get the error.
Can anyone please help.
Thanks
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Computerpilot on 02/11/2003
I have been taking some time off this board. Sorry for the missed reply.For everyone that is curious, the KBA article is #Q129605. You can also try an SFC (Q185836). Computerpilot
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Kimball on 02/09/2003
Hi,I was wondering if you ever found a solution to this problem. I am getting the same error when I try to open microsoft word on an XP machine. Word was installed from an Office 2000 CD. thanks
kimball
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Computerpilot on 12/15/2002
Sounds like you somehow have the wrong version NTDLL.DLL file. I would extract a new one from your install CD (Windows) and overwrite the current version. This should get rid of your problem.I don't have the KBA article number handy on how to do the extractions. If you need it, then just post back and I will probably be able to find it. Computerpilot
| |
Votes:
Rating: 0
Delete: 0
|
|
|
|
|
