Plantage écran bleu

[Invité louiswing]

Bonjour

Mon PC (XP ) plante régulièrement, avec différnts messages dans ecrans bleus.

Le rapport "whocrashed" est le suivant:

 

Est réparable? cela provient d'Avast ou de pb drivers? Qiue faire?

Merci de votre aide

 

Rapport:

System Information (local)

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

 

computer name: BUREAU

windows version: Windows XP Service Pack 3, 5.1, build: 2600

windows dir: C:\WINDOWS

CPU: GenuineIntel Intel® Pentium® 4 CPU 3.00GHz Intel586, level: 15

2 logical processors, active mask: 3

RAM: 2682961920 total

VM: 2147352576, free: 2039848960

 

 

 

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

Crash Dump Analysis

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

 

Crash dump directory: C:\WINDOWS\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Wed 14/09/2011 06:38:17 GMT your computer crashed

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

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

Bugcheck code: 0x1000000A (0x0, 0x1C, 0x1, 0xFFFFFFFF804E1C18)

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 Wed 14/09/2011 06:29:03 GMT your computer crashed

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

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

Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE1261130, 0xFFFFFFFFE1261178, 0xC090802)

Error: BAD_POOL_HEADER

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

product: avast! Antivirus System

company: AVAST Software

description: avast! File System Filter Driver for Windows XP

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.

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 BAD_POOL_HEADER

 

 

 

 

On Mon 12/09/2011 07:54:45 GMT your computer crashed

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

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

Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFAA58E550, 0xFFFFFFFFAA58E24C, 0xFFFFFFFF80702AA0)

Error: NTFS_FILE_SYSTEM

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

product: avast! Antivirus System

company: AVAST Software

description: avast! File System Filter Driver for Windows XP

Bug check description: This indicates a problem occurred in the NTFS file system.

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 NTFS_FILE_SYSTEM

 

 

 

 

On Mon 12/09/2011 07:51:42 GMT your computer crashed

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

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

Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFABD18514, 0xFFFFFFFFABD18210, 0xFFFFFFFF80551171)

Error: NTFS_FILE_SYSTEM

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

product: avast! Antivirus System

company: AVAST Software

description: avast! File System Filter Driver for Windows XP

Bug check description: This indicates a problem occurred in the NTFS file system.

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 NTFS_FILE_SYSTEM

 

 

 

 

On Mon 12/09/2011 07:49:49 GMT your computer crashed

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

This was probably caused by the following module: ntfs.sys (Ntfs+0x22E4F)

Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE12C9000, 0xFFFFFFFFE12C90E8, 0xC1D0200)

Error: BAD_POOL_HEADER

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

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 Sun 11/09/2011 16:22:04 GMT your computer crashed

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

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

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8057D764, 0xFFFFFFFFA7814660, 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

 

 

 

 

 

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

Conclusion

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

 

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

 

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

 

aswmon2.sys (avast! File System Filter Driver for Windows XP, 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.

[bleuet]

Salut !

 

 

Il semblerait que la cause principale est Avast.

 

ntoskrnl.exe est repéré aussi au début.(processus critique de Windows XP servant au démarrage (boot-up) de Microsoft Windows).

 

 

Suggestions :

Analyser ntoskrnl.exe >

Analyse en ligne d'un fichier système avec VIRUS TOTAL:

 

• Ouvrir le site Virus Total .
  
• Utiliser l'onglet "Analysis" / "Upload a file" :
  
• Par "Parcourir" récupérer le fichier suspect.
  
• Clic sur "Send file". Patienter....
  
• A la nouvelle fenêtre, à la question en bas "What do you wish to do ?" (que voulez-vous faire ?) clic sur "Reanalyse".
  
• Laisser travailler VirusTotal. La liste d'analyse se constitue.
  A la fin de l'analyse le résultat s'affiche: Result: 0 / 44 (0.0%) ou le % trouvé.(dans la colonne "Result").
  
• Copier/coller l'adresse de la page.

 

En attente du résultat.

 

En fonction, éventuellement désinstaller Avast, nettoyer et le ré installer.

 

Sous réserve de possibles infections, à apprécier en dernier.

 

 

Bonne journée.bleuet[14/09/2011)

[Invité Louiswing]

Merci de votre aide

 

J ai trouvé au moins 8 fichiers ntoskrnl.exe sur mon disque, dans le répertoire windows.

J ai fait le scan pour celui qui me paraissait le plus opérant (dans system32.

Ci après la réponse..rien d'anormal a priori?

Faut il faire un scan de tous les fichiers nommés ainsi?

 

Merci

 

Complete scanning result of "ntoskrnl.exe", processed in VirusTotal at 09/14/2011 20:55:11 (CET).

 

[ file data ]

* name..: ntoskrnl.exe

* size..: 2150912

* md5...: e8de6ca43363b663645ae4639f2f41d6

* sha1..: 1bf3e4eb017a68a81a926e069e74e04140e92eb0

* peid..: -

 

[ scan result ]

AhnLab-V3 2011.09.14.00/20110914 found nothing

AntiVir 7.11.14.204/20110914 found nothing

Antiy-AVL 2.0.3.7/20110914 found nothing

Avast 4.8.1351.0/20110914 found nothing

Avast5 5.0.677.0/20110914 found nothing

AVG 10.0.0.1190/20110914 found nothing

BitDefender 7.2/20110914 found nothing

ByteHero 1.0.0.1/20110913 found nothing

CAT-QuickHeal 11.00/20110914 found nothing

ClamAV 0.97.0.0/20110914 found nothing

Commtouch 5.3.2.6/20110914 found nothing

Comodo 10112/20110914 found nothing

DrWeb 5.0.2.03300/20110914 found nothing

Emsisoft 5.1.0.11/20110914 found nothing

eSafe 7.0.17.0/20110914 found nothing

eTrust-Vet 36.1.8560/20110914 found nothing

F-Prot 4.6.2.117/20110914 found nothing

F-Secure 9.0.16440.0/20110914 found nothing

Fortinet 4.3.370.0/20110914 found nothing

GData 22/20110914 found nothing

Ikarus T3.1.1.107.0/20110914 found nothing

Jiangmin 13.0.900/20110914 found nothing

K7AntiVirus 9.113.5133/20110914 found nothing

Kaspersky 9.0.0.837/20110914 found nothing

McAfee 5.400.0.1158/20110914 found nothing

McAfee-GW-Edition 2010.1D/20110914 found nothing

Microsoft 1.7604/20110914 found nothing

NOD32 6464/20110914 found nothing

Norman 6.07.11/20110914 found nothing

nProtect 2011-09-14.01/20110914 found nothing

Panda 10.0.3.5/20110914 found nothing

PCTools 8.0.0.5/20110914 found nothing

Prevx 3.0/20110914 found nothing

Rising 23.74.03.03/20110909 found nothing

Sophos 4.69.0/20110914 found nothing

SUPERAntiSpyware 4.40.0.1006/20110914 found nothing

Symantec 20111.2.0.82/20110914 found nothing

TheHacker 6.7.0.1.296/20110914 found nothing

TrendMicro 9.500.0.1008/20110914 found nothing

TrendMicro-HouseCall 9.500.0.1008/20110914 found nothing

VBA32 3.12.16.4/20110914 found nothing

VIPRE 10474/20110914 found nothing

ViRobot 2011.9.14.4668/20110914 found nothing

VirusBuster 14.0.212.0/20110914 found nothing

[bleuet]

 

Peut être rien à voir mais ça donnera déjà un point de repère. Peux-tu stp ?

 

 

A TITRE PREVENTIF

 

Télécharger ZHPdiag

 

/!\Il est très important de l'enregistrer sur le bureau / !\

 

Une fois téléchargé, Une icône apparaitra alors sur le bureau.

Ouvrir alors ce fichier, (clic droit exécuter en tant qu'administrateur pour Vista/W 7) pour lancer le programme d'assistant d'installation.

Installer le avec les paramètres par défaut sans oublier de cocher la case "Créer une icône sur le bureau"

Lancement et diagnostic :

Une fois installé si le logiciel ne se lance pas tout seul, double clic sur le raccourci qui se sera créé sur le bureau (clique droit, exécuter en tant qu'administrateur pour VISTA/ W 7)

En même temps que ZHPDiag, sont créés les icônes de ZHPFix et MBRCheck qui peuvent être utilisés.(Ces programmes se retrouvent dans le dossier programme ZHPDiag).

• Cliquer sur la flèche verte pour sa mise à jour.S'il est à jour, message > "votre version est à jour".
  
• Cliquer alors sur la loupe pour lancer le diagnostic.
  Patientez jusqu'à la fin de l'analyse. Il peut arriver que le logiciel donne l'impression d'être bloqué ; patienter.
  En cas de blocage sur la section O80, cliquer sur le tournevis pour le décocher.
  
• Le diagnostic terminé,sauvegarder le rapport sur le Bureau en cliquant sur la disquette bleue.
  
• Enregistrer le rapport sur le bureau affin de le retrouver plus facilement

Puis l' héberger comme suit (le rapport risque d'être très long) :

 

A partir de ce lien : www.cijoint.fr

 

ou celui-ci si le précédent est en erreur.

 

cjoint.com

 

Sur la page qui s'ouvre :

• Cliquer sur "Parcourir" dans la partie "Sélectionnez le fichier que vous souhaitez déposer"
  
• Sélectionner le rapport ZHPdiag.txt qui se trouve sur le Bureau
  
• Cliquer ensuite sur " Cliquez ici pour déposer le fichier ". Un lien va se former.

 

Il ne reste plus qu'à copier/coller ce lien sur le forum.

 

Note : ZHPDiag une fois installé, vérifier sa dernière mise à jour avec la grosse flèche verte.

 

 

Bonne journée.bleuet[15/09/2011)