[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2693
  • Last Modified:

Office ntdll.dll crashes

Hi there, we currently having the below error message be it Outlook, Word even IE. This is happening on about 30 computers. They're crashing about 4 to 6 times a day doing different things each time.

Faulting application winword.exe, version 11.0.8326.0, stamp 4c1c23b8, faulting module ntdll.dll, version 5.1.2600.5755, stamp 49901d48, debug? 0, fault address 0x000374e9.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

So far we have removed Office then installed, ran a detect and repair, deleted profiles, setup the users profile onto a new imaged computer. Uninstalled AV, updated Windows XP with the latest patches, updated Office 2003 with the latest patches. Moved the problem users to a different mail store in exchange.  Ran a full AV scan and spyware scan. Stopped the printer spooler services and uninstalled the printer drivers.

We haven't any system changes recently.

If someone has any ideas please let me know.
0
gladmins
Asked:
gladmins
  • 3
  • 2
1 Solution
 
Lukasz ChmielewskiCommented:
0
 
MINDSUPERBCommented:
gladmins,

Here's a similar thread of your issue. You may get information from it.

http://www.experts-exchange.com/Applications/MS_Office/Word/Q_21684861.html

"Ran a full AV scan and spyware scan."
You have mentioned the quoted remarks above, yet in the link I posted the author admitted that even though he ran AV, the virus was not detected.

You might have the same situation.

Sincerely,

Ed
0
 
gladminsAuthor Commented:
Hi mate, have had a look at this thread and I have checked out to see if it was a Virus that wasn't being detected I couldn't see anything similar.

Also I have just tried running sfc / scannow still no cigar!
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
MINDSUPERBCommented:
gladmins,

As I see, you did already all the actions to isolate the problem however, the issue still exist. Have the idea of having System Restore came in? This might be the best bet before doing a fresh install of your operation system.

Sincerely,

Ed
0
 
gladminsAuthor Commented:
Hi

This was down to a printer driver installed on a print server which caused MS applications to crash. It became apparent when we ran a vb script across all the desktops for the particular event ID and it was clear when the problem started. We then matched this with chaneg control and a printer driver was installed hours before the PCs started to crash. We initially pointed clients to a new print servers tro identify the driver and then removed the driver from the main print server. The key to solving this issue was the query the event log on all PCs. This then showed us a clear picture when the PCs startted to crash...

Gladmins
0
 
gladminsAuthor Commented:
This was an old question that we struggled to get help with. The answer provided was retrospective and was only known after we fixed the problem
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now