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. Add a fix to improve the logging capabilities of the Storport.sys driver to troubleshoot poor disk I/O performance in Windows Server 2008 R2

Add a fix to improve the logging capabilities of the Storport.sys driver to troubleshoot poor disk I/O performance in Windows Server 2008 R2

View products that this article applies to.

Symptoms

On a Windows Server 2008 R2-based computer, it usually takes you lots of 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 faulty or underperforming drivers. These latency issues occur specifically with disk or 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. With 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 thresholdcan be set by the user. 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 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, your computer must be running Windows Server 2008 R2 or Windows 7.

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 global 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 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • 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 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 7
File nameFile versionFile sizeDateTimePlatform
Storport.sys6.1.7600.20631147,33630-Jan-201007:51x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Storport.sys6.1.7600.20631185,73630-Jan-201008:16x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Storport.sys6.1.7600.20631425,86430-Jan-201006:44IA-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, and then select Binaryfor Data entry format. In the Filter data box, enter a threshold value in little endian format (measured in milliseconds), and then click OK. Please refer to the following table for the most common entries (measured in milliseconds):
    DecimalHexadecimalBinary (little endian)
    1101 00 00 00 00 00 00 00
    5505 00 00 00 00 00 00 00
    10A0A 00 00 00 00 00 00 00
    15F0F 00 00 00 00 00 00 00

    Note You must complete the whole data line in little endian format when you enter the threshold value.
  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 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, and then select Binaryfor Data entry format. In the Filter data box, enter a threshold value in little endian format (measured in milliseconds), and then click OK. Please refer to the following table for the most common entries (measured in milliseconds):
    DecimalHexadecimalBinary (little endian)
    1101 00 00 00 00 00 00 00
    5505 00 00 00 00 00 00 00
    10A0A 00 00 00 00 00 00 00
    15F0F 00 00 00 00 00 00 00

    Note You must complete the whole data line in little endian format when you enter the threshold value.
  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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot Applicable
File size1,674
Date (UTC)01-Feb-2010
Time (UTC)17:36
PlatformNot Applicable
File nameX86_af048c4cddcbb151bd143c9c1b05b319_31bf3856ad364e35_6.1.7600.20631_none_66c4565eda51d968.manifest
File versionNot Applicable
File size696
Date (UTC)01-Feb-2010
Time (UTC)17:36
PlatformNot Applicable
File nameX86_microsoft-windows-storport_31bf3856ad364e35_6.1.7600.20631_none_280e53d7aa7b244b.manifest
File versionNot Applicable
File size15,725
Date (UTC)30-Jan-2010
Time (UTC)08:10
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_3573b9091f04759bc5e410ed568929bc_31bf3856ad364e35_6.1.7600.20631_none_7d147b04e4fff9ec.manifest
File versionNot Applicable
File size700
Date (UTC)01-Feb-2010
Time (UTC)17:36
PlatformNot Applicable
File nameAmd64_microsoft-windows-storport_31bf3856ad364e35_6.1.7600.20631_none_842cef5b62d89581.manifest
File versionNot Applicable
File size15,727
Date (UTC)30-Jan-2010
Time (UTC)08:38
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,906
Date (UTC)01-Feb-2010
Time (UTC)17:36
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_c5da8ab21f1689df98cbaaa98c9f0ea9_31bf3856ad364e35_6.1.7600.20631_none_2f3f6e41c90f5df9.manifest
File versionNot Applicable
File size698
Date (UTC)01-Feb-2010
Time (UTC)17:36
PlatformNot Applicable
File nameIa64_microsoft-windows-storport_31bf3856ad364e35_6.1.7600.20631_none_280ff7cdaa792d47.manifest
File versionNot Applicable
File size15,726
Date (UTC)30-Jan-2010
Time (UTC)08:43
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,684
Date (UTC)01-Feb-2010
Time (UTC)17:36
PlatformNot Applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 978000
Revision : 3
Created on : 9/28/2018
Published on : 9/28/2018
Exists online : False
Views : 380