Microsoft KB Archive/918564

From BetaArchive Wiki

Article ID: 918564

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



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS

After you install the Microsoft Windows Server 2003 Scalable Networking Pack on a Microsoft Windows Server 2003-based computer, you may receive a Stop error message that resembles one of the following:

  • x64-based versions

    STOP: 0x0000003B (0xc0000005, parameter2, parameter3, parameter4)
    STATUS_ACCESS_VIOLATION

  • x86-based versions

    STOP 0x0000008E (0xc0000005, parameter2, parameter3, parameter4)
    STATUS_ACCESS_VIOLATION

Note The parameter values vary.

CAUSE

This problem may occur if the following conditions are true:

  • The computer is using offload-enabled network adapters.
  • The same Internet Protocol (IP) address is assigned to multiple network adapters.


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

To resolve this problem, install the hotfix that is described in the following Microsoft Knowledge Base article.

919948 Error message after you install the Windows Server 2003 Scalable Networking Pack and then change the network settings on a Windows Server 2003-based computer: "STOP 0x000000D1"


WORKAROUND

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this problem, do not set duplicate IP addresses to multiple network adapters. To start the computer in Normal mode so that you can configure the IP addresses for the network adapters, follow the steps in either of the following methods:

Method 1

  1. Restart the computer in Safe Mode:
    1. Restart the computer.
    2. When you are prompted to select the operating system to start, press F8.
    3. On the Windows Advanced Option menu, use the ARROW keys to select Safe Mode, and then press ENTER.
    4. If you are using a dual-boot computer or a multiple-boot computer, select Microsoft Windows Server 2003 from the list that is displayed, and then press ENTER.
  2. Click Start, click Run, type regedit, and then click OK.
  3. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TcpIp\Parameters\Interfaces

  4. Select each interface in the list of interface subkeys, and note the IPAddress registry entry in the right pane.
  5. For any entry that uses a duplicate IP address, double-click the entry, and then change the IP address value in the Value data box to a unique value.
  6. Exit Registry Editor.

Method 2

  1. Turn off the computer, disconnect the AC power, and then remove the network adapters.
  2. Restart the computer.
  3. Click Start, click Run, type regedit, and then click OK.
  4. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TcpIp\Parameters\Interfaces

  5. Select each interface in the list of interface subkeys, and note the IPAddress registry entry in the right screen.
  6. For any entry that uses a duplicate IP address, double-click the entry, and then change the IP address value in the Value data box to a unique value.
  7. Exit Registry Editor.


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 Microsoft Windows Server 2003 Scalable Networking Pack



Additional query words: BugCheck NDIS.Sys

Keywords: kbqfe kbwinserv2003sp2fix kbtshoot kbexpertiseinter kberrmsg KB918564