A Stop error occurs on a Windows Server 2003-based server when a user accesses shared files on the server by using an SMB connection

When a user accesses shared files on the server by using a server message block (SMB) connection, one of the following Stop errors occurs on a Windows Server 2003-based server:

• 0x0000000A (IRQL_NOT_LESS_OR_EQUAL)
• 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED)
• 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA)
• 0x000000C5 (DRIVER_CORRUPTED_EXPOOL)
• 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)
• 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
• 0x00000024 (NTFS_FILE_SYSTEM)

This problem has typically been observed on terminal server platforms where user activities on the network can cause an error.

Note Because of the generality of memory corruption problems, you are not necessarily affected by this specific problem if a Stop error on this list occurs on the server. We recommend that you contact Microsoft Customer Support Services to determine whether this problem is occurring or not.

This problem occurs because the Netbt.sys (NetBIOS) network driver incorrectly handles a buffer when a malformed packet is received from the network.

Invalid fields in a malformed packet are very rare. However, this problem has been reported under certain circumstances on Samba servers that are earlier than version 2.0.28.

This problem has also been reported on networks when malfunctioning network switches corrupt certain data packets on the network.

Hotfix information for Windows Server 2003

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, the server must run Windows Server Windows Server 2003 Service Pack 2.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the following hotfixes:

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 Service Pack 2, x86-based version

Windows Server 2003 Service Pack 2, Itanium-based version

Windows Server 2003 Service Pack 2, x64-based version

Windows XP Service Pack 2, x64-based version

To work around this problem, use one of the following methods.

Workaround 1

If Samba servers that are earlier than version 2.0.28 are used in the network environment, upgrade the Samba servers to version 2.0.28 or a later version.

Workaround 2

If you identify networking hardware that is malfunctioning, repair this hardware. Microsoft Customer Support Services can extract the source IP address of the malformed packet from the call stack.

Workaround 3

You can significantly reduce the number of occurrences of this problem by disabling remote notification of subfolder changes in Windows Explorer. This method does not resolve the root problem, but it does greatly reduce certain network traffic (SMB packets) that can be affected by malformed packets. Therefore, this problem occurs less frequently.

To implement this workaround, install hotfix 831129. Then, follow the steps in the "Installation information" section of Microsoft knowledge base article 831129. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Notes

• If the server is running Windows Server 2003 Service Pack 2, you do not have to install hotfix 831129. This is because hotfix 831129 is already included in Windows Server 2003 Service Pack 2.
• When you enable the NoRemoteRecursiveEvents registry entry or the NoRemoteChangeNotify registry entry on a computer that uses a network-based configuration (such as when a %USERPROFILE% variable points to a network drive or to a UNC path), Windows Explorer does not automatically update the display when file changes or folder changes are made by other users.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The stop error codes that are mentioned in the "Symptoms" section are very common and may occur because of any type of memory corruption. To correctly troubleshoot this problem, you must identify a cause on the network.

When you troubleshoot this problem by using the memory dump that is generated after the Stop error, you may find the netbt!NbtCopyToStartOfIndicate function on top of the call stack of one processor in the system.

For more information about memory dumps, click the following article number to view the article in the Microsoft Knowledge Base:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.