Microsoft KB Archive/919948

From BetaArchive Wiki

Article ID: 919948

Article Last Modified on 12/3/2007



APPLIES TO

  • Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
  • Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
  • Microsoft Windows Server 2003 R2 Standard x64 Edition
  • Microsoft Windows Server 2003 R2 Enterprise x64 Edition
  • Microsoft Windows Server 2003 R2 Datacenter x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Server 2003 Service Pack 1, when used with:
    • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
    • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
    • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
    • Microsoft Windows Small Business Server 2003 Standard Edition
    • Microsoft Windows Small Business Server 2003 Premium Edition
    • Microsoft Windows Server 2003, Web Edition
    • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
    • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems




SYMPTOMS

Consider the following scenario. You install the Microsoft Windows Server 2003 Scalable Networking Pack on a Windows Server 2003-based computer. Then, you change the network settings. For example, you configure the computer to use a static IP address instead of Dynamic Host Configuration Protocol (DHCP), or vice versa. Or, you change the default gateway address. In this scenario, you receive a Stop error message that resembles the following:

STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL

Note The parameter values may vary.


CAUSE

This problem occurs when the computer is using a TCP Offload-enabled network adapter. Specifically, when a change is made to the route table, Windows Server 2003 R2 performs a check to determine whether a reconnection to any existing connection can be made over the same path. Occasionally, the new route is not fully initialized. Therefore, a "Stop 0x000000D1" error is generated.

STATUS

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

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003


Hotfix information

Prerequisites

You must be running one of the following operating systems to install this hotfix:

  • Windows Server 2003 versions with SP1
  • Windows Server 2003, Itanium versions with SP1
  • Windows Server 2003, R2 versions
  • Windows x64 versions

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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, x86-based versions
File name File version File size Date Time Platform
Tcpip.sys 5.2.3790.2723 386,048 13-Jun-2006 10:46 x86
Windows Server 2003, x64-based versions
File name File version File size Date Time Platform
Tcpip.sys 5.2.3790.2723 813,056 13-Jun-2006 13:04 x64
Windows Server 2003, Itanium-based versions
File name File version File size Date Time Platform
Tcpip.sys 5.2.3790.2723 1,284,096 13-Jun-2006 13:06 IA-64


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

MORE INFORMATION

For more information about the Windows Server 2003 Scalable Networking Pack, click the following article number to view the article in the Microsoft Knowledge Base:

912222 The Microsoft Windows Server 2003 Scalable Networking Pack release




Technical support for x64-based versions of Microsoft Windows

Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:

For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:



For more information, 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



Additional query words: BugCheck Winx64 Windowsx64 64bit 64-bit

Keywords: kbqfe kbwinserv2003sp2fix kberrmsg kbbug kbexpertiseinter KB919948