Unable to understand the memory dump of Windows server 2012

%3CLINGO-SUB%20id%3D%22lingo-sub-210477%22%20slang%3D%22en-US%22%3EUnable%20to%20understand%20the%20memory%20dump%20of%20Windows%20server%202012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-210477%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20an%20VM%20and%20it%20was%20unresponsive%20so%20had%20an%20memory%20dump%20but%20unable%20to%20understand%20the%20dump%20so%20someone%20can%20help%20me%20on%20this%20please%26nbsp%3B%3C%2FP%3E%3CP%3E......%3CBR%20%2F%3E*******************************************************************************%3CBR%20%2F%3E*%20*%3CBR%20%2F%3E*%20Bugcheck%20Analysis%20*%3CBR%20%2F%3E*%20*%3CBR%20%2F%3E*******************************************************************************%3C%2FP%3E%3CP%3EUse%20!analyze%20-v%20to%20get%20detailed%20debugging%20information.%3C%2FP%3E%3CP%3EBugCheck%2080%2C%20%7B4f4454%2C%200%2C%200%2C%200%7D%3C%2FP%3E%3CP%3EProbably%20caused%20by%20%3A%20ntkrnlmp.exe%20(%20nt!PpmIdleDefaultExecute%2Ba%20)%3C%2FP%3E%3CP%3EFollowup%3A%20MachineOwner%3CBR%20%2F%3E---------%3C%2FP%3E%3CP%3E0%3A%20kd%26gt%3B%20!analyze%20-v%3CBR%20%2F%3E*******************************************************************************%3CBR%20%2F%3E*%20*%3CBR%20%2F%3E*%20Bugcheck%20Analysis%20*%3CBR%20%2F%3E*%20*%3CBR%20%2F%3E*******************************************************************************%3C%2FP%3E%3CP%3ENMI_HARDWARE_FAILURE%20(80)%3CBR%20%2F%3EThis%20is%20typically%20due%20to%20a%20hardware%20malfunction.%20The%20hardware%20supplier%20should%3CBR%20%2F%3Ebe%20called.%3CBR%20%2F%3EArguments%3A%3CBR%20%2F%3EArg1%3A%2000000000004f4454%3CBR%20%2F%3EArg2%3A%200000000000000000%3CBR%20%2F%3EArg3%3A%200000000000000000%3CBR%20%2F%3EArg4%3A%200000000000000000%3C%2FP%3E%3CP%3EDebugging%20Details%3A%3CBR%20%2F%3E------------------%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EDEFAULT_BUCKET_ID%3A%20WIN8_DRIVER_FAULT%3C%2FP%3E%3CP%3EBUGCHECK_STR%3A%200x80%3C%2FP%3E%3CP%3EPROCESS_NAME%3A%20System%3C%2FP%3E%3CP%3ECURRENT_IRQL%3A%200%3C%2FP%3E%3CP%3EANALYSIS_VERSION%3A%206.3.9600.16384%20(debuggers(dbg).130821-1623)%20amd64fre%3C%2FP%3E%3CP%3EDPC_STACK_BASE%3A%20FFFFF8004FF27FB0%3C%2FP%3E%3CP%3ELAST_CONTROL_TRANSFER%3A%20from%20fffff8004e5b641e%20to%20fffff8004e42681f%3C%2FP%3E%3CP%3ESTACK_TEXT%3A%3CBR%20%2F%3Efffff800%604ff209d8%20fffff800%604e5b641e%20%3A%20ffffe001%60de358250%20ffffe001%60de358010%2000000000%6000000000%20fffff800%604e763180%20%3A%20hal!HalProcessorIdle%2B0xf%3CBR%20%2F%3Efffff800%604ff209e0%20fffff800%604e582cc3%20%3A%20fffff800%604e763180%20fffff800%604ff20a00%2000000000%6000000000%20ffffe001%60de358010%20%3A%20nt!PpmIdleDefaultExecute%2B0xa%3CBR%20%2F%3Efffff800%604ff20a10%20fffff800%604e4c3dd6%20%3A%20fffff800%604e763180%20fffff800%604ff20b4c%20fffff800%604ff20b50%20fffff800%604ff20b58%20%3A%20nt!PpmIdleExecuteTransition%2B0x3f3%3CBR%20%2F%3Efffff800%604ff20b10%20fffff800%604e5d40fc%20%3A%20fffff800%604e763180%20fffff800%604e763180%20fffff800%604e7caa00%2000000b14%6000000000%20%3A%20nt!PoIdle%2B0x2f6%3CBR%20%2F%3Efffff800%604ff20c60%2000000000%6000000000%20%3A%20fffff800%604ff21000%20fffff800%604ff1b000%2000000000%6000000000%2000000000%6000000000%20%3A%20nt!KiIdleLoop%2B0x2c%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ESTACK_COMMAND%3A%20kb%3C%2FP%3E%3CP%3EFOLLOWUP_IP%3A%3CBR%20%2F%3Ent!PpmIdleDefaultExecute%2Ba%3CBR%20%2F%3Efffff800%604e5b641e%2033c0%20xor%20eax%2Ceax%3C%2FP%3E%3CP%3ESYMBOL_STACK_INDEX%3A%201%3C%2FP%3E%3CP%3ESYMBOL_NAME%3A%20nt!PpmIdleDefaultExecute%2Ba%3C%2FP%3E%3CP%3EFOLLOWUP_NAME%3A%20MachineOwner%3C%2FP%3E%3CP%3EMODULE_NAME%3A%20nt%3C%2FP%3E%3CP%3EIMAGE_NAME%3A%20ntkrnlmp.exe%3C%2FP%3E%3CP%3EDEBUG_FLR_IMAGE_TIMESTAMP%3A%205accf215%3C%2FP%3E%3CP%3EBUCKET_ID_FUNC_OFFSET%3A%20a%3C%2FP%3E%3CP%3EFAILURE_BUCKET_ID%3A%200x80_nt!PpmIdleDefaultExecute%3C%2FP%3E%3CP%3EBUCKET_ID%3A%200x80_nt!PpmIdleDefaultExecute%3C%2FP%3E%3CP%3EANALYSIS_SOURCE%3A%20KM%3C%2FP%3E%3CP%3EFAILURE_ID_HASH_STRING%3A%20km%3A0x80_nt!ppmidledefaultexecute%3C%2FP%3E%3CP%3EFAILURE_ID_HASH%3A%20%7B58acf3bd-67a3-5c4a-6586-345c82c9c5d7%7D%3C%2FP%3E%3CP%3EFollowup%3A%20MachineOwner%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-210477%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-210574%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20understand%20the%20memory%20dump%20of%20Windows%20server%202012%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-210574%22%20slang%3D%22en-US%22%3E%3CP%3EThese%20ones%20might%20help.%3C%2FP%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2750146%2Fnmi-hardware-failure-error-when-an-nmi-is-triggered-on-windows-8-and-w%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2750146%2Fnmi-hardware-failure-error-when-an-nmi-is-triggered-on-windows-8-and-w%3C%2FA%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fes-cl%2Fhelp%2F969556%2Fcreating-or-starting-hyper-v-virtual-machines-may-fail-with-error-0x80%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fes-cl%2Fhelp%2F969556%2Fcreating-or-starting-hyper-v-virtual-machines-may-fail-with-error-0x80%3C%2FA%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.hpe.com%2Fhpsc%2Fdoc%2Fpublic%2Fdisplay%3FdocId%3Dmmr_kc-0128485%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.hpe.com%2Fhpsc%2Fdoc%2Fpublic%2Fdisplay%3FdocId%3Dmmr_kc-0128485%3C%2FA%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I have an VM and it was unresponsive so had an memory dump but unable to understand the dump so someone can help me on this please 

......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 80, {4f4454, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PpmIdleDefaultExecute+a )

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

0: 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:
------------------


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x80

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE: FFFFF8004FF27FB0

LAST_CONTROL_TRANSFER: from fffff8004e5b641e to fffff8004e42681f

STACK_TEXT:
fffff800`4ff209d8 fffff800`4e5b641e : ffffe001`de358250 ffffe001`de358010 00000000`00000000 fffff800`4e763180 : hal!HalProcessorIdle+0xf
fffff800`4ff209e0 fffff800`4e582cc3 : fffff800`4e763180 fffff800`4ff20a00 00000000`00000000 ffffe001`de358010 : nt!PpmIdleDefaultExecute+0xa
fffff800`4ff20a10 fffff800`4e4c3dd6 : fffff800`4e763180 fffff800`4ff20b4c fffff800`4ff20b50 fffff800`4ff20b58 : nt!PpmIdleExecuteTransition+0x3f3
fffff800`4ff20b10 fffff800`4e5d40fc : fffff800`4e763180 fffff800`4e763180 fffff800`4e7caa00 00000b14`00000000 : nt!PoIdle+0x2f6
fffff800`4ff20c60 00000000`00000000 : fffff800`4ff21000 fffff800`4ff1b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PpmIdleDefaultExecute+a
fffff800`4e5b641e 33c0 xor eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PpmIdleDefaultExecute+a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5accf215

BUCKET_ID_FUNC_OFFSET: a

FAILURE_BUCKET_ID: 0x80_nt!PpmIdleDefaultExecute

BUCKET_ID: 0x80_nt!PpmIdleDefaultExecute

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x80_nt!ppmidledefaultexecute

FAILURE_ID_HASH: {58acf3bd-67a3-5c4a-6586-345c82c9c5d7}

Followup: MachineOwner

1 Reply