This article describes an issue when you make a stress test in iSCSI initiator in Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1. Check out the details of the stress test where this problem occurs.

Resolution

To resolve this issue, install the hotfix that is described in this article or the update rollup (recommended) that contains this hotfix. You must restart the computer after you install the hotfix or update rollup.

Windows version

Hotfix

Hotfix prerequisite

Update rollup

Update rollup prerequisite

Windows 8.1, Windows Server 2012 R2

Click "Hotfix Download Available"

Install Update 2919355 first

Get update rollup

Install Update 2919355 first

Windows 8, Windows Server 2012

Click "Hotfix Download Available"

No prerequisite

Get update rollup

No prerequisite

Windows 7 SP1, Windows Server 2008 R2 SP1

Click "Hotfix Download Available"

No prerequisite

Not available

Not applicable



The update rollup fixes many other issues in addition to the issue that the hotfix fixes. We recommend that you use the update rollup. The update rollup is larger than the hotfix. Therefore, the update rollup takes longer to download.

Details of the stress test

This problem occurs when the stress test has the following conditions:

  • The stress test involves multiple iSCSI targets on external storage.

  • Each iSCSI target contains a Logical Unit Number (LUN).

  • A header and data digest are enabled for a cyclic redundancy check (CRC) function or for a checksum function on an iSCSI Initiator.

  • The test load writes to and reads from each volume.

In this scenario, the computer freezes because of the memory leak caused by the msiscsi.sys driver. 

Additionally, in a cluster environment, the computer (the cluster node) may unexpectedly lose cluster disk reservation before the freeze. Because the msiscsi.sys driver sends wrong information that is stored in leaked memory to the cluster disk driver, this causes the cluster to lose disk reservation.

Status

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

More Information

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

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, submit a request to 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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Registry information

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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 files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17xxx

    Windows 8.1 and Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. 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 8.1

File name

File version

File size

Date

Time

Platform

Msiscsi.sys

6.3.9600.17090

240,472

06-Apr-2014

15:27

x86

For all supported x64-based versions of Windows 8.1and of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Msiscsi.sys

6.3.9600.17090

275,800

06-Apr-2014

16:34

x64

Windows 8 and Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 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 8/Windows Server 2012" 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, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.20xxx

    Windows 8 and Windows Server 2012

    RTM

    LDR

    6.2.920 0.21xxx

    Windows 8 and Windows Server 2012

    RTM

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. 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 8

File name

File version

File size

Date

Time

Platform

Iscsilog.dll

6.2.9200.20555

16,384

06-Nov-2012

04:02

x86

Msiscsi.sys

6.2.9200.21006

238,424

04-Apr-2014

02:12

x86

For all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Iscsilog.dll

6.2.9200.20555

16,384

06-Nov-2012

04:04

x64

Msiscsi.sys

6.2.9200.21006

278,872

04-Apr-2014

03:59

x64

Windows 7 and Windows Server 2008 R2 file information and 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 files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760 1.16xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    GDR

    6.1.760 1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. 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 name

File version

File size

Date

Time

Platform

Iscsilog.dll

6.1.7600.16385

16,384

14-Jul-2009

01:06

x86

Msiscsi.sys

6.1.7601.22647

235,456

04-Apr-2014

02:17

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Iscsilog.dll

6.1.7600.16385

16,384

14-Jul-2009

01:28

x64

Msiscsi.sys

6.1.7601.22647

275,392

04-Apr-2014

02:37

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Iscsilog.dll

6.1.7600.16385

16,384

14-Jul-2009

01:36

IA-64

Msiscsi.sys

6.1.7601.22647

684,992

04-Apr-2014

01:51

IA-64



Additional file information

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×