It's a 0x124 error that you could read about here on how to attempt to alleviate them. Most important thing is to read about the overclocking, if you are.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Temp\Rar$DI00.531\111309-21812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82855000 PsLoadedModuleList = 0x82994570
Debug session time: Fri Nov 13 15:36:04.125 2009 (GMT-5)
System Uptime: 0 days 0:00:09.968
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, 861498fc, 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: 00000000, Machine Check Exception
Arg2: 861498fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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:
8d452cc4 829181c5 861498e0 829b2f88 829b2f80 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8d452ce4 82918fe1 829b2f80 861498e0 829b2fb0 nt!WheapProcessWorkQueueItem+0x56
8d452d00 828b0043 829b2f80 00000000 850ba020 nt!WheapWorkQueueWorkerRoutine+0x1f
8d452d50 82a3cd16 00000001 b1e38d40 00000000 nt!ExpWorkerThread+0x10d
8d452d90 828de159 828aff36 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_PRV
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_PRV
Followup: MachineOwner
---------