ntdll.dll hassle in MS Word 2000 & 2003

[AntonioAnsell]

Hi..

I've started to get the following Windows Error message when I try to print from MS Word 2000. I then upgraded to MS Office 2003 and it's still the same. I'm using XP Pro with Service Pack 2. Here's the error:

AppName: winword.exe AppVer: 11.0.5604.0 ModName: ntdll.dll
ModVer: 5.1.2600.2180 Offset: 00011629

Thank you in advance.

 

[SirBlack]

Hi Antonio,
First, are you running any AV application? The error you're getting could be due to a corrupted file. This file is located in the c:\windows\system32 or c:\winnt\system32 directory and can also be found in the c:\i386 directory.
If you aren't running an up to date AV program, you can download free apps from Avast or Grisoft. Both are very good programs available @:

http://www.avast.com/eng/download-avast-home.html

http://free.grisoft.com/

Grisoft also offers free AntiSpyware & AntiRootkit apps.

If the file is missing or corrupted beyond repair, you can download the DLL file from:

http://www.dll-files.com/dllindex/pop.php?ntdll

Hope this helps!

Bob

 

[AntonioAnsell]

Thanks Bob...

I'm running Sophos AV...

Strange thing with my problem is it began when I installed an HP LaserJet 4050T printer... Before when I was using a cheap HP colour printer via USB (as opposed to a CAT cable from the PC to the printer (I'm not on a network)I had no problems!

It seems to be printing from MS Word to the LaserJet.

 

[SirBlack]

Hi Antonio,

Judging by your latest post, it suggests at least a partially corrupt printer driver, possibly even a corrupt font. Check that you have the latest driver for your printer and then delete and reinstall it. Not to familiar with Sophos AV, hopefully you check for updates on a regular basis & install as soon as they are available. You may want to download, install & run Grisoft's AV, AS & AntiRoootkit to verify nothing is slipping by. Hope this resolves your problem.

Bob B-)

 

[BadBigBen]

I would also do a system file check, to see if one or more are corrupted...

in a CLI window (runbox i.e.) type SFC /SCANNOW and have your XP CD ready at hand...

what this does is checks for corruption of the system files and replaces them if necessary with good working ones...

also do a memtest (Memtest86+ is good) and a CHKDSK on the C: partition...


Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[linney]

A lot of these indicate the Printer/driver as a cause.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1263492&SiteID=17

http://www.nocrash.com/ncbbs/msgs/2653.shtml

http://www.nocrash.com/ncbbs/msgs/3139.shtml