BSOD playing Games (BF3 / SWTOR)

Hi everyone,

I have several crashes since I think all the times.

Here is the story:

Config in 2010
Antec Sonata 3
Asus p6T
NOCTUA 12P
i920 c0
6go g skill
Radeon 4870
Win 64 bits ultimate

From times to times I get some BSOD but not really annoying.

1 year ago
I get the 5870 XFX.
Now I get a crash systematically in SWTOR, BF3 games that use a lot GPU / CPU.
The behaviour is quite strange too, as I can feel the crash / dump coming.
The sound is crackling like there is some disturb in the sound or some echo and then few secondes after it crashes and get the bsod.

My main pb is that the dump analysis but the debogger seems different time to time. It's maybe Realtek or "Machine Owner".

I have tried to enhance the cooling of my computer as I have notice that with an open PC case I get less crashes but it's only a feeling.

For information I get at max 70 on CPU with OCCT.

I have attached all the required stuff. Thanks for your help !
FYI I will stop my current overclocking :)

Antivirus Software:

Code:

avastsvc.exe	c:\program files\alwil software\avast5\avastsvc.exe	1660	8	200	1380	02/03/2012 20:55	6.0.1367.0	43,72 Ko (44*768 octets)	09/12/2011 01:06
avastui.exe	c:\program files\alwil software\avast5\avastui.exe	3700	8	200	1380	02/03/2012 20:56	6.0.1367.0	3,57 Mo (3*744*552 octets)	09/12/2011 01:06

Possible virus detected!!!:

Code:

spup	fffff880`01076000	fffff880`011aa000	Sun Mar 22 06:35:35 2009 (49c63097)	000dfd67		spup.sys

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Manhouch\Windows_NT6_BSOD_jcgriff2\022912-21824-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0344f000 PsLoadedModuleList = 0xfffff800`03694670
Debug session time: Tue Feb 28 16:01:52.955 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:09.938
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, fffffa80069ce368, 0, 0}

Probably caused by : hardware

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

3: 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: fffffa80069ce368, 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`037706f0 fffff800`03711c59 : fffffa80`069ce340 fffffa80`055bd740 00000000`00000008 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03770c10 fffff800`035f1f57 : fffffa80`069ce340 fffff800`0366c2b8 fffffa80`055bd740 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03770c40 fffff800`035595d5 : fffff800`036cdae0 00000000`00000001 fffffa80`065b8820 fffffa80`055bd740 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03770c80 fffff800`034d6001 : fffff880`01304e00 fffff800`035595b0 fffffa80`055bd700 022c022c`a3d6a3d6 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03770cb0 fffff800`03766fee : 22b222b2`f05bf05b fffffa80`055bd740 00000000`00000080 fffffa80`0548e890 : nt!ExpWorkerThread+0x111
fffff880`03770d40 fffff800`034bd5e6 : fffff880`03586180 fffffa80`055bd740 fffff880`035910c0 80cb80cb`77047704 : nt!PspSystemThreadStartup+0x5a
fffff880`03770d80 00000000`00000000 : fffff880`03771000 fffff880`0376b000 fffff880`0323b690 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
---------

Loading Dump File [D:\Kingston\BSODDmpFiles\Manhouch\Windows_NT6_BSOD_jcgriff2\022612-22245-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0340e000 PsLoadedModuleList = 0xfffff800`03653670
Debug session time: Sun Feb 26 07:54:12.017 2012 (UTC - 7:00)
System Uptime: 0 days 3:57:01.001
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff880009bac70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff880009bac70
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff80003a09818 to fffff8000348ac40

STACK_TEXT:  
fffff880`009bac38 fffff800`03a09818 : 00000000`0000009c 00000000`00000000 fffff880`009bac70 00000000`00000000 : nt!KeBugCheckEx
fffff880`009bac40 fffff800`03a08f57 : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`009bad90 fffff800`039fce88 : fffff880`009b2180 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`009badc0 fffff800`0348952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009badf0 fffff800`03489393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009baf30 fffff800`03460661 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0c7e17c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KxMcheckAbort+6c
fffff800`0348952c 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KxMcheckAbort+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

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

1. Stop 0x124: See below
2. MSDN Bug Check Code Reference said:

   In Windows Vista and later operating systems, this bug check occurs only in the following circumstances.
   WHEA is not fully initialized.
   All processors that rendezvous have no errors in their registers.

• Download and install the free, standalone (do not start the trial) version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download and run a full scan of the system.
  
  
• Stop 0x124 - what it means and what to try
  
  • Monitor temperatures during the following tests.
    
    Use the following programs to monitor the temperatures.
    • Real Temp is a good CPU temperature monitor.
    • Speccy - System Information - Free Download will monitor all hardware temperatures.
    • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
    
    
    • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
      
      
      
    • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

Testing that as soon as I can and get back to you.

thanks for your time !