An updated Storport storage driver (version 5.2.3790.139) is available for Windows Server 2003

When you use the Microsoft Storport storage driver for your host bus adapter (HBA) removable storage, you may experience one or more of the following symptoms:

• On a computer with more than 4 gigabytes (GB) of random access memory (RAM), Storport.sys may generate a kernel-mode Stop error message. On adapters that use 32-bit direct memory access (DMA) on a computer that uses Physical Address Extension and that has more than 4 GB of RAM, the hardware abstraction layer (HAL) may double-map the buffers. Therefore, Storport may pass the virtual address of the original, incorrect buffer to the miniport driver. This problem may occur when you use commands that expect mapped buffers, such as the inquiry command. When you install the hotfix that is described in this article, Storport passes the virtual address of the correct buffer after obtaining it from the HAL.
• If you start your server from an external disk that uses a Storport driver, the installation of some non-Microsoft multipath failover software may generate a kernel-mode "0xa" Stop error message. This problem occurs because Storport handles the IRP_MN_USAGE_NOTIFICATION I/O request packet (IRP) incorrectly. When the lower driver does not complete the IRP synchronously, a Stop error is generated.
• Storport handles SRB_FUNCTION_FLUSH_QUEUE differently than the SCSIPort driver does. This may cause incorrect behavior. For example, SRB_FUNCTION_FLUSH expects the port driver to complete all I/O requests in the logical unit number (LUN) queue and to unfreeze the queue. When you install the hotfix that is described in this article, Storport implements this functionality correctly.
• Storport incorrectly uses the ExAllocatePoolWithTag function instead of the ExAllocatePool function. Therefore, some memory allocations are performed without a tag.

Hotfix information

This hotfix has been replaced by the hotfix that is described in the following Microsoft Knowledge Base article:

837413 hotfix information

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: 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

No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces 817789, 820362, 821138, 823728, 824494, 825236, and 828021.

File information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

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

For additional information about the terminology that is used in this article, click the following article number to view the article in the Microsoft Knowledge Base: