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


Loading Dump File [E:\dumps\062814-5718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*E:\Symbols*http://msdl.microsoft.com/download/symbols

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*E:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*E:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: srv*E:\Symbols*http://msdl.microsoft.com/download/symbols
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff803`d8c0d000 PsLoadedModuleList = 0xfffff803`d8ed72d0
Debug session time: Sat Jun 28 22:49:24.286 2014 (UTC + 3:00)
System Uptime: 1 days 5:07:26.878
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe001e5ed2028, bf800000, 124}

Probably caused by : GenuineIntel

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

1: kd> kd: Reading initial command '.locale .1251; !analyze -v; q'
Locale: Russian_Russia.1251
*******************************************************************************
*                                                                             *
*                        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: ffffe001e5ed2028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

STACK_TEXT:  
ffffd000`24525df8 fffff803`d93cd203 : 00000000`00000124 00000000`00000000 ffffe001`e5ed2028 00000000`bf800000 : nt!KeBugCheckEx
ffffd000`24525e00 fffff803`d8dcd825 : 00000000`00000001 ffffe001`e44af1a0 ffffe001`e44af1a0 ffffe001`e5ed2028 : hal!HalBugCheckSystem+0xcf
ffffd000`24525e40 fffff803`d93cd68c : 00000000`00000728 00000000`00000001 ffffd000`24526230 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`24525ea0 fffff803`d93cda11 : ffffe001`00000010 ffffe001`e44af1a0 ffffd000`24526048 ffffe001`e44af1a0 : hal!HalpMcaReportError+0x50
ffffd000`24525ff0 fffff803`d93cd8f4 : ffffe001`e44aebf0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`24526040 fffff803`d93cdb4e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`24526080 fffff803`d93cdcd7 : ffffe001`e44aebf0 ffffd000`245262b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`245260b0 fffff803`d8d6babb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`245260e0 fffff803`d8d6b871 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`24526220 fffff800`12047922 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd000`21bec710 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x9a2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

quit: