BSoD only in MW2

Hello everyone
I have some problems with BSoDing in Modern Warfare 2.
It starts off with my screen shaking really weird with a big fps drop and by alt+tabbing out and in it fixes it then the BSoD can happen at any time but most times It never comes.
Sometimes I get away with a simple directx error (can't remember what it says).
This only happends sometimes when I get hit by something like a flash or stun grenade that causes my screen to shake.
On the BSoD It says that the computer has been shut down to prevent damage or something like that.

I would appreciate any help I could get.

Things I have already done:
* Formatted with a clean install of XP on a new harddrive.
* Changed my monitor from a tft to crt.
* Updated to latest nvidia non-beta driver.

Here is the latest minidump from after the format, I've attached a file with pre-format dumps but they are basicly the same.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini112509-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Nov 25 00:03:54.500 2009 (GMT+1)
System Uptime: 0 days 4:17:09.239
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
............
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bd0cadd9, b3c2eaa4, 0}

Probably caused by : nv4_disp.dll ( nv4_disp+b8dd9 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bd0cadd9, The address that the exception occurred at
Arg3: b3c2eaa4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nv4_disp+b8dd9
bd0cadd9 8b89e8000000 mov ecx,dword ptr [ecx+0E8h]

TRAP_FRAME: b3c2eaa4 -- (.trap 0xffffffffb3c2eaa4)
ErrCode = 00000000
eax=e6ba5e80 ebx=40012f98 ecx=66727553 edx=e8bf3fc0 esi=e8bf3fc0 edi=bd5770b8
eip=bd0cadd9 esp=b3c2eb18 ebp=e8bf43c0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nv4_disp+0xb8dd9:
bd0cadd9 8b89e8000000 mov ecx,dword ptr [ecx+0E8h] ds:0023:6672763b=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iw4mp.exe

LAST_CONTROL_TRANSFER: from e16c2800 to bd0cadd9

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b3c2eb14 e16c2800 bd0d4e4b e16c55c0 e8bf43c0 nv4_disp+0xb8dd9
b3c2ec14 80502353 bd0c99b3 b3c2ecfc e1600714 0xe16c2800
b3c2ec3c bf8f70e5 b3c2ecfc e1600714 e39a4018 nt!KiInsertTimerTable+0x1b
b3c2ed04 b8490671 e1600714 e37d82b8 bf8f7180 win32k!WatchdogDdDestroySurface+0x38
b3c2ed1c bf845a14 b3c2ed5c b3c2ed38 00000000 watchdog!WdEnterMonitoredSection+0x5f
b3c2ed28 00000000 b3c2ed54 bd00b3a4 e1600008 win32k!DxEngLockHdev+0x24


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_disp+b8dd9
bd0cadd9 8b89e8000000 mov ecx,dword ptr [ecx+0E8h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_disp+b8dd9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4ac001a1

FAILURE_BUCKET_ID: 0x8E_nv4_disp+b8dd9

BUCKET_ID: 0x8E_nv4_disp+b8dd9
Followup: MachineOwner
---------

 

i was getting that with CodWaw. i believe it was temperature related. I run an 8800GT and anytime it got near 90C it would freeze up. sometimes i would get that crash. Try running Hwmonitor during a game, and see what temps you get to while playing.

http://majorgeeks.com/HWMonitor_d5842.html

It only ever crashed in xp, when i played in vista it would freeze, but recover itself. Once i figured out it was overheating, I turned AA down to 2x or off. seemed to keep the temps down, and I really didn't notice a quality difference especially in multiplayer.