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.

A hotfix is available that improves the logging capabilities of the Storport.sys driver to troubleshoot poor performance issues for the disk I/O in Windows Server 2008


View products that this article applies to.

Symptoms

On a Windows Server 2008-based computer or on a Windows Vista-based computer, it takes a long time to troubleshoot slow performance or unresponsiveness issues that occur when you perform disk I/O operations.

The most common cause of I/O latency issues is drivers that are faulty or underperforming. Specifically, these latency issues occur on disk drivers or on filter drivers. Disk drivers typically are associated with third-party Storage Area Network (SAN) products. Filter drivers typically are associated with antivirus, security, or encryption products.

↑ Back to the top


Resolution

To resolve this issue, install the following hotfix. By using this hotfix, you can log an event when the latency time for I/O to storage is equal to or greater than a threshold. The user can set the threshold. This operation is taken at the Adapter Driver level so that you can see whether there is a performance issue on the SAN. Then, you can contact the storage vendor to address the issue.

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 the problem described in this article. 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 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

To apply this hotfix, your computer must be running one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

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 (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600 0 . 20xxxWindows VistaRTMLDR
    6.0.600 1 . 22xxxWindows Vista and Windows Server 2008SP1LDR
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are very important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Storport.sys6.0.6001.22623123,78402-Feb-201016:08x86
Storport.sys6.0.6002.22327126,44802-Feb-201015:48x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Storport.sys6.0.6001.22623159,62402-Feb-201016:35x64
Storport.sys6.0.6002.22327166,27202-Feb-201015:45x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Storport.sys6.0.6001.22623374,78402-Feb-201016:18IA-64
Storport.sys6.0.6002.22327372,09602-Feb-201017:38IA-64

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

↑ Back to the top


More information

After you install the hotfix, follow these steps to enable the System log when the latency time for I/O to storage is equal or greater than a threshold:

Command line version:
  1. Click Start, type cmd.
  2. Right-click the cmd icon, and then click Run as Administrator.
  3. At the command prompt, type the following command, and then press ENTER:
    Logman.exe create trace Storport_Disk_IO_ETW_Trace -p Microsoft-Windows-Storport 8 255 -ets -o "c:\trace\Storport_Logging.etl"
    Notes
    • C:\ should be a drive letter where you have ample amount of disk space.
    • The directory that is specified must be created if it does not already exist.
  4. Type the command "perfmon" at the command prompt to open the Reliability and Performance Monitor console.
  5. In the Reliability and Performance Monitor (Perfmon.exe) console, locate the following item:
    Data Collector Sets\Event Trace Sessions
  6. Double-click Storport_Disk_IO_ETW_Trace.
  7. In the Properties list, click Keywords(All), and then click Edit....
  8. In the Automatic list, click to select the IOPerfNotification check box, and then click OK.
  9. In the Properties list, click Filter, and then click Edit....
  10. Click to select the Filter enabled check box, then input a threshold value (measured in milliseconds) in hexadecimal format in the Filter data box, and then click OK

    Note Make sure that you set a hexadecimal value. For example, f would mean 15 milliseconds.
  11. Click OK to save the Storport_Disk_IO_ETW_Trace properties.
  12. Stop the data collector set after the I/O latency issue occurs. To do this, type the following command at the command prompt:
    Logman.exe stop trace Storport_Disk_IO_ETW_Trace -ets
    Note To start the trace again in the future, you can type the following command at the command prompt:
    Logman.exe start Storport_Disk_IO_ETW_Trace -ets
  13. View the log by using the "Event Viewer" utility. Use the "Open Saved Log" function to open the "c:\trace\Storport_Logging.etl" file.

    Note It has to be viewed on a system with the same architecture (x86 or x64 or IA-64), the same operating system, and the same service pack level.
GUI Version:
  1. In the Reliability and Performance Monitor (Perfmon.exe) console, click Data Collector Sets.
  2. Right-click Event Trace Sessions, click New, and then click Data Collector Set.
  3. Input a name for a new data collector set, select the Create manually (Advanced) option, and then click Next.
  4. Click Add..., click the Microsoft-Windows-Storport item, and then click OK.
  5. In the Properties list, click Keywords(All), and then click Edit....
  6. In the Automatic list, click to select the IOPerfNotification check box, and then click OK.
  7. In the Properties list, click Filter, and then click Edit....
  8. Click to select the Filter enabled check box, then input a threshold value (measured in milliseconds) in hexadecimal format in the Filter data box, and then click OK

    Note Make sure that you set a hexadecimal value. For example, f would mean 15 milliseconds.
  9. Follow the wizard to create the new data collector set.
  10. Right-click the newly created data collector set, and then click Properties.
  11. On the File tab, make sure that you have sufficient disk space to store logging.
  12. Right-click the new data collector set, and then click Start.
  13. Stop the data collector set after the I/O latency issue occurs.
  14. View the log by using the "Event Viewer" utility. Use the "Open Saved Log" function to open the "c:\trace\Storport_Logging.etl" file.
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

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameUpdate.mum
File versionNot Applicable
File size3,565
Date (UTC)03-Feb-2010
Time (UTC)10:39
PlatformNot Applicable
File nameX86_9db3429df4ea5b4ba6fcedf495bfe11a_31bf3856ad364e35_6.0.6002.22327_none_a636292e0833bb4c.manifest
File versionNot Applicable
File size696
Date (UTC)03-Feb-2010
Time (UTC)10:39
PlatformNot Applicable
File nameX86_a788da6bf18bf49742b662f97a7aa22c_31bf3856ad364e35_6.0.6001.22623_none_ce5a360005eab4ac.manifest
File versionNot Applicable
File size696
Date (UTC)03-Feb-2010
Time (UTC)10:39
PlatformNot Applicable
File nameX86_microsoft-windows-storport_31bf3856ad364e35_6.0.6001.22623_none_27f355f84959fb47.manifest
File versionNot Applicable
File size5,145
Date (UTC)02-Feb-2010
Time (UTC)20:22
PlatformNot Applicable
File nameX86_microsoft-windows-storport_31bf3856ad364e35_6.0.6002.22327_none_29ddc908467cb5c7.manifest
File versionNot Applicable
File size5,145
Date (UTC)02-Feb-2010
Time (UTC)18:11
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_7e806841149921beddf8637e45a4a7a6_31bf3856ad364e35_6.0.6001.22623_none_472f939c2da02125.manifest
File versionNot Applicable
File size700
Date (UTC)03-Feb-2010
Time (UTC)10:39
PlatformNot Applicable
File nameAmd64_a3f37b81871d4466573d1c1a388d7e61_31bf3856ad364e35_6.0.6002.22327_none_85def9e146feef27.manifest
File versionNot Applicable
File size700
Date (UTC)03-Feb-2010
Time (UTC)10:40
PlatformNot Applicable
File nameAmd64_microsoft-windows-storport_31bf3856ad364e35_6.0.6001.22623_none_8411f17c01b76c7d.manifest
File versionNot Applicable
File size5,397
Date (UTC)02-Feb-2010
Time (UTC)17:44
PlatformNot Applicable
File nameAmd64_microsoft-windows-storport_31bf3856ad364e35_6.0.6002.22327_none_85fc648bfeda26fd.manifest
File versionNot Applicable
File size5,397
Date (UTC)02-Feb-2010
Time (UTC)16:45
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size3,593
Date (UTC)03-Feb-2010
Time (UTC)10:40
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_3a0e011b3e66e1570cbe2d999fafa99f_31bf3856ad364e35_6.0.6002.22327_none_9e9a775ec3ad09d5.manifest
File versionNot Applicable
File size698
Date (UTC)03-Feb-2010
Time (UTC)10:39
PlatformNot Applicable
File nameIa64_935c77a67b4b7aea6bfabf7a381e9e40_31bf3856ad364e35_6.0.6001.22623_none_922283298434d593.manifest
File versionNot Applicable
File size698
Date (UTC)03-Feb-2010
Time (UTC)10:39
PlatformNot Applicable
File nameIa64_microsoft-windows-storport_31bf3856ad364e35_6.0.6001.22623_none_27f4f9ee49580443.manifest
File versionNot Applicable
File size5,395
Date (UTC)02-Feb-2010
Time (UTC)21:50
PlatformNot Applicable
File nameIa64_microsoft-windows-storport_31bf3856ad364e35_6.0.6002.22327_none_29df6cfe467abec3.manifest
File versionNot Applicable
File size5,395
Date (UTC)02-Feb-2010
Time (UTC)18:20
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,748
Date (UTC)03-Feb-2010
Time (UTC)10:39
PlatformNot Applicable

↑ Back to the top


Keywords: kbprb, kbsurveynew, kbexpertiseadvanced, kbhotfixserver, kbautohotfix, kbqfe, kbfix, KB979764

↑ Back to the top

Article Info
Article ID : 979764
Revision : 3
Created on : 3/22/2010
Published on : 3/22/2010
Exists online : False
Views : 321