- Application: sitecomp.exe, module: kernel32.dll - See
ME954214 for a hotfix applicable to Microsoft System Center Configuration Manager 2007.
- Application: printdrvstress.exe, module: ntdll.dll - See
ME934013.
- Application: exshell.exe, module: ntdll.dll - See
ME950112.
- Application: vds.exe, module: ntdll.dll - See
ME948699 and
ME949001 for hotfixes applicable to Microsoft Windows Server 2003.
- Application: nissvc.exe, module: msvcrt.dll - See
ME945166 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: Rtvscan.exe, module: Rtvscan.exe - See
EV100004.
- Application: grovel.exe, module: grovel.exe - See
ME939383 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: mcupdate.exe, module: kernel32.dll - See
ME935685 for a hotfix applicable to Windows Vista.
- Application: devenv.exe, module: ntdll.dll - See
ME935842 for a hotfix applicable to Microsoft Visual Studio 2005.
- Application: WinCal.exe, module: WinCal.exe - See
ME933942 for a hotfix applicable to Windows Vista.
- Application: msoobe.exe, module: urlmon.dll - See
ME932442.
- Application: lsass.exe, module: secur32.dll - See
ME897648 for a hotfix applicable to Microsoft Windows Server 2003 and Microsoft Windows XP, and
ME870997 for a hotfix applicable to Microsoft Windows 2000 and Microsoft Windows XP.
- Application: emsmta.exe, module: kernel32.dll - See
ME924835 for a hotfix applicable to Microsoft Exchange Server 2003.
- Application: setup.exe, module: wizardui.dll - See
ME842466.
- Application: spoolsv.exe, module: unknown - From a newsgroup post: "Disabling DEP (Data Execution Protection) solved the problem". See
ME875352 for a detailed description of the Data Execution Prevention (DEP) feature.
- Application: mmc.exe, module: hipobjects.dll - See
ME930285 for a hotfix applicable to Microsoft Host Integration Server 2006.
- Application: mmc.exe, module: aclui.dll - See
ME870995 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: fs9.exe, module: mfc70.dll - See
ME555608.
- Application: w3wp.exe, module: davex.dll - See
ME945401 for a hotfix applicable to Microsoft Exchange Server 2003.
- Application: w3wp.exe, module: rpcrt4.dll - See
ME917781 and
ME933729.
- Application: w3wp.exe, module: exprox.dll - See
ME329067 and
ME953539.
- Application: w3wp.exe, module: mscorwks.dll - See
ME913384 for a hotfix applicable to Microsoft .NET Framework 2.0.
- Application: w3proxy.exe, module: LinkTrans.dll - See
ME915411 for a hotfix applicable to Microsoft Internet Security and Acceleration Server 2000.
- Application: winlogon.exe, module: rpcrt4.dll - See
ME914048.
- Application: winlogon.exe, module: ntdll.dll - See
ME914048.
- Application: outlook.exe, module: rtfhtml.dll - See
ME318658.
- Application: tecadwins001.exe, module: msvcrt.dll - See
EV100013
- Application: mapsvc.exe, module: mapper.dll - See
ME883520 for a hotfix applicable to Microsoft Windows Services for UNIX 3.5.
- Application: svchost.exe, module: qmgr.dll - See
ME939159 for a hotfix applicable to Windows Vista.
- Application: svchost.exe, module: ntdll.dll - See
ME910666.
- Application: svchost.exe, module: iassam.dll - See
ME894538 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: svchost.exe, module: rpcss.dll - Microsoft article
ME326964 describes a similar situation. Also, several newsgroup posts suggest that installing
ME823980 solves the problem.
- Application: svchost.exe, module: msi.dll - See
ME927385 and
ME939273.
- Application: snalink.exe, module: snaipdlc.dll - See
ME898555 for a hotfix applicable to Microsoft Host Integration Server 2004.
- Application: msimn.exe, module: msoe.dll - See
ME898807.
- Application: mngcli.exe, module: snatrc.dll - See
ME883850.
- Application: store.exe, module: unknown - See
ME947174 for a hotfix applicable to Microsoft Exchange Server 2003.
- Application: store.exe, module: store.exe - See
ME833817 for a hotfix applicable to Microsoft Exchange Server 2003, and
ME933398 for additional information on this event.
- Application: store.exe, module: exoledb.dll - See
ME903935 for a hotfix applicable to Microsoft Exchange Server 2003 and
ME945938 for additional information.
- Application: store.exe, module: EXWIN32.DLL - See
EV100009.
- Application: dllhost.exe, module: DasServer.dll - See
ME924394.
- Application: dllhost.exe, module: scrrun.dll - See
ME906092 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: dllhost.exe, module: ntdll.dll - See
ME898921.
- Application: dllhost.exe, module: sqloledb.dll - See
ME838976 for a hotfix applicable to Microsoft Data Access Components.
- Application: explorer.exe, module: kernel32.dll - See
ME898051 for a hotfix applicable to Microsoft Windows Server 2003 and
ME322687 for additional information.
- Application: explorer.exe, module: shlwapi.dll - See
EV100002.
- Application: explorer.exe, module: rkadmin.dll – See
ME900004 for information on this event.
- Application: explorer.exe, module: ntdll.dll - See
ME824136 for a hotfix applicable to Microsoft Windows XP and Microsoft Windows 2000.
- Application: wmiprvse.exe - See
ME914831 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: wmiprvse.exe, module: unknown - See
ME948730.
- Application: wmiprvse.exe, module: HMonitor.dll - From a newsgroup post: "Adjusting configuration and security for WMI namespace, solved the problem. See
ME325353 for information on how to do this".
- Application: wmiprvse.exe, module: svrenumapi.dll - See
ME938911 for a hotfix applicable to Microsoft SQL Server 2005 and
ME942907 for additional information.
- Application: wmiprvse.exe, module: Fastprox.dll - See
ME835438 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: wmiprsve.exe, module: mngbase.dll - See
ME916137 for a hotfix applicable to Microsoft Host Integration Server 2000 and 2004.
- Application: wmiprvse.exe - See
EV100012
- Application: inetinfo.exe, module: unknown - See
ME930952 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: inetinfo.exe - From a newsgroup post: "I got the hotfix (
ME827214) the other day and applied it. It did require a reboot of the box. I have not had any problems since I applied the hotfix".
- Application: java.exe, module: symcjit.dll - From a newsgroup post: "Please change the symcjit.dll file name to another name. (make a backup for that file). Run "Services.msc" on the SBS 2003 command line. Find the Oracle_POHTTPServer service, right-click on it to change its property to manual, stop the service and then click Apply and OK to save these changes. Change the name of the symcjit.dll file back the way it was. If the problem still exists, please contact Oracle for more support".
- Application: iexplore.exe, module: mshtml.dll - See
ME923996 and
ME949922.
- Application: iexplore.exe, module: browseui.dll - See
EV100002.
- Application: iexplore.exe, module: urlmon.dll - From a newsgroup post: "The problem was found by running the "Filemon utility" (see
EV100014). In the Filemon log, just as a file was downloaded and IE crashed, there was another program installed that also had a file called URLMON.DLL that was registered as well in the registry. When I renamed this file, everything worked as it should". Also, see
ME946627 for additional information about this event.
- Application: locator.exe, module: locator.exe - From a newsgroup post: "It seems to only happen when I am using the computer and it is not connected to the domain. As soon as I connect to the network where the DC resides, the error stops popping up. Removing NAI VirusScan 8i and going back to 7.1.0 fixed this problem".
- Application: Rtvscan.exe, module: PATCH32I.DLL - From a newsgroup post: "We just got off the phone with Symantec. A definition update caused the problem. According to them, our server was set up to aggressively receive updates once every few minutes, rather than the standard schedule, so we pulled an update that was not "fully tested" yet. Right now, about 30 servers and an unknown number of clients are infected. We have to run an executable that Symantec supplied and then manually start the SAV service on each affected box. We are going to patch and fix the servers manually and throw the client fix in a logon script".
If your computer is running Microsoft Windows Services for UNIX 3.5, and all Interix applications stop responding, see
ME914680 for a hotfix applicable to Microsoft Windows Services for UNIX 3.5.