New
#1
My dump file
Hello, im very new to this so if i make some mistakes , sorry for that.
Sinds a short time i noticed a system problem and for the first time i saw a blue screen. it robooted and thats it... At some moments i notice that the processor suddenly goes from 10 to 40%. usually after that and when i reboot it shows the message i can see the dump file, i could never see that untill i installed the driverkit.. How to open DMP files in Windows 7? | Windows 7 Themes
My system is a i5, 64 bit, 8GB memory, 650 @320ghz
maybe 1 year old.
Below is the dump, who can tell me whats wrong ?
*******************************************************************************
* *
* 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: fffffa8007eba028, 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: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff880`009efa58 fffff800`03219a3b : 00000000`00000124 00000000`00000000 fffffa80`07eba028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009efa60 fffff800`033dd513 : 00000000`00000001 fffffa80`07ebbea0 00000000`00000000 fffffa80`07ebbef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009efaa0 fffff800`03219700 : 00000000`00000728 fffffa80`07ebbea0 fffff880`009efe30 fffff880`009efe00 : nt!WheaReportHwError+0x263
fffff880`009efb00 fffff800`03219052 : fffffa80`07ebbea0 fffff880`009efe30 fffffa80`07ebbea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009efc50 fffff800`03218f0d : 00000000`00000004 00000000`00000001 fffff880`009efeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009efc90 fffff800`0320ce88 : 00000000`00000056 fffffa80`09b733d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009efcc0 fffff800`032cb52c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009efcf0 fffff800`032cb393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009efe30 fffff880`04d5ec5e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`04b2d6e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 1394ohci!IoWorkers::StopTransmitContext+0x6a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware ( lmvm hardware )
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
---------