Plantage a repetition fichier dmp

Bonjour,

Mon ordi plante de plus en plus souvent. J'ai récuperé le fichier .dmp qui resulte du crash, j'ai fais un gros test avec memtest qui me dit que ma memoire est OK. Quelqu'un aurait un semblant de réponse ou d'idée la dessus? Je suis sous Windows 7 avec un ATHLON 64 X2 Dual Core processor 5600+ 2.8 Ghz.

Fichier dmp:


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


Loading Dump File [C:\Users\Ska\Desktop\070512-20748-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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82e00000 PsLoadedModuleList = 0x82f494f0
Debug session time: Thu Jul 5 20:53:05.864 2012 (UTC + 2:00)
System Uptime: 0 days 9:23:43.643
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 98e1d26b, 8efe4c58, 0}

Probably caused by : hardware ( win32k!RawInputThread+48a )

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: c000001d, The exception code that was not handled
Arg2: 98e1d26b, The address that the exception occurred at
Arg3: 8efe4c58, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Instruction non autoris e Tentative d

FAULTING_IP:
win32k!RawInputThread+48a
98e1d26b 1d28300399 sbb eax,offset win32k!gdwUpdateKeyboard (99033028)

TRAP_FRAME: 8efe4c58 -- (.trap 0xffffffff8efe4c58)
ErrCode = 00000000
eax=00000003 ebx=00000000 ecx=00000000 edx=00000000 esi=00000001 edi=82e3bfb0
eip=98e1d26b esp=8efe4ccc ebp=8efe4d04 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!RawInputThread+0x48a:
98e1d26b 1d28300399 sbb eax,offset win32k!gdwUpdateKeyboard (99033028)
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
win32k!RawInputThread+48a
98e1d26b 1d28300399 sbb eax,offset win32k!gdwUpdateKeyboard (99033028)

LAST_CONTROL_TRANSFER: from 98e2d7d7 to 98e1d26b

FAILED_INSTRUCTION_ADDRESS:
win32k!RawInputThread+48a
98e1d26b 1d28300399 sbb eax,offset win32k!gdwUpdateKeyboard (99033028)

STACK_TEXT:
8efe4d04 98e2d7d7 00000004 00000002 8edea400 win32k!RawInputThread+0x48a
8efe4d18 98ee3bfd 00000004 01d6ff8c 8efe4d34 win32k!xxxCreateSystemThreads+0x4a
8efe4d28 82e3e1fa 00000004 01d6ffcc 773670b4 win32k!NtUserCallNoParam+0x1b
8efe4d28 773670b4 00000004 01d6ffcc 773670b4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01d6ffcc 00000000 00000000 00000000 00000000 0x773670b4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!RawInputThread+48a
98e1d26b 1d28300399 sbb eax,offset win32k!gdwUpdateKeyboard (99033028)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!RawInputThread+48a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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