[Résolu] Écran bleu à cause d'Avast

[jyrhunn]

salut à tous

 

j'espère que je suis sur le bon forum pour mon probléme , sinon dites le moi et je reposte ailleurs ..

 

Voilà , je me suis monté un PC bureautique avec du vieux matos :

 

* athlon 2000

* 1 Go de mémoire ( 2 barrettes de 512 )

* carte mére Gigabit GA-7VT600 1394

* 1DD seagate barracuda 80 Go ( esclave )

* 1DD maxtor diamond max 30 Go ( maitre )

 

le tout sous XP.

 

au début tout allait bien , mais depuis quelque temps , j'ai des message " la mémoire ne peut être read " suivi au bout de deux ou trois de ces messages d'un écran bleu me disant " vidage de la mémoire physique .

 

quelqu'un peut il m'aider la dessus ? Qu'est ce qui est en train de me lâcher ?

 

merci

@+

[Invité Notpa]

Bonjour jyrhunn,

 

Télécharge l'utilitaire WhoCrashed et exécute-le. Il va analyser le vidage mémoire et nous dire quel est le programme qui provoque cette erreur. En général (mais c'est à prouver), c'est dû à la carte graphique. Comme tu ne nous parle pas de celle-ci, donne-nous la marque, le type et vérifie que les drivers sont à jour.

 

Copie le résultat d'analyse de WhoCrsahed dans ta réponse.

 

A+

 

Notpa

[jyrhunn]

merci pour ta réponse notpa.

 

pour la carte video j'avais une elsa gladiac 511 ( nvidia ), du coup comme j'avais également une "ATI Radeon 7500 (RV200) (Gigabyte GV-AR64S-H)" dans un coin , je l'ai mise dedans à la place de la gladiac . Juste au cas où ce serait ça , je te tiens au courant pour le résulatat de la carte .

 

pour whocrash , voilà ce qu'il me dit , si tu peux en tirer quelque chose ... pour moi c'est un peu de l'hébreu !!!:

 

 

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\WINDOWS\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Tue 29/05/2012 13:23:08 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini052912-03.dmp

This was probably caused by the following module: aswsnx.sys (aswSnx+0x463CC)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFF4003B70, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\drivers\aswsnx.sys

product: avast! Antivirus System

company: AVAST Software

description: avast! Virtualization 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.

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 KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

 

 

 

 

On Tue 29/05/2012 13:18:41 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini052912-02.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5C876)

Bugcheck code: 0x19 (0x20, 0xFFFFFFFF85A5FF18, 0xFFFFFFFF85A5FFC0, 0xA150008)

Error: BAD_POOL_HEADER

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 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 which cannot be identified at this time.

 

 

On Tue 29/05/2012 9:58:24 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini052912-01.dmp

This was probably caused by the following module: aswsp.sys (aswSP+0x253CE)

Bugcheck code: 0x100000D0 (0xFFFFFFFFFF00FFFF, 0x2, 0x1, 0xFFFFFFFF8054A196)

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 28/05/2012 16:58:05 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini052812-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0x2A05)

Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE1113CC0, 0xFFFFFFFFE1113CE0, 0xC040404)

Error: BAD_POOL_HEADER

file path: C:\WINDOWS\system32\win32k.sys

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote Win32 multi-utilisateurs

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 Fri 25/05/2012 16:35:05 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini052512-01.dmp

This was probably caused by the following module: aswmon2.sys (aswMon2+0x7776)

Bugcheck code: 0x10000050 (0xFFFFFFFF94A4955D, 0x0, 0xFFFFFFFF94A4955D, 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 Sun 20/05/2012 16:03:29 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini052012-02.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7D1C)

Bugcheck code: 0x1000000A (0x4, 0xFF, 0x1, 0xFFFFFFFF804DED1C)

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 20/05/2012 12:31:25 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini052012-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7D1C)

Bugcheck code: 0x1000000A (0x4, 0xFF, 0x1, 0xFFFFFFFF804DED1C)

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.

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

7 crash dumps have been found and analyzed. 3 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:

 

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

 

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

 

aswsnx.sys (avast! Virtualization 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.

[jyrhunn]

pour info , j'ai les mêmes symtôme avec la radeon 7500 que je viens d'installer ...

[Invité Notpa]

Re,

 

Résultat de WhoCrashed :

 

7 crash dumps have been found and analyzed. 3 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:

 

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

 

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

 

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

 

Fautif : Avast.

 

Problème déjà traité par l'ami Bleuet ---> ici

 

Resté sans réponse du demandeur. Suis les instructions de Bleuet. Éventuellement, désinstalle Avast, nettoie tout avec CCleaner, puis ré-installe la dernière version d'Avast si tu veux conserver ce programme comme antivirus.

 

Petite rectification : j'ai déplacé ton sujet dans le forum Software (plus approprié que hardware), et modifié légèrement le titre : Écran bleu à cause d'Avast, titre plus précis.

 

A+

Notpa

[jyrhunn]

bon j'ai réglé le problème de façon ... radical.

 

j'ai desinstallé Avast et du coup j'avais 10 fois plus d'écran bleu ( le PC n'avait même plus le temps de démarer ) , donc j'en ai profité , j'ai changer la carte mére .

 

Bon il faut préciser que comme l'autre carte mére ( l'ancienne ) était vraiment ancienne il m'a fallut également un nouveau processeur pour aller dessus , ah oui la mémoire a dû être changé aussi ainsi que la carte video.

 

bon en fait je n'ai gardé que le boitier ... j'espère que les écrans bleu sont partis avec le reste des pieces!!!

 

@+

[Dylav]

J'espère que les écrans bleu sont partis avec le reste des pièces !

Moi aussi… sinon il faudrait incriminer le boîtier… et là, tu finirais avec un ordinateur entièrement neuf !

[Invité Notpa]

Et bien, la méthode est radicale ! Heureusement que tous les BSOD ne se règlent pas comme ça !

 

Bonne continuation avec ton PC relooké à neuf !

Cordialement

Notpa