"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

Applies To
Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Standard Windows 7 Enterprise Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Ultimate

Symptoms

Consider the following scenario:

  • You have a computer that is running Windows Server 2008 R2 or Windows 7.
  • You configure the computer to start from an iSCSI disk or PCI Express NIC.
  • The computer supports PCI Express Serial Number Capability.
  • You replace the iSCSI or PCI Express network adapter or the motherboard on the computer with an identical device. 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:

Note

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.

  • A similar problem occurs on Windows Server 2008-based or Windows Vista-based computers. 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 with 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

Cause

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

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:

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, you must be running Windows 7 or 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 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 7 and Windows Server 2008 R2 file information notes

Important Windows 7 and Windows Server 2008 R2 updates are included in the same packages.

  • 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
    0.16xxx
    Windows 7 and Windows Server 2008 R2 RTM GDR
    6.1.760
    0.20xxx
    Windows 7 and Windows Server 2008 R2 RTM LDR
  • 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 Server 2008 R2 and for Windows 7" 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 x86-based versions of Windows 7

File name File version File size Date Time Platform
Agp440.sys 6.1.7600.16385 53,312 14-Jul-2009 01:26 x86
Amdagp.sys 6.1.7600.16385 53,312 14-Jul-2009 01:26 x86
Isapnp.sys 6.1.7600.16385 46,656 14-Jul-2009 01:20 x86
Msisadrv.sys 6.1.7600.16385 13,888 14-Jul-2009 01:20 x86
Mssmbios.sys 6.1.7600.16385 28,240 14-Jul-2009 01:20 x86
Nv_agp.sys 6.1.7600.16385 105,024 14-Jul-2009 01:20 x86
Pci.sys 6.1.7600.20776 153,968 10-Aug-2010 04:35 x86
Sisagp.sys 6.1.7600.16385 52,304 14-Jul-2009 01:19 x86
Streamci.dll 6.1.7600.16385 22,096 14-Jul-2009 01:19 x86
Swenum.sys 6.1.7600.16385 12,240 14-Jul-2009 01:19 Not applicable
Termdd.sys 6.1.7600.20776 51,568 10-Aug-2010 04:35 x86
Uliagpkx.sys 6.1.7600.16385 57,424 14-Jul-2009 01:19 x86
Vdrvroot.sys 6.1.7600.16385 32,832 14-Jul-2009 01:19 x86
Viaagp.sys 6.1.7600.16385 53,328 14-Jul-2009 01:19 x86
Volmgr.sys 6.1.7600.20776 53,128 10-Aug-2010 04:35 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
Agp440.sys 6.1.7600.16385 61,008 14-Jul-2009 01:52 x64
Isapnp.sys 6.1.7600.16385 20,544 14-Jul-2009 01:48 x64
Msisadrv.sys 6.1.7600.16385 15,424 14-Jul-2009 01:48 x64
Mssmbios.sys 6.1.7600.16385 32,320 14-Jul-2009 01:48 x64
Nv_agp.sys 6.1.7600.16385 122,960 14-Jul-2009 01:48 x64
Pci.sys 6.1.7600.20776 184,688 10-Aug-2010 05:22 x64
Streamci.dll 6.1.7600.16385 24,144 14-Jul-2009 01:45 x64
Swenum.sys 6.1.7600.16385 12,496 14-Jul-2009 01:45 x64
Termdd.sys 6.1.7600.20776 62,320 10-Aug-2010 05:22 x64
Uliagpkx.sys 6.1.7600.16385 64,592 14-Jul-2009 01:45 x64
Vdrvroot.sys 6.1.7600.16385 36,432 14-Jul-2009 01:45 x64
Volmgr.sys 6.1.7600.20776 72,048 10-Aug-2010 05:22 x64

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

File name File version File size Date Time Platform
Agp460.sys 6.1.7600.16385 137,216 13-Jul-2009 23:45 IA-64
Isapnp.sys 6.1.7600.16385 34,384 14-Jul-2009 01:58 IA-64
Msisadrv.sys 6.1.7600.16385 22,592 14-Jul-2009 01:58 IA-64
Mssmbios.sys 6.1.7600.16385 58,432 14-Jul-2009 01:58 IA-64
Pci.sys 6.1.7600.20776 455,536 10-Aug-2010 04:11 IA-64
Streamci.dll 6.1.7600.16385 43,072 14-Jul-2009 01:56 IA-64
Swenum.sys 6.1.7600.16385 16,192 14-Jul-2009 01:56 Not applicable
Termdd.sys 6.1.7600.20776 160,112 10-Aug-2010 04:11 IA-64
Vdrvroot.sys 6.1.7600.16385 66,112 14-Jul-2009 01:56 IA-64
Volmgr.sys 6.1.7600.20776 160,624 10-Aug-2010 04:11 IA-64

Status

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

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

  For more information about a related issue, click the following article number to view the article in the Microsoft Knowledge Base:

976042 Windows may fail to boot from an iSCSI drive if networking hardware is changed.

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 name Update.mum
File version Not Applicable
File size 1,648
Date (UTC) 10-Aug-2010
Time (UTC) 08:36
Platform Not applicable
File name X86_machine.inf_31bf3856ad364e35_6.1.7600.20776_none_ba7eb61239190390.manifest
File version Not Applicable
File size 9,456
Date (UTC) 10-Aug-2010
Time (UTC) 08:41
Platform Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name Amd64_machine.inf_31bf3856ad364e35_6.1.7600.20776_none_169d5195f17674c6.manifest
File version Not Applicable
File size 7,894
Date (UTC) 10-Aug-2010
Time (UTC) 08:44
Platform Not applicable
File name Update.mum
File version Not Applicable
File size 1,658
Date (UTC) 10-Aug-2010
Time (UTC) 08:36
Platform Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name Ia64_machine.inf_31bf3856ad364e35_6.1.7600.20776_none_ba805a0839170c8c.manifest
File version Not Applicable
File size 6,844
Date (UTC) 10-Aug-2010
Time (UTC) 08:37
Platform Not applicable
File name Update.mum
File version Not Applicable
File size 1,451
Date (UTC) 10-Aug-2010
Time (UTC) 08:36
Platform Not applicable