Memory_corruption ECRAN BLEU

Bonjour,

voila j'ai eu plusieurs crash (ecran bleu), j'ai ouvert le fichier DUMP (avec WINDBG) , et il m'a donné ce diagnostic :

Map win32k.sys:
Image region 380:18a280 does not fit in mapping
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf820b78, b91a4710, 0}

Map ACPI.sys:
Image region 300:1af00 does not fit in mapping


Probably caused by : memory_corruption

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

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: bf820b78, The address that the exception occurred at
Arg3: b91a4710, 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:
win32k+20b78
bf820b78 894024 mov dword ptr [eax+24h],eax

TRAP_FRAME: b91a4710 -- (.trap 0xffffffffb91a4710)
ErrCode = 00000002
eax=000000dd ebx=e108d008 ecx=00000000 edx=bc0570d0 esi=b91a47e8 edi=b91a47f8
eip=bf820b78 esp=b91a4784 ebp=b91a4830 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210206
win32k+0x20b78:
bf820b78 894024 mov dword ptr [eax+24h],eax ds:0023:00000101=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: Photoshop.exe

LAST_CONTROL_TRANSFER: from bf81f510 to bf820b78

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b91a4830 bf81f510 bc0570d0 b91a4898 00000000 win32k+0x20b78
b91a488c bf822257 00000001 00000000 bc0570f2 win32k+0x1f510
b91a48ac bf8fd86f bc0570d0 00000000 00000000 win32k+0x22257
b91a48d0 bf80ea66 bc0570d0 b91a4938 bf80ead3 win32k+0xfd86f
b91a48f8 bf80eb56 00000001 00000001 b91a491c win32k+0xea66
b91a495c 804ddf0f 00020a8a 00000001 0012d490 win32k+0xeb56
b91a495c 7c91eb94 00020a8a 00000001 0012d490 nt!KiFastCallEntry+0xfc
0012d428 00000000 00000000 00000000 00000000 0x7c91eb94


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
bf820b79 - win32k+20b79
[ 43:40 ]
1 error : !win32k (bf820b79)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BYTE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE

Followup: memory_corruption


-ce que j'ai compris que j'ai un problème avec la RAM (jai fais plusieurs passes avec memtest86) mais sans erreurs!!

aidez moi svp car il crash souvent!

MERCI