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.

"0x0000007B" Stop error after you replace an identical iSCSI network adapter in Windows Server 2008 R2 SP1 or in Windows 7 SP1


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1) or Windows 7 Service Pack 1 (SP1). The computer supports PCI Express Serial Number Capability.
  • You configure the computer to start from an iSCSI disk.
  • You use an identical device to replace the iSCSI network adapter. For example, the network adapter is a separate network adapter card, or the network adapter is a built-in device on a motherboard.

    For example, you replace the device because of a hardware failure.
  • You log on to the computer, and then you restart the computer.
In this scenario, 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 issue.
  • A similar issue occurs on computers that are running Windows Server 2008 or Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    2487376 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"

  • Note the replacement network adapter must be placed in the same slot as the original network adapter.
  • 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 reinstallation of the device does not occur.
  • 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 issue occurs because Windows recognizes the network adapter or the motherboard as a new device.

When the serial number of the network adapter or of the motherboard differs from the serial number of the previous network adapter or motherboard, Windows recognizes a new device.

↑ 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 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: 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 Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

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

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
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 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.1.760
    0.16xxx
    Windows 7 and Windows Server 2008 R2RTMGDR
    6.1.760
    0.20xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
    6.1.760
    1.17xxx
    Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.21xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical 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
Agp440.sys6.1.7600.1638553,31214-Jul-200901:26x86
Amdagp.sys6.1.7600.1638553,31214-Jul-200901:26x86
Isapnp.sys6.1.7600.1638546,65614-Jul-200901:20x86
Msisadrv.sys6.1.7600.1638513,88814-Jul-200901:20x86
Mssmbios.sys6.1.7600.1638528,24014-Jul-200901:20x86
Nv_agp.sys6.1.7600.16385105,02414-Jul-200901:20x86
Pci.sys6.1.7601.17630153,98411-Jun-201104:27x86
Sisagp.sys6.1.7600.1638552,30414-Jul-200901:19x86
Streamci.dll6.1.7600.1638522,09614-Jul-200901:19x86
Swenum.sys6.1.7600.1638512,24014-Jul-200901:19Not applicable
Termdd.sys6.1.7601.1751453,12020-Nov-201012:30x86
Uliagpkx.sys6.1.7600.1638557,42414-Jul-200901:19x86
Vdrvroot.sys6.1.7600.1638532,83214-Jul-200901:19x86
Viaagp.sys6.1.7600.1638553,32814-Jul-200901:19x86
Volmgr.sys6.1.7601.1751453,12020-Nov-201012:30x86
Agp440.sys6.1.7600.1638553,31214-Jul-200901:26x86
Amdagp.sys6.1.7600.1638553,31214-Jul-200901:26x86
Isapnp.sys6.1.7600.1638546,65614-Jul-200901:20x86
Msisadrv.sys6.1.7600.1638513,88814-Jul-200901:20x86
Mssmbios.sys6.1.7600.1638528,24014-Jul-200901:20x86
Nv_agp.sys6.1.7600.16385105,02414-Jul-200901:20x86
Pci.sys6.1.7601.21744154,49611-Jun-201105:54x86
Sisagp.sys6.1.7600.1638552,30414-Jul-200901:19x86
Streamci.dll6.1.7600.1638522,09614-Jul-200901:19x86
Swenum.sys6.1.7600.1638512,24014-Jul-200901:19Not applicable
Termdd.sys6.1.7601.1751453,12020-Nov-201012:30x86
Uliagpkx.sys6.1.7600.1638557,42414-Jul-200901:19x86
Vdrvroot.sys6.1.7600.1638532,83214-Jul-200901:19x86
Viaagp.sys6.1.7600.1638553,32814-Jul-200901:19x86
Volmgr.sys6.1.7601.2174453,12011-Jun-201105:54x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Agp440.sys6.1.7600.1638561,00814-Jul-200901:52x64
Isapnp.sys6.1.7600.1638520,54414-Jul-200901:48x64
Msisadrv.sys6.1.7600.1638515,42414-Jul-200901:48x64
Mssmbios.sys6.1.7600.1638532,32014-Jul-200901:48x64
Nv_agp.sys6.1.7600.16385122,96014-Jul-200901:48x64
Pci.sys6.1.7601.17630184,70411-Jun-201105:39x64
Streamci.dll6.1.7600.1638524,14414-Jul-200901:45x64
Swenum.sys6.1.7600.1638512,49614-Jul-200901:45x64
Termdd.sys6.1.7601.1751463,36020-Nov-201013:33x64
Uliagpkx.sys6.1.7600.1638564,59214-Jul-200901:45x64
Vdrvroot.sys6.1.7600.1638536,43214-Jul-200901:45x64
Volmgr.sys6.1.7601.1751471,55220-Nov-201013:34x64
Agp440.sys6.1.7600.1638561,00814-Jul-200901:52x64
Isapnp.sys6.1.7600.1638520,54414-Jul-200901:48x64
Msisadrv.sys6.1.7600.1638515,42414-Jul-200901:48x64
Mssmbios.sys6.1.7600.1638532,32014-Jul-200901:48x64
Nv_agp.sys6.1.7600.16385122,96014-Jul-200901:48x64
Pci.sys6.1.7601.21744185,21611-Jun-201105:25x64
Streamci.dll6.1.7600.1638524,14414-Jul-200901:45x64
Swenum.sys6.1.7600.1638512,49614-Jul-200901:45x64
Termdd.sys6.1.7601.1751463,36020-Nov-201013:33x64
Uliagpkx.sys6.1.7600.1638564,59214-Jul-200901:45x64
Vdrvroot.sys6.1.7600.1638536,43214-Jul-200901:45x64
Volmgr.sys6.1.7601.2174470,52811-Jun-201105:25x64
For all supported IA-64based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Agp460.sys6.1.7600.16385137,21613-Jul-200923:45IA-64
Isapnp.sys6.1.7600.1638534,38414-Jul-200901:58IA-64
Msisadrv.sys6.1.7600.1638522,59214-Jul-200901:58IA-64
Mssmbios.sys6.1.7600.1638558,43214-Jul-200901:58IA-64
Pci.sys6.1.7601.17630456,06411-Jun-201104:08IA-64
Streamci.dll6.1.7600.1638543,07214-Jul-200901:56IA-64
Swenum.sys6.1.7600.1638516,19214-Jul-200901:56Not applicable
Termdd.sys6.1.7601.17514162,68820-Nov-201010:33IA-64
Vdrvroot.sys6.1.7600.1638566,11214-Jul-200901:56IA-64
Volmgr.sys6.1.7601.17514160,64020-Nov-201010:33IA-64
Agp460.sys6.1.7600.16385137,21613-Jul-200923:45IA-64
Isapnp.sys6.1.7600.1638534,38414-Jul-200901:58IA-64
Msisadrv.sys6.1.7600.1638522,59214-Jul-200901:58IA-64
Mssmbios.sys6.1.7600.1638558,43214-Jul-200901:58IA-64
Pci.sys6.1.7601.21744458,11211-Jun-201104:13IA-64
Streamci.dll6.1.7600.1638543,07214-Jul-200901:56IA-64
Swenum.sys6.1.7600.1638516,19214-Jul-200901:56Not applicable
Termdd.sys6.1.7601.17514162,68820-Nov-201010:33IA-64
Vdrvroot.sys6.1.7600.1638566,11214-Jul-200901:56IA-64
Volmgr.sys6.1.7601.21744164,22411-Jun-201104:13IA-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

This issue was previously resolved by hotfix 2344941 for Windows 2008 R2 and for Windows 7. The hotfix applies to versions of Windows 2008 R2 and Windows 7 that do not have Service Pack 1 applied. Hotfix 2550978 applies only to operating systems that have Service Pack 1 installed. If you installed Service Pack 1 on a computer that has hotfix 2344941 installed, you must apply this new hotfix to resolve this issue on Service Pack 1.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2344941 "0x0000007B" Stop error when you replace an iSCSI or PCI Express network adapter or a motherboard with an identical device on a Windows Server 2008 R2-based or Windows 7-based computer
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-bf.mum
File versionNot applicable
File size1,888
Date (UTC)11-Jun-2011
Time (UTC)09:51
PlatformNot applicable
File nameX86_machine.inf_31bf3856ad364e35_6.1.7601.17630_none_bc00b80d1d06c232.manifest
File versionNot applicable
File size9,456
Date (UTC)11-Jun-2011
Time (UTC)09:56
PlatformNot applicable
File nameX86_machine.inf_31bf3856ad364e35_6.1.7601.21744_none_bc8386143628e349.manifest
File versionNot applicable
File size9,456
Date (UTC)11-Jun-2011
Time (UTC)09:56
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_machine.inf_31bf3856ad364e35_6.1.7601.17630_none_181f5390d5643368.manifest
File versionNot applicable
File size7,894
Date (UTC)11-Jun-2011
Time (UTC)10:00
PlatformNot applicable
File nameAmd64_machine.inf_31bf3856ad364e35_6.1.7601.21744_none_18a22197ee86547f.manifest
File versionNot applicable
File size7,894
Date (UTC)11-Jun-2011
Time (UTC)10:00
PlatformNot applicable
File nameUpdate-bf.mum
File versionNot applicable
File size1,900
Date (UTC)11-Jun-2011
Time (UTC)09:51
PlatformNot applicable
Additional files for all supported IA-64based versions of Windows Server 2008 R2
File nameIa64_machine.inf_31bf3856ad364e35_6.1.7601.17630_none_bc025c031d04cb2e.manifest
File versionNot applicable
File size6,844
Date (UTC)11-Jun-2011
Time (UTC)09:51
PlatformNot applicable
File nameIa64_machine.inf_31bf3856ad364e35_6.1.7601.21744_none_bc852a0a3626ec45.manifest
File versionNot applicable
File size6,844
Date (UTC)11-Jun-2011
Time (UTC)09:51
PlatformNot applicable
File nameUpdate-bf.mum
File versionNot applicable
File size1,429
Date (UTC)11-Jun-2011
Time (UTC)09:51
PlatformNot applicable

↑ Back to the top


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

↑ Back to the top

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