Bonjour,
J'ai installé le soft conseillé et voila ce que m'apprend l'analyse effectué.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 02/10/2011 14:37:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100211-19141-01.dmp
This was probably caused by the following module: klif.sys (klif+0x1FF42)
Bugcheck code: 0x21 (0x0, 0x1, 0x6C3B0021, 0x6BD3553B)
Error: QUOTA_UNDERFLOW
file path: C:\Windows\system32\drivers\klif.sys
product: Kaspersky™ Anti-Virus ®
company: Kaspersky Lab
description: Klif Mini-Filter [fre_wlh_x86]
Bug check description: This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged.
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: klif.sys (Klif Mini-Filter [fre_wlh_x86], Kaspersky Lab).
Google query: klif.sys Kaspersky Lab QUOTA_UNDERFLOW
On Sun 02/10/2011 14:37:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: klif.sys (klif+0x1FF42)
Bugcheck code: 0x21 (0x0, 0x1, 0x6C3B0021, 0x6BD3553B)
Error: QUOTA_UNDERFLOW
file path: C:\Windows\system32\drivers\klif.sys
product: Kaspersky™ Anti-Virus ®
company: Kaspersky Lab
description: Klif Mini-Filter [fre_wlh_x86]
Bug check description: This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged.
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: klif.sys (Klif Mini-Filter [fre_wlh_x86], Kaspersky Lab).
Google query: klif.sys Kaspersky Lab QUOTA_UNDERFLOW
On Sat 01/10/2011 18:47:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100111-14820-01.dmp
This was probably caused by the following module: kl1.sys (kl1+0x3B93C)
Bugcheck code: 0xD1 (0x7B8EA7D2, 0x2, 0x0, 0xFFFFFFFF9007A93C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\kl1.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Kaspersky Unified Driver
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: kl1.sys (Kaspersky Unified Driver, Kaspersky Lab).
Google query: kl1.sys Kaspersky Lab DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 01/10/2011 10:31:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100111-17565-01.dmp
This was probably caused by the following module: klif.sys (klif+0x21B9A)
Bugcheck code: 0x50 (0xFFFFFFFFE14121A6, 0x1, 0xFFFFFFFF830B953B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\klif.sys
product: Kaspersky™ Anti-Virus ®
company: Kaspersky Lab
description: Klif Mini-Filter [fre_wlh_x86]
Bug check description: This indicates that invalid system memory has been referenced.
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: klif.sys (Klif Mini-Filter [fre_wlh_x86], Kaspersky Lab).
Google query: klif.sys Kaspersky Lab PAGE_FAULT_IN_NONPAGED_AREA
On Fri 30/09/2011 22:29:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100111-16302-01.dmp
This was probably caused by the following module: kl1.sys (kl1+0x3F23B)
Bugcheck code: 0xD1 (0xFFFFFFFFB6EA3614, 0x2, 0x0, 0xFFFFFFFF890C5BF3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\kl1.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Kaspersky Unified Driver
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: kl1.sys (Kaspersky Unified Driver, Kaspersky Lab).
Google query: kl1.sys Kaspersky Lab DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 30/09/2011 05:32:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093011-19546-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A23)
Bugcheck code: 0x1A (0x41287, 0x7E6CA4F, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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.
On Thu 29/09/2011 20:58:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092911-15974-01.dmp
This was probably caused by the following module: ci.dll (CI+0x5943)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF88AFD943, 0xFFFFFFFF9E8F4AB0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ci.dll
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Module d’intégrité du code
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 which cannot be identified at this time.
On Thu 29/09/2011 05:34:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092911-18891-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1DAAA)
Bugcheck code: 0xC2 (0x7, 0x1097, 0xFFFFFFFF9B70E3CC, 0xFFFFFFFF86F7BA88)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 which cannot be identified at this time.
On Tue 27/09/2011 19:22:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092711-17908-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x37B0)
Bugcheck code: 0xD1 (0x3C3E6563, 0x2, 0x8, 0x3C3E6563)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
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.
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.
On Tue 27/09/2011 05:28:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092711-19999-01.dmp
This was probably caused by the following module: kl1.sys (kl1+0x3DD26)
Bugcheck code: 0xC5 (0x2E2556EB, 0x2, 0x1, 0xFFFFFFFF82F3C067)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\kl1.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Kaspersky Unified Driver
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.
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: kl1.sys (Kaspersky Unified Driver, Kaspersky Lab).
Google query: kl1.sys Kaspersky Lab DRIVER_CORRUPTED_EXPOOL
On Mon 26/09/2011 09:56:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092611-19250-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A977)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF88E26977, 0xFFFFFFFF8AF0FBB4, 0xFFFFFFFF8AF0F790)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a system thread 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 which cannot be identified at this time.
On Sat 24/09/2011 19:59:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-17316-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x71AB1)
Bugcheck code: 0x21 (0x0, 0x1, 0x660A0D0A, 0x65CB46B8)
Error: QUOTA_UNDERFLOW
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 24/09/2011 11:54:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-19531-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2E8C)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF86E87E08, 0xFFFFFFFF86E87E08, 0xFFFFFFFFFA777EF7)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 which cannot be identified at this time.
On Sat 24/09/2011 01:13:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-19078-01.dmp
This was probably caused by the following module: afd.sys (afd+0x28DB0)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x39DFD502, 0xFFFFFFFF8627B008)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\afd.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 which cannot be identified at this time.
On Fri 23/09/2011 14:54:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092311-19453-01.dmp
This was probably caused by the following module: klif.sys (klif+0x1FF42)
Bugcheck code: 0x50 (0xFFFFFFFFD86D6E2E, 0x0, 0xFFFFFFFF82EAF723, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\klif.sys
product: Kaspersky™ Anti-Virus ®
company: Kaspersky Lab
description: Klif Mini-Filter [fre_wlh_x86]
Bug check description: This indicates that invalid system memory has been referenced.
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: klif.sys (Klif Mini-Filter [fre_wlh_x86], Kaspersky Lab).
Google query: klif.sys Kaspersky Lab PAGE_FAULT_IN_NONPAGED_AREA
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 15 are included in this report. 6 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
klif.sys (Klif Mini-Filter [fre_wlh_x86], Kaspersky Lab)
wudfrd.sys (Windows Driver Foundation - User-mode Driver Framework Reflector, Microsoft Corporation)
kl1.sys (Kaspersky Unified Driver, Kaspersky Lab)
athrusb.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
_____________
Je pense ne pas être dans l'erreur en affirmant que mes problèmes viennent de mon antivirus et du système.
Quelles seraient les solutions que je pourrais adopté pour que ce problème récurent cesse ?
Merci d'avance
