Probleme Ecran Bleu a cause de css (ou steam)

Bonjour,

Donc comme préciser dans le titre j'ai des bsod qui se produisent depuis 1 semaine deja et le probleme vien a 100% a cause de css ( ou steam ) et apres avoir fait des recherches il a fallu que je DL windbg pour lire les fichiers DMP et celui ou l'erreur est généré ( apparemment )
Moi qui n'y connait pas grand chause j'ai reussi a me débrouiller et cela me donne ceci :

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


Loading Dump File [C:\WINDOWS\Minidump\Mini021911-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.6055) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Feb 19 19:17:39.390 2011 (UTC + 1:00)
System Uptime: 0 days 8:19:26.368
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bd009b2a, b0ab5bfc, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

3: 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: bd009b2a, The address that the exception occurred at
Arg3: b0ab5bfc, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction "0x%08lx" emploie l'adresse m moire "0x%08lx". La m moire ne peut pas tre "%s".

FAULTING_IP:
dxg!pDdLockSurfaceOrBuffer+2be
bd009b2a f722 mul eax,dword ptr [edx]

TRAP_FRAME: b0ab5bfc -- (.trap 0xffffffffb0ab5bfc)
ErrCode = 00000000
eax=00000000 ebx=e3552018 ecx=0000000d edx=00000000 esi=bf9636f2 edi=e1abc714
eip=bd009b2a esp=b0ab5c70 ebp=b0ab5cdc iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxg!pDdLockSurfaceOrBuffer+0x2be:
bd009b2a f722 mul eax,dword ptr [edx] ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: hl2.exe

LAST_CONTROL_TRANSFER: from bd00b0b9 to bd009b2a

STACK_TEXT:
b0ab5cdc bd00b0b9 e1abc714 00000000 b0ab5d10 dxg!pDdLockSurfaceOrBuffer+0x2be
b0ab5d54 8054167c 1b409a7b 13cbfc10 13cbfc44 dxg!DxDdLockD3D+0x69
b0ab5d54 7c91e514 1b409a7b 13cbfc10 13cbfc44 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
13cbfc44 00000000 00000000 00000000 00000000 0x7c91e514


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxg
bd009b23 - dxg!pDdLockSurfaceOrBuffer+2b7
[ 01:0d ]
bd009b2a - dxg!pDdLockSurfaceOrBuffer+2be (+0x07)
[ 75:f7 ]
2 errors : !dxg (bd009b23-bd009b2a)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

3: kd> lmvm memory_corruption
start end module name

Bon c'est long et je vois sa pour la premiere fois et vu que je n'y connais pas grand chose je vien poster ici pour avoir la chance de tomber sur quelqu'un a qui c'est deja arrivé et qui c'est d'ou cela peut venir.

Pour information j'ai fait toutes les MAJ pour direct X la Carte Graphique Windows Steam etc... j'ai réinstaller steam css etc..
Et quand je joue a d'autre jeu du genre TrackMania ou des MMORPG genre Rappelz plus longtemps aucun bug ne provient.

Ne manque plus que le formatage comme dernier recours....

Voila merci de bien vouloir m'aider en esperant résoudre ce probleme.

Cordialement,
Sylenze