BSOD: Excel, 1 VM running, Google Chrome Open, and XBMC playing movie

nmprodan · 23 Jan 2014

Received a BSOD using Excel, 1 VM running, Google Chrome Open and streaming music, and XBMC playing a movie.

This is the second time I've received it today, first time didn't have music streaming. Haven't really had problems, but may have been set off by a recent MS update.

koolkat77 · 24 Jan 2014

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_23-01-2014 (1)\SF_23-01-2014\012314-30997-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`032476d0
Debug session time: Fri Jan 24 01:14:48.701 2014 (UTC + 6:00)
System Uptime: 1 days 2:32:32.386
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa801b602028, be000000, 800400}

Probably caused by : GenuineIntel

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa801b602028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  CrashPlanServi

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`0484fa98 fffff800`035fba3b : 00000000`00000124 00000000`00000000 fffffa80`1b602028 00000000`be000000 : nt!KeBugCheckEx
fffff800`0484faa0 fffff800`03190463 : 00000000`00000001 fffffa80`1b605a60 00000000`00000000 fffffa80`1b605ab0 : hal!HalBugCheckSystem+0x1e3
fffff800`0484fae0 fffff800`035fb700 : 00000000`00000728 fffffa80`1b605a60 fffff800`0484fe70 fffff800`0484fe00 : nt!WheaReportHwError+0x263
fffff800`0484fb40 fffff800`035fb052 : fffffa80`1b605a60 fffff800`0484fe70 fffffa80`1b605a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`0484fc90 fffff800`035faf0d : 00000000`00000008 00000000`00000001 fffff800`0484fef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`0484fcd0 fffff800`035eee88 : 00000000`dae0de88 00000000`00000069 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`0484fd00 fffff800`030784ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`0484fd30 fffff800`03078313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`0484fe70 00000000`01545943 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0948e490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1545943


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

nmprodan · 25 Jan 2014

Thanks for the help and feedback.