Ecran bleu

Bonjour,

J'ai souvent des écrans bleus mais je n 'ai pas toujours le temps de les prendre en photos pour les comprendre. Je n'y connais pas grand chose en informatique profonde...
DOnc en suivant quelques conseils de ce forum j'ai installé WhoCrashed et voilà le rapport.
Est ce que quelqu'un peut m'aider à l'analyser, merci !

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4300 @ 2.10GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3184119808 total
VM: 2147352576, free: 1999695872




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

Crash dump directory: C:\windows\Minidump

Crash dumps are enabled on your computer.

On Tue 05/02/2013 09:41:58 GMT your computer crashed
crash dump file: C:\windows\Minidump\020513-24102-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2490)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFAC23D3F0, 0xFFFFFFFF81010000, 0x3)
Error: BAD_POOL_HEADER
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 05/02/2013 09:41:58 GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFAC23D3F0, 0xFFFFFFFF81010000, 0x3)
Error: BAD_POOL_HEADER
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 05/02/2013 07:27:04 GMT your computer crashed
crash dump file: C:\windows\Minidump\020513-26504-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2490)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC01C2B88, 0xA9F025, 0xFFFFFFFF88B97A30)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\ntoskrnl.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 that cannot be identified at this time.



On Fri 01/02/2013 15:24:04 GMT your computer crashed
crash dump file: C:\windows\Minidump\020113-26582-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2490)
Bugcheck code: 0x1A (0x5002, 0xFFFFFFFFC0402000, 0x2E70, 0xFFFFFFFF82E71FFE)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\ntoskrnl.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 that cannot be identified at this time.



On Wed 30/01/2013 07:07:24 GMT your computer crashed
crash dump file: C:\windows\Minidump\013013-27222-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118DA8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF83130DA8, 0xFFFFFFFFC7BBA9D4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 21/01/2013 07:40:13 GMT your computer crashed
crash dump file: C:\windows\Minidump\012113-19297-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2490)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0402346, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\ntoskrnl.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 that cannot be identified at this time.



On Sun 20/01/2013 21:08:00 GMT your computer crashed
crash dump file: C:\windows\Minidump\012013-21933-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x94DB)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x1, 0xFFFFFFFF83316F81, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA



On Tue 15/01/2013 08:56:56 GMT your computer crashed
crash dump file: C:\windows\Minidump\011513-17503-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xDC46)
Bugcheck code: 0x19 (0x22, 0xFFFFFFFF81000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 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 Mon 14/01/2013 09:12:23 GMT your computer crashed
crash dump file: C:\windows\Minidump\011413-18049-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118C4E)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFAE938A08, 0xFFFFFFFFAE939280, 0x4B0F0811)
Error: BAD_POOL_HEADER
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 14/01/2013 09:09:06 GMT your computer crashed
crash dump file: C:\windows\Minidump\011413-17643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2490)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0402080, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\ntoskrnl.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 that cannot be identified at this time.



On Sat 12/01/2013 07:35:08 GMT your computer crashed
crash dump file: C:\windows\Minidump\011213-21060-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x3B3FB)
Bugcheck code: 0x1A (0x5002, 0xFFFFFFFFC0402000, 0x10, 0xFFFFFFFFD1011FFE)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software MEMORY_MANAGEMENT



On Wed 09/01/2013 08:14:35 GMT your computer crashed
crash dump file: C:\windows\Minidump\010913-23914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2490)
Bugcheck code: 0x1A (0x5002, 0xFFFFFFFFC0402000, 0x22A8, 0xFFFFFFFFD22A9FFE)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\ntoskrnl.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 that cannot be identified at this time.



On Fri 28/12/2012 14:10:44 GMT your computer crashed
crash dump file: C:\windows\Minidump\122812-25022-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xA839)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF830A85A6, 0xFFFFFFFF80E689D0, 0xFFFFFFFF80E685B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 that cannot be identified at this time.



On Fri 28/12/2012 13:27:19 GMT your computer crashed
crash dump file: C:\windows\Minidump\122812-23166-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2490)
Bugcheck code: 0x1A (0x31, 0xFFFFFFFF8735D790, 0xFFFFFFFF90711000, 0xFFFFFFFFA8C9D077)
Error: MEMORY_MANAGEMENT
file path: C:\windows\system32\ntoskrnl.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 that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

14 crash dumps have been found and analyzed. A third party driver has 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:

aswsp.sys (avast! self protection module, AVAST Software)

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.