Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You may receive a "STOP 0x00000035 NO_MORE_IRP_STACK_LOCATIONS" error message when you try to log on to a domain

You may receive a "STOP 0x00000035 NO_MORE_IRP_STACK_LOCATIONS" error message when you try to log on to a domain

View products that this article applies to.

Symptoms

Consider the following scenario:
  • On a computer that is running Microsoft Windows XP with Service Pack 2 (SP2), Microsoft Windows XP with Service Pack 3 (SP3), Microsoft Windows Server 2003 with Service Pack 1 (SP1), or Microsoft Windows Server 2003 with Service Pack 2 (SP2), you install more than three programs that are related to file security. For example, you install more than three antivirus programs or file-encryption programs.
  • The computer is part of a domain.
In this scenario, when you try to log on to the domain, you may receive a Stop error message that is similar to the following:
STOP 0x00000035 (0x8207ecd8, 0x00000000, 0x00000000, 0x00000000) NO_MORE_IRP_STACK_LOCATIONS
Note The first parameter in this error message may vary.

↑ Back to the top

Cause

This problem occurs because the Mup.sys driver assumes that there must be no more than three file-system filter drivers running at the same time. The Mup.sys driver handles Distributed File System (DFS) file I/O requests. If there are four or more file system filter drivers, the I/O request packet (IRP) location buffer that is pre-allocated by Mup.sys will overflow. When this occurs, you receive the Stop error that is described in the Symptoms section.

↑ Back to the top

Resolution

Hotfix information for Windows XP

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. 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:
http://support.microsoft.com/contactus/?ws=support
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 have Windows XP SP2 installed on the computer.

Restart requirement

You must restart the 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.
File nameFile versionFile sizeDateTimePlatform
Mup.sys5.1.2600.2763105,08823-Sep-200501:26x86

Registry information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
  • On a computer that is running Windows XP with SP3, do not install this hotfix. This hotfix is inclued in Windows XP with SP3.
  • On a computer that is running Windows XP with SP2, install this hotfix or a service pack that resolves this issue.
After you install this hotfix or Service Pack 3 that includes this fix, modify the
DfsIrpStackSize registry entry. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click
    OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup\Parameters
  3. In the right pane, right-click
    DfsIrpStackSize, and then click
    Modify.

    Note If the DfsIrpStackSize registry entry does not exist, you must create it. To do this, follow these steps:
    1. On the Edit menu, point to New, and then click DWORD Value.
    2. Type DfsIrpStackSize, and then press ENTER.
  4. In the Base box, click Decimal, type 10 in the Value data box, and then click OK.

    Notes
    • A value of 10 allows for a maximum of eight file system filter drivers.
    • The default value of the DfsIrpStackSize registry entry is 5. A value of 5 allows for a maximum of three file system filter drivers.
    • If you set the value to a number that is greater than 10, the value is automatically set back to 5.

    • If you do not apply this hotfix, the DfsIrpStackSize registry value is ignored.
  5. Exit Registry Editor.
  6. Restart the computer.

↑ Back to the top

Service pack information for Windows Server 2003

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 for Windows Server 2003

Prerequisites

To apply this hotfix, you must have Windows Server 2003 SP1 installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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 nameFile versionFile sizeDateTimePlatform
Mup.sys5.2.3790.2791100,35213-Sep-200610:25x86
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Mup.sys5.2.3790.2791178,68812-Sep-200621:55x64
Windows Server 2003, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Mup.sys5.2.3790.2791310,78412-Sep-200621:55IA-64

Registry information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
  • On a computer that is running Windows Server 2003 with SP2, do not install this hotfix. This hotfix is inclued in Windows Server 2003 with SP2.
  • On a computer that is running Windows Server 2003 with SP1, install this hotfix or a service pack that resolves this issue.
After you install this hotfix or Service Pack 2 that includes this fix, modify the DfsIrpStackSize registry entry. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click
    OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup\Parameters
  3. In the right pane, right-click
    DfsIrpStackSize, and then click
    Modify.

    Note You need to create the DfsIrpStackSize registry entry if it does not exist. To do this, follow these steps:
    1. On the Edit menu, point to New, and then click DWORD Value.
    2. Type DfsIrpStackSize, and then press ENTER.
  4. In the Base box, click Decimal, type 10 in the Value data box, and then click OK.

    Notes
    • A value of 10 allows for a maximum of eight file system filter drivers.
    • The default value of the DfsIrpStackSize registry entry is 5. A value of 5 allows for a maximum of three file system filter drivers.
    • If you set the value to a number that is greater than 10, the value is automatically set back to 5.

    • If you do not apply this hotfix, the DfsIrpStackSize registry value is ignored.
  5. Exit Registry Editor.
  6. Restart the computer.

↑ Back to the top

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 Microsoft Windows Server 2003 Service Pack 2.

↑ Back to the top

More Information


Note for later operating systems like Microsoft Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2 there is a functional equivalent for the Windows XP/2003 DfsIrpStackSize registry entry with a name of IrpStackSize.

Name: IrpStackSize

Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup\Parameters

Type: DWORD

Default Value: 3

Min Value: 3

Max Value: 10 (decimal)

By default MUP initialisation will set the device object stack size to be 3. An Administrator may specify a larger number, but decimal 10 is the maximum value allowed. A Reboot is required for this change to take effect.


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

↑ Back to the top

Keywords: kbautohotfix, kbwinserv2003presp2fix, kbqfe, kbhotfixserver, kbwinxpsp3fix, kbwinxppresp3fix, kbentirenet, kbfix, kbbug, kbpubtypekc, kb

↑ Back to the top

Article Info
Article ID : 906866
Revision : 3
Created on : 4/17/2018
Published on : 4/18/2018
Exists online : False
Views : 525