BSOD after random, different error messages.

[Lizhong]

Some times I do not receive any error message. Sometimes I get "uncorrectable hardware error". This has been going on for a while but the crashes happen every two days or so. It is very annoying so I would be grateful for any help.

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
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:
[COLOR=SeaGreen]Arg1: 0000000000000000, Machine Check Exception[/COLOR]
Arg2: fffffa800966f028, 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:  dwm.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009bbb58 fffff800`03028a3b : 00000000`00000124 00000000`00000000 fffffa80`0966f028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009bbb60 fffff800`031ebb13 : 00000000`00000001 fffffa80`095c1660 00000000`00000000 fffffa80`095c16b0 : hal!HalBugCheckSystem+0x1e3
fffff880`009bbba0 fffff800`03028700 : 00000000`00000728 fffffa80`095c1660 fffff880`009bbf30 fffff880`009bbf00 : nt!WheaReportHwError+0x263
fffff880`009bbc00 fffff800`03028052 : fffffa80`095c1660 fffff880`009bbf30 fffffa80`095c1660 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009bbd50 fffff800`03027f0d : 00000000`00000008 00000000`00000001 fffff880`009bbfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009bbd90 fffff800`0301be88 : 00000000`041a0c70 00000000`040bf700 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009bbdc0 fffff800`030dc8ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009bbdf0 fffff800`030dc713 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009bbf30 000007fe`f55e64bc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`040bf458 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f55e64bc


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 a hardware caused BSOD; but which hardware is actually failing is difficult to determine. Better you follow the guide: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html