New
#1
Random BSODs, Machine Check Exception
I am aware that MCEs are usually hardware related. I just want to make sure it isn't driver related before I get an exchange. I have my error dump file right here if anyone can check it out and tell me what's up. I really appreciate any help.
Code:Simple: Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Only kernel address space is available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 8 Kernel Version 10240 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 10240.16412.amd64fre.th1.150729-1800 Machine Name: Kernel base = 0xfffff800`92c89000 PsLoadedModuleList = 0xfffff800`92fae030 Debug session time: Wed Aug 5 20:29:32.058 2015 (UTC - 5:00) System Uptime: 0 days 6:58:04.739 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................ Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9C, {0, ffffd000d92fc860, 0, 0} Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 ) Followup: MachineOwner Advanced: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MACHINE_CHECK_EXCEPTION (9c) A fatal Machine Check Exception has occurred. KeBugCheckEx parameters; x86 Processors If the processor has ONLY MCE feature available (For example Intel Pentium), the parameters are: 1 - Low 32 bits of P5_MC_TYPE MSR 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of P5_MC_ADDR MSR 4 - Low 32 bits of P5_MC_ADDR MSR If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are: 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error IA64 Processors 1 - Bugcheck Type 1 - MCA_ASSERT 2 - MCA_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing MCA. 3 - MCA_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 4 - MCA_FATAL FW reported a fatal MCA. 5 - MCA_NONFATAL SAL reported a recoverable MCA and we don't support currently support recovery or SAL generated an MCA and then couldn't produce an error record. 0xB - INIT_ASSERT 0xC - INIT_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 0xD - INIT_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 0xE - INIT_FATAL Not used. 2 - Address of log 3 - Size of log 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO AMD64 Processors 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arguments: Arg1: 0000000000000000 Arg2: ffffd000d92fc860 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x9C_GenuineIntel DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre LAST_CONTROL_TRANSFER: from fffff80092c4dee1 to fffff80092dd6220 STACK_TEXT: ffffd000`d92fc828 fffff800`92c4dee1 : 00000000`0000009c 00000000`00000000 ffffd000`d92fc860 00000000`00000000 : nt!KeBugCheckEx ffffd000`d92fc830 fffff800`92c4e2a8 : 00000000`00000008 ffffd000`d92fcb30 00000000`00000000 00000000`00000008 : hal!HalpMcaReportError+0xf5 ffffd000`d92fc980 fffff800`92c4e450 : ffffe000`440b6d50 ffffd000`d92fcbb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xb0 ffffd000`d92fc9b0 fffff800`92ddfb7b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 ffffd000`d92fc9e0 fffff800`92ddf931 : 00000000`00000000 fffff800`92ddf8b0 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b ffffd000`d92fcb20 fffff801`c7772778 : fffff801`c7771330 00000000`00000046 00000000`00000000 ffffe000`4aa9b9e0 : nt!KiMcheckAbort+0x171 ffffd000`d931c858 fffff801`c7771330 : 00000000`00000046 00000000`00000000 ffffe000`4aa9b9e0 ffffd000`d92f2180 : intelppm!MWaitIdle+0x18 ffffd000`d931c860 fffff800`92c95a02 : 00000000`00000000 ffffe000`00000001 00000000`00000000 ffffe000`49803300 : intelppm!AcpiCStateIdleExecute+0x20 ffffd000`d931c890 fffff800`92c9526d : 00000000`00000003 00000000`00000002 ffffe000`498033e0 00000000`00000000 : nt!PpmIdleExecuteTransition+0x5e2 ffffd000`d931cb00 fffff800`92dd8f4c : ffffd000`d92f2180 ffffd000`d92f2180 00000000`00000000 ffffd000`d92fecc0 : nt!PoIdle+0x33d ffffd000`d931cc60 00000000`00000000 : ffffd000`d931d000 ffffd000`d9317000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: intelppm!MWaitIdle+18 fffff801`c7772778 c3 ret SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: intelppm!MWaitIdle+18 FOLLOWUP_NAME: MachineOwner MODULE_NAME: intelppm IMAGE_NAME: intelppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 559f383b BUCKET_ID_FUNC_OFFSET: 18 FAILURE_BUCKET_ID: 0x9C_GenuineIntel_intelppm!MWaitIdle BUCKET_ID: 0x9C_GenuineIntel_intelppm!MWaitIdle ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_intelppm!mwaitidle FAILURE_ID_HASH: {b437bf01-d2c2-2e2f-fa19-a64dea7afbde} Followup: MachineOwner
Once again. Thanks for any help!
Last edited by robonerd; 10 Aug 2015 at 22:29. Reason: Falsely marked solved