Skip to main content

List of UEFI events

This section lists all messages that can be sent from UEFI.

  • 11002: [11002] A processor mismatch has been detected between one or more processors in the system.

    [11002] A processor mismatch has been detected between one or more processors in the system.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. This message could occur with messages about other processor configuration problem Resolve those messages first.
    2. If the problem persists, ensure that matching processors are installed (e., matching option part numbers, etc)
    3. Verify that the processors are installed in the correct socket If not, correct that problem.
    4. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    5. Replace mismatching processor. Inspect the processor socket and replace the system board first if the socket is damaged.

  • 11004: [11004] A processor within the system has failed the BIST.

    [11004] A processor within the system has failed the BIST.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. If the processor or firmware was just updated, check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    2. If there are multiple processors, swap processors to move affected processor to another processor socket and retry. If problem follows the affected processor, or this is a single processor system, replace the processor. Inspect the processor socket on each processor removal and replace system board first if the processor socket is damaged or mis-aligned pins are found.
    3. Replace the system board.

  • 1100C: [1100C] An uncorrectable error has been detected on processor %.

    [1100C] An uncorrectable error has been detected on processor %.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Reboot the system. If problem persists, contact Support.

  • 18005: [18005] A discrepancy has been detected in the number of cores reported by one or more processor packages within the system.

    [18005] A discrepancy has been detected in the number of cores reported by one or more processor packages within the system.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. If this is a newly installed option, ensure that matching processors are installed in the correct processor socket
    2. Check the IBM support site for an applicable service bulletin that applies to this processor error.
    3. Replace the processor. Inspect the processor socket and replace the system board first if the socket is damaged.

  • 18006: [18006] A mismatch between the maximum allowed QPI link speed has been detected for one or more processor package

    [18006] A mismatch between the maximum allowed QPI link speed has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. If this is a newly installed option, ensure that matching processors are installed in the correct processor socket
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    3. Replace the processor. Inspect the processor socket and replace the system board first if the socket is damaged.

  • 18007: [18007] A power segment mismatch has been detected for one or more processor package

    [18007] A power segment mismatch has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Processors installed do not have the same power requirements
    2. Ensure that all Processors have matching power requirements (such as 65, 95, or 130 Watts)
    3. If power requirements match, check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    4. Replace the processor. Inspect the processor socket and replace the system board first if the socket is damaged.

  • 18009: [18009] A core speed mismatch has been detected for one or more processor package

    [18009] A core speed mismatch has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Verify that matching processors are installed in the correct processor socket Correct any mismatch issues found.
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    3. Replace the processor. Inspect the processor socket and replace the system board first if the socket is damaged.

  • 1800A: [1800A] A mismatch has been detected between the speed at which a QPI link has trained between two or more processor package

    [1800A] A mismatch has been detected between the speed at which a QPI link has trained between two or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Verify that the processor is a valid option that is listed as a Server Proven device for this system. If not, remove the Processor and install one listed on the Server Proven website.
    2. Verify that matching processors are installed in the correct processor socket Correct any mismatch found.
    3. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    4. Replace the processor. Inspect the processor socket and replace the system board first if the socket is damaged.

  • 1800B: [1800B] A cache size mismatch has been detected for one or more processor package

    [1800B] A cache size mismatch has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Verify that matching processors are installed in the correct processor socket Correct any mismatch found.
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    3. Replace the system board.

  • 1800C: [1800C] A cache type mismatch has been detected for one or more processor package

    [1800C] A cache type mismatch has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Verify that matching processors are installed in the correct processor socket Correct any mismatch found.
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    3. Replace the system board.

  • 1800D: [1800D] A cache associativity mismatch has been detected for one or more processor package

    [1800D] A cache associativity mismatch has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Verify that matching processors are installed in the correct processor socket Correct any mismatch found.
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    3. Replace the system board.

  • 1800E: [1800E] A processor model mismatch has been detected for one or more processor package

    [1800E] A processor model mismatch has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Verify that matching processors are installed in the correct processor socket Correct any mismatch found.
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this Processor error.
    3. Replace the system board.

  • 1800F: [1800F] A processor family mismatch has been detected for one or more processor package

    [1800F] A processor family mismatch has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Verify that matching processors are installed in the correct processor socket Correct any mismatch found.
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    3. Replace the system board.

  • 18010: [18010] A processor stepping mismatch has been detected for one or more processor package

    [18010] A processor stepping mismatch has been detected for one or more processor package

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Verify that matching processors are installed in the correct processor socket Correct any mismatch found.
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
    3. Replace the system board.

  • 2011001: [2011001] An Uncorrected PCIe Error has Occurred at Bus % Device % Function %. The Vendor ID for the device is % and the Device ID is %.

    [2011001] An Uncorrected PCIe Error has Occurred at Bus % Device % Function %. The Vendor ID for the device is % and the Device ID is %.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. If this compute node and/or any attached cables were recently installed, moved, serviced or upgraded,
      1. Reseat the adapter and any attached cable
      2. Reload the device driver.
      3. If device is not recognized, reconfiguring slot to Gen1 or Gen2 may be required. Gen1/Gen2 settings can be configured via F1 Setup -> System Settings -> Devices and I/O Ports -> PCIe Gen1/Gen2/Gen3 Speed Selection, or the ASU Utility.
    2. Check the IBM support site for an applicable device driver, firmware update, or other information that applies to this error. Load the new device driver and install any required firmware update
    3. If the problem persists, remove the adapter. If system reboots successfully without the adapter, replace that adapter.
    4. Replace the processor.

  • 2018001: [2018001] An Uncorrected PCIe Error has Occurred at Bus % Device % Function %. The Vendor ID for the device is % and the Device ID is %.

    [2018001] An Uncorrected PCIe Error has Occurred at Bus % Device % Function %. The Vendor ID for the device is % and the Device ID is %.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. If this compute node and/or any attached cables were recently installed, moved, serviced or upgraded:
      1. Reseat the adapter and any attached cable
      2. Reload the device driver.
      3. If device is not recognized, reconfiguring slot to Gen1 or Gen2 may be required. Gen1/Gen2 settings can be configured via F1 Setup -> System Settings -> Devices and I/O Ports -> PCIe Gen1/Gen2/Gen3 Speed Selection, or the ASU Utility.
    2. Check the IBM support site for an applicable device driver, firmware update, or other information that applies to this error. Load the new device driver and install any required firmware update
    3. If the problem persists, remove the adapter. If the system reboots successfully without the adapter, replace that adapter.
    4. Replace the processor.

  • 2018002: [2018002] The device found at Bus % Device % Function % could not be configured due to resource constraint The Vendor ID for the device is % and the Device ID is %.

    [2018002] The device found at Bus % Device % Function % could not be configured due to resource constraint The Vendor ID for the device is % and the Device ID is %.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. If this PCIe device and/or any attached cables were recently installed, moved, serviced or upgraded, reseat the adapter and any attached cable
    2. Check the IBM support site for any applicable service bulletin or UEFI or adapter firmware update that applies to this error.

      NOTE: It may be necessary to disable unused option ROMs from UEFI F1 setup or ASU or using adapter manufacturer utilities so that adapter firmware can be updated.

    3. Move the adapter to a different slot. If a slot is not available or error recurs, replace the adapter.
    4. If the adapter was moved to a different slot and the error did not recur, verify that this is not a system limitation. Then replace the system board. Also, if this is not the initial installation and the error persists after adapter replacement, replace the system board.

  • 2018003: [2018003] A bad option ROM checksum was detected for the device found at Bus % Device % Function %. The Vendor ID for the device is % and the Device ID is %.

    [2018003] A bad option ROM checksum was detected for the device found at Bus % Device % Function %. The Vendor ID for the device is % and the Device ID is %.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. If this PCIe device and/or any attached cables were recently installed, moved, serviced or upgraded, reseat the adapter and any attached cable
    2. Move the adapter to a different system slot, if available.
    3. Check the IBM support site for any applicable service bulletin or UEFI or adapter firmware update that applies to this error.

      NOTE: It may be necessary to configure slot to Gen1 or to use special utility software so that adapter firmware can be upgraded. Gen1/Gen2 settings can be configured via F1 Setup -> System Settings -> Devices and I/O Ports -> PCIe Gen1/Gen2/Gen3 Speed Selection, or the ASU Utility.

    4. Replace the adapter.

  • 3020007: [3020007] A firmware fault has been detected in the UEFI image.

    [3020007] A firmware fault has been detected in the UEFI image.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Update the UEFI image.
    3. Replace the system board.

  • 3028002: [3028002] Boot permission timeout detected.

    [3028002] Boot permission timeout detected.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check CMM/IMM logs for communication errors and resolve.
    2. Reseat the system.
    3. If problem persists, contact Support.

  • 3030007: [3030007] A firmware fault has been detected in the UEFI image.

    [3030007] A firmware fault has been detected in the UEFI image.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Update the UEFI image.
    3. Replace the system board.

  • 3040007: [3040007] A firmware fault has been detected in the UEFI image.

    [3040007] A firmware fault has been detected in the UEFI image.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Update the UEFI image.
    3. Replace the system board.

  • 3048005: [3048005] UEFI has booted from the backup flash bank.

    [3048005] UEFI has booted from the backup flash bank.

    • Severity: Info

    User Response:

    Complete the following steps:

    Return the system to primary bank.

  • 3048006: [3048006] UEFI has booted from the backup flash bank due to an Automatic Boot Recovery (ABR) event.

    [3048006] UEFI has booted from the backup flash bank due to an Automatic Boot Recovery (ABR) event.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Update the primary UEFI image.
    3. Replace the system board.

  • 3050007: [3050007] A firmware fault has been detected in the UEFI image.

    [3050007] A firmware fault has been detected in the UEFI image.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Update the UEFI image.
    3. Replace the system board.

  • 305000A: [305000A] An invalid date and time have been detected.

    [305000A] An invalid date and time have been detected.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Check IMM/chassis event log. This event should immediately precede 0068002 error. Resolve that event or any other battery related error
    2. Use F1 Setup to reset date and time. If problem returns after a system reset, replace CMOS battery.
    3. If problem persists then check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    4. Replace the system board.

  • 3058004: [3058004] A Three Strike boot failure has occurred. The system has booted with default UEFI setting

    [3058004] A Three Strike boot failure has occurred. The system has booted with default UEFI setting

    • Severity: Error

    User Response:

    Complete the following steps:
    1. This event resets UEFI to the default settings for the next boot. If successful, the Setup Utility is displayed. The original UEFI settings are still present.
    2. If you did not intentionally trigger the reboots, check logs for probable cause.
    3. Undo recent system changes (settings or devices added). If there were no recent system changes, remove all options, and then remove the CMOS battery for 30 seconds to clear CMOS content Verify that the system boot Then, re-install the options one at a time to locate the problem.
    4. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    5. Update the UEFI firmware.
    6. Remove and re-install CMOS battery for 30 seconds to clear CMOS contents
    7. Replace the system board.

  • 3058009: [3058009] DRIVER HEALTH PROTOCOL: Missing Configuraiton. Requires Change Settings From F1.

    [3058009] DRIVER HEALTH PROTOCOL: Missing Configuraiton. Requires Change Settings From F1.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Go to the Setup Utility (System Settings -> Settings -> Driver Health Status List) and find a driver/controller reporting Configuration Required statu
    2. Search for the driver menu from System Settings and change settings appropriately.
    3. Save settings and restart system.

  • 305800A: [305800A] DRIVER HEALTH PROTOCOL: Reports 'Failed' Status Controller.

    [305800A] DRIVER HEALTH PROTOCOL: Reports 'Failed' Status Controller.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Reboot the system.
    2. If problem persists, switch to backup UEFI or update the current UEFI image.
    3. Replace the system board.

  • 305800B: [305800B] DRIVER HEALTH PROTOCOL: Reports 'Reboot' Required Controller.

    [305800B] DRIVER HEALTH PROTOCOL: Reports 'Reboot' Required Controller.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. No action required. The system will reboot at the end of POST.
    2. If the problem persists, switch to the backup UEFI image or update the current UEFI image.
    3. Replace the system board.

  • 305800C: [305800C] DRIVER HEALTH PROTOCOL: Reports 'System Shutdown' Required Controller.

    [305800C] DRIVER HEALTH PROTOCOL: Reports 'System Shutdown' Required Controller.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Reboot the system.
    2. If problem persists, switch to the backup UEFI image or update the current UEFI image.
    3. Replace system board.

  • 305800D: [305800D] DRIVER HEALTH PROTOCOL: Disconnect Controller Failed. Requires 'Reboot'.

    [305800D] DRIVER HEALTH PROTOCOL: Disconnect Controller Failed. Requires 'Reboot'.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Reboot the system to reconnect the controller.
    2. If problem persists, switch to the backup UEFI image or update the current UEFI image.
    3. Replace the system board.

  • 305800E: [305800E] DRIVER HEALTH PROTOCOL: Reports Invalid Health Status Driver.

    [305800E] DRIVER HEALTH PROTOCOL: Reports Invalid Health Status Driver.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Reboot the system.
    2. If problem persists, switch to the backup UEFI image or update the current UEFI image.
    3. Replace the system board.

  • 3060007: [3060007] A firmware fault has been detected in the UEFI image.

    [3060007] A firmware fault has been detected in the UEFI image.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Update the UEFI image.
    3. Replace the system board.

  • 3070007: [3070007] A firmware fault has been detected in the UEFI image.

    [3070007] A firmware fault has been detected in the UEFI image.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Update the UEFI image.
    3. Replace the system board.

  • 3108007: [3108007 ] The default system settings have been restored.

    [3108007 ] The default system settings have been restored.

    • Severity: Error

    User Response:

    Complete the following steps:

    Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.

  • 3808000: [3808000] An IMM communication failure has occurred.

    [3808000] An IMM communication failure has occurred.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Reset the IMM from the CMM.
    2. Use the CMM to remove auxilliary power from the compute node. This will reboot the compute node.
    3. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    4. Update the UEFI Firmware.
    5. Replace the system board.

  • 3808002: [3808002] An error occurred while saving UEFI settings to the IMM.

    [3808002] An error occurred while saving UEFI settings to the IMM.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Use the Setup Utility to verify and save the settings (which will recover the settings).
    2. Reset the IMM from the CMM.
    3. Use CMM to remove auxilliary power from the compute node. This will reboot the compute node.
    4. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    5. Update the IMM Firmware.
    6. Remove and re-install CMOS battery for 30 seconds to clear CMOS content
    7. Replace the system board.

  • 3808003: .[3808003] Unable to retrieve the system configuration from the IMM.

    .[3808003] Unable to retrieve the system configuration from the IMM.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Use the Setup Utility to verify and save the settings (which will recover the settings).
    2. Reset the IMM from the CMM.
    3. Use CMM to remove auxilliary power from the compute node. This will reboot the compute node.
    4. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    5. Update the IMM Firmware.
    6. Remove and re-install CMOS battery for 30 seconds to clear CMOS content
    7. Replace the system board.

  • 3808004: [3808004] The IMM System Event log (SEL) is full.

    [3808004] The IMM System Event log (SEL) is full.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Use the IMM Web Interface to clear the event log.
    2. If IMM communication is unavailable, use the Setup Utility to access the System Event Logs Menu and choose Clear IMM System Event Log and Restart Server.

  • 3818001: [3818001] The firmware image capsule signature for the currently booted flash bank is invalid.

    [3818001] The firmware image capsule signature for the currently booted flash bank is invalid.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Reboot the system. Will come up on backup UEFI image. Update the primary UEFI image.
    2. If error does not persist no additional recovery action is required.
    3. If error persists, or boot is unsuccessful, replace the system board.

  • 3818002: [3818002] The firmware image capsule signature for the non-booted flash bank is invalid.

    [3818002] The firmware image capsule signature for the non-booted flash bank is invalid.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. Update the backup UEFI image.
    2. If error does not persist, no additional recovery action is required.
    3. If error persists, or boot is unsuccessful, replace the system board.

  • 3818003: [3818003] The CRTM flash driver could not lock the secure flash region.

    [3818003] The CRTM flash driver could not lock the secure flash region.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. If system failed to boot successfully, DC cycle the system.
    2. If system boots to F1 setup, update the UEFI image and reset bank to primary (if required). If the system boots without error, recovery is complete and no additional action is required.
    3. If system fails to boot, or if the firmware update attempt fails, replace the system board.

  • 3818004: [3818004] The CRTM flash driver could not successfully flash the staging area. A failure occurred.

    [3818004] The CRTM flash driver could not successfully flash the staging area. A failure occurred.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Continue booting the system. If the system does not reset, manually reset the system.
    2. If the error is not reported on the subsequent boot, no additional recovery action is required.
    3. If the error persists, continue booting system and update the UEFI image.
    4. Replace the system board.

  • 3818005: [3818005] The CRTM flash driver could not successfully flash the staging area. The update was aborted

    [3818005] The CRTM flash driver could not successfully flash the staging area. The update was aborted

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Continue booting system. If system does not reset, manually reset the system.
    2. If the error is not reported on the subsequent boot, no additional recovery action is required.
    3. If the event persists, continue booting system and update the UEFI image.
    4. Replace the system board.

  • 3818007: [3818007] The firmware image capsules for both flash banks could not be verified.

    [3818007] The firmware image capsules for both flash banks could not be verified.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. If system failed to boot successfully, DC cycle system.
    2. If system boots to F1 setup, update the UEFI image and reset bank to primary (if required). If the system boots without error, recovery is complete and no additional action is required.
    3. If system fails to boot, or if the firmware update attempt fails, replace the system board.

  • 3818009: [3818009] The TPM could not be properly initialized.

    [3818009] The TPM could not be properly initialized.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Reboot the system.
    3. If the error continues, replace the system-board assembly (see Removing the system-board assembly and Installing the system-board assembly).

  • 3868000: [3868000] IFM: System reset performed to reset adapter

    [3868000] IFM: System reset performed to reset adapter

    • Severity: Info

    User Response:

    Complete the following steps:

    Information only; no action is required.

  • 3868001: [3868001] IFM: Reset loop avoided - Multiple resets not allowed.

    [3868001] IFM: Reset loop avoided - Multiple resets not allowed.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Update all firmware (including adapter firmware) to the latest level
    2. If problem persists, contact Support.

  • 3868002: [3868002] BOFM: Error communicating with the IMM - BOFM may not be deployed correctly.

    [3868002] BOFM: Error communicating with the IMM - BOFM may not be deployed correctly.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. Update all firmware (including adapter firmware) to the latest level
    2. If problem persists, contact Support.

  • 3868003: [3868003] BOFM: Configuration to large for compatibility mode.

    [3868003] BOFM: Configuration to large for compatibility mode.

    • Severity: Info

    User Response:

    Complete the following steps:

    Information only; no action is required.

  • 3938002: [3938002] A boot configuration error has been detected.

    [3938002] A boot configuration error has been detected.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. F1 Setup -> Save Setting
    2. Retry the configuration update.

  • 50001: [50001] A DIMM has been disabled due to an error detected during POST.

    [50001] A DIMM has been disabled due to an error detected during POST.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. If the DIMM was disabled because of a memory fault, follow the procedure for that event.
    2. If no memory fault is recorded in the logs and no DIMM connector error LEDs are lit, re-enable the DIMM through the Setup utility or the Advanced Settings Utility (ASU).
    3. If the problem persists, Power cycle the compute node from the management console.
    4. Reset the IMM to default setting
    5. Reset UEFI to default setting
    6. Update IMM and UEFI firmware.
    7. Replace the system board.

  • 51003: [51003] An uncorrectable memory error was detected in DIMM slot % on rank %.

    [51003] An uncorrectable memory error was detected in DIMM slot % on rank %.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. If the compute node has recently been installed, moved, serviced, or upgraded, verify that the DIMM is properly seated and visually verify that there is no foreign material in any DIMM connector on that memory channel. If either of these conditions is found, correct and retry with the same DIMM. (Note: The event Log might contain a recent 00580A4 event denoting detected change in DIMM population that could be related to this problem.)
    2. If no problem is observed on the DIMM connectors or the problem persists, replace the DIMM identified by LightPath and/or event log entry.
    3. If problem recurs on the same DIMM connector, replace the other DIMMs on the same memory channel.
    4. Check the IBM support site for an applicable service bulletin or firmware update that applies to this memory error.
    5. If problem recurs on the same DIMM connector, inspect connector for damage. If found, replace the system board.
    6. Replace the affected processor.
    7. Replace system board.

  • 51006: [51006] A memory mismatch has been detected. Please verify that the memory configuration is valid.

    [51006] A memory mismatch has been detected. Please verify that the memory configuration is valid.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Could follow an uncorrectable memory error or failed memory test. Check the log and service that event first. DIMMs disabled by other errors or actions could cause this event.
    2. Verify that the DIMMs are installed in the correct population sequence.
    3. Disable memory mirroring and sparing. If this action eliminates the mismatch, check the IBM Support site for information related to this problem.
    4. Update UEFI firmware.
    5. Replace the DIMM
    6. Replace the processor.

  • 51009: [51009] No system memory has been detected.

    [51009] No system memory has been detected.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. If any memory errors are logged other than this one, take actions indicated for those codes first.
    2. If no other memory diagnostic codes appear in the logs, verify that all DIMM connectors are enabled using the Setup utility or the Advanced Settings Utility (ASU).
    3. If the problem remains, shut down and remove node from chassis and physically verify that one or more DIMMs are installed and that all DIMMs are installed in the correct population sequence.
    4. If DIMMs are present and properly installed, check for any lit DIMM-connector LEDs, and if found, reseat those DIMM
    5. Reinstall node in chassis, power on node, then check logs for memory diagnostic code
    6. If the problem remains, replace the processor.
    7. If the problem remains, replace the system board.

  • 5100B: [5100B] An unqualified DIMM serial number has been detected: serial number % found in slot % of memory card %.

    [5100B] An unqualified DIMM serial number has been detected: serial number % found in slot % of memory card %.

    • Severity: Info

    User Response:

    Complete the following steps:
    1. If this information event is logged in the IMM event log, the server does not have qualified memory installed.
    2. The memory installed may not be covered under warranty.
    3. Without qualified memory, speeds supported above industry standards will not be enabled.
    4. Please contact your Local Sales Representative or Authorized Business Partner to order qualified memory to replace the unqualified DIMM(s).
    5. After you install qualified memory and power up the server, check to make sure this informational event is not logged again.

  • 58001: [58001] The PFA Threshold limit (correctable error logging limit) has been exceeded on DIMM number % at address %. MCx_Status contains % and MCx_Misc contains %.

    [58001] The PFA Threshold limit (correctable error logging limit) has been exceeded on DIMM number % at address %. MCx_Status contains % and MCx_Misc contains %.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. If the compute node has recently been installed, moved, serviced, or upgraded, verify that the DIMM is properly seated and visually verify that there is no foreign material in any DIMM connector on that memory channel. If either of these conditions is found, correct and retry with the same DIMM. (Note: The event Log might contain a recent 00580A4 event denoting detected change in DIMM population that could be related to this problem.)
    2. Check the IBM support site for an applicable firmware update that applies to this memory error. The release notes will list the known problems the update addresse
    3. If the previous steps do not resolve the problem, at the next maintenance opportunity, replace the affected DIMM (as indicated by LightPath and/or failure log entry).
    4. If PFA re-occurs on the same DIMM connector, swap the other DIMMs on the same memory channel one at a time to a different memory channel or processor. If PFA follows a moved DIMM to any DIMM connector on the different memory channel, replace the moved DIMM.
    5. Check the IBM support site for an applicable Service Bulletins (Service bulletins) that applies to this memory error. (Link to IBM support service bulletins)
    6. If problem continues to re-occur on the same DIMM connector, inspect DIMM connector for foreign material and remove, if found. If connector is damaged, replace system board.
    7. Remove the affected processor and inspect the processor socket pins for damaged or mis-aligned pin If damage is found or the processor is an upgrade part, replace the system board.
    8. Replace affected processor.
    9. Replace the system board.

  • 58007: [58007] Invalid memory configuration (Unsupported DIMM Population) detected. Please verify memory configuration is valid.

    [58007] Invalid memory configuration (Unsupported DIMM Population) detected. Please verify memory configuration is valid.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. This event could follow an uncorrectable memory error or failed memory test. Check the log and resolve that event first. DIMMs disabled by other errors or actions could cause this event.
    2. Ensure that the DIMM connectors are populated in the correct sequence.

  • 58008: [58008] A DIMM has failed the POST memory test.

    [58008] A DIMM has failed the POST memory test.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. You must AC-cycle the system to re-enable the affected DIMM connector or re-enable manually using the Setup utility.
    2. If the compute node has been recently installed, serviced, moved, or upgraded, check to ensure that DIMMs are firmly seated and that no foreign material can be seen in the DIMM connector. If either condition is observed, correct and retry with the same DIMM. (Note: The event Log might contain a recent 00580A4 event denoting detected change in DIMM population that could be related to this problem.)
    3. If problem persists, replace the DIMM identified by LightPath and/or event log entry.
    4. If problem recurs on the same DIMM connector, swap the other DIMMs on the same memory channel across channels one at a time to a different memory channel or processor. If problem follows a moved DIMM to a different memory channel, replace that DIMM.
    5. Check the IBM support site for an applicable service bulletin or firmware update that applies to this memory error.
    6. If problem stays with the original DIMM connector, re-inspect DIMM connector for foreign material and remove, if found. If connector is damaged, replace system board.
    7. Remove the affected processor and inspect the processor socket pins for damaged or mis-aligned pin If damage is found, or this is an upgrade processor, replace the system board. If there are multiple processors, swap them to move affected procesor to another processor socket and retry. If problem follows the affected processor (or there is only one processor), replace the affected processor.
    8. Replace the system board.

  • 58015: [58015] Memory spare copy initiated.

    [58015] Memory spare copy initiated.

    • Severity: Info

    User Response:

    Complete the following steps:

    Information only; no action is required.

  • 580A1: [580A1] Invalid memory configuration for Mirror Mode. Please correct memory configuration.

    [580A1] Invalid memory configuration for Mirror Mode. Please correct memory configuration.

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. If a DIMM connector error LED is lit, resolve the failure.
    2. Make sure that the DIMM connectors are correctly populated for mirroring mode.

  • 580A2: [580A2] Invalid memory configuration for Sparing Mode. Please correct memory configuration.

    [580A2] Invalid memory configuration for Sparing Mode. Please correct memory configuration.

    • Severity: Warning

    User Response:

    Complete the following steps:

    Make sure that the DIMM connectors are correctly populated for sparing mode.

  • 580A4: [580A4] Memory population change detected.

    [580A4] Memory population change detected.

    • Severity: Info

    User Response:

    Complete the following steps:

    Check system event log for uncorrected DIMM failures and replace those DIMM

  • 580A5: [580A5] Mirror Fail-over complete. DIMM number % has failed over to to the mirrored copy.

    [580A5] Mirror Fail-over complete. DIMM number % has failed over to to the mirrored copy.

    • Severity: Info

    User Response:

    Complete the following steps:

    Check the system-event log for uncorrected DIMM failures and replace those DIMM

  • 580A6: [580A6] Memory spare copy has completed successfully.

    [580A6] Memory spare copy has completed successfully.

    • Severity: Info

    User Response:

    Complete the following steps:

    Check system log for related DIMM failures and replace those DIMM

  • 68002: [68002] A CMOS battery error has been detected

    [68002] A CMOS battery error has been detected

    • Severity: Warning

    User Response:

    Complete the following steps:
    1. If the system was recently installed, moved, or serviced, make sure the battery is properly seated.
    2. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    3. Replace the CMOS battery.
    4. Replace the system board.

  • 68005: [68005] An error has been detected by the the IIO core logic on Bus %. The Global Fatal Error Status register contains %. The Global Non-Fatal Error Status register contains %. Please check error logs for the presence of additional downstream device error data.

    [68005] An error has been detected by the the IIO core logic on Bus %. The Global Fatal Error Status register contains %. The Global Non-Fatal Error Status register contains %. Please check error logs for the presence of additional downstream device error data.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the log for a separate error related to an associated PCIe device and resolve that error.
    2. Check the IBM support site for an applicable service bulletin or firmware update for the system or adapter that applies to this error.
    3. Replace the system board.

  • 680B8: [680B8] Internal QPI Link Failure Detected.

    [680B8] Internal QPI Link Failure Detected.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Inspect the processor socket for foreign debris or damage. If debris is found, remove the debri
    3. If error recurs, or socket damage is found, replace the system board.

  • 680B9: [680B9] External QPI Link Failure Detected.

    [680B9] External QPI Link Failure Detected.

    • Severity: Error

    User Response:

    Complete the following steps:
    1. Check the IBM support site for an applicable service bulletin or firmware update that applies to this error.
    2. Inspect the processor socket for foreign debris or damage. If debris is found, remove the debri
    3. If error recurs, or socket damage is found, replace the system board.