nv4_disp.dll-bsod-bf2-precision m70, help please!

been getting this weird problem and it seems to be only with bf on my precision m70

here is whats happening when i play bf2 i get bsod 10 to 20 min after starting to play so far i tryed the more then outdated 84.3 dell driver for the go1400 and also a couple of the omega, lv2g, x-treme g driver and all gave me bsod aftera while playing bf2 i tryed browsing the web about bf2-quadro-bsod but none where helpfull

i say only bf2 as i am able to play r6 vegas2 and assassin creeds without it crashing so i guess this could almost rule out the hardware failling as i guess it would fail with those game to as they are demanding to

the bsod is always linked to nv4_disp.dll

i did a windbg of the last minidump i got here are the result

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
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, de37ccc2, f1460ac4, 0}

*** WARNING: Unable to verify timestamp for dxg.sys
Probably caused by : nv4_disp.dll ( nv4_disp!g_PM+1da72 )

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

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: de37ccc2, The address that the exception occurred at
Arg3: f1460ac4, 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!g_PM+1da72
de37ccc2 660fe707 movntdq xmmword ptr [edi],xmm0

TRAP_FRAME: f1460ac4 -- (.trap 0xfffffffff1460ac4)
ErrCode = 00000002
eax=00000000 ebx=00000040 ecx=000058bb edx=00162ec4 esi=06f50040 edi=00000000
eip=de37ccc2 esp=f1460b38 ebp=f1460b44 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!g_PM+0x1da72:
de37ccc2 660fe707 movntdq xmmword ptr [edi],xmm0 ds:0023:00000000=????????????????????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: BF2.exe

LAST_CONTROL_TRANSFER: from de0f4c38 to de37ccc2

STACK_TEXT:
f1460b44 de0f4c38 00000000 06f50040 00162ec4 nv4_disp!g_PM+0x1da72
f1460ba0 f1460bb8 00000000 fffdffff e311b000 nv4_disp!vppColourControl+0x38
WARNING: Frame IP not in any known module. Following frames may be wrong.
f1460bcc 0018cbe4 ddfc3852 f1460d18 fffffff8 0xf1460bb8
f1460bd0 ddfc3851 f1460d18 fffffff8 f1460ce4 0x18cbe4
f1460bd4 f1460d18 fffffff8 f1460ce4 e42654f0 dxg!DxD3dValidateTextureStageState+0xb9
f1460bd8 fffffff8 f1460ce4 e42654f0 f1460c68 0xf1460d18
f1460d18 00000000 e4eaa750 00000000 f1460c74 0xfffffff8


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_disp!g_PM+1da72
de37ccc2 660fe707 movntdq xmmword ptr [edi],xmm0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_disp!g_PM+1da72

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 47567aa4

FAILURE_BUCKET_ID: 0x8E_nv4_disp!g_PM+1da72

BUCKET_ID: 0x8E_nv4_disp!g_PM+1da72

Followup: MachineOwner

 

What are the temps before the crashing?Are they related?

 

temp are surrounding the 70 to 75 celcius wich is what it runs at in about all fps

EDIT: ok i think i found the solution, deleting the content of the battlefield2 folder in my document seem to have solved the problem played true 3 maps without a glitch while i wasnt even able to finish one before