BSOD BBcode 124

My computer is

Asus p5k-e
E2160@3.0
gigabyte Gts 450 OC

When I play game maybe 30-45' computer restart and said bbcode 124

here my dump file

It's happening 2days ago until now :)

newbieIT said:

My computer is

Asus p5k-e
E2160@3.0
gigabyte Gts 450 OC

When I play game maybe 30-45' computer restart and said bbcode 124

here my dump file

It's happening 2days ago until now :)

Your crash was caused by hardware

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

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\051011-19172-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e56000 PsLoadedModuleList = 0xfffff800`03093e50
Debug session time: Mon May  9 18:10:57.094 2011 (GMT-4)
System Uptime: 0 days 0:00:10.717
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, fffffa8004b906a8, 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: fffffa8004b906a8, 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`035f66f0 fffff800`03110a99 : fffffa80`04b90680 fffffa80`03a07680 00000000`00000006 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`035f6c10 fffff800`02ff2677 : fffffa80`04b90680 fffff800`0306b5f8 fffffa80`03a07680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`035f6c40 fffff800`02f5ac45 : fffff800`030cd360 fffffa80`04b72718 fffffa80`04b72710 fffffa80`03a07680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`035f6c80 fffff800`02ed3961 : fffff880`010e1e00 fffff800`02f5ac20 fffffa80`03a07680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`035f6cb0 fffff800`031697c6 : 00000000`01e490c0 fffffa80`03a07680 00000000`00000080 fffffa80`039f4740 : nt!ExpWorkerThread+0x111
fffff880`035f6d40 fffff800`02ea4c26 : fffff880`009e9180 fffffa80`03a07680 fffff880`009f3f40 00000001`036590c0 : nt!PspSystemThreadStartup+0x5a
fffff880`035f6d80 00000000`00000000 : fffff880`035f7000 fffff880`035f1000 fffff880`03d957c0 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_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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