BSOD when I play one game

[fuchyouse]

Hello
I'm having a problem,when I play Call of Duty Moder Warfare 2 online,after some minutes I got a bluescreen withouth the screen, because I saw that when i started my computer again I saw an error saying that it was BSOD
Here is my pc:
phenom x3 8450
9600gt
3gb ram dd3
motherboard: M2N68-AM SE2
DMP:

 

[zigzag3143]

Hello
I'm having a problem,when I play Call of Duty Moder Warfare 2 online,after some minutes I got a bluescreen withouth the screen, because I saw that when i started my computer again I saw an error saying that it was BSOD
Here is my pc:
phenom x3 8450
9600gt
3gb ram dd3
motherboard: M2N68-AM SE2
DMP:

THIS IS ANOTHER IN A PLAGUE OF NEW 64BIT CRASHES



Hi and welcome


This dump was probably caused by hardware. There isnt much info on which piece. I would pull everything not essential (leave just the keyboard, mouse, mobo, monitor) then add back till it crashes

I also would download and memtestx86 and run it for several hours to test your ram and to see if heat is an issue

Run a system file check to verify and repair your system files to do that
type cmd in search>right click and run as admin>sfc /scannow

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\122209-13556-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02a5a000 PsLoadedModuleList = 0xfffff800`02c97e50
Debug session time: Tue Dec 22 16:32:55.757 2009 (GMT-5)
System Uptime: 0 days 0:00:06.832
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, fffffa8003669038, 0, 0}

[B]Probably caused by : hardware[/B]

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

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

[B]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: fffffa8003669038, 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.[/B]

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0334e6f0 fffff800`02d14a89 : fffffa80`03669010 fffffa80`0245f040 fffff8a0`00000003 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0334ec10 fffff800`02bf6547 : fffffa80`03669010 fffff800`02c6f5f8 fffffa80`0245f040 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0334ec40 fffff800`02b5eb95 : fffff800`02cd1360 fffffa80`035d8be8 fffffa80`035d8be0 fffffa80`0245f040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0334ec80 fffff800`02ad9161 : fffff880`012dbe00 fffff800`02b5eb70 fffffa80`0245f040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0334ecb0 fffff800`02d6f166 : 00000000`00000000 fffffa80`0245f040 00000000`00000080 fffffa80`0234c040 : nt!ExpWorkerThread+0x111
fffff880`0334ed40 fffff800`02aaa486 : fffff880`03163180 fffffa80`0245f040 fffff880`0316df80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0334ed80 00000000`00000000 : fffff880`0334f000 fffff880`03349000 fffff880`0334df50 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_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

Hope this helps


Ken J+

 

[fuchyouse]

if I change my windows 7 x64 to x32 it will solve the problem?