Ecran bleu et analyse du dump

Bonjour,

J'ai un petit soucis, depuis quelque temps déjà, j'ai aléatoirement un écran bleu qui apparait et redémare le pc.
J'ai donc installé windbg, fais une analyse et voici ce que j'obtiens :


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


Loading Dump File [C:\Windows\Minidump\021313-21481-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800'0320b000 PsLoadedModuleList = 0xfffff800'0344f670
Debug session time: Wed Feb 13 13:32:55.554 2013 (UTC + 1:00)
System Uptime: 0 days 0:39:49.428
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89cc4aa1c, b3b7465eef42d29a, fffff88000d9b3d8, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89cc4aa1c, Reserved
Arg2: b3b7465eef42d29a, Reserved
Arg3: fffff88000d9b3d8, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

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

BUGCHECK_STR: 0x109

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003289fc0

STACK_TEXT:
fffff880'0355b498 00000000'00000000 : 00000000'00000109 a3a039d8'9cc4aa1c b3b7465e'ef42d29a fffff880'00d9b3d8 : nt!KeBugCheckEx


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !CLFS
fffff88000d9b919 - CLFS!CClfsLogFcbPhysical::WriteRestart+541
[ 10:18 ]
1 error : !CLFS (fffff88000d9b919)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

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

Bon, je pense que c'est donc un problème au niveau de la mémoire, mais j'aimerai votre avis et ce que je devrai faire pour réparer.
Merci d'avance, Miguel