ProLiant Servers - Netservers

HP Proliant Microserver Gen8 - G1610T 2.3ghz Keeps Rebooting

 
MichaelToon
Visitor

HP Proliant Microserver Gen8 - G1610T 2.3ghz Keeps Rebooting

Hi all,

I am having an issue with the above server restarting itself randomly. The errors on the Management Page are;

Unrecoverable System Error (NMI) has occurred. System Firmware will log additional details in a separate IML entry if possible

User Initiated NMI Switch

Then the minidump contains the following details;

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
-----------------
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 14393.2339.amd64fre.rs1_release_inmarket.180611-1502
SYSTEM_MANUFACTURER: HP
SYSTEM_PRODUCT_NAME: ProLiant MicroServer Gen8
SYSTEM_SKU: 712317-421
BIOS_VENDOR: HP
BIOS_VERSION: J06
BIOS_DATE: 07/16/2015
DUMP_TYPE: 2
BUGCHECK_P1: 4f4454
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 2
CPU_MHZ: 8f7
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1C'00000000 (cache) 1C'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x80
PROCESS_NAME: java.exe
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: BK07744
ANALYSIS_SESSION_TIME: 07-12-2018 11:25:36.0765
ANALYSIS_VERSION: 10.0.17134.12 amd64fre
LAST_CONTROL_TRANSFER: from fffff8024ba4621e to fffff8024bbe09b0
STACK_TEXT:
ffffaf00`e8d9bc08 fffff802`4ba4621e : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffaf00`e8d9bc10 fffff802`4bcb2ba8 : ffff850a`2307e968 fffff802`4ba5da70 fffff802`4ba5da70 00000000`00000001 : hal!HalBugCheckSystem+0x7e
ffffaf00`e8d9bc50 fffff802`4ba471ee : fffff802`000006c0 fffff802`4be41670 ffffaf00`e8d9bd30 fffff802`4bb2878d : nt!WheaReportHwError+0x258
ffffaf00`e8d9bcb0 fffff802`4baff33a : 00000005`612482f0 00000000`00000000 00000000`00000001 fffff802`4baff7e8 : hal!HalHandleNMI+0xfe
ffffaf00`e8d9bce0 fffff802`4bbeb342 : 00000005`612482f0 ffffaf00`e8d9bef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x106
ffffaf00`e8d9bd30 fffff802`4bbeb140 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffaf00`e8d9be70 00000000`037b6d6e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x1c0
00000000`2c40f190 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x37b6d6e
THREAD_SHA1_HASH_MOD_FUNC: b7b3ecfcf29850d1f1f7b1ad5911f9e3246de177
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e72bb5362904cd60b750b35f320f43096e55f89e
THREAD_SHA1_HASH_MOD: 92f9f07aed224bcfd65a617bfd6643269638f3ce
FOLLOWUP_IP:
nt!WheaReportHwError+258
fffff802`4bcb2ba8 eb70 jmp nt!WheaReportHwError+0x2ca (fffff802`4bcb2c1a)
FAULT_INSTR_CODE: 418d70eb
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!WheaReportHwError+258
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5b1f16e0
IMAGE_VERSION: 10.0.14393.2339
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 258
FAILURE_BUCKET_ID: 0x80_nt!WheaReportHwError
BUCKET_ID: 0x80_nt!WheaReportHwError
PRIMARY_PROBLEM_CLASS: 0x80_nt!WheaReportHwError
TARGET_TIME: 2018-07-11T08:04:50.000Z
OSBUILD: 14393
OSSERVICEPACK: 2339
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 Server TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-06-12 01:42:08
BUILDDATESTAMP_STR: 180611-1502
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.2339.amd64fre.rs1_release_inmarket.180611-1502
ANALYSIS_SESSION_ELAPSED_TIME: 63b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x80_nt!wheareporthwerror
FAILURE_ID_HASH: {d5f8e3c5-00d9-a505-9cff-8d968ebc3f39}

Followup: MachineOwner
---------

And these are the logs from the Memory.dmp file;

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
Page e80 not present in the dump file. Type ".hh dbgerr004" for details
Page e80 not present in the dump file. Type ".hh dbgerr004" for details
Page e80 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 14393.2363.amd64fre.rs1_release.180625-1741
SYSTEM_MANUFACTURER: HP
SYSTEM_PRODUCT_NAME: ProLiant MicroServer Gen8
SYSTEM_SKU: 712317-421
BIOS_VENDOR: HP
BIOS_VERSION: J06
BIOS_DATE: 07/16/2015
DUMP_TYPE: 1
BUGCHECK_P1: 4f4454
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 2
CPU_MHZ: 8f7
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1C'00000000 (cache) 1C'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x80
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: BK07744
ANALYSIS_SESSION_TIME: 07-12-2018 11:28:51.0325
ANALYSIS_VERSION: 10.0.17134.12 amd64fre
LAST_CONTROL_TRANSFER: from fffff80008a7121e to fffff800083769b0
STACK_TEXT:
fffff800`09dddc08 fffff800`08a7121e : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff800`09dddc10 fffff800`08448ba8 : ffff9b87`04ac4968 fffff800`08a88a70 fffff800`08a88a70 00000000`00000001 : hal!HalBugCheckSystem+0x7e
fffff800`09dddc50 fffff800`08a721ee : fffff800`000006c0 fffff800`085d7670 fffff800`09dddd30 00000000`00000000 : nt!WheaReportHwError+0x258
fffff800`09dddcb0 fffff800`0829533a : 00000000`00000001 00000000`00000000 00000002`b2b2dcd8 fffff800`082957e8 : hal!HalHandleNMI+0xfe
fffff800`09dddce0 fffff800`08381342 : 00000000`00000001 fffff800`09dddef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x106
fffff800`09dddd30 fffff800`08381140 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff800`09ddde70 fffff80b`a9ce3e1e : fffff80b`a9ce1323 00000000`00000000 ffff9b87`04a4eb10 fffff800`0855e180 : nt!KiNmiInterrupt+0x1c0
fffff800`09dcb948 fffff80b`a9ce1323 : 00000000`00000000 ffff9b87`04a4eb10 fffff800`0855e180 00000000`00000000 : intelppm!MWaitIdle+0x2e
fffff800`09dcb950 fffff800`082719ac : 00000000`00000000 00000b04`0175c2a7 00000000`00000000 00000000`00000003 : intelppm!AcpiCStateIdleExecute+0x23
fffff800`09dcb980 fffff800`08270b3a : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0xcbc
fffff800`09dcbc00 fffff800`08379fec : 00000000`00050b05 fffff800`0855e180 fffff800`085d9940 ffff9b87`06c0f540 : nt!PoIdle+0x33a
fffff800`09dcbd60 00000000`00000000 : fffff800`09dcc000 fffff800`09dc6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
THREAD_SHA1_HASH_MOD_FUNC: de588e0752e3f5f3e9b60d5dc1178386861b718c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 430c09a16fcf7b7520d28d0461798b1073a26793
THREAD_SHA1_HASH_MOD: 660bcac133d31e5273140ad75d80b5b0294f8e45
FOLLOWUP_IP:
intelppm!MWaitIdle+2e
fffff80b`a9ce3e1e 4585c0 test r8d,r8d
FAULT_INSTR_CODE: 74c08545
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: intelppm!MWaitIdle+2e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5ae3f7ea
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 2e
FAILURE_BUCKET_ID: 0x80_intelppm!MWaitIdle
BUCKET_ID: 0x80_intelppm!MWaitIdle
PRIMARY_PROBLEM_CLASS: 0x80_intelppm!MWaitIdle
TARGET_TIME: 2018-07-12T09:18:15.000Z
OSBUILD: 14393
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 Server TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-06-26 04:06:53
BUILDDATESTAMP_STR: 180625-1741
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.2363.amd64fre.rs1_release.180625-1741
ANALYSIS_SESSION_ELAPSED_TIME: 658
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x80_intelppm!mwaitidle
FAILURE_ID_HASH: {4d921e65-7fcd-f5e4-043a-b02bdcd10b07}

Followup: MachineOwner
---------

I am so stuck, please can anyone help?

Thank you

2 REPLIES 2
SB6
HPE Pro

Re: HP Proliant Microserver Gen8 - G1610T 2.3ghz Keeps Rebooting

To narrow down this issue, advisable action would be to bring server to minimum configuration i.e. like Just 1 DIMM, no PCIe cards (if installed).

Try NVRAM clear further to see if makes any difference, if you are comfortable with same.

http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03783380-6.pdf

>> Location System Maintenance Switch, power off server, disconnect power cord, on System Maintenance switch turn on SW6 and then power on server

>> Wait for 2-3 minutes and power of server again and disconnect power cord and turn SW6 back to off and power on server.

If this does not help to narrow down this issue, I would advise to engage HPE support with AHS logs from iLo to further diagnose on this issue.

https://support.hpe.com/hpesc/public/home

Thank You!

I am a HPE employee

_________________________________________

Was the post useful? Click on the white KUDOS! Thumb below.  Kudos is a way of saying thank you to a post.

 


I am a HPE Employee

Accept or Kudo

parnassus
Honored Contributor

Re: HP Proliant Microserver Gen8 - G1610T 2.3ghz Keeps Rebooting

Just curious: were HPE iLO and System ROM (BIOS) firmwares updated to latest available for HPE ProLiant Microserver Gen 8? ...then is the OS used among those listed as supported?

I'm not an HPE Employee
Kudos and Accepted Solution banner