Article ID: 000056555 Content Type: Troubleshooting Last Reviewed: 04/26/2023

Unable to Post Due to “Fatal Error: System Encounter a Stopper Error!” POST Message While Booting

Environment

OS Independent

BUILT IN - ARTICLE INTRO SECOND COMPONENT
Summary

Steps resolve "Fatal Error: System encounter a Stopper Error!" POST message with POST code 30/32

Description

Node no longer boots up.

Note

The Fatal Error: System encounter a Stopper Error! shows up on the screen (with POST Code 30 or 32 at the bottom right).

example image

Resolution

This error indicates memory initialization error and is usually caused by 1 or more memory DIMMs installed in the system has gone bad. While less common, this can also cause by a bad memory slot on the mother board or memory controller in the CPU.

To solve the issue, it is required to identify the DIMM/location that is causing the issue.

If System Event Log is available, check if there is any ECC errors, remove the corresponding DIMMs and see if the system can finish POST successfully. Otherwise, follow below steps:

  1. Remove all DIMMs from the system except for DIMM A1 of the first CPU.
  2. Verify if the system can finish POST successfully.
    • If issue persists, replace DIMM A1.
    • If issue persists, install a DIMM in A1 of both processors. If the server boots re-install the firmware.
  3. If system POST successfully, add 1 more DIMM back to the system and try again.
    • First DIMM of each channel (blue slots) must be populated first before the second DIMM (black slots) of that channel can be populated.
  4. Repeat 2~3 until the DIMM causing the issue is isolated.
  5. Swap the DIMM causing the issue with a known good one and check if issue follows the DIMM or stays in slot.
    • If issue follows the DIMM, replace DIMM.
    • If issue stays in the same DIMM slot, swap the CPU and check if issue follows the CPU or stays in slot.
      • Replace CPU if issue follows CPU.
      • Replace motherboard if issue stays in the same slot.