Microsoft KB Archive Search

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.

  1. Home
  2. "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

"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

View products that this article applies to.

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:
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

↑ Back to the top

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.

↑ 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:
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:
    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
  • 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 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.7600.20776153,96810-Aug-201004:35x86
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.7600.2077651,56810-Aug-201004:35x86
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.7600.2077653,12810-Aug-201004:35x86
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.7600.20776184,68810-Aug-201005:22x64
Streamci.dll6.1.7600.1638524,14414-Jul-200901:45x64
Swenum.sys6.1.7600.1638512,49614-Jul-200901:45x64
Termdd.sys6.1.7600.2077662,32010-Aug-201005:22x64
Uliagpkx.sys6.1.7600.1638564,59214-Jul-200901:45x64
Vdrvroot.sys6.1.7600.1638536,43214-Jul-200901:45x64
Volmgr.sys6.1.7600.2077672,04810-Aug-201005:22x64
For all supported IA-64-based 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.7600.20776455,53610-Aug-201004:11IA-64
Streamci.dll6.1.7600.1638543,07214-Jul-200901:56IA-64
Swenum.sys6.1.7600.1638516,19214-Jul-200901:56Not applicable
Termdd.sys6.1.7600.20776160,11210-Aug-201004:11IA-64
Vdrvroot.sys6.1.7600.1638566,11214-Jul-200901:56IA-64
Volmgr.sys6.1.7600.20776160,62410-Aug-201004:11IA-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

 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 nameUpdate.mum
File versionNot Applicable
File size1,648
Date (UTC)10-Aug-2010
Time (UTC)08:36
PlatformNot applicable
File nameX86_machine.inf_31bf3856ad364e35_6.1.7600.20776_none_ba7eb61239190390.manifest
File versionNot Applicable
File size9,456
Date (UTC)10-Aug-2010
Time (UTC)08:41
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.7600.20776_none_169d5195f17674c6.manifest
File versionNot Applicable
File size7,894
Date (UTC)10-Aug-2010
Time (UTC)08:44
PlatformNot applicable
File nameUpdate.mum
File versionNot Applicable
File size1,658
Date (UTC)10-Aug-2010
Time (UTC)08:36
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_machine.inf_31bf3856ad364e35_6.1.7600.20776_none_ba805a0839170c8c.manifest
File versionNot Applicable
File size6,844
Date (UTC)10-Aug-2010
Time (UTC)08:37
PlatformNot applicable
File nameUpdate.mum
File versionNot Applicable
File size1,451
Date (UTC)10-Aug-2010
Time (UTC)08:36
PlatformNot applicable

↑ Back to the top

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

↑ Back to the top

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