Aide lecture rapport WhoCrashed

[Morgane]

Bonjour, j'ai depuis longtemps le problème "Bluescreen", j'ai téléchargé whocrashed, j'ai fais une analyse, mais je n'y comprends rien,je ne suis pas une pro de l'informatique alors je viens vous demander votre aide pour n'aider à déchiffrer ce rapport.

System Information (local)
--------------------------------------------------------------------------------

computer name: PC
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Celeron(R) CPU 420 @ 1.60GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 938299392 total
VM: 2147352576, free: 2004230144

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 18/10/2012 14:33:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101812-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x8CAE)
Bugcheck code: 0x50 (0xFFFFFFFFD007A068, 0x0, 0xFFFFFFFF8D865CAE, 0x2)
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 Thu 18/10/2012 14:33:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1251C)
Bugcheck code: 0x50 (0xFFFFFFFFD007A068, 0x0, 0xFFFFFFFF8D865CAE, 0x2)
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 Thu 18/10/2012 14:16:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101812-01.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x3315)
Bugcheck code: 0xD1 (0xB, 0x2, 0x0, 0xFFFFFFFF8D047315)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswtdi.sys
product: avast! Antivirus
company: AVAST Software
description: avast! TDI Filter 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: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 14/10/2012 17:47:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101512-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98339)
Bugcheck code: 0x1A (0x41287, 0x16E87B64, 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 that cannot be identified at this time.



On Sun 14/10/2012 17:41:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101412-05.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AFA7)
Bugcheck code: 0x1 (0xFFFFFFFF848506D6, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 14/10/2012 17:32:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101412-04.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x8F574)
Bugcheck code: 0xA (0x1A0AAFFB, 0x2, 0x0, 0xFFFFFFFF846F3857)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 14/10/2012 16:57:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101412-03.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1089)
Bugcheck code: 0xD1 (0x2DF39A71, 0x2, 0x0, 0xFFFFFFFF857AA089)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 that cannot be identified at this time.



On Sun 14/10/2012 16:57:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101412-02.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Sun 14/10/2012 16:45:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101412-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x19FFF)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFFC97E7988, 0xFFFFFFFFC97E7684, 0xFFFFFFFF846E9877)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sat 13/10/2012 17:05:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101312-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)
Bugcheck code: 0xA (0xFFFFFFFF9458EA7C, 0x2, 0x1, 0xFFFFFFFF846BC4F8)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 13/10/2012 07:13:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101312-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)
Bugcheck code: 0xA (0x4A650EDC, 0x1B, 0x1, 0xFFFFFFFF846BFF4A)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Fri 12/10/2012 14:07:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101212-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98339)
Bugcheck code: 0x50 (0xFFFFFFFFFD7A73C1, 0x0, 0xFFFFFFFF846F551F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 11/10/2012 12:54:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101112-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AFA7)
Bugcheck code: 0x1 (0xFFFFFFFF8483E6D6, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 11/10/2012 11:31:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101112-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x2C339)
Bugcheck code: 0x50 (0xFFFFFFFF89324AC3, 0x8, 0xFFFFFFFF89324AC3, 0x2)
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 Thu 11/10/2012 11:17:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101112-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2631E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8463631E, 0xFFFFFFFFAC7E9994, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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.


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

32 crash dumps have been found and analyzed. Only 15 are included in this report. 4 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:

aswsp.sys (avast! self protection module, AVAST Software)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
aswrdr.sys (avast! TDI Redirect Driver, AVAST Software)
aswtdi.sys (avast! TDI Filter Driver, 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.

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.

Merci d'avance

[bernard53]

Bonsoir
Déjà tu as plusieurs du à AVAST donc tu le désinstalle proprement via leur désinstallateur.
http://www.avast.com/fr-fr/uninstall-utility

Ensuite nouvelle installe.
http://www.avast.com/fr-fr/free-antivirus-download

[Morgane]

Merci beaucoup pour votre réponse, j'ai fais ce que vous m'avez écrit en espérant avoir moins de "bluescreen".

[bernard53]

Remets un nouveau rapport whocrashed si cela se reproduit.

[EinsteinZero]

Je reviens vers vous, car mon problème ne m'a malheureusement pas quitté, j'ai toujours énormément de bluescreen, parfois mon ordinateur est à peine rallumé qu'il re-plante aussitôt, je ne sais plus quoi faire. On m'a dit que cela pourrait peut-être du à un manque de RAM, mais bon je n'y connais rien.

Code: Tout sélectionner

System Information (local)
--------------------------------------------------------------------------------

computer name: PC
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Celeron(R) CPU 420 @ 1.60GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 938299392 total
VM: 2147352576, free: 2004021248




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 15/11/2012 16:05:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111512-06.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x8CAE)
Bugcheck code: 0x50 (0xFFFFFFFFB9813C1F, 0x0, 0xFFFFFFFF8DA65CAE, 0x2)
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 Thu 15/11/2012 16:05:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1251C)
Bugcheck code: 0x50 (0xFFFFFFFFB9813C1F, 0x0, 0xFFFFFFFF8DA65CAE, 0x2)
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 Thu 15/11/2012 15:55:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111512-05.dmp
This was probably caused by the following module: hal.dll (hal+0x3FF9)
Bugcheck code: 0xA (0x5E864C55, 0x2, 0x1, 0xFFFFFFFF849C7FF9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Thu 15/11/2012 15:45:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111512-04.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8811E958, 0xFFFFFFFF8811F418, 0x1958D9E9)
Error: BAD_POOL_HEADER
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 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 Thu 15/11/2012 14:10:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111512-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)
Bugcheck code: 0xA (0xFFFFFFFFEEF2BFD1, 0x2, 0x0, 0xFFFFFFFF84688505)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Thu 15/11/2012 13:40:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111512-02.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x47F2)
Bugcheck code: 0x35 (0xFFFFFFFF8843A968, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This bug check occurs when the IoCallDriver packet has no more stack locations remaining.
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 13/11/2012 19:47:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111512-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17910)
Bugcheck code: 0x50 (0xFFFFFFFFCB8020E2, 0x0, 0xFFFFFFFF846E7034, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA



On Mon 12/11/2012 16:39:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111212-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)
Bugcheck code: 0xA (0xFFFFFFFF919B39DE, 0x2, 0x0, 0xFFFFFFFF846D051F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 12/11/2012 13:35:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111212-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x7DCA0)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x104946A7, 0xFFFFFFFF880F09A0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP 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.



On Mon 12/11/2012 13:02:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111212-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AFA7)
Bugcheck code: 0x1 (0xFFFFFFFF8484A6D6, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 11/11/2012 15:05:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111112-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x10F64)
Bugcheck code: 0x50 (0xFFFFFFFFF238A3E7, 0x0, 0xFFFFFFFF8DC6FF64, 0x2)
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 Sun 11/11/2012 14:49:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111112-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)
Bugcheck code: 0xA (0xFFFFFFFF8D03CA81, 0x1B, 0x0, 0xFFFFFFFF846F8275)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 10/11/2012 17:53:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111012-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB251F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF846C051F, 0xFFFFFFFFA693AC04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Thu 08/11/2012 09:53:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110812-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x10F64)
Bugcheck code: 0x50 (0xFFFFFFFFEF55FB5D, 0x0, 0xFFFFFFFF8D670F64, 0x2)
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 Wed 07/11/2012 11:45:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110712-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98339)
Bugcheck code: 0x50 (0xFFFFFFFFCF7D718B, 0x0, 0xFFFFFFFF84894F7F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

52 crash dumps have been found and analyzed. Only 15 are included in this report. 4 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:

aswsp.sys (avast! self protection module, AVAST Software)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
aswrdr.sys (avast! TDI Redirect Driver, AVAST Software)
aswtdi.sys (avast! TDI Filter Driver, 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.

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.

Merci d'avance

[EinsteinZero]

Bonsoir

Message technique de la modération

j'ai ajouté des balises "code" sur le rapport car la longueur du message le rendait peu lisible...

[bernard53]

Bonjour
Morgane fait ceci s.t.p
1- vérifies que le pc ne chauffe pas avec speccy .
http://www.piriform.com/speccy

Teste les barrettes mémoires:
http://www.commentcamarche.net/download ... -memtest86

[Morgane]

Bonjour,
Merci pour votre aide, voila le rapport de Speccy

Système d'exploitation
Microsoft Windows Vista Édition Familiale Basique 32-bit SP2
Processeur
Intel Celeron 420 @ 1.60GHz 57 °C
Technologie Conroe-L 65nm
RAM
1,00 Go Canal-Simple DDR2 @ 333 MHz (5-5-5-15)
Carte mère
Acer F671CR (Socket 775) 36 °C
Graphiques
W2243 (1280x1024@1Hz)
Carte graphique VGA standard
Disques durs
149 Go FUJITSU MAXTOR STM3160215AS ATA Device (SATA) 39 °C
Disques optiques
HL-DT-ST DVD-RW_GSA-H41N ATA Device
Audio
Périphérique High Definition Audio

RAM
Emplacements mémoire
Nombre d'emplacements mémoire 2
Emplacements mémoire utilisés 2
Emplacements mémoire libres 0
Mémoire
Type DDR2
Taille 1024 Mo
Canal # Simple
Fréquence DRAM 333.4 MHz
Latence CAS# (CL) 5 horloges
Délai RAS# vers CAS# (tRCD) 5 horloges
Précharge RAS# (tRP) 5 horloges
Temps de cycle (tRAS) 15 horloges
Mémoire physique
Utilisation mémoire 78 %
Total (physique) 894 Mo
Disponible (physique) 190 Mo
Total (virtuelle) 2.00 Go
Disponible (virtuelle) 1.10 Go
SPD
Nombre de modules SPD 2
Emplacement #1
Emplacement #2

Je n'arrive pas à tester mes barrettes de mémoires avec l'autre lien.

[Pac428]

Bonjour Morgane

Pour Memtest :

Le Fichier est une Iso il faut donc la graver sur un CD avec un logiciel de gravure.
Vous pouvez ensuite lancer le logiciel via votre lecteur DVD/CD au démarrage de votre pc

To as bien fait ça ? Le fichier est bien gravé en tant que ISO par ton logiciel ?

Question "idiote" : tu as bien un graveur de CD/DVD sur ton PC ? c'est un Aspire M1600 ou dans le genre ?

++

[bernard53]

Température OK pour le pc

[Grego]

Bonjour ici, Bonjour Pac428 content de te retrouver ici

On à toujours le droit de faire des paries ici ?

Moi je vote pour un double anti virus installé sur l'ordinateur

Mais comme je suis en pleine réinstallation moi même et que j'ai juste 2 ans de retard sur les logiciels, je pense que c'est Pac428 qui va nous expliquer comment Morgane va pouvoir nous afficher la liste complète des processus en cours d'utilisation sur son ordi ^^

[Pac428]

Salut Mangouin !

Un plaisir de te retrouver