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