Community
cancel
Showing results for 
Search instead for 
Did you mean: 
SDiem
Novice
2,354 Views

Unexpected Shutdown

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 https://msdl.microsoft.com/download/symbols

Symbol search path is: srv*https://msdl.microsoft.com/download/symbols 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_SH...

0 Kudos
14 Replies
idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

Regarding your question, "with Unexpected Shutdown and error log in Windows".

 

This error messages could be related to OS or even Hardware.

 

Could you please provide me with the Processor model number and the number of memory sticks been use and the model of the memory sticks.

 

 

You also stated that the system had been running fine for about 4 months, do remember prior to this problem if there were any software updates, for Example, Windows Security or any application.

 

Or if you install any application on the system.

 

Or if you had added any new hardware to the system.

 

 

If there is anything else we can help please feel free to ask.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

I just will like to follow up and verify if there is anything else I can help.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
SDiem
Novice
382 Views

Hi Henry

Sorry for the delay.

No, we do not install any application or added any new hardware to the system.

In the Windows Update history i don't see any activity before the crashes.

CPU 1 (just one)

Manufacturer : Intel(R) Corporation

Version : Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz

Processor Signature : 0x506E3

Processor Type : Central Processor

Family :Intel(R) Xeon(R)

Speed : 3.6 GHz

Number of Cores : 4

Voltage : 1.1 V

DIMMS:

DIMM_A2 16384 DDR4 2133 Kingston DIMM_A2_AssetTag F01F3027 9965669-017.A00G

DIMM_B2 16384 DDR4 2133 Kingston DIMM_B2_AssetTag E81F3027 9965669-017.A00G

idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

Thank you for the updated information and no worries about the delay. I just wanted to let you know that we are here to help as much as possible.

 

My recommendation at this moment will be to Clear Windows Logs.

 

I hope it does not happens again, but if it does, then we will need to gather the windows logs and the system board logs.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

I just will like to follow up and verify if there is anything else I can help.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

We haven't received any updates from this case

 

For the moment I will close this topic.

 

If necessary we can create a new one and refer to this one.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
SDiem
Novice
382 Views

Hi Henry

Just for your information it happens again today.

idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

Thank you for the print screen on the error message. According to the error code 0x00000080 is related to drivers or hardware.

 

Is recommended to first ensure to flash to latest BIOS on the system board.

 

Also, ensure you have the latest hardware drivers, starting with the chipsets and video.

 

 

Also, I will recommend testing one memory DIMM at a time. Then both again but on different slots. Meaning the A2 move to B2 and B2 to A2.

 

And last but not least, to run a stress test on each of your HDD.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

I just will like to follow up and verify if you were able to flash the BIOS and test one Dimm at a time.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
SDiem
Novice
382 Views

Hi Henry,

we replaced the all DIMMs with new ones. Now we will see if the Problem still occures.

Thanks in advance

idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

Thank you for the update and I am glad you have the opportunity to test different memory sticks.

 

I will await your update.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

I just will like to see if you had the time to test the memory and or if you have encountered any other shutdown.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
idata
Community Manager
382 Views

Hello Siliconbrain,

 

 

We haven't heard any additional updates on the forum. I will proceed on closing it. If you requiere any additional help please don't hesitate to contact us on a new forum.

 

 

Please feel free to ask.

 

 

Best regards,

 

 

Henry A.
SDiem
Novice
382 Views

Hi Henry

we had the problem just every month. so we will see in a couple of weeks if the problem is solved.

but you can close here.

Thanks for your help and support.

Silvan

Reply