Blue Screen Minidump que faire?

Bonjour à tous,
Voici mon problème, depuis un moment mon ordinateur fais des crashs (blue screen) assez régulièrement. J'ai pas mal cherché sur internet des solutions à mon problème, j'ai un peux avancé en ouvrant les fichiers Minidump avec "whocrashed" mais pour na pas vous mentir je ne sais pas trop quoi faire avec ces rapports. Si je comprend bien il y aurait plusieurs problèmes.

Voici les différents rapports que j'ai :
Rapport_01 :

Crash dump file:        C:\Windows\Minidump\032912-24523-01.dmp  
Date/time:              28/03/2012 23:57:50 GMT  
Uptime:                 11:36:34  
Machine:                  
Bug check name:         SYSTEM_SERVICE_EXCEPTION  
Bug check code:         0x3B  
Bug check parm 1:       0xC000001D  
Bug check parm 2:       0xFFFFF8800140773F  
Bug check parm 3:       0xFFFFF8800AA053B0  
Bug check parm 4:       0x0  
Probably caused by:     tdx.sys  
Driver description:     TDI Translation Driver  
Driver product:         Microsoft® Windows® Operating System  
Driver company:         Microsoft Corporation  
OS build:               Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330  
Architecture:           x64 (64 bit)  
CPU count:              4  
Page size:              4096  

Bug check description:  
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.   

Comments:  
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.   
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.   

Rapport_02 :

Crash dump file:        C:\Windows\Minidump\033012-31262-01.dmp  
Date/time:              30/03/2012 20:54:48 GMT  
Uptime:                 08:03:41  
Machine:                  
Bug check name:         DRIVER_IRQL_NOT_LESS_OR_EQUAL  
Bug check code:         0xD1  
Bug check parm 1:       0x2  
Bug check parm 2:       0x2  
Bug check parm 3:       0x0  
Bug check parm 4:       0xFFFFF88006CC0F0C  
Probably caused by:     ntoskrnl.exe  
Driver description:     NT Kernel & System  
Driver product:         Microsoft® Windows® Operating System  
Driver company:         Microsoft Corporation  
OS build:               Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330  
Architecture:           x64 (64 bit)  
CPU count:              4  
Page size:              4096  

Bug check description:  
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.  

Comments:  
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.   
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.   

Rapport_03 :

Crash dump file:        C:\Windows\Minidump\033112-25927-01.dmp  
Date/time:              31/03/2012 21:23:33 GMT  
Uptime:                 06:05:36  
Machine:                  
Bug check name:         NTFS_FILE_SYSTEM  
Bug check code:         0x24  
Bug check parm 1:       0xC08A5  
Bug check parm 2:       0x0  
Bug check parm 3:       0x0  
Bug check parm 4:       0x0  
Probably caused by:     ntfs.sys  
Driver description:     Pilote du système de fichiers NT  
Driver product:         Système d'exploitation Microsoft® Windows®  
Driver company:         Microsoft Corporation  
OS build:               Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330  
Architecture:           x64 (64 bit)  
CPU count:              4  
Page size:              4096  

Bug check description:  
This indicates a problem occurred in the NTFS file system.   

Comments:  

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.   

Rapport_04 :

Crash dump file:        C:\Windows\Minidump\040312-29078-01.dmp  
Date/time:              03/04/2012 19:11:26 GMT  
Uptime:                 07:43:27  
Machine:                  
Bug check name:         MEMORY_MANAGEMENT  
Bug check code:         0x1A  
Bug check parm 1:       0x41287  
Bug check parm 2:       0x30  
Bug check parm 3:       0x0  
Bug check parm 4:       0x0  
Probably caused by:     ntoskrnl.exe  
Driver description:     NT Kernel & System  
Driver product:         Microsoft® Windows® Operating System  
Driver company:         Microsoft Corporation  
OS build:               Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330  
Architecture:           x64 (64 bit)  
CPU count:              4  
Page size:              4096  

Bug check description:  
This indicates that a severe memory management error occurred.  

Comments:  
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.   
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.   

Rapport_05 :

Crash dump file:        C:\Windows\memory.dmp  
Date/time:              03/04/2012 19:11:26 GMT  
Uptime:                 07:43:27  
Machine:                  
Bug check name:         MEMORY_MANAGEMENT  
Bug check code:         0x1A  
Bug check parm 1:       0x41287  
Bug check parm 2:       0x30  
Bug check parm 3:       0x0  
Bug check parm 4:       0x0  
Probably caused by:     ntkrnlmp.exe  
Driver description:       
Driver product:           
Driver company:           
OS build:               Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330  
Architecture:           x64 (64 bit)  
CPU count:              4  
Page size:              4096  

Bug check description:  
This indicates that a severe memory management error occurred.  

Comments:  
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.   
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.   

Tous mes pilotes sont à jour, j'ai fait une analyse anti-virus complète de l'ordinateur.

Merci d'avance pour votre aide

Cordialement.