IBM Support

System cannot start Operating System on Microsoft Windows 2012 in Legacy Mode - IBM System x

Troubleshooting


Problem

When users install Microsoft Windows 2012 Operating System (OS) with Unified Extensible Firmware Interface (UEFI) on an IBM System x3250 M4 or x3100 M4 with the start setting set to 'Legacy boot,' with the next system restart, the Operating System cannot be started and the monitor displays only a black screen. Once the issue occurs, the Window 2012 installation DVD or CD kit also will not start.

Resolving The Problem

Source

RETAIN tip: H21416

Symptom

When users install Microsoft Windows 2012 Operating System (OS) with Unified Extensible Firmware Interface (UEFI) on an IBM System x3250 M4 or x3100 M4 with the start setting set to 'Legacy boot,' with the next system restart, the Operating System cannot be started and the monitor displays only a black screen.

Once the issue occurs, the Window 2012 installation DVD or CD kit also will not start.

Affected configurations

The system may be any of the following IBM servers:

  • System x3100 M4, type 2582, any model
  • System x3250 M4, type 2583, any model

This tip is not software specific.

This tip is not option specific.

The following system Basic Input or Output System (BIOS) or Unified Extensible Firmware Interface (UEFI) level(s) are affected:

  • Prior to version 1.04 Build ID: JQE156CUS

Solution

This behavior is corrected in Unified Extensible Firmware Interface (UEFI) Version 1.04 Build ID: JQE156DUS.

The file is available by selecting the appropriate Product Group, type of System, Product name, Product machine type, and Operating system on IBM Support's Fix Central web page, at the following URL:

Additional information

The Compatible System Module (CSM) is a component of the firmware that emulates a Basic Input or Output System (BIOS) environment, allowing legacy Operating Systems and some option Read Only Memories (ROMs) that do not support UEFI to still be used.

The secure start, which can secure the start process by preventing the loading of drivers, Trusted Platform Management (TPM) and Operating System loader that are not signed with an acceptable digital signature.

The root cause is that the CSM waiting time is not long enough to get a return value from secure start (where secure start still is loading with TPM), then this causes the system to hang in the CSM phase (the black screen).

Document Location

Worldwide

Operating System

System x:Operating system independent / None

[{"Type":"HW","Business Unit":{"code":"BU016","label":"Multiple Vendor Support"},"Product":{"code":"QU90ACJ","label":"System x->System x3100 M4->2582"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}},{"Type":"HW","Business Unit":{"code":"BU016","label":"Multiple Vendor Support"},"Product":{"code":"QU90ACK","label":"System x->System x3250 M4->2583"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 January 2019

UID

ibm1MIGR-5093200