Search This Blog

Friday, February 26, 2010

Unexpected Windows 2003 server shutdown when working with a file on DFS share

http://support.microsoft.com/kb/906866

Unlike the scenario described in MS KB (BSOD on logon) in my case a Windows 2003 SP2 Server was producing BSOD when saving Word file on a DFS share (no matter domain or stand-alone one). The bugcheck was: 0x00000035 (0x88ee95f8, 0x00000000, 0x00000000, 0x00000000).
Another server had 0x00000035 (0x87b34008, 0x00000000, 0x00000000, 0x00000000)

If you save the same file somewhere else and then copy it to the share, nothing happens.
Sometimes I saw similar behavior on other Windows 2003 servers when you try to rename a file on DFS share (either from command line or File Explorer).
The hotfix seems to be superseded by SP2 (SP2 has newer version of mup.sys - it's 2-Feb-2007 instead of 23-Sep-2005), so all you need is just to modify the DfsIrpStackSize registry entry and reboot:

Click Start, click Run, type regedit, and then click OK.
  1. Locate and then click the following registry subkey:






    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup\Parameters

  2. 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

  3. 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 (Check mup.sys timestamp - if it's 23-Sep-2005 or later - you do not need to install the hotfix)

  4. Exit Registry Editor.

  5. Restart the computer.


Affected servers:
s00339 ticket PN0000007617745
s00338
S00283
app-prd008
s00408



Followers