Hi,
Since 4 months we have a Windows 2016 Server with S1200SP Systemboard running smooth without any problems:
System Information
Remote Management Module key : Installed
Device (BMC) Available : Yes
BMC FW Build Time : 2017-09-11 15:42:03
BIOS ID : S1200SP.86B.03.01.0026.092720170729
BMC FW Rev : 1.10.10925
Boot FW Rev : 1.05
SDR Package Version : SDR Package 0.26
Mgmt Engine (ME) FW Rev : 04.01.04.054
but the last two day we had unexpected Shutdowns, but we have nothing changed (except: Windows Updates!)
Windows Eventlog:
BMC:
Memory.dmp:
icrosoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Temp\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 14393.2007.amd64fre.rs1_release.171231-1800
Machine Name:
Kernel base = 0xfffff802`18007000 PsLoadedModuleList = 0xfffff802`1830f1a0
Debug session time: Tue Feb 13 10:03:59.159 2018 (UTC + 1:00)
System Uptime: 0 days 18:18:50.499
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 80, {4f4454, 0, 0, 0}
Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* 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:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 14393.2007.amd64fre.rs1_release.171231-1800
SYSTEM_MANUFACTURER: Intel Corporation
SYSTEM_PRODUCT_NAME: S1200SP
SYSTEM_SKU: SKU Number
SYSTEM_VERSION: ....................
BIOS_VENDOR: Intel Corporation
BIOS_VERSION: S1200SP.86B.03.01.0026.092720170729
BIOS_DATE: 09/27/2017
BASEBOARD_MANUFACTURER: Intel Corporation
BASEBOARD_PRODUCT: S1200SP
BASEBOARD_VERSION: H57534-250
DUMP_TYPE: 1
BUGCHECK_P1: 4f4454
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 8
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: BA'00000000 (cache) BA'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x80
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: xx
ANALYSIS_SESSION_TIME: 02-13-2018 16:25:58.0583
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff8021885f23e to fffff802181626e0
STACK_TEXT:
ffff8580`5dccee08 fffff802`1885f23e : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8580`5dccee10 fffff802`18236b7c : ffffab8d`fc48b968 fffff802`18876a70 fffff802`18876a70 00000000`00000001 : hal!HalBugCheckSystem+0x7e
ffff8580`5dccee50 fffff802`1886020e : fffff802`000006c0 fffff802`183c563c ffff8580`5dccef30 fffff802`180817f8 : nt!WheaReportHwError+0x258
ffff8580`5dcceeb0 fffff802`1808111a : ffff8580`5dcc1180 00000000`00000000 00000035`f7981a91 fffff802`180815c8 : hal!HalHandleNMI+0xfe
ffff8580`5dcceee0 fffff802`1816df02 : ffff8580`5dcc1180 ffff8580`5dccf0f0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x106
ffff8580`5dccef30 fffff802`1816dcc2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffff8580`5dccf070 fffff804`b3f51348 : fffff804`b3f51320 ffffab8d`fc8783d0 ffffab8d`fc4128d0 0000d7e0`07c7bf8c : nt!KiNmiInterrupt+0x482
ffff8580`5dcf27d8 fffff804`b3f51320 : ffffab8d`fc8783d0 ffffab8d`fc4128d0 0000d7e0`07c7bf8c 00000000`00000000 : intelppm!MWaitIdle+0x18
ffff8580`5dcf27e0 fffff802`1805d71c : 00000000`00000000 0000d7e0`0000001b 00000035`f7981a91 00000000`00000020 : intelppm!AcpiCStateIdleExecute+0x20
ffff8580`5dcf2810 fffff802`1805c8ca : fffff802`1805b150 00406299`00406299 fffff802`18007000 00406299`00406299 : nt!PpmIdleExecuteTransition+0xc9c
ffff8580`5dcf2a80 fffff802`18165ebc : 00000000`00000000 ffff8580`5dcc1180 ffff8580`5dccf200 ffffab8d`fed4c080 : nt!PoIdle+0x33a
ffff8580`5dcf2be0 00000000`00000000 : ffff8580`5dcf3000 ffff8580`5dcec000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: de588e0752e3f5f3e9b60d5dc1178386861b718c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 971c378bba6c1258bb583b5a27c253ba725bd373
THREAD_SHA1_HASH_MOD: 660bcac133d31e5273140ad75d80b5b0294f8e45
FOLLOWUP_IP:
intelppm!MWaitIdle+18
fffff804`b3f51348 c3 ret
FAULT_INSTR_CODE: ccccccc3
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: intelppm!MWaitIdle+18
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 578997a3
BUCKET_ID_FUNC_OFFSET: 18
FAILURE_BUCKET_ID: 0x80_intelppm!MWaitIdle
BUCKET_ID: 0x80_intelppm!MWaitIdle
PRIMARY_PROBLEM_CLASS: 0x80_intelppm!MWaitIdle
TARGET_TIME: 2018-02-13T09:03:59.000Z
OSBUILD: 14393
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 2
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 LanManNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-01-01 05:38:03
BUILDDATESTAMP_STR: 171231-1800
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.2007.amd64fre.rs1_release.171231-1800
ANALYSIS_SESSION_ELAPSED_TIME: b1e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x80_intelppm!mwaitidle
FAILURE_ID_HASH: {4d921e65-7fcd-f5e4-043a-b02bdcd10b07}
Followup: MachineOwner
---------
Any Ideas? Thanks in advance.