windows 7 64 bit BSOD help reading dmp file :(

I just recently upgraded my pc to windows 7 64bit ultimate running on

i5-750@2.67mhz
4gb ddr3 g.skill 1600-2000mhz @2000mhz
asrock h55m motherboard

i been getting a lot of blue screen could someone help me read my minidump file

i really need help to find out the causes.


thank you!

long said:

I just recently upgraded my pc to windows 7 64bit ultimate running on

i5-750@2.67mhz
4gb ddr3 g.skill 1600-2000mhz @2000mhz
asrock h55m motherboard

i been getting a lot of blue screen could someone help me read my minidump file

i really need help to find out the causes.


thank you!

this crash was caused by hardware. read here for what it means and how to fix. https://www.sevenforums.com/crash-loc...-what-try.html

hope this helps

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\022610-30919-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c50e50
Debug session time: Fri Feb 26 13:38:06.217 2010 (GMT-5)
System Uptime: 0 days 8:30:07.512
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800504e028, fa000000, 400405}

Probably caused by : hardware

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: fffffa800504e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, 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:  firefox.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`0413fa98 fffff800`03002903 : 00000000`00000124 00000000`00000000 fffffa80`0504e028 00000000`fa000000 : nt!KeBugCheckEx
fffff800`0413faa0 fffff800`02b99513 : 00000000`00000001 fffffa80`0504fea0 00000000`00000000 fffffa80`0504fef0 : hal!HalBugCheckSystem+0x1e3
fffff800`0413fae0 fffff800`030025c8 : 00000000`00000728 fffffa80`0504fea0 fffff800`0413fe70 fffff800`0413fe00 : nt!WheaReportHwError+0x263
fffff800`0413fb40 fffff800`03001f1a : fffffa80`0504fea0 fffff800`0413fe70 fffffa80`0504fea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`0413fc90 fffff800`03001dd5 : 00000000`00000004 00000000`00000001 fffff800`0413fef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`0413fcd0 fffff800`02ff5e88 : fffffa80`06d9a450 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`0413fd00 fffff800`02a837ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`0413fd30 fffff800`02a83613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`0413fe70 fffff800`02a9103f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`07b43af0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExEnterPriorityRegionAndAcquireResourceExclusive+0x17


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: 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
---------

is this an intel i5-750 fault then?
BUGCHECK_STR: 0x124_GenuineIntel