Bsod en chaine

Bonjour, j'ai un gros souci de BSOD en chaine depuis plus de quinze jours ca devient decourageant, quelqu'un peut il m'aider

voici ma configuration
Modules



Système d'exploitation

Windows 8.1 ?(X86)?

Date d'installation: 17/06/2014


Processeur

Intel Pentium G2020 Cadencé à 2.90 GHz

Nombre de coeurs: 2 physique(s), 2 logique(s)
Socket: Socket 1155 LGA


Carte mère

MSI H61M-P20 (G3) (MS-7788) 1.0

Numéro de série (carte mère): To be filled by O.E.M.
SKU Number: To be filled by O.E.M.
Version du bios: V1.9
Date: 09/01/2013


Chipset

Pont nord : Intel Ivy Bridge

Identifiant de révision: 09


Pont sud : Intel H61

Identifiant de révision: B3


Mémoire

4 Go de mémoire totale de type DDR3

Timings mémoire: 9.0 clocks-9 clocks-9 clocks-24 clocks-1 TT


Barrette Kingston de 4 Go

Fréquence maximale: 667 MHz
Bande passante: PC3-10700


Carte Graphique

AMD Radeon HD 6450

Version DirectX installée: 11.0


Disque dur

Disque dur HitachiHDP725050GLA360 de 465.76 Go SATA II

Firmware: GM4OA57A
Version du SATA: SATA Rev 2.6
Numéro de série: GEA530RE1NA0XE
Température HDD: 30 °C
Temps de fonctionnement: 24600 heures


Disque dur ST1000DM003-9YN162 de 931.51 Go SATA III

Firmware: CC4D
Numéro de série: S1D1AEK4
Température HDD: 34 °C
Temps de fonctionnement: 9592 heures


Lecteurs optiques

HL-DT-ST DVD-RAM GH10L

Type: DVD-RAM Recorder
Version du firmware: FC09
Date du firmware: 18/01/2008 11:34


Réseau

Realtek PCIe FE Family Controller

Type d'adaptateur: ethernet


Software Loopback Interface 1

Type d'adaptateur: Loopback


Cartes multimedia

Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller

Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series]


ainsi que la liste des derniers Bsod

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 25/06/2014 17:26:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062514-13406-01.dmp
This was probably caused by the following module: wpcfltr.sys (wpcfltr+0x2947)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x1D0003, 0xFFFFFFFFD5EA8318)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\wpcfltr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Family Safety Filter Driver
Bug check description: This indicates that the current thread is making a bad pool request.
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 that cannot be identified at this time.
Google query: Microsoft Corporation BAD_POOL_CALLER



On Tue 24/06/2014 20:40:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062414-15765-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1D51C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF8217FCE1, 0xFFFFFFFFAF9E8558, 0xFFFFFFFFAF9E8120)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 that cannot be identified at this time.



On Tue 24/06/2014 08:34:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062414-13375-01.dmp
This was probably caused by the following module: klwfp.sys (klwfp+0x4525)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x81D000C, 0xFFFFFFFF925D4DA8)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\klwfp.sys
product: Kaspersky(TM) Anti-Virus ®
company: Kaspersky Lab ZAO
description: Network filtering component [RC_BUILD_OPT]
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klwfp.sys (Network filtering component [RC_BUILD_OPT], Kaspersky Lab ZAO).
Google query: Kaspersky Lab ZAO BAD_POOL_CALLER



On Mon 23/06/2014 19:52:28 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062314-27468-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1D51C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF81393CE1, 0xFFFFFFFFAB7D5578, 0xFFFFFFFFAB7D5140)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 that cannot be identified at this time.



On Mon 23/06/2014 14:03:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062314-17640-01.dmp
This was probably caused by the following module: klwfp.sys (klwfp+0x1BC6)
Bugcheck code: 0x100000D1 (0xFFFFFFFFEDC1A581, 0x2, 0x1, 0xFFFFFFFF82521F06)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\klwfp.sys
product: Kaspersky(TM) Anti-Virus ®
company: Kaspersky Lab ZAO
description: Network filtering component [RC_BUILD_OPT]
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klwfp.sys (Network filtering component [RC_BUILD_OPT], Kaspersky Lab ZAO).
Google query: Kaspersky Lab ZAO CUSTOM_ERROR



On Mon 23/06/2014 11:09:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062314-13765-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1D51C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF81F90CE1, 0xFFFFFFFFD6FF4558, 0xFFFFFFFFD6FF4120)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 that cannot be identified at this time.



On Sun 22/06/2014 21:16:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062214-20765-01.dmp
This was probably caused by the following module: npfs.sys (Npfs+0x5EC1)
Bugcheck code: 0x19 (0xE, 0xFFFFFFFFCBD60710, 0x0, 0xFFFFFFFFA4957BF1)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 22/06/2014 14:16:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062214-12890-01.dmp
This was probably caused by the following module: klwfp.sys (klwfp+0x684A)
Bugcheck code: 0xD1 (0xFFFFFFFF8C6A2E1D, 0x2, 0x1, 0xFFFFFFFF82718F06)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\klwfp.sys
product: Kaspersky(TM) Anti-Virus ®
company: Kaspersky Lab ZAO
description: Network filtering component [RC_BUILD_OPT]
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klwfp.sys (Network filtering component [RC_BUILD_OPT], Kaspersky Lab ZAO).
Google query: Kaspersky Lab ZAO DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 22/06/2014 14:16:21 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: klwfp.sys (klwfp+0x684A)
Bugcheck code: 0xD1 (0xFFFFFFFF8C6A2E1D, 0x2, 0x1, 0xFFFFFFFF82718F06)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\klwfp.sys
product: Kaspersky(TM) Anti-Virus ®
company: Kaspersky Lab ZAO
description: Network filtering component [RC_BUILD_OPT]
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klwfp.sys (Network filtering component [RC_BUILD_OPT], Kaspersky Lab ZAO).
Google query: Kaspersky Lab ZAO DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 22/06/2014 11:22:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062214-22859-01.dmp
This was probably caused by the following module: afd.sys (afd+0x33695)
Bugcheck code: 0xC5 (0x1, 0x2, 0x0, 0xFFFFFFFF819E00C3)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de fonction connexe pour WinSock
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.