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.

FIX: Stop error when you replace an iSCSI network adapter or a motherboard by using an identical device on a Windows Server 2008-based or Windows Vista-based computer: "0x0000007B"


View products that this article applies to.


For a Windows Server 2008 R2 and Windows 7 version of this article, see 2344941 .

↑ Back to the top


Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 or Windows Vista.
  • You configure the computer to start from an iSCSI disk.
  • The computer supports PCI Express Serial Number Capability.
  • You replace the iSCSI network adapter or the motherboard on the computer by using an identical device. For example, you replace the device because of a hardware failure.
  • You log on to the computer and then restart the computer.

In this scenario, you can restart the computer successfully the first time. However, when you try to restart the computer again, you receive the following Stop error message:
STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE

Notes
  • The four parameters in this Stop error message may vary, depending on the configuration of the computer.
  • Not all "0x0000007B" Stop error messages are caused by this problem.

Note: After applying this hotfix, even when you replace the device with the PCI Express device holding a different serial number, the device instance path would not be modified as long as the same device model is connected to the same slot. In this case, the same device instance path, which is stored in the registry, would continue to be used. Thus, the re-installation of the device does not occur.

When you apply this hotfix, length of the serial number in device instance path would be changed from 32 bit to 64 bit. Thus, the device instance path of existing PCI Express devices would be modified and this causes device re-installation of those devices..

Note that if the failed iSCSI network adapter is a built-in device, and you choose to use a different built-in adapter for iSCSI boot, that installing this hotfix will not resolve the issue, because the adapter would not be in the same PCI-Express location. You would need to manually unbind the Light Weight Filter (LWF) from the second network adapter. See the following KBs for more details: KB2507616, KB976042

↑ Back to the top


Cause

This problem occurs because Windows recognizes the network adapter or the motherboard as a new device. This occurs because the serial number of the network adapter or of the motherboard differs from the serial number of the previous network adapter or motherboard.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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 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

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Vista Service Pack 2 (SP2)
  • 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 information

You may have to 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.xxxxx 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 for maintaining 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 Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Agp440.sys6.0.6002.2256753,13610-Jan-201120:53x86
Amdagp.sys6.0.6002.2256754,16010-Jan-201120:53x86
Isapnp.sys6.0.6002.2256746,48010-Jan-201120:53x86
Msisadrv.sys6.0.6002.2256713,20010-Jan-201120:53x86
Mssmbios.sys6.0.6002.2256728,04810-Jan-201120:53x86
Nv_agp.sys6.0.6002.22567105,87210-Jan-201120:53x86
Pci.sys6.0.6002.22567148,88010-Jan-201120:53x86
Rdpdr.sys6.0.6002.22567250,36810-Jan-201114:05x86
Sisagp.sys6.0.6002.2256752,62410-Jan-201120:53x86
Streamci.dll6.0.6002.2256721,90410-Jan-201120:53x86
Swenum.sys6.0.6002.2256712,04810-Jan-201120:53Not applicable
Termdd.sys6.0.6002.2256751,60010-Jan-201120:53x86
Uliagpkx.sys6.0.6002.2256757,74410-Jan-201120:53x86
Viaagp.sys6.0.6002.2256753,64810-Jan-201120:53x86
Volmgr.sys6.0.6002.2256749,55210-Jan-201120:53x86

For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Agp440.sys6.0.6002.2256761,32810-Jan-201120:49x64
Isapnp.sys6.0.6002.2256720,36810-Jan-201120:49x64
Msisadrv.sys6.0.6002.2256714,73610-Jan-201120:49x64
Mssmbios.sys6.0.6002.2256731,63210-Jan-201120:49x64
Nv_agp.sys6.0.6002.22567123,28010-Jan-201120:49x64
Pci.sys6.0.6002.22567178,57610-Jan-201120:49x64
Rdpdr.sys6.0.6002.22567315,90410-Jan-201114:25x64
Streamci.dll6.0.6002.2256723,44010-Jan-201120:49x64
Swenum.sys6.0.6002.2256712,30410-Jan-201120:49x64
Termdd.sys6.0.6002.2256760,81610-Jan-201120:49x64
Uliagpkx.sys6.0.6002.2256764,91210-Jan-201120:49x64
Volmgr.sys6.0.6002.2256764,40010-Jan-201120:49x64

For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Agp460.sys6.0.6002.22567136,70410-Jan-201113:26IA-64
Isapnp.sys6.0.6002.2256734,19210-Jan-201120:45IA-64
Msisadrv.sys6.0.6002.2256721,90410-Jan-201120:45IA-64
Mssmbios.sys6.0.6002.2256754,16010-Jan-201120:45IA-64
Pci.sys6.0.6002.22567441,23210-Jan-201120:45IA-64
Rdpdr.sys6.0.6002.22567711,68010-Jan-201114:10IA-64
Streamci.dll6.0.6002.2256742,89610-Jan-201120:45IA-64
Swenum.sys6.0.6002.2256716,01610-Jan-201120:45Not applicable
Termdd.sys6.0.6002.22567156,56010-Jan-201120:45IA-64
Volmgr.sys6.0.6002.22567145,29610-Jan-201120:45IA-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

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

↑ Back to the top


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 namePackage_1_for_kb2487376~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size2,471
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_2_for_kb2487376~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size2,309
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_3_for_kb2487376~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size2,309
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_client_2~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size1,699
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_client~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size1,436
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size1,695
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_sc~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size1,428
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_server_1~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size1,699
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_server~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot applicable
File size1,436
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File nameX86_machine.inf_31bf3856ad364e35_6.0.6002.22567_none_bc492bb6d51f1380.manifest
File versionNot applicable
File size9,974
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable

Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_machine.inf_31bf3856ad364e35_6.0.6002.22567_none_1867c73a8d7c84b6.manifest
File versionNot applicable
File size8,242
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_1_for_kb2487376~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size2,489
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_2_for_kb2487376~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size2,325
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_3_for_kb2487376~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size2,325
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_client_2~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,711
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_client~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,444
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_sc_1~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,707
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,436
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,711
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_server~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,444
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable

Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_machine.inf_31bf3856ad364e35_6.0.6002.22567_none_bc4acfacd51d1c7c.manifest
File versionNot applicable
File size7,081
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_1_for_kb2487376~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot applicable
File size2,151
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_2_for_kb2487376~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot applicable
File size2,151
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_sc_1~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot applicable
File size1,535
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_sc~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot applicable
File size1,432
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_server_1~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot applicable
File size1,539
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable
File namePackage_for_kb2487376_server~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot applicable
File size1,440
Date (UTC)10-Jan-2011
Time (UTC)20:59
PlatformNot applicable


↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2487376
Revision : 1
Created on : 1/7/2017
Published on : 6/5/2012
Exists online : False
Views : 342