Uncorrectable Machine Check Exception on HP DL360 G7


i have about every hour in IML (hplog) from HP DL360 G7 record:

CRITICAL: CPU - Uncorrectable Machine Check Exception (Board 0, Processor 1, APIC ID 0x00000003, Bank 0x00000005, Status 0xBE000000'00800400, Address 0x00003FFF'811239E0, Misc 0x00000000'00007FFF)

hpasmcli> show server
System        : ProLiant DL360 G7   
ROM version   : P68 09/30/2010
iLo present   : Yes

Can someone tell me what part is being referenced by the IML status codes above?

Thank in advance!

asked on Server Fault Mar 20, 2014 by ReDSerpenT • edited May 19, 2015 by ewwhite

2 Answers


Please upgrade the BIOS on the server to the current revision. If this is reproducible on such a regular interval, that is absolutely the first thing I would try.

The safest way to run this update is to use the offline HP Service Pack for ProLiant DVD image. If not, can you tell us what operating system is in use? You can download specific updates for your server from here.

Beyond that, this could be a system board issue. You can try moving/reseating the DIMMs to see if the error message changes (following the DIMM). If it doesn't, it's likely the CPU socket for Processor 1. Inspect the LGA socket for bent pins.

You can also call HP ProLiant Support...

answered on Server Fault Mar 20, 2014 by ewwhite • edited Mar 20, 2014 by ewwhite

See here for more people experiencing a similar problem.

Possible workaround: In the BIOS, change the Power Regulator mode to "Static High Performance"

Resolution is likely brought by the May 5, 2011 BIOS update:

Resolved an issue that may result in any of the following conditions: operating system stops responding, unexpected system reset, Blue Screen when using a Microsoft Windows operating system, kernel panic when using a Linux operating system, or Purple Screen when using VMware ESX. A message may be displayed by the operating system or logged in the HP Integrated Management Log (IML) when this issue occurs indicating an "Uncorrectable Machine Check Exception." However, there are instances where the system resets before the operating system displays an error message and instances where the IML contains no log entry when this issue occurs. This issue does not occur if the Minimum Processor Idle State is configured for No C-states or C1E-state.

answered on Server Fault Mar 20, 2014 by the-wabbit

User contributions licensed under CC BY-SA 3.0