Microsoft Windows Server Installation Halts with StopCode: 0x0000007B

Troubleshooting

Problem

This document provides information about a problem where a Microsoft Windows server crashed while performing an installation.

Resolving The Problem

Note: The following issue is a unique instance of the 0x0000007B stop code. Refer to the following document prior to proceeding with this procedure. Also, refer to the note at the bottom of this document for a potential circumvention to the problem that does not require changing the firmware.

N1014984, Microsoft Windows Server Crashes with StopCode 0x0000007B

A Microsoft Windows server will crash and display the Stop Code 0x0000007B when it is unable to detect a system drive and/or the loss of the system drive. There are many reasons why Windows can crash and post this Stop Code when it is not able to access the system driver.

In this article, we are identifying a new condition in the iSCSI solution that could lead to or contribute to this failure. However, you might encounter a new problem.

The GbESM firmware is comprised of the following code images:

o	Boot code
o	Switch operating system

At the time this document was written, it was found that the latest Nortel Networks Layer 2/3 GbE Switch Module firmware was at release level v1.2.5.1. This latest release was causing the Windows stop code.

There are the following circumventions to this issue:

o	Go to the previous level v1.2.4.1 of the Nortel firmware (or to the previous release v1.2.3.11).
o	Apply the following code images: o Boot code image = v1.2.5.1 o Operating system image = v1.2.4.1 After the switch met either of the two successful code images, the installation was successful.

Note: Limited testing was performed, and the following was concluded relative to the problem:

There is one change in the Nortel 1.2.5.1 firmware update that will cause this issue. The update will change the default value of the autonegotiation field for the INTERNAL ports from DISABLED to ENABLED. Changing the autonegotiation field back to DISABLED for every INTERNAL port that will be used for iSCSI connectivity resolves this issue.

This same failure can occur when using the Nortel 1.2.4.1 firmware by changing the autonegotiation field for the INTERNAL port(s) used for iSCSI connectivity, from DISABLED to ENABLED.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]

Historical Number

448738819

Was this topic helpful?

Document Information

Modified date:
18 December 2019

UID

nas8N1018896

Tips