Windows 7 - Bsod: 0x00000124 Dump included.

Hi.. recently brought a new pc with the following specs:
920 @ 3.8 ghz
Asus P6TD Deluxe
6 GB DDR 1600 Corsair
Asus Xonar D2
ATI 5870.

but been having a bsod of 0x00000124..well i say bsod, screen goes grey/black lines in middle of WoW(found the error code via bluescreenview, presuming after a google search that found you guys thats it the overclock not being as stable as i thought? have reverted to stock for now, but still would like some inport, have also e-mailed the company i brought it off, but as it's the weekend thought it'd give this a shot dump is below.
103009-16536-01.rar

Hi carlow and welcome to sevenforums

this dump was caused by hardware. either an incompatible device or bad driver.

I assume you are not

Over clocking

Running a RAID

download and run an app like memtestgx86 preferably overnight

Update the bios,

run a system file check byt typing cmd in search>right click and run as admin.
type sfc /scannow

let us know if this doesnt help


Ken


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-16536-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02c9fe50
Debug session time: Fri Oct 30 16:42:16.643 2009 (GMT-4)
System Uptime: 0 days 0:00:09.502
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, fffffa8006eaf038, 0, 0}

Probably caused by : hardware

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

4: 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: fffffa8006eaf038, 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_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0357e6f0 fffff800`02d1ca89 : fffffa80`06eaf010 fffffa80`05517b60 00000000`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0357ec10 fffff800`02bfe547 : fffffa80`06eaf010 fffff800`02c775f8 fffffa80`05517b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0357ec40 fffff800`02b66b95 : fffff800`02cd9360 fffffa80`06e97188 fffffa80`06e97180 fffffa80`05517b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0357ec80 fffff800`02ae1161 : fffff880`0104ee00 fffff800`02b66b70 fffffa80`05517b60 fffffa80`05517b60 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0357ecb0 fffff800`02d77166 : 1cfa1cfa`58f958f9 fffffa80`05517b60 00000000`00000080 fffffa80`054fc040 : nt!ExpWorkerThread+0x111
fffff880`0357ed40 fffff800`02ab2486 : fffff880`03386180 fffffa80`05517b60 fffff880`033910c0 54505450`4e194e19 : nt!PspSystemThreadStartup+0x5a
fffff880`0357ed80 00000000`00000000 : fffff880`0357f000 fffff880`03579000 fffff880`03065540 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_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

at the time of the dumb it was overclocked to 3.8ghz, since reverted to stock. and yes no raid. and the company i brought it from already stress tested/mem test(results where screen shots on my desktop ).

and the system scan showed no problems, although i did notice that Xonar 32 bit driver was instailled, have just instailled 64 (least i think it was 32, had (32) in the app name.

least i'm trying to..won't go in..please connecting Asus Xonar D2 , rolled back to drivers it was shipped with, no longer has (32) in name tho.

did a short memtest when i went to watch footy, it resulted in 30+ errors. going to RMA it on monday.(as said was brought Pre built with OC).