- Notes, Cautions, and Warnings
- Introduction
- AMP Event Messages
- ASR Event Messages
- BAR Event Messages
- BAT Event Messages
- BIOS Event Messages
- BOOT Event Messages
- CBL Event Messages
- CMC Event Messages
- CPU Event Messages
- CPUA Event Messages
- CTL Event Messages
- DH Event Messages
- DIAG Event Messages
- DIS Event Messages
- DKM Event Messages
- ECM Event Messages
- ENC Event Messages
- EPP Event Messages
- FAN Event Messages
- FC Event Messages
- FCD Event Messages
- FLDC Event Messages
- FSD Event Messages
- HWC Event Messages
- IOID Event Messages
- IOV Event Messages
- IPA Event Messages
- ISM Event Messages
- JCP Event Messages
- LC Event Messages
- LIC Event Messages
- LNK Event Messages
- LOG Event Messages
- MEM Event Messages
- NIC Event Messages
- OSD Event Messages
- OSE Event Messages
- PCI Event Messages
- PDR Event Messages
- PFM Event Messages
- POW Event Messages
- PR Event Messages
- PST Event Messages
- PSU Event Messages
- PSUA Event Messages
- PWR Event Messages
- RAC Event Messages
- RDU Event Messages
- RED Event Messages
- RFL Event Messages
- RFLA Event Messages
- RFM Event Messages
- RRDU Event Messages
- RSI Event Messages
- SEC Event Messages
- SEL Event Messages
- SSD Event Messages
- STOR Event Messages
- SUP Event Messages
- SWC Event Messages
- SWU Event Messages
- SYS Event Messages
- TMP Event Messages
- TMPS Event Messages
- TST Event Messages
- UEFI Event Messages
- USR Event Messages
- VDR Event Messages
- VF Event Messages
- VFL Event Messages
- VFLA Event Messages
- VLT Event Messages
- VME Event Messages
- VRM Event Messages
Event and Error Message Reference Guide for 13th Generation Dell PowerEdge ServersVersion 1.2
UEFI Event Messages
UEFI0000
- Message
- CPU Exception Type 0x00: Divide by Zero (Software).
- Detailed Description
- A CPU type 0x00, divide by zero exception, (type 0x00) occurred in the pre-boot UEFI environment. The software attempted to do a mathematical divide by zero, an illegal operation.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception.Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0001
- Message
- CPU Exception Type 0x03: Breakpoint (Software).
- Detailed Description
- A CPU software breakpoint exception (type 0x03) occurred in the pre-boot UEFI environment. The software used it for debugging purposes.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0004
- Message
- CPU Exception Type 0x06: Invalid Opcode (Software).
- Detailed Description
- A CPU invalid opcode exception (type 0x06) occurred in the pre-boot UEFI environment. The software attempted to execute invalid code.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0005
- Message
- CPU Exception Type 0x07: Math Coprocessor Not Available (Hardware).
- Detailed Description
- A CPU math coprocessor not available (type 0x07) exception occurred in the pre-boot UEFI environment.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0006
- Message
- CPU Exception Type 0x08: Double Fault (Software).
- Detailed Description
- A CPU double fault exception (type 0x08) occurred.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0007
- Message
- CPU Exception Type 0x09: Coprocessor Segment Overrun (Software).
- Detailed Description
- A CPU coprocessor segment overrun exception (type 0x09) occurred in the pre-boot UEFI environment.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0008
- Message
- CPU Exception Type 0x0A: Invalid Task Segment State Segment (TSS) (Software).
- Detailed Description
- A CPU invalid task segment state (TSS) exception (type 0x0A) occurred in the pre-boot UEFI environment.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0009
- Message
- CPU Exception Type 0x0B: Segment Not Present (Software).
- Detailed Description
- A CPU segment not present exception (type 0x0B) occurred in the pre-boot UEFI environment.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0010
- Message
- CPU Exception Type 0x0C: Stack-Segment Fault (Software).
- Detailed Description
- A CPU stack-segment fault (type 0x0C) exception occurred in the pre-boot UEFI environment.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0011
- Message
- CPU Exception Type 0x0D: General Protection (Software).
- Detailed Description
- A CPU general protection (type 0x0D) exception occurred in the pre-boot UEFI environment.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0012
- Message
- CPU Exception Type 0x0E: Page Fault (Software).
- Detailed Description
- A CPU page fault (type 0x0E) exception occurred in the pre-boot UEFI environment. A program accessed a page mapped in the virtual address space, but not loaded in physical memory.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0013
- Message
- CPU Exception Type 0x10: Floating Point Error (Software).
- Detailed Description
- A CPU floating point error (type 0x10) exception occurred in the pre-boot UEFI environment.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0014
- Message
- CPU Exception Type 0x11: Alignment Check (Software).
- Detailed Description
- A CPU alignment check exception (type 0x11) occurred in the pre-boot UEFI environment.
- Recommended Response Action
- Recently installed hardware or updated software may cause this exception. Update or remove the hardware or software.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0015
- Message
- Lifecycle Controller (LC) firmware was not accessible and is therefore in Recovery mode.
- Detailed Description
- The BIOS is unable to access the Lifecycle Controller firmware. No Lifecycle Controller functionality is available while in Recovery Mode.
- Recommended Response Action
- Perform the following actions: 1)Reboot the system. 2) Press F2 during boot to enter System Setup. 3) Select iDRAC Settings then Lifecycle Controller. 4) Change Lifecycle Controller back to Enabled. If subsequent failures occur, press and hold the system ID button down for 15 seconds to reset the iDRAC. For more information on how to reset iDRAC, see iDRAC Users Guide.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0016
- Message
- Lifecycle Controller (LC) firmware was not accessible and is therefore in Recovery mode.
- Detailed Description
- Unable to find a Lifecycle Controller partition. No Lifecycle Controller functionality is available while in Recovery Mode.
- Recommended Response Action
- Perform the following actions: 1)Reboot the system. 2) Press F2 during boot to enter System Setup. 3) Select iDRAC Settings then Lifecycle Controller. 4) Change Lifecycle Controller back to Enabled. If subsequent failures occur, press and hold the system ID button down for 15 seconds to reset the iDRAC. For more information on how to reset iDRAC, see iDRAC Users Guide.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0017
- Message
- Lifecycle Controller (LC) firmware was not accessible and is therefore in Recovery mode.
- Detailed Description
- Unable to locate a file required to run Lifecycle Controller. No Lifecycle Controller functionality is available while in Recovery Mode.
- Recommended Response Action
- Repair Lifecycle Controller firmware using the Lifecycle Controller Dell Update Package (DUP) or Lifecycle Controller Repair Package via iDRAC. For more information, see Lifecycle Controller Users Guide.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0018
- Message
- Lifecycle Controller (LC) is unable to complete a requested task or function and therefore is in Recovery Mode.
- Detailed Description
- An internal error occurred. No Lifecycle Controller functionality is available while in Recovery Mode.
- Recommended Response Action
- Repair Lifecycle Controller firmware using the Lifecycle Controller Dell Update Package (DUP) or Lifecycle Controller Repair Package via iDRAC. For more information, see Lifecycle Controller Users Guide.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0019
- Message
- Lifecycle Controller (LC) is unable to complete a requested task or function and prevented the boot process from completing on multiple attempts. LC is in Recovery Mode.
- Detailed Description
- The system boot process did not complete repeatedly due to problems encountered while performing a Lifecycle Controller task for function. No Lifecycle Controller functionality is available while in Recovery Mode.
- Recommended Response Action
- Repair Lifecycle Controller firmware using the Lifecycle Controller Dell Update Package (DUP) or Lifecycle Controller Repair Package via iDRAC. For more information, see Lifecycle Controller Users Guide.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0021
- Message
- The Lifecycle Controller feature is disabled.
- Detailed Description
- The Lifecycle Controller feature is disabled. The feature was disabled because of one of the following conditions: 1) The feature was disabled manually using the F2 System Setup utility or through an iDRAC interface, 2) BIOS encountered an issue starting the feature and automatically disabled it.
- Recommended Response Action
- To enable the Lifecycle Controller (LC) feature using F2 System Setup, select the iDRAC Settings > Lifecycle Controller and then select Enabled. If LC becomes disabled automatically, update the Lifecycle Controller firmware or apply the Lifecycle Controller Repair Package.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0022
- Message
- Unable to initialize Management Engine because the Management Engine is not responding.
- Detailed Description
- The Management Engine firmware cannot be initialized because the Management Engine is not responding.
- Recommended Response Action
- Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0023
- Message
- BIOS is unable to send the End of POST message to Management Engine because the Management Engine is not responding.
- Detailed Description
- The End of POST message could not be sent to the Management Engine because the Management Engine is not responding.
- Recommended Response Action
- Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0024
- Message
- The Management Engine is not responding.
- Detailed Description
- The Management Engine firmware is not responding to the BIOSvia the HECI interface.
- Recommended Response Action
- Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0025
- Message
- Unable to initialize Management Engine firmware.
- Detailed Description
- The Management Engine firmware cannot be initialized. The BIOS will reset the system to retry the initialization process.
- Recommended Response Action
- Wait for the BIOS to reset the system and reinitialize the Management Engine. If the issue persists, turn off the input power to the system and turn on again.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0026
- Message
- iDRAC is not responding.
- Detailed Description
- iDrac is not responding to BIOS commands. The BIOS will reset the system to retry the initialization process.
- Recommended Response Action
- Wait for the BIOS to reset the system and reinitialize the iDRAC. If the issue persists, remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0027
- Message
- The system must be restarted for the new license to become effective.
- Detailed Description
- A license change for the system or a component in the system requires a system reset in order for the new license to take effect.
- Recommended Response Action
- Wait for the BIOS to reset the system.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0028
- Message
- iDRAC is not responding after a recovery system reset was performed.
- Detailed Description
- The iDRAC is not responding after a recovery system reset was performed. BIOS will continue POST startup with iDRAC in a non functional state.
- Recommended Response Action
- Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0029
- Message
- Unable to initialize iDRAC because of some critical issues.
- Detailed Description
- iDRAC could not be initialized because of some critical issues. Continuing to boot may result in unexpected power loss because of unknown power inventory and unavailability of features such as remote out of band access, active power management, thermal management, inventory collection, LCD, or system error reporting.
- Recommended Response Action
- Do one of the following: 1) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system. 2) Update the iDRAC firmware. 3) Continue to boot. Note: This may result in unexpected power loss because of unknown power inventory and unavailability of features such as remote out of band access, active power management, thermal management, inventory collection, LCD, or system error reporting.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0031
- Message
- PCIe downtrain is detected on arg1 . Expected link width: arg2 Actual link width: arg3
- Arguments
- arg1 = device location, arg2 = size, arg3 = size
- Detailed Description
- The PCIe device identified in the message was not trained at the expected link width.
- Recommended Response Action
- Do one of the following: 1) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system. 2) Update the firmware on the PCIe device.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0032
- Message
- Unable to initialize the TPM chip because the TPM chip is not functioning.
- Detailed Description
- The TPM chip cannot be initialized because the TPM chip is not functioning.
- Recommended Response Action
- Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0033
- Message
- Default system BIOS settings are in use because NVRAM_CLR jumper is installed on the system board.
- Detailed Description
- The NVRAM_CLR jumper is installed to clear the BIOS configuration. After clearing the BIOS configuration, remove the NVRAM_CLR jumper so that the system can function normally and any non-default BIOS system setting changes can be persistently saved.
- Recommended Response Action
- To change the system BIOS settings and persistently save the settings, remove the NVRAM_CLR jumper and then go to the System Setup to configure system settings.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0034
- Message
- A CMOS battery loss is detected resulting in an invalid BIOS configuration.
- Detailed Description
- A CMOS battery loss is detected resulting in an invalid BIOS configuration.
- Recommended Response Action
- Go to the System Setup to configure system settings, system time and date.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0035
- Message
- The BIOS passwords are disabled because the PWRD_EN jumper is removed from the system board.
- Detailed Description
- The BIOS passwords are disabled because the PWRD_EN jumper is removed from the system board.
- Recommended Response Action
- To enable the BIOS passwords, install the PWRD_EN jumper.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0036
- Message
- Unable to initialize the iDRAC Shared Memory Architecture (SMA) interface.
- Detailed Description
- The iDRAC Shared Memory Architecture (SMA) interface cannot be initialized. The BIOS will use the Keyboard Controller Style (KCS) interface.
- Recommended Response Action
- Do one of the following: 1) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system. 2) Update the iDRAC firmware on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0037
- Message
- Unable to communicate with iDRAC because of an issue in the iDRAC Shared Memory Architecture (SMA) Intelligent Platform Management Interface (IPMI).
- Detailed Description
- Unable to communicate with iDRAC because of an issue in the iDRAC Shared Memory Architecture (SMA) Intelligent Platform Management Interface (IPMI). Continuing to boot may result in unexpected power loss because of unknown power inventory and unavailability of features such as active power management, thermal management.
- Recommended Response Action
- Do one of the following: 1) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system. 2) Update the iDRAC firmware on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0038
- Message
- Unable to communicate with iDRAC because of missing interrupts on the Shared Memory Architecture (SMA) interface.
- Detailed Description
- Unable to communicate with iDRAC because an expected interrupt(s) from the iDRAC SMA (Shared Memory Architecture) interface did not happen. Continuing to boot may result in unexpected power loss because of unknown power inventory and unavailability of features such as active power management, thermal management.
- Recommended Response Action
- Do one of the following: 1) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system. 2) Update the iDRAC firmware on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0039
- Message
- Unable to communicate with iDRAC because of an issue in the iDRAC Keyboard Controller Style (KCS) Intelligent Platform Management Interface (IPMI).
- Detailed Description
- Unable to communicate with iDRAC because of an issue in the iDRAC Keyboard Controller Style (KCS) Intelligent Platform Management Interface (IPMI). Continuing to boot may result in unexpected power loss because of unknown power inventory and unavailability of features such as remote out of band access, active power management, thermal management, inventory collection, LCD, or system error reporting.
- Recommended Response Action
- Do one of the following: 1) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system. 2) Update the iDRAC firmware on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0040
- Message
- The TXT feature is disabled because of an unexpected issue.
- Detailed Description
- The TXT has been disabled due to an unexpected issue. Check the SEL (System Event Log) for details of the issue.
- Recommended Response Action
- Do one of the following: 1) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the system. 2) Update the BIOS firmware on the system. For information about the issue, see System Event Log (SEL).
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0041
- Message
- Unable to enable the TXT feature because the Virtualization Technology (VT) feature is not enabled on the processor.
- Detailed Description
- Unable to turn on the TXT feature because the Virtualization Technology (VT) feature is not enabled on the processor.
- Recommended Response Action
- From System Setup, enable VT, and then enable TXT. If the issue persists, update the system BIOS firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0042
- Message
- Unable to enable the TXT feature because Trusted Platform Module (TPM) configuration is invalid.
- Detailed Description
- Unable to enable the TXT feature because Trusted Platform Module (TPM) configuration is invalid.
- Recommended Response Action
- Go to System Setup > System Security page, select the "On with pre-boot measurement" option for TPM Security, and click the "Activate" option under TPM command. Restart the system, go to System Setup > System Security page, and then enable TXT.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0043
- Message
- Unable to enable the TXT feature because the processor does not support TXT.
- Detailed Description
- Unable to enable the TXT feature because the processor does not support TXT.
- Recommended Response Action
- Install a TXT-capable processor and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0044
- Message
- Unable to enable the TXT feature because the motherboard chipset does not support TXT.
- Detailed Description
- Unable to enable the TXT feature because the processor does not support TXT.
- Recommended Response Action
- Contact your service provider.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0045
- Message
- Unable to enable the TXT feature because a TPM chip is not present.
- Detailed Description
- Unable to enable the TXT feature because a TPM chip is not present.
- Recommended Response Action
- Install a TPM chip module by following the installation procedure. Refer to the platform Owners Manual for more information or contact your service provider.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0046
- Message
- An issue is observed in the previous invocation of TXT SINIT Authenticated Code Module (ACM) because the TXT information stored in the TPM chip may be corrupted.
- Detailed Description
- An issue in observed in the previous invocation of TXT SINIT Authenticated Code Module (ACM) because the TXT information stored in the TPM chip may be corrupted.
- Recommended Response Action
- Do one of the following: 1) Update the BIOS firmware. 2) Go to System Setup > System Security page, click the "Clear" option under TPM command. Restart the system, go to System Setup > System Security page, click the "Activate" option under TPM command, and then enable TXT.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0047
- Message
- One or more keys in the keyboard is stuck and not functional.
- Detailed Description
- One or more keys in the keyboard is stuck and not functional.
- Recommended Response Action
- Make sure that the key is not stuck in the keyboard and retry the operation.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0048
- Message
- The Collect System Inventory on Restart (CSIOR) operation is not performed during this restart because Lifecycle Controller is not functioning.
- Detailed Description
- The Collect System Inventory on Restart (CSIOR) operaiton is not performed during this restart because Lifecycle Controller firmware could not be accessed or run properly.
- Recommended Response Action
- Repair Lifecycle Controller using the Update Package. For more information, see the Lifecycle Controller Users Guide.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0049
- Message
- Unable to enable the Non-maskable Interrupt (NMI) button because either the NMI button is stuck or iDRAC firmware is not updated.
- Detailed Description
- The NMI button cannot be enabled because either the NMI button is stuck or iDRAC firmware is not updated.
- Recommended Response Action
- Correct the NMI button if stuck or update iDRAC firmware on the system.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0051
- Message
- Brand information is successfully collected. The system is being restarted.
- Detailed Description
- Brand information is successfully collected. The system is being restarted. The rebranding process is completed.
- Recommended Response Action
- No response action is required.
- Category
- Work Notes (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0052
- Message
- Unable to complete the rebranding operation because of the issue(s) displayed earlier.
- Detailed Description
- The rebranding process cannot be completed because of the reasons identified on the computer screen.
- Recommended Response Action
- Do one of the following and retry the operation: 1) Update the iDRAC firmware. 2) Update the system BIOS. 3) Update the OEM ID module.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0055
- Message
- Unable to complete the debranding operation because of the issue(s) displayed earlier.
- Detailed Description
- The debranding process cannot be completed because of the reasons identified on the computer screen.
- Recommended Response Action
- Check the screen display for details of the failure. Retry the debrand process again, or update the system BIOS and then retry.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0056
- Message
- A PCIe error has occurred.
- Detailed Description
- The PCIe error is logged during Power-on-Self-Test (POST). The error could have occurred during either the current or the previous POST.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the PCIe device that is not functioning correctly, and then update the device firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0057
- Message
- A Machine-Check Exception (MCE) error has occurred.
- Detailed Description
- The MCE is logged during Power-on-Self-Test (POST). MCE could have occured during either the current or the previous POST.
- Recommended Response Action
- Check the System Event Log (SEL) to identify Machine-Check Exception (MCE) event source. Resolve the issue identified in the SEL that caused the MCE. For further information, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0058
- Message
- An uncorrectable Memory Error has occurred because a Dual Inline Memory Module (DIMM) is not functioning.
- Detailed Description
- Uncorrectable Memory Error has occurred because a Dual Inline Memory Module (DIMM) is not functioning.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the non-functioning DIMM, and then replace it.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0059
- Message
- The Power Supply Units (PSUs) in the system do not match.
- Detailed Description
- The Power Supply Units (PSUs) in the system do not match.
- Recommended Response Action
- Check the PSU types and make sure they are appropriately matched, and then retry the operation. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0060
- Message
- Power required by the system exceeds the power supplied by the Power Supply Units (PSUs).
- Detailed Description
- Power required by the system exceeds the power supplied by the PSUs. Continuing to restart the system may automatically turn off the system without any notification.
- Recommended Response Action
- Check the PSU and system configuration, and then upgrade the PSU, if necessary.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0063
- Message
- Unable to change an attribute because of issues in the Attribute Configuration Interface (ACI) data block.
- Detailed Description
- An attribute cannot be successfully configured because of an issue in the ACI data block.
- Recommended Response Action
- Check the ACI data block for any invalid configuration dtata and settings, and then retry the operation. If the issue persists, contact your service provider.
- Category
- Updates (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0064
- Message
- One or more attributes are successfully configured. The system is being restarted.
- Detailed Description
- One or more attributes were successfully configured. The system will be automatically restarted.
- Recommended Response Action
- No response action is required.
- Category
- Updates (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0065
- Message
- One or more attributes are successfully configured. The system will be automatically turned off in 5 seconds.
- Detailed Description
- One or more attributes are successfully configured. The system is automatically turned off in 5 seconds.
- Recommended Response Action
- No response action is required.
- Category
- Updates (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0066
- Message
- A PCIe link training failure is observed in arg1 and the link is disabled. The system has halted.
- Arguments
- arg1 = PCIe device
- Detailed Description
- A PCIe Link failure is observed in the device identified in the message and device link is disabled. The system will be halted.
- Recommended Response Action
- Do one of the following: 1) Turn off the input power to the system and turn on again. 2) Update the PCIe device firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0067
- Message
- A PCIe link training failure is observed in arg1 and device link is disabled.
- Arguments
- arg1 = PCIe device
- Detailed Description
- A PCIe link failure is observed in the PCIe device identified in the message and device link is disabled.
- Recommended Response Action
- Do one of the following: 1) Turn off the input power to the system and turn on again. 2) Update the PCIe device firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0068
- Message
- The mezzanine card configuration used is not supported on this Chassis.
- Detailed Description
- The mezzanine card configuration used is not supported on this Chassis. Server modules used in different Chassis may require cards with different configuration properties. For more information, contact your service provider.
- Recommended Response Action
- Make sure that a supported mezzanine card is used and retry the operation. For more information, see the platform Owners Manual of the Chassis available at the support site.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0069
- Message
- A CMOS checksum error has occurred. CMOS is reinitialized.
- Detailed Description
- A CMOS checksum error has occurred resulting in an invalid BIOS configuration. BIOS configuraiton is reset to detault settings.
- Recommended Response Action
- Go to the System Setup and configure the desired settings. Save and exit to apply the settings.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0070
- Message
- One or more correctable PCIe errors have occurred.
- Detailed Description
- One or more correctable PCIe errors have occurred. Data about the errors are logged into SEL during the POST operation.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the PCIe device, and then update its firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0071
- Message
- One or more UEFI network interfaces is not available. The corresponding UEFI network devices are disabled.
- Detailed Description
- One or more UEFI network interfaces is not available. The corresponding UEFI network devices are disabled.
- Recommended Response Action
- Connect the missing network interface card to the system and enable the UEFI network interface in System Setup.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0072
- Message
- Unable to load the firmware from arg1 because of the Secure Boot policy.
- Arguments
- arg1 = device name
- Detailed Description
- When the Secure Boot feature is enabled, the system BIOS authenticates each UEFI driver against the Secure Boot policy. If a UEFI driver does not meet the policy criteria, the system BIOS does not load or execute the UEFI driver and displays this message at the end of POST. The Secure Boot policy consists of authorized and unauthorized X.509 certificates; signed drivers must chain to an authorized certificate. The policy may also authorize hash values of individual UEFI driver images. Users can configure the Secure Boot feature and the Secure Boot policy in F2 System Setup > System BIOS > Security Settings page.
- Recommended Response Action
- If the Secure Boot feature is not desired, disable it in System Setup > System BIOS > Security Settings page. Otherwise, do the following: 1) Make sure the firmware on the failing device is up-to-date. 2) If subsequent failures occur, review the Secure Boot Policy Summary in System Setup > System BIOS > Security Settings page. The device firmware must be authorized by a public key or hash value in the Authorized Signature Database. The public key or hash value must not be present in the Forbidden Signature Database.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0073
- Message
- Unable to boot arg1 because of the Secure Boot policy.
- Arguments
- arg1 = Boot Option name
- Detailed Description
- When the Secure Boot feature is enabled, the system BIOS authenticates each boot option against the Secure Boot policy. If a boot option does not meet the policy criteria, the system BIOS does not boot to the boot option and displays this message. The Secure Boot policy consists of authorized and unauthorized X.509 certificates; signed boot images must chain to an authorized certificate. The policy may also authorize hash values of individual boot images. Users can configure the Secure Boot feature and the Secure Boot policy in System Setup > System BIOS > Security Settings page.
- Recommended Response Action
- If the Secure Boot feature is not desired, disable it in System Setup > System BIOS > Security Settings page. Otherwise, do the following: 1) review the Secure Boot Policy Summary in F2 System Setup > System BIOS > Security Settings page. The boot option must be authorized by a public key or hash value in the Authorized Signature Database. 2) If the boot option is not authorized but it can be trusted, enter System Setup > System BIOS > Security Settings page, set Secure Boot Policy to Custom, and add a entry for the boot option in the Authorized Signature Database (System Setup > System BIOS > Security Settings > Custom Policy Settings > Authorized Signature Database > Import Database Entry).
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0074
- Message
- The Secure Boot policy has been modified since the last time the system was started.
- Detailed Description
- The system BIOS logs this message after detecting a change in Secure Boot policy settings. Such a change may result from user configuration or a system BIOS update. Changes to the following settings trigger this message: 1) Secure Boot (Enable/Disable) 2) Secure Boot Policy (Standard/Custom) 3) Platform Key 4) Key Exchange Keys 5) Authorized Signature Database (db) 6) Forbidden Signature Database (dbx).
- Recommended Response Action
- Review the Secure Boot policy settings in System Setup > System BIOS > Security Settings page. If policy changes were expected, no action is necessary. Otherwise, modify the Secure Boot policy settings as needed.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0076
- Message
- One or more Corrected Machine Check(CMC) errors have occurred.
- Detailed Description
- A Corrected Machine Check error(s) has occured.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the Corrected Machine Check (CMC) errors. Resolve the issue identified in the SEL that caused the CMC.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0077
- Message
- One or more PCIe device errors occurred in the previous boot.
- Detailed Description
- One or more PCIe device errors occured in the previous boot.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the PCIe device with errors, and then update its firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0078
- Message
- One or more Machine Check errors occurred in the previous boot.
- Detailed Description
- One or more Machine Check errors occurred in the previous boot.
- Recommended Response Action
- Check the System Event Log (SEL) to identifiy the source of the Machine Check error and resolve the issues.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0079
- Message
- One or more Uncorrectable Memory errors occurred in the previous boot.
- Detailed Description
- One or more Uncorrectable Memory errors occurred in the previous boot.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the non-functional DIMM, and then replace the DIMM.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0080
- Message
- PCIe link speed is not optimal for arg1 . Expected link speed: Gen arg2 and actual link speed: Gen arg3 .
- Arguments
- arg1 = PCIe device, arg2 = generation number, arg3 = generation number
- Detailed Description
- The PCIe link speed is not optimal for the identified PCIe device.
- Recommended Response Action
- Do one of the following: 1) Turn off the input power to the system and turn on again. 2) Update the PCIe device firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0081
- Message
- Memory size has changed from the last time the system was started.
- Detailed Description
- Memory size has changed from the last time the system was started. No action is required if memory was added or removed.
- Recommended Response Action
- If the change is expected, no action is necessary. Otherwise, check the DIMM population inside the system and memory settings in System Setup for configuration changes. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0082
- Message
- The system was reset due to a timeout from the watchdog timer.
- Detailed Description
- The system was reset due to a timeout from the watchdog timer.
- Recommended Response Action
- Check the System Event Log (SEL) or crash dumps from Operating System to identify the source that caused the watchdog timer reset. Update the firmware or driver for the identified device.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0083
- Message
- One or more PCI System errors (SERR) have occurred.
- Detailed Description
- One or more PCI System errors (SERR) have occurred.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the PCI device that caused the SERR. Update the identifed device firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0084
- Message
- One or more PCI Parity errors (PERR) have occurred.
- Detailed Description
- One or more PCI Parity errors (PERR) have occurred.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the PCI device that caused the PERR. Update the identifed device firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0085
- Message
- One or more chipset errors have occurred.
- Detailed Description
- One or more chipset errors have occurred.
- Recommended Response Action
- Check the System Event Log (SEL) to identify the chipset error. Do one of the following: 1) Turn off the input power to the system and turn on again. 2) Update the PCIe device firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0086
- Message
- Unsupported Small Outline Dual In-line Memory Module (SODIMM) memory is installed on RDIMM memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- Unsupported Small Outline Dual In-line Memory Module (SODIMM) memory is installed on the RDIMM memory slot indentified in the message.
- Recommended Response Action
- Remove the unsupported SODIMM module from the identified memory slot and replace it with a supported module. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0087
- Message
- Unsupported 4Gb technology DIMM module is installed on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- Unsupported 4Gb technology DIMM module is installed on the memory slot indentified in the message.
- Recommended Response Action
- Remove the unsupported DIMM module from the identified memory slot and replace it with a supported module. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0088
- Message
- Unsupported 8Gb technology DIMM module is installed on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- Unsupported 8Gb technology DIMM module is installed on the memory slot indentified in the message.
- Recommended Response Action
- Remove the unsupported DIMM module from the identified memory slot and replace it with a supported module. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0089
- Message
- Incompatible x16 data bus width DIMM is installed on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- Incompatible x16 data bus width DIMM is installed on the memory slot indentified in the message.
- Recommended Response Action
- Remove the unsupported DIMM module from the identified memory slot and replace it with a supported module. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0090
- Message
- A DIMM with an incompatible number of ranks is installed on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- A DIMM with an incompatible number of ranks is installed on the memory slot identified in the message.
- Recommended Response Action
- Remove the unsupported DIMM module from the identified memory slot and replace it with a supported module. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0091
- Message
- A Quad-Rank (QR) DIMM is installed on memory slot: arg1 . QR DIMMs should be installed on the first DIMM slot in a channel if there is only one QR DIMM in the channel. QR DIMMs cannot be installed on the third slot of the channel.
- Arguments
- arg1 = slot number
- Detailed Description
- A Quad-Rank (QR) DIMM is installed on the memory slot indentified in the message. QR DIMMs should be installed on the first DIMM slot in a channel if there is only one QR DIMM in the channel. QR DIMMs cannot be installed on the third slot of the channel.
- Recommended Response Action
- Install the QR DIMM in the correct channel. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0092
- Message
- The number of DIMM ranks has exceeded the maximum allowed ranks per channel limit.
- Detailed Description
- The number of DIMM ranks has exceeded the maximum allowed ranks per channel limit.
- Recommended Response Action
- Check the total number of ranks in each channel to make sure it does not exceed the maximum allowed limit. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0093
- Message
- The DIMM installed on the memory slot: arg1 does not meet the minimum supported frequency.
- Arguments
- arg1 = slot number
- Detailed Description
- The DIMM installed on the memory slot identified in the message does not meet the minimum supported frequency.
- Recommended Response Action
- Remove all unsupported DIMM modules from the system. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0094
- Message
- Unsupported Non-ECC memory module is installed on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- Unsupported Non-ECC memory module is installed on the memory slot identified in the message.
- Recommended Response Action
- Remove all Non-ECC DIMMs and replace them with ECC DIMMs. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0095
- Message
- A DIMM with unsupported voltage is installed on memory slot arg1 .
- Arguments
- arg1 = Slot
- Detailed Description
- A DIMM with unsupported voltage is installed on the memory slot identified in the message.
- Recommended Response Action
- Remove the unsupported DIMM module and replace it with a DIMM with a supported voltage. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0096
- Message
- Unable to enable the Advanced ECC memory operating mode because the current DIMM population or system configuration does not support Advanced ECC mode.
- Detailed Description
- The Advanced ECC memory operating mode cannot be enabled because the current DIMM population or system configuration does not support Advanced ECC mode.
- Recommended Response Action
- Check DIMM population and system configuration to make sure Advanced ECC memory operating mode can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0097
- Message
- Unable to enable the Advanced ECC memory operating mode because of mismatches in the DIMM channel configurations.
- Detailed Description
- The Advanced ECC memory operating mode cannot be enabled because of mismatches in the DIMM channel configurations.
- Recommended Response Action
- Make sure identical memory modules in corresponding slots of channel pairs are populated. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0098
- Message
- The memory Built-In Self-test (BIST) has detected one or more errors on the DIMM installed on memory slot: arg1 . As a result, the corresponding DIMM has been disabled.
- Arguments
- arg1 = slot number
- Detailed Description
- The memory Built-In Self-test (BIST) has detected one or more errors on the DIMM installed on memory slot: <slot number>. As a result, the corresponding DIMM has been disabled.
- Recommended Response Action
- Replace the DIMM module identified in the message. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0099
- Message
- Unable to enable the Memory Mirroring feature because the current DIMM population or hardware configuration does not support the feature.
- Detailed Description
- The Memory Mirroring feature cannot be enabled because the current DIMM population or hardware configuration does not support the feature.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure the Memory Mirroring feature can be supported. For more information, see platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0100
- Message
- Unable to enable the Memory Mirroring feature because of mismatches in the DIMM channel configurations.
- Detailed Description
- The Memory Mirroring feature cannot be enabled because of mismatches in the DIMM channel configurations.
- Recommended Response Action
- Make sure identical memory modules in corresponding slots of channel pairs are populated. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0101
- Message
- Total amount of installed memory has exceeded limit.
- Detailed Description
- The total amount of installed memory has exceeded the amount supported by the platform.
- Recommended Response Action
- Remove memory modules from the system to reduce the total amount of installed memory. For more information on installed memory limit, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0102
- Message
- Unable to enable the Memory Sparing feature because the current DIMM population or hardware configuration does not support the feature.
- Detailed Description
- The Memory Sparing feature cannot be enabled because the current DIMM population or hardware configuration does not support the feature.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure Memory Sparing feature can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0103
- Message
- One or more memory initialization errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot
- Detailed Description
- One or more memory initialization error have occurred on the memory slot identified in the message.
- Recommended Response Action
- Replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0104
- Message
- The DIMM module on memory slot arg1 is populated out of order in the DIMM channel.
- Arguments
- arg1 = slot
- Detailed Description
- The DIMM module on memory slot identified in the message is populated out of order in the channel.
- Recommended Response Action
- Install DIMM modules in sequential order without skipping any slots in the channel. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0105
- Message
- Unable to enable the Cluster on Die (COD) feature because of an unsupported memory configuration.
- Detailed Description
- The Cluster on Die (COD) feature cannot be enabled because of an unsupported memory configuration.
- Recommended Response Action
- Make sure to populate all memory channels in the system with a minimum of one DIMM per channel. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0106
- Message
- One or more memory correctable training errors have occurred on memory slot: arg1
- Arguments
- arg1 = slot
- Detailed Description
- One or more memory correctable training errors have occurred on the memory slot identified in the message.
- Recommended Response Action
- Remove input power to the system, reseat the DIMM module and restart the system. If the correctable error persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0107
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot
- Detailed Description
- One or more memory errors have occurred on the memory slot identified in the message. The error occurred during Read DQ/DQS initialization.
- Recommended Response Action
- Remove input power to the system, reseat the DIMM module and restart the system. If the issues persist, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0108
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot
- Detailed Description
- One or more memory errors have occurred on memory slot identified in the message. The error occured during Read Receiving Enable initialization.
- Recommended Response Action
- Remove input power to the system, reseat the DIMM module and restart the system. If the issues persist, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0109
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot
- Detailed Description
- One or more memory errors have occurred on memory slot identified in the message. The error occurred during write leveling initialization.
- Recommended Response Action
- Remove input power to the system, reseat the DIMM module and restart the system. If the issues persist, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0110
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot
- Detailed Description
- One or more memory errors have occurred on memory slot identified in the message. The error occurred during Write DQ/DQS initialization.
- Recommended Response Action
- Remove input power to the system, reseat the DIMM module and restart the system. If the issues persist, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0111
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot
- Detailed Description
- One or more memory errors have occurred on memory slot identified in the message. The error occurred during memory test.
- Recommended Response Action
- Remove input power to the system, reseat the DIMM module and restart the system. If the issues persist, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0112
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot
- Detailed Description
- One or more memory errors have occurred on memory slot identified in the message. The error occurred during the LRDIMM interface initialization.
- Recommended Response Action
- Remove input power to the system, reseat the DIMM module and restart the system. If the issues persist, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0113
- Message
- Unable to enable the Fault Resilient Memory (FRM) feature because the current DIMM population or hardware configuration does not support the feature.
- Detailed Description
- The Fault Resilient Memory (FRM) feature cannot be enabled because the current DIMM population or hardware configuration does not support the feature.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure the Memory Mirroring feature can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0114
- Message
- Unable to enable the Fault Resilient Memory (FRM) operating mode because of mismatches in DIMM channel configurations.
- Detailed Description
- The Fault Resilient Memory (FRM) operating mode cannot be enabled because of mismatches in DIMM channel configurations.
- Recommended Response Action
- Make sure identical memory modules in corresponding slots of channel pairs are populated. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0115
- Message
- The Management Engine firmware has recovered from one or more correctable errors.
- Detailed Description
- The BIOS has recovered the Management Engine after it became unresponsive via the HECI interface. There is no performance degradation and the Management Engine is functioning normally now.
- Recommended Response Action
- The Management Engine is functioning normally now. No response action is required.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0116
- Message
- One or more boot drivers have reported issue(s).
- Detailed Description
- One or more boot drivers have reported issue(s) via the UEFI Driver Health Protocol.
- Recommended Response Action
- Check the Driver Health Menu in Boot Manager for details.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0117
- Message
- Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 1.
- Detailed Description
- Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 1.
- Recommended Response Action
- Do one of the following: 1) Check the IDSDM or the SD card media. 2) Try reseat or replace the SD card media. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0118
- Message
- Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 2.
- Detailed Description
- Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 2.
- Recommended Response Action
- Do one of the following: 1) Check the IDSDM or the SD card media. 2) Try reseat or replace the SD card media. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0119
- Message
- The Internal Dual Secure Digital Module (IDSDM) RAID redundancy was lost.
- Detailed Description
- Internal Dual Secure Digital Module (IDSDM) RAID redundancy was lost. The system BIOS should have prompted the user for the rebuild process.
- Recommended Response Action
- No additional response action is required if you have followed the instructions on the screen to start the rebuild process.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0120
- Message
- Both of the Internal Dual Secure Digital Module (IDSDM) SD card media are missing, or not responding.
- Detailed Description
- Both of the Internal Dual Secure Digital Module (IDSDM) SD card media are missing, or not responding.
- Recommended Response Action
- Make sure both the SD card media are properly installed and retry the system start up. If the issue persists, replace the SD card media.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0121
- Message
- The primary SD card is missing, not responding, or in write-protected mode.
- Detailed Description
- The primary SD card is missing, not responding, or in write-protected mode.
- Recommended Response Action
- Do one of the following: 1) Install a SD card media in the primary SD card slot. 2) Reseat or replace the SD card media. 3) If write-protected mode is expected, then no response action is required.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0122
- Message
- The secondary SD card is missing, not responding, or in write-protected mode.
- Detailed Description
- The secondary SD card is missing, not responding, or in write-protected mode.
- Recommended Response Action
- Do one of the following: 1) Install a SD card media in the secondary SD card slot. 2) Reseat or replace the SD card media. 3) If the secondary SD card is intentionally not installed or write-protected mode is expected, then no response action is required.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0123
- Message
- The secondary SD card has now become the primary SD card.
- Detailed Description
- The secondary SD card has now become the primary SD card.
- Recommended Response Action
- Check the screen display or the Lifecycle Log for prior messages. If the switch is expected, then no response action is required.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0124
- Message
- The size and speed of the secondary SD card do not match those of the primary SD card.
- Detailed Description
- The size and speed of the primary SD card do not match those of the secondary SD card. The secondary SD card needs to have equal or greater capacity and speed than the primary SD card.
- Recommended Response Action
- Replace the secondary SD card with one that has equal or greater capacity and speed than the primary SD card.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0125
- Message
- Unable to finish The Internal Dual Secure Digital Module (IDSDM) image rebuild process because of issues.
- Detailed Description
- Unable to finish The Internal Dual Secure Digital Module (IDSDM) image rebuild process because of issues.
- Recommended Response Action
- Do one of the following: 1) Reseat or replace the SD card media. 2) Update the iDRAC firmware. Restart the system and retry the operation. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0128
- Message
- Both the primary and secondary SD cards are in write-protected mode.
- Detailed Description
- Both the primary and secondary SD cards are in write-protected mode.
- Recommended Response Action
- No response action is required if this is intentional.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0129
- Message
- The Internal Dual Secure Digital Module (IDSDM) has encountered an unknown issue.
- Detailed Description
- The Internal Dual Secure Digital Module (IDSDM) has encountered an unknown issue. This may be because new error codes are coming from the IDSDM firmware and the system BIOS or the iDRAC firwmare need to be updated to process correctly.
- Recommended Response Action
- Do one of the following: 1) Update the system BIOS. 2) Update the iDRAC firmware. 3) Reseat or replace the SD card media. Restart the system and retry the operation. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0131
- Message
- Unable to load one or more option ROMs because of insufficient shadow memory.
- Detailed Description
- Unable to load one or more option ROMs because of insufficient shadow memory. The option ROM shadow memory is located between C0000h and F0000h.
- Recommended Response Action
- Do one of the following: 1) Remove unused PCIe card(s) to free up option ROM space. 2) Disable unused boot protocol instances (such as PXE, iSCSI, etc.) from applicable PCIe card(s) option ROM configurations. 3) If possible, install and run the Operating System in UEFI boot mode.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0132
- Message
- Unable to load one or more option ROMs because of insufficient base memory.
- Detailed Description
- Unable to load one or more option ROMs because of insufficient base memory. The base memory is memory below 640K.
- Recommended Response Action
- Do one of the following: 1) Remove unused PCIe card(s) to free up option ROM space. 2) Disable unused boot protocol instances (such as PXE, iSCSI, etc.) from applicable PCIe card(s) option ROM configurations. 3) If possible, install and run the Operating System in UEFI boot mode.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0133
- Message
- Unable to perform PXE boot because the VLAN settings conflict with that of the iSCSI device settings.
- Detailed Description
- Unable to perform PXE boot because the VLAN settings conflict with that of the iSCSI device settings.
- Recommended Response Action
- Do one of the following: 1) Go to System Setup and change the VLAN configuration for the PXE device to match that of the iSCSI device. Either both devices must be configured with VLAN enabled or both devices must be configured with VLAN disabled. 2) Change the PXE device interface setting to use a different NIC interface than the NIC interface used by the iSCSI device.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0134
- Message
- Unable to allocate Memory Mapped Input Output (MMIO) resources for one or more PCIe devices because of insufficient MMIO memory.
- Detailed Description
- Unable to allocate Memory Mapped Input Output (MMIO) resources for one or more PCIe devices because of insufficient MMIO memory.
- Recommended Response Action
- Do one of the following: 1) Remove unused PCIe card(s) to free up MMIO space. 2) Go to System Setup and enable the Memory Mapped I/O above 4GB option.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0135
- Message
- Unable to execute CSIOR (Collect System Inventory on Restart) because the Lifecycle Controller (LC) firmware was not accessible.
- Detailed Description
- The CSIOR (Collect System Inventory on Restart) operation cannot be executed because the Lifecycle Controller (LC) firmware was not accessible. This issue is caused by LC partition attach issues.
- Recommended Response Action
- Do one of the following: 1) Restart the system and retry the operation. 2) Update the iDRAC firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0136
- Message
- Unable to execute CSIOR (Collect System Inventory on Restart) because the Lifecycle Controller (LC) firmware was not accessible.
- Detailed Description
- The CSIOR (Collect System Inventory on Restart) operation cannot be executed because the Lifecycle Controller (LC) firmware was not accessible. This issue is caused by missing LC partitions.
- Recommended Response Action
- Do one of the following: 1) Restart the system and retry the operation. 2) Update the iDRAC firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0137
- Message
- Unable to execute CSIOR (Collect System Inventory on Restart) because the Lifecycle Controller (LC) firmware was not accessible.
- Detailed Description
- The CSIOR (Collect System Inventory on Restart) operation cannot be executed because the Lifecycle Controller (LC) firmware was not accessible. This issue is caused by missing LC files.
- Recommended Response Action
- Do one of the following: 1) Restart the system and retry the operation. 2) Update the iDRAC firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0138
- Message
- Unable to execute CSIOR (Collect System Inventory on Restart) because the Lifecycle Controller (LC) firmware was unable to complete a requested task or function.
- Detailed Description
- The CSIOR (Collect System Inventory on Restart) operation cannot be executed because the Lifecycle Controller (LC) firmware is unable to complete a requested task or function.
- Recommended Response Action
- Do one of the following: 1) Restart the system and retry the operation. 2) Update the iDRAC firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0139
- Message
- Unable to enter System Service Mode (SSM) because the Lifecycle Controller (LC) firmware was not accessible.
- Detailed Description
- The System Service Mode (SSM) cannot be entered because the Lifecycle Controller (LC) firmware was not accessible. This situation is caused by LC partition attach issues.
- Recommended Response Action
- Do one of the following: 1) Restart the system and retry the operation. 2) Update the iDRAC firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0140
- Message
- Unable to enter System Service Mode (SSM) because the Lifecycle Controller (LC) firmware was not accessible.
- Detailed Description
- The System Service Mode (SSM) cannot be entered because the Lifecycle Controller (LC) firmware was not accessible. This situation is caused by missing LC partitions.
- Recommended Response Action
- Do one of the following: 1) Restart the system and retry the operation. 2) Update the iDRAC firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0141
- Message
- Unable to enter System Service Mode (SSM) because the Lifecycle Controller (LC) firmware was not accessible.
- Detailed Description
- The System Service Mode (SSM) cannot be entered because the Lifecycle Controller (LC) firmware was not accessible. This situation is caused by missing LC files.
- Recommended Response Action
- Do one of the following: 1) Restart the system and retry the operation. 2) Update the iDRAC firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0142
- Message
- Unable to enter System Service Mode (SSM) because the Lifecycle Controller (LC) firmware was unable to complete a requested task or function.
- Detailed Description
- The System Service Mode (SSM) cannot be entered because the Lifecycle Controller (LC) firmware was unable to complete a requested task or function.
- Recommended Response Action
- Do one of the following: 1) Restart the system and retry the operation. 2) Update the iDRAC firmware. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0143
- Message
- Unsupported processor(s) are installed.
- Detailed Description
- Unsupported processor(s) are installed.
- Recommended Response Action
- Replace the processor(s) with supported ones. For more information about supported processors, contact your service provider.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0144
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot ID
- Detailed Description
- One or more memory errors have occurred on memory slot identified in the message. The error happens during the identification of memory module type or memory size.
- Recommended Response Action
- Remove input power to the system, reseat the DIMM module and restart the system. If the issues persist, replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0145
- Message
- The Trusted Platform Module (TPM) installed on this system is not supported.
- Detailed Description
- The Trusted Platform Module (TPM) installed on this system is not supported.
- Recommended Response Action
- Do one of the following: 1) Update the BIOS firmware. 2) Replace the TPM with a supported one. If the issue persists, contact your service provider.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0146
- Message
- Unable to verify the chassis type via iDRAC and CMC. System configuration may be incorrect as a result.
- Detailed Description
- Unable to verify the chassis type via iDRAC and CMC. System configuration may be incorrect as a result.
- Recommended Response Action
- Do one of the following: 1) Restart the system. 2) Update the iDRAC firmware and then restart the system. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0147
- Message
- The system hardware or cabling configuration is invalid.
- Detailed Description
- The system hardware or cabling configuration is invalid.
- Recommended Response Action
- Do the following: 1) Make sure the system cables, risers, and CPU configuration are installed correctly. 2) Reseat each PCIe riser and reconnect the cables. For more information, see the system Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0148
- Message
- The SAS cable arg1 for the primary SAS expander daughter card is missing or misconfigured.
- Arguments
- arg1 = label number
- Detailed Description
- The SAS cable for the primary SAS expander daughter card is missing or misconfigured.
- Recommended Response Action
- Check the cable configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0149
- Message
- The PERC storage adapter in arg1 is not supported by the installed storage backplane.
- Arguments
- arg1 = device location
- Detailed Description
- The PERC storage adapter identified in this message is not supported by the installed storage backplane.
- Recommended Response Action
- Install a compatible storage adapter. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0150
- Message
- The system has detected a storage backplane that is not supported in this system or configuration. The backplanes functionality may be degraded or disabled.
- Detailed Description
- The system has detected a storage backplane that is not supported in this system or configuration. The backplanes functionality may be degraded or disabled.
- Recommended Response Action
- Install a supported backplane configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0151
- Message
- A PERC storage adapter is installed in arg1 but the internal storage slot is empty. This configuration is not supported.
- Arguments
- arg1 = slot number
- Detailed Description
- A PERC storage adapter is installed in a slot identified by this message but the internal storage slot is empty This configuration is not supported.
- Recommended Response Action
- Install a compatible storage adapter in the internal storage slot. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0153
- Message
- Unable to find the Dell Processor Acceleration Technology (DPAT) Enterprise license. Related DPAT BIOS settings will be lost if the license is not found in three consecutive reboots.
- Detailed Description
- Unable to find the Dell Processor Acceleration Technology 2.0 (DPAT 2.0) Enterprise license. Related DPAT 2.0 BIOS settings will be lost if the license is not found in three consecutive reboots.
- Recommended Response Action
- Do one of the following: 1) Reload the license. 2) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the sysetm. 3) Update the iDRAC firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0154
- Message
- Unable to find the Dell Processor Acceleration Technology (DPAT) Enterprise license after three consecutive boots. The Dell Controlled Turbo BIOS setup configuration is being reverted to default because of the absent license.
- Detailed Description
- Unable to find the Dell Processor Acceleration Technology (DPAT) Enterprise license after three consecutive boots. The Dell Controlled Turbo BIOS setup configuration is being reverted to default because of the absent license.
- Recommended Response Action
- If the absence of license is expected, no action is necessary. Otherwise do one of the following: 1) Reload the license. 2) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the sysetm. 3) Update the iDRAC firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0155
- Message
- Unable to find the Dell Processor Acceleration Technology (DPAT) Enterprise license after three consecutive boots. The Number of Cores per Processor BIOS setup configuration is being reverted to default because of the absent license.
- Detailed Description
- Unable to find the Dell Processor Acceleration Technology (DPAT) Enterprise license after three consecutive boots. The Number of Cores per Processor BIOS setup configuration is being reverted to default because of the absent license.
- Recommended Response Action
- If the absence of license is expected, no action is necessary. Otherwise do one of the following: 1) Reload the license. 2) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the sysetm. 3) Update the iDRAC firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0156
- Message
- Unable to find the Dell Processor Acceleration Technology (DPAT) Enterprise license in three consecutive boots. The Number of Cores per Processor and the Dell Controlled Turbo BIOS setup options are being reverted to default beacuse of the absent license.
- Detailed Description
- Unable to find the Dell Processor Acceleration Technology (DPAT) Enterprise license in three consecutive boots. The Number of Cores per Processor and the Dell Controlled Turbo BIOS setup options are being reverted to default beacuse of the absent license.
- Recommended Response Action
- If the absence of license is expected, no action is necessary. Otherwise do one of the following: 1) Reload the license. 2) Remove input power from the system, wait for 30 seconds, and re-apply input power. Turn on the sysetm. 3) Update the iDRAC firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0157
- Message
- The iDRAC request to reset BIOS to default settings is successfully completed.
- Detailed Description
- The request to reset BIOS to default settings is successfully completed.
- Recommended Response Action
- No response action is required.
- Category
- Work Notes (UEFI = UEFI Event)
- Severity
- Severity 3 (Informational)
UEFI0158
- Message
- Unable to complete the iDRAC request to reset BIOS to default settings.
- Detailed Description
- The iDRAC request to reset BIOS to default settings cannot be completed.
- Recommended Response Action
- Restart the system and retry the operation. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0159
- Message
- Unsupported Unregistered Dual In-line Memory Module (UDIMM) memory is installed on memory slot: arg1
- Arguments
- arg1 = slot number
- Detailed Description
- Unsupported 4Gb technology DIMM module is installed on the memory slot identified in the message.
- Recommended Response Action
- Remove the unsupported DIMM module from the identified memory slot and replace it with a supported module. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0160
- Message
- The number of DIMM ranks has exceeded the maximum allowed ranks per channel limit on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- The number of DIMM ranks has exceeded the maximum allowed ranks per channel limit.
- Recommended Response Action
- Check the total number of ranks in the channel to make sure it does not exceed the maximum allowed limit. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0161
- Message
- An unsupported DIMM population has been detected on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An unsupported DIMM population has been detected on memory slots identified by this message.
- Recommended Response Action
- Remove all unsupported DIMM modules from the system. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0162
- Message
- A 3 DIMM Per Channel (DPC) configuration has been detected on a 2 DPC memory buffer.
- Detailed Description
- An incompatibility has been detected between an installed memory buffer and the downstream DDR channel design.
- Recommended Response Action
- Contact your service provider.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0163
- Message
- Unsupported DIMM module with less than 2Gb technology is installed on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- Unsupported DIMM module with technology less than 2Gb is installed on the memory slot indentified in the message.
- Recommended Response Action
- Remove the unsupported DIMM module from the identified memory slot and replace it with a supported module. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0164
- Message
- Unable to enable the Advanced ECC memory operating mode beause of mismatches in the DIMM channel configurations on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- The Advanced ECC memory operating mode cannot be enabled because of mismatches in the DIMM channel configurations.
- Recommended Response Action
- Make sure identical memory modules in corresponding slots of channel pairs are populated. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0165
- Message
- Unable to configure memory interleaving on DIMM modules on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- Memory could not be interleaved because the number of allowable System Address Decode (SAD) rules exceeded during memory initialization.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure interleaving can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0166
- Message
- Unable to configure memory interleaving on DIMM modules on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- Memory could not be interleaved because the number of allowable Target Address Decode (TAD) rules exceeded during memory initialization.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure interleaving can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0167
- Message
- Unable to configure memory interleaving on DIMM modules on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- Memory could not be interleaved because the number of allowable Rank Interleave Register (RIR) rules exceeded during memory initialization.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure interleaving can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0168
- Message
- Unable to configure memory interleaving on DIMM modules on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- Memory could not be interleaved because a negative Target Address Decode (TAD) offset was calculated during memory initialization.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure interleaving can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0169
- Message
- Unable to configure memory interleaving on DIMM modules on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- Memory could not be interleaved because low memory (i.e. memory below the 4GB boundary) cannot be split evenly across processor sockets during memory initialization.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure interleaving can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0170
- Message
- Unable to configure memory interleaving on DIMM modules on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- Memory could not be interleaved because of an attempt to simultaneously configure incompatible A7 mode and Target Address Decode (TAD) 3-way interleave during memory initialization.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure interleaving can be supported. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0171
- Message
- A Dual Rank DIMM module is installed on memory slot arg1 after a Single Rank DIMM module.
- Arguments
- arg1 = slot number
- Detailed Description
- A memory population violation has been detected on the identified DIMM slot.
- Recommended Response Action
- Dual Rank DIMM modules must be installed before Single Rank DIMM modules on the channel. Populate memory modules in a supported configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0172
- Message
- A Quad Rank DIMM module is installed on memory slot arg1 after a Single Rank DIMM module.
- Arguments
- arg1 = slot number
- Detailed Description
- A memory population violation has been detected on the identified DIMM slot.
- Recommended Response Action
- Quad Rank DIMM modules must be installed before Single Rank DIMM modules on the channel. Populate memory modules in a supported configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0173
- Message
- A Quad Rank DIMM module is installed on memory slot arg1 after a Dual Rank DIMM module.
- Arguments
- arg1 = slot number
- Detailed Description
- A memory population violation has been detected on the identified DIMM slot.
- Recommended Response Action
- Quad Rank DIMM modules must be installed before Dual Rank DIMM modules on the channel. Populate memory modules in a supported configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0174
- Message
- A Quad Rank DIMM module is installed on memory slot arg1 after an Octal Rank DIMM module.
- Arguments
- arg1 = slot number
- Detailed Description
- A memory population violation has been detected on the identified DIMM slot.
- Recommended Response Action
- Quad Rank and Octal Rank DIMM modules cannot be mixed on a channel. Populate memory modules in a supported configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0175
- Message
- A Octal Rank DIMM module is installed on memory slot arg1 after a Quad Rank DIMM module.
- Arguments
- arg1 = slot number
- Detailed Description
- A memory population violation has been detected on the identified DIMM slot.
- Recommended Response Action
- Quad Rank and Octal Rank DIMM modules cannot be mixed on a channel. Populate memory modules in a supported configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0176
- Message
- Multiple Quad Rank DIMM modules are installed on a DDR channel. Refer to DIMM modules on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- A memory population violation has been detected on the identified DIMM slots.
- Recommended Response Action
- Only a single Quad Rank DIMM module can be installed on a channel. Populate memory modules in a supported configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0177
- Message
- A DIMM module is installed on memory slot arg1 after a Quad Rank DIMM module.
- Arguments
- arg1 = slot number
- Detailed Description
- A memory population violation has been detected on the identified DIMM slot.
- Recommended Response Action
- Only a single Quad Rank DIMM module can be installed on a channel. Populate memory modules in a supported configuration. For more information, see the platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0178
- Message
- One or more memory correctable training errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- One or more memory correctable training errors have occurred on the memory slot identified in the message. A corrected Read DQ/DQS error was detected.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the correctable error persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0179
- Message
- One or more memory correctable training errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- One or more memory correctable training errors have occurred on the memory slot identified in the message. A corrected Read Receive Enable error was detected.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the correctable error persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0180
- Message
- One or more memory correctable training errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- One or more memory correctable training errors have occurred on the memory slot identified in the message. A corrected Write Leveling error was detected.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the correctable error persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0181
- Message
- One or more memory correctable training errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- One or more memory correctable training errors have occurred on the memory slot identified in the message. A corrected Write DQ/DQS error was detected.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the correctable error persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0182
- Message
- One or more memory correctable training errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- One or more memory correctable training errors have occurred on the memory slot identified in the message. A corrected Early Vref Centering error was detected.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the correctable error persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0183
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- One or more memory errors have occurred on memory slot identified in the message. The error occurred during Early Vref Centering initialization.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0184
- Message
- One or more memory errors have occurred on memory slot: arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- One or more memory errors have occurred on memory slot identified in the message. The error occurred during Load Reduced DIMM (LR-DIMM) buffer initialization.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0185
- Message
- Load Reduced DIMM (LR-DIMM) training errors have occurred on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- A Load-Reduced DIMM (LR-DIMM) buffer initialization failure was detected during memory initialization.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0186
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the DC Detection phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0187
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Clock Detection phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0188
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Host Impedance phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0189
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Transmit DQS DCC phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0190
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Clock DCC Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0191
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the VCK Reference Clock phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0192
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Clock Alignment phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0193
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Coarse Command Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0194
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Fine Command Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0195
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Read Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0196
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Error Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0197
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Read Level Coarse Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0198
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Read Level Fine Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0199
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Write Level Fine Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0200
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Write Level Coarse Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0201
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Write Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0202
- Message
- An error occurred during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Scalable Memory Interconnect initialization during the Health Check phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0203
- Message
- A failing memory buffer has been detected during Scalable Memory Interconnect (SMI) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- A failing memory buffer has been identified on the memory riser identified in the message.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0204
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Clock Training FIFO Reset phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0205
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Command Clock Training - Group 0 phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0206
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Command Clock Training - Group 1 phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0207
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Command Clock Training - Group 2 phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0208
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Command Clock Training - Group All phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0209
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Transmit Buffer Per Bit Deskew Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0210
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Receive Buffer Vref Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0211
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Transmit Buffer Vref Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0212
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Early Command Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0213
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Basic Read DQ/DQS Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0214
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Basic Receive Enable Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0215
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Basic Write Level Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0216
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Late Command Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0217
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Basic Write DQ/DQS Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0218
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Write Timing Centering 2D Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0219
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Read Timing Centering 2D Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0220
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Write Voltage Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0221
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Read Voltage Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0222
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Round Trip Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0223
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Receive Buffer Per Bit Deskew Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0224
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Transmit Buffer Per Bit Deskew Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0225
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the DDR4 LR-DIMM Receive Buffer Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0226
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the DDR4 LR-DIMM Transmit Buffer Training phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0227
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Receive Enable Training - Configuration Read phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0228
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Receive Enable Training - Configuration Write phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0229
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Receive Enable Training - Calibration phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0230
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Receive Enable Training - Calculation phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0231
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Write Leveling Training - Configuration Read phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0232
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Write Leveling Training - Configuration Write phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0233
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Write Leveling Training - FIFO Reset phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0234
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Write Leveling Training - Memory Test phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0235
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Memory Buffer Write Leveling Training - Calibration phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0236
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Write DQ/DQS Training - FIFO Reset phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0237
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Write DQ/DQS Training - Memory Test phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0238
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Write DQ/DQS Training - Calibration phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0239
- Message
- An error occurred during DDR memory channel initialization on memory slots: arg1 .
- Arguments
- arg1 = slot numbers
- Detailed Description
- An error occurred during DDR memory initialization during the Write DQ/DQS Training - Calculation phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the DIMM module and 3) Restart the system. If the issue persists, then replace the faulty memory module(s) identified in the message.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0240
- Message
- An error occurred during Voltage Regulator (VR) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Memory Voltage Regulator initialization during the VR0 SVID Ramp phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0241
- Message
- An error occurred during Voltage Regulator (VR) initialization on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- An error occurred during Memory Voltage Regulator initialization during the VR1 SVID Ramp phase.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0242
- Message
- Unable to enable the requested Partial Mirror size of arg1 GB due to the current DIMM population or hardware configuration does not support the requested size. arg2 GB was allocated instead.
- Arguments
- arg1 = requested memory size, arg2 = allocated memory size
- Detailed Description
- The Partial Memory Mirroring feature cannot be enabled because the current DIMM population or hardware configuration does not support the requested size.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure the requested Partial Mirror size can be supported. For more information, see platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0243
- Message
- Scalable Memory Interconnect (SMI) operating at reduced width on memory riser arg1 .
- Arguments
- arg1 = riser letter
- Detailed Description
- The Scalable Memory Interconnect (SMI) channel identified in the message is operating at a degraded width. This allows continued uptime although indicates an error condition requiring further investigation.This maybe an early indication of upcoming memory riser failure.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Reseat the memory riser and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0244
- Message
- Quick Path Interconnect (QPI) links are operating in slow speed mode.
- Detailed Description
- Quick Path Interconnect (QPI) links failed to come up to full operating frequency.
- Recommended Response Action
- Reseat all processors in the system and ensure all processors are matching. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0245
- Message
- Quick Path Interconnect (QPI) link initialization error detected.
- Detailed Description
- Quick Path Interconnect (QPI) initialization failed to configure all installed processors to the maximum common frequency.
- Recommended Response Action
- Reseat all processors in the system and ensure all processors are matching. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0246
- Message
- Quick Path Interconnect (QPI) initialization error detected.
- Detailed Description
- Quick Path Interconnect (QPI) initialization encountered a programmatic error. Link option mismatch detected.
- Recommended Response Action
- Reseat all processors in the system and ensure all processors are matching. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0247
- Message
- Quick Path Interconnect (QPI) initialization error detected.
- Detailed Description
- Quick Path Interconnect (QPI) initialization encountered a programmatic error. The requested Memory Mapped IO (MMIOH) size is not supported. MMIOH allocation was forced instead.
- Recommended Response Action
- Reseat all processors in the system and ensure all processors are matching. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0248
- Message
- Quick Path Interconnect (QPI) initialization error detected on processor arg1 .
- Arguments
- arg1 = processor number
- Detailed Description
- Quick Path Interconnect (QPI) initialization encountered a programmatic error. A resource allocation was forced because resources were not requested for the identified processor. .
- Recommended Response Action
- Reseat all processors in the system and ensure all processors are matching. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0249
- Message
- Quick Path Interconnect (QPI) initialization error detected.
- Detailed Description
- Quick Path Interconnect (QPI) initialization encountered a programmatic error. A requested resource could not be allocated. Resource was forced to maximum possible value instead.
- Recommended Response Action
- Reseat all processors in the system and ensure all processors are matching. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0250
- Message
- Quick Path Interconnect (QPI) initialization error detected.
- Detailed Description
- Quick Path Interconnect (QPI) initialization encountered a programmatic error. The Legacy VGA range processor target is not populated. Decode was forced to the Legacy CPU socket.
- Recommended Response Action
- Reseat all processors in the system and ensure all processors are matching. If the issue persists, contact your service provider.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0251
- Message
- Memory riser arg1 is populated behind an empty processor socket.
- Arguments
- arg1 = riser number
- Detailed Description
- A memory riser was detected behind an empty processor socket. Memory must be installed behind a populated processor socket in order to be recognized by the system and available for usage. Check to make sure processors and memory are installed in a supported configuration.
- Recommended Response Action
- Do the following: 1) Remove input power to the system, 2) Populate processors and memory in a supported configuration and 3) Restart the system. For more information, see the platform Owners Manual.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0252
- Message
- Unable to boot a boot option because the watchdog timer has expired. System will reset.
- Detailed Description
- The watchdog timer is armed before the BIOS boot manager invokes an UEFI boot option. The watchdog is set to a period of 5 minutes. The Operating System boot loader from the boot option is required to disable the watchdog timer after it is successfully loaded, otherwise the system will reset if the timer expires.
- Recommended Response Action
- Check the boot option image and boot loader. Update them to the latest version if possible.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0253
- Message
- Unable to enable NUMA Fault Resilient Memory (FRM) feature due to the current configuration does not support it.
- Detailed Description
- Unable to enable NUMA Fault Resilient Memory (FRM) feature due to the current configuration does not support it.
- Recommended Response Action
- Check the DIMM population and hardware configuration to make sure NUMA FRM feature can be supported. For more information, see platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0254
- Message
- Unable to enable NUMA Fault Resilient Memory operating mode because of channel configuration mismatches.
- Detailed Description
- Unable to enable NUMA Fault Resilient Memory operating mode because of channel configuration mismatches.
- Recommended Response Action
- Make sure identical memory modules in corresponding slots of channel pairs are populated. For more information, see platform Owners Manual.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0255
- Message
- Network Daughter Card 1 and Network Daughter Card 2 in the system do not match.
- Detailed Description
- Network Daughter Card 1 and Network Daughter Card 2 in the system do not match.
- Recommended Response Action
- Check the Network Daughter Cards and make sure they are the same type.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
UEFI0256
- Message
- Unable to allocate legacy I/O resources for one of more PCIe devices because the legacy I/O space limit was reached.
- Detailed Description
- Unable to allocate legacy I/O resources for one of more PCIe devices because the legacy I/O space limit was reached. The legacy I/O space limit is 64K.
- Recommended Response Action
- Do one of the following and retry the operation: 1) Remove unused PCIe cards to free up legacy I/O space. 2) Go to System Setup and disable unused PCIe cards to free up legacy I/O space.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0257
- Message
- Unable to boot to Service Partition because the target Service Partition was not found in the boot list.
- Detailed Description
- Cannot boot to Service Partition because the target Service Partition was not found in the boot list.
- Recommended Response Action
- Retry the operation. If the issue persists, do one of the following and retry the operation: 1) Update the system BIOS. 2) Update the iDRAC firmware.
- Category
- System Health (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0258
- Message
- An issue is observed on the Hard-drive/SSD backplane.
- Detailed Description
- An issue is observed on the Hard-drive/SSD backplane.
- Recommended Response Action
- Do one of the following: 1) Make sure the correct type of Hard-drive/SSD backplane is installed. 2) Check the configuration of Hard-drive/SSD backplane and make sure its power cable is connected. Restart the system and retry the operation. If the issue persists, contact your service provider.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 1 (Critical)
UEFI0263
- Message
- Unable to perform iSCSI boot on connection arg1 because the network cable is not connected.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the network cable is not connected.
- Recommended Response Action
- Check the network cable connection of the system and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0264
- Message
- Unable to perform iSCSI boot because the iSCSI initiator name is invalid.
- Detailed Description
- Unable to perform iSCSI boot because the iSCSI initiator name is invalid.
- Recommended Response Action
- Go to System Setup > Network Settings page, make sure there is no typographical error in the iSCSI Initiator Name field, and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0265
- Message
- Unable to perform iSCSI boot on connection arg1 because the iSCSI initiator IPv4 address is invalid.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the iSCSI initiator IPv4 address is invalid.
- Recommended Response Action
- Go to System Setup > Network Settings > iSCSI Device Settings page, make sure there is no typographical error in the Initiator IP address field, and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0266
- Message
- Unable to perform iSCSI boot on connection arg1 because the iSCSI initiator IPv4 subnet mask address is invalid.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the iSCSI initiator IPv4 subnet mask address is invalid.
- Recommended Response Action
- Go to System Setup > Network Settings > iSCSI Device Settings page, make sure there is no typographical error in the Initiator Subnet Mask field, and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0267
- Message
- Unable to perform iSCSI boot on connection arg1 because the IPv4 initiator gateway address is invalid.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the IPv4 initiator gateway address is invalid.
- Recommended Response Action
- Go to System Setup > Network Settings > iSCSI Device Settings page, make sure there is no typographical error in the Initiator Gateway field, and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0268
- Message
- Unable to perform iSCSI boot on connection arg1 because the iSCSI target name is invalid.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the iSCSI target name is invalid.
- Recommended Response Action
- Go to System Setup > Network Settings > iSCSI Device Settings > Connection Settings page, make sure the iSCSI Target Name in the iSCSI setup page is correct, and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0269
- Message
- Unable to perform iSCSI boot on connection arg1 because the iSCSI target IP address is invalid.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the iSCSI target IP address is invalid.
- Recommended Response Action
- Go to System Setup > Network Settings > iSCSI Device Settings > Connection Settings page, do the following: 1) Make sure the Target IP Address is set correspoding to the mode enabled (IPv4/IPv6). 2) Make sure there is no typographical error in the Target IP Address field. 3) Retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0270
- Message
- Unable to perform iSCSI boot on connection arg1 because the network connection to DHCPv4 server is not established.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the network connection to DHCPv4 server is not established.
- Recommended Response Action
- Check the network cable connection of the initiator or the DHCPv4 server and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0271
- Message
- Unable to perform iSCSI boot on connection arg1 because the network connection to DHCPv6 server is not established.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the network connection to DHCPv6 server is not established.
- Recommended Response Action
- Check the network cable connection of the initiator or the DHCPv6 server and retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0272
- Message
- Unable to perform iSCSI boot on connection arg1 because the BIOS cannot obtain the initiator information from DHCPv4 server.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the BIOS cannot obtain the initiator information from DHCPv4 server.
- Recommended Response Action
- Do one of the following: 1) Check the configuration of DHCPv4 server. 2) Go to System Setup > Network Settings > iSCSI Device Settings > Connection Settings page, disable DHCP and configure the initiator information manually. Retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0273
- Message
- Unable to perform iSCSI boot on connection arg1 because the iSCSI target configuration data obtained from DHCPv4 server is invalid.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the iSCSI target configuration data obtained from DHCPv4 server is invalid.
- Recommended Response Action
- Do one of the following: 1) Reconfigure the DHCPv4 server root path option, and note that server name must be speicfied. 2) Go to System Setup > Network Settings > iSCSI Device Settings > Connection Settings page, disable Target Info via DHCP and configure the parameters manually. Retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0274
- Message
- Unable to perform iSCSI boot on connection arg1 because the iSCSI login operation did not complete successfully.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the iSCSI login operation did not complete successfully.
- Recommended Response Action
- Do the following: 1) Go to System Setup > Network Settings > iSCSI Device Settings > Connection Settings page, make sure the target name is correct. 2) On the iSCSI target system, make sure the initiator name is added into the target identifiers. 3) Compare the authentication settings in the iSCSI initiator setup page to that of the iSCSI target system and make sure the settings match. 4) Retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0275
- Message
- Unable to perform iSCSI boot on connection arg1 because the TCP connection timed out when connecting to the iSCSI target.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the TCP connection timed out when connecting to the iSCSI target.
- Recommended Response Action
- Do the following: 1) Make sure the iSCSI target system is online with the firewall configured to allow TCP access. 2) Make sure the server network infrastructure is configured to allow access to the iSCSI target. 3) Go to System Setup > Network Settings > iSCSI Device Settings > Connection Settings page, make sure the iSCSI initiator settings (iSCSI, DHCP, VLAN, initiator/target IP addresses) are configured correctly. 4) Retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0276
- Message
- Unable to perform iSCSI boot on connection arg1 because the initiator information from DHCPv6 server cannot be obtained.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection identified in the message because the initiator information from DHCPv6 server cannot be obtained.
- Recommended Response Action
- Do one of the following: 1) Check the configuration of DHCPv6 server. 2) Go to System Setup > Network Settings > iSCSI Device Settings > Connection Settings page, disable DHCP and configure the initiator information manually. Retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
UEFI0277
- Message
- Unable to perform iSCSI boot on connection arg1 because the iSCSI target configuration data obtained from DHCPv6 server is invalid.
- Arguments
- arg1 = number
- Detailed Description
- Unable to perform iSCSI boot on the connection number identified in the message because the iSCSI target configuration data obtained from DHCPv6 server is invalid.
- Recommended Response Action
- Do one of the following: 1) Reconfigure the DHCPv6 server boot file URL option, and note that server name must be specified. 2) Go to System Setup > Network Settings > iSCSI Device Settings > Connection Settings page, disable Target Info via DHCP and configure the parameters manually. Retry the operation.
- Category
- Configuration (UEFI = UEFI Event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\