Here are some minidumps that I have from the crashing... hopefully they can shed some light on this situation
Hi Moshee
Sorry this took so long. I just didnt see this one. Your dmps are identical the cause is hardware
I would
Update all the drivers Bios, chipset, video, wifi, etc
download and run memtestx86 for several hours at least
If you are Overclocking stop
If you have a raid upload its driver
run a system file check to verify and fux system files.
type cmd in search>right click and run as admin>sfc /scannow
let us know the results
Hope this helps
Ken J++
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\103009-29250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
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`02e55000 PsLoadedModuleList = 0xfffff800`03092e50
Debug session time: Sat Oct 31 01:42:47.783 2009 (GMT-5)
System Uptime: 0 days 0:00:09.469
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80055f56c8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
1: 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: fffffa80055f56c8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`02fc46f0 fffff800`0310fa89 : fffffa80`055f56a0 fffffa80`03a1b040 00000000`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc4c10 fffff800`02ff1547 : fffffa80`055f56a0 fffff800`0306a5f8 fffffa80`03a1b040 00000000`00000282 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc4c40 fffff800`02f59b95 : fffff800`030cc360 fffffa80`055f0688 fffffa80`055f0680 fffffa80`03a1b040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc4c80 fffff800`02ed4161 : fffff880`00e3be00 fffff800`02f59b70 fffffa80`03a1b040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc4cb0 fffff800`0316a166 : 00000560`00000000 fffffa80`03a1b040 00000000`00000080 fffffa80`03a099e0 : nt!ExpWorkerThread+0x111
fffff880`02fc4d40 fffff800`02ea5486 : fffff880`02d64180 fffffa80`03a1b040 fffff880`02d6efc0 00000560`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc4d80 00000000`00000000 : fffff880`02fc5000 fffff880`02fbf000 fffff880`02fc41d0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------