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.

Can't save a dump file when the system crashes and the Round Robin MPIO policy is used in Windows Server 2012


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a server that's running Windows Server 2012 or Windows Server 2012 R2.
  • You have Microsoft Multipath I/O (MPIO) boot enabled on the server.
  • You have the MPIO policy set to use Round Robin load balancing policy.
  • You start the system with the available paths connected as specified in the Round Robin policy, and then you disconnect one of the paths.
In this scenario, the system crashes, and the dump file is not saved.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website: 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

There are no prerequisites for installing this hotfix in Windows Server 2012.

To apply this hotfix in Windows Server 2012 R2, you must first have update 2919355 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top


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

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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 8" 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.

    VersionProductMilestoneService branch
    6.2.920 0.17 xxxWindows Server 2012RTMGDR
    6.2.920 0.21 xxxWindows Server 2012RTMLDR
  • 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 8 and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Crashdmp.sys6.2.9200.1721961,76019-Dec-201409:54x64
Crashdmp.sys6.2.9200.2133661,76019-Dec-201402:21x64

Windows Server 2012 R2 file information and notes

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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 8.1" 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.

    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows Server 2012 R2RTMGDR
  • 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 8.1 and Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Crashdmp.sys6.3.9600.1762269,44019-Dec-201403:55x64

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_77d94891e5b5febf0c241f5072fd7370_31bf3856ad364e35_6.2.9200.17219_none_47b6bd5d41dc36a6.manifest
File versionNot Applicable
File size701
Date (UTC)19-Dec-2014
Time (UTC)18:13
File nameAmd64_83cc010f788c2040531dd7e22bd7bb3d_31bf3856ad364e35_6.2.9200.21336_none_d83cfa3c0a78ee46.manifest
File versionNot Applicable
File size701
Date (UTC)19-Dec-2014
Time (UTC)18:13
File nameAmd64_microsoft-windows-crashdump_31bf3856ad364e35_6.2.9200.17219_none_fea79d5ba05d1050.manifest
File versionNot Applicable
File size4,950
Date (UTC)19-Dec-2014
Time (UTC)09:58
File nameAmd64_microsoft-windows-crashdump_31bf3856ad364e35_6.2.9200.21336_none_ff189970b98d9bf7.manifest
File versionNot Applicable
File size4,950
Date (UTC)19-Dec-2014
Time (UTC)02:25
File namePackage_1_for_kb3027113_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size1,781
Date (UTC)19-Dec-2014
Time (UTC)18:13
File namePackage_1_for_kb3027113~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,489
Date (UTC)19-Dec-2014
Time (UTC)18:13
File namePackage_2_for_kb3027113_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,233
Date (UTC)19-Dec-2014
Time (UTC)18:13
File namePackage_2_for_kb3027113~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,949
Date (UTC)19-Dec-2014
Time (UTC)18:13
File namePackage_3_for_kb3027113_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size1,792
Date (UTC)19-Dec-2014
Time (UTC)18:13
File namePackage_3_for_kb3027113~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,500
Date (UTC)19-Dec-2014
Time (UTC)18:13
File namePackage_for_kb3027113_rtm_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,848
Date (UTC)19-Dec-2014
Time (UTC)18:13
File namePackage_for_kb3027113_rtm~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,907
Date (UTC)19-Dec-2014
Time (UTC)18:13
File nameUpdate-bf.mum
File versionNot Applicable
File size2,447
Date (UTC)19-Dec-2014
Time (UTC)18:13

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_c9e0ff1ad78f243cbc33a25a2135daad_31bf3856ad364e35_6.3.9600.17622_none_54f3127ae3c3bbf4.manifest
File versionNot Applicable
File size701
Date (UTC)20-Dec-2014
Time (UTC)01:49
File nameAmd64_microsoft-windows-crashdump_31bf3856ad364e35_6.3.9600.17622_none_968a8ba7ea9e3ff9.manifest
File versionNot Applicable
File size4,950
Date (UTC)19-Dec-2014
Time (UTC)03:59
File namePackage_1_for_kb3027113~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,823
Date (UTC)20-Dec-2014
Time (UTC)01:49
File namePackage_2_for_kb3027113~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,709
Date (UTC)20-Dec-2014
Time (UTC)01:49
File namePackage_for_kb3027113_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,691
Date (UTC)20-Dec-2014
Time (UTC)01:49
File namePackage_for_kb3027113_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,561
Date (UTC)20-Dec-2014
Time (UTC)01:49

↑ 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


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, atdownload, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 3027113
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2015
Exists online : False
Views : 155