Windows 7: Event 7036

Problem, crashed from game after 1-2h playing.

General:
The Application Experience service entered the running state.

Details:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7036</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2011-02-09T22:55:37.991209500Z" />
<EventRecordID>22822</EventRecordID>
<Correlation />
<Execution ProcessID="596" ThreadID="2472" />
<Channel>System</Channel>
<Computer>Tibor-PC</Computer>
<Security />
</System>
- <EventData>
<Data Name="param1">Application Experience</Data>
<Data Name="param2">running</Data>
<Binary>410065004C006F006F006B00750070005300760063002F0034000000</Binary>
</EventData>
</Event>


Here is one minidump from week ago. If someone can check...

Minidump info, plz tell me more

*******************************************************************************
* *
* 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: fffffa8006ce1038, 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`033626f0 fffff800`034d5a89 : fffffa80`06ce1010 fffffa80`05522040 fffffa80`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03362c10 fffff800`033b7547 : fffffa80`06ce1010 fffff800`034305f8 fffffa80`05522040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03362c40 fffff800`0331fb95 : fffff800`03492360 fffffa80`064b7bf8 fffffa80`064b7bf0 fffffa80`05522040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03362c80 fffff800`0329a161 : fffff880`01171e00 fffff800`0331fb70 fffffa80`05522040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03362cb0 fffff800`03530166 : a80aa80a`c3f8c3f8 fffffa80`05522040 00000000`00000080 fffffa80`05506040 : nt!ExpWorkerThread+0x111
fffff880`03362d40 fffff800`0326b486 : fffff880`0316a180 fffffa80`05522040 fffff880`031750c0 38f738f7`7c487c48 : nt!PspSystemThreadStartup+0x5a
fffff880`03362d80 00000000`00000000 : fffff880`03363000 fffff880`0335d000 fffff880`02e1b540 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
---------

5: 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: fffffa8006ce1038, 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`033626f0 fffff800`034d5a89 : fffffa80`06ce1010 fffffa80`05522040 fffffa80`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03362c10 fffff800`033b7547 : fffffa80`06ce1010 fffff800`034305f8 fffffa80`05522040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03362c40 fffff800`0331fb95 : fffff800`03492360 fffffa80`064b7bf8 fffffa80`064b7bf0 fffffa80`05522040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03362c80 fffff800`0329a161 : fffff880`01171e00 fffff800`0331fb70 fffffa80`05522040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03362cb0 fffff800`03530166 : a80aa80a`c3f8c3f8 fffffa80`05522040 00000000`00000080 fffffa80`05506040 : nt!ExpWorkerThread+0x111
fffff880`03362d40 fffff800`0326b486 : fffff880`0316a180 fffffa80`05522040 fffff880`031750c0 38f738f7`7c487c48 : nt!PspSystemThreadStartup+0x5a
fffff880`03362d80 00000000`00000000 : fffff880`03363000 fffff880`0335d000 fffff880`02e1b540 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
---------

Hi BuzzFuzz. Without looking at your dump files but reading your post:

You're getting a stop0x124, which means blame the hardware. See this thread for pointers: Stop 0x124 - what it means and what to try

Some hardware tests to run:

Links to Hard Drive Diagnostics Tools
RAM - How to Test with Memtest86+
Also see: Guide to using Memtest86+
CPU - Stress Test with Prime95. Run the "Blend" and "Small FFTs" tests.
Video Card - Stress Test with Furmark

Thanks mate, fixed. My clock voltage...
Cheers