Les fameux ecrans bleus de la mort qui tue...

Bonjour,

J ai un problème avec mon ordi: assez fréquemment j ai de jolies écrans bleus qui apparaissent régulièrement c'est bien joli 5mn mais au bout du 10eme, on s en lasse vite!

Après un scan d'Avast et de Malware, aucun des 2 ne trouvent de virus.

Les écrans bleus apparaissent généralement quand je joue à des gros jeux PC (à tous les coups en général dans les 5mns après le débuts du jeu) ou lorsque je regarde des vidéos (c est plus aléatoire dans ce cas là).
Hier, ça m est arrivé en jouant à un jeu flash sur le net, et juste avant que ca plante j ai eut le droit à un message disant "Le plugin flash a planté" et quand j ai rafraichi la page... Ecran bleu! Et dans les heures qui ont suivi quoi que je fasse j avais rapidement soit un écran bleu soit l image se figeait...

Voila le rapport de Whocrashed

windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Phenom(tm) 9650 Quad-Core Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 3488854016 total
VM: 2147352576, free: 2033782784

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 03/04/2012 12:23:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040312-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x8F, 0x89CB0, 0x89C00, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 which cannot be identified at this time.

On Tue 03/04/2012 12:20:11 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3933B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8051033B, 0xFFFFFFFFAF032A44, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 which cannot be identified at this time.

On Mon 02/04/2012 21:24:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-07.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFAF0788D4)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF80520FB3, 0xFFFFFFFFAF078C00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
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: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

On Mon 02/04/2012 21:22:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-06.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0xAB7)
Bugcheck code: 0x10000050 (0xFFFFFFFFD52C0000, 0x0, 0xFFFFFFFF80569408, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software CUSTOM_ERROR

On Mon 02/04/2012 21:12:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-05.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xBBAC)
Bugcheck code: 0x1000000A (0x10, 0x2, 0x1, 0xFFFFFFFF805229DF)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys AVAST Software CUSTOM_ERROR

On Mon 02/04/2012 20:58:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-04.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xBBAC)
Bugcheck code: 0x1000000A (0x10, 0x2, 0x1, 0xFFFFFFFF805229DF)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys AVAST Software CUSTOM_ERROR

On Mon 02/04/2012 20:47:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2A79D)
Bugcheck code: 0x1000000A (0x535151F1, 0x2, 0x1, 0xFFFFFFFF80514068)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Mon 02/04/2012 20:35:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B718)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF80522718)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 02/04/2012 20:31:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040212-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74950)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFFFF8054B950, 0xFFFFFFFFB84FBC6C, 0xFFFFFFFFB84FB968)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 30/03/2012 11:41:26 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini033012-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B718)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF80522718)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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/03/2012 22:10:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini033012-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0xAB7)
Bugcheck code: 0x1000000A (0xC8, 0x2, 0x0, 0xFFFFFFFF8051563F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software CUSTOM_ERROR

On Mon 19/03/2012 21:41:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031912-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1D255)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF80522718)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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: aswsnx.sys AVAST Software CUSTOM_ERROR

On Sun 18/03/2012 22:56:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-12.dmp
This was probably caused by the following module: dxg.sys (dxg+0x745)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFFBD000745, 0xFFFFFFFFAE259C00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxg.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Driver
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 Sun 18/03/2012 16:18:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-11.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B9DF)
Bugcheck code: 0x1000000A (0x10, 0x2, 0x1, 0xFFFFFFFF805229DF)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 18/03/2012 16:13:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-10.dmp
This was probably caused by the following module: ksecdd.sys (KSecDD+0x89D0)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFEC, 0x0, 0xFFFFFFFF8053684C, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ksecdd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Security Support Provider Interface
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.

The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini040312-02.dmp

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

On your computer a total of 29 crash dumps have been found. Only 28 could be analyzed. Only 15 are included in this report. 13 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)

nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 177.83 , NVIDIA Corporation)

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)

unknown

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.

Une remarque, je constate quand même que plusieurs des écran bleu dû à Avast ont eut lieu juste avant que mon ordi me dise que la mise a jour de la base viral d Avast a été mis à jour.
Du coup j ai plusieurs questions:
Avast a l'air d'être à l'origine du problème, mais ça me paraît quand meme étrange. Comment peut il faire ça? Le problème n est-il pas ailleurs et Avast et d autres choses ne feraient que le déclenchait? Et puis apparemment il n a pas l'air d'être la seul source des écrans bleus...
Si je désinstalle Avast y a t il une chance que cela résolve le problème? En cas de désinstallation d'Avast que devient les virus mis en quarantaine? Si je désinstalle, est ce que je peux réinstaller Avast ou il faut que je fasse une croix dessus?

Qu en pensez-vous? J aurai bien besoin d un coup de main!

En remerciant par avance tout ceux qui veulent bien m aider.