Network connectivity is lost when many users run applications on a remote server in Windows 7 or Windows Server 2008 R2

Applies to: Windows Server 2008 R2 Service Pack 1Windows Server 2008 R2 DatacenterWindows Server 2008 R2 Enterprise

Symptoms


Consider the following scenario:

  • You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
  • The computer works as a server where more than 50 users run applications by using Remote Desktop Protocol (RDP) at the same time.
  • The server is running under unusual heavy processor (CPU) and network load.
In this scenario, the network interface of the server is reset, and all the connected users may lose network connectivity from this remote server unexpectedly.

Cause


When users run applications on the server, the applications trigger many object identifier (also known as OID) requests to the network miniport driver.

In this case, the Microsoft Network Device Interface Specification (NDIS) driver detects that the network miniport driver does not respond to an object identifier request in two seconds, and then the request times out. In this situation, NDIS resets the network miniport driver. When there are a large number of OID requests issued from the same kernel thread, Windows may detect that the thread is taking up too much CPU time, causing Windows CPU quota enforcement to place the thread on the CPU idle queue. The NDIS driver does not protect the calling thread from being placed on the CPU idle queue, which can cause an OID request to time out.

In severe cases, all users lose TCP network connectivity, and access to their applications is disrupted.

How to obtain this hotfix


To resolve this issue, we have released hotfixes for Windows 7 or Windows Server 2008 R2.

Before you install this hotfix, check the prerequisite of the hotfix.

Hotfix for Windows 7 or Windows Server 2008 R2

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 this specific problem.

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, submit a request to 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 website: 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, you must first install SP1 in Windows 7 or Windows 2008 R2. For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

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

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates.

Status


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