[Résolu] Plantage avec écran bleu sans message d'erreur

[Cécillette]

Ca y est, c'est fait. J'ai fait aussi un peu de tri dans msconfig. Tu penses qu'il y a autre chose à faire encore ou cette fois, c'est bon ?

Merci mille fois.

[bernard53]

Ok je pense que déjà c'est pas mal

 

A toi de me dire si de ton coté tu as du mieux s.t.p.

[Cécillette]

J'ai vu une nette différence après le nettoyage avec ZHPfix déjà. Ecoute, pour l'instant, je crois que ça va. Il ne me reste plus qu'à te remercier chaleureusement pour ton aide précieuse.

Modifié le 4 février 2012 par Cécillette

[bernard53]

Ok bonne nouvelle

 

 

Fait ceci pour supprimer les logiciels qui ont servis à cette désinfection.

 

Télécharge << DELFIX >> de Xplode pour supprimer les logiciels qui ont servis a cette désinfection.

 

 

Lance-le.

 

* A l'invite, [suppression] ()

 

* Un rapport va s'ouvrir à la fin, colle le dans la réponse

 

Ensuite pour le désinstaller ; tu relances et tu passes à l'option [Désinstallation]

 

Puis::

 

Maintenant on va mettre la restauration du système propre.

 

Cliquez avec le bouton droit sur l'icône Poste de travail, puis cliquez sur Propriétés

ou touche "Windows+Pause"

Cliquez sur l'onglet Restauration du système

 

Sélectionnez Désactiver la Restauration du système sur tous les lecteurs.

 

Cliquez sur Appliquer puis OUI dans la fenêtre suivante.

 

Attendre quelques instants puis :

 

activer la restauration du système de nouveau. en décochant la case que vous venez de cocher puis valider par Appliquer et OK

 

Maintenant on crée un nouveau point de restauration.

 

Démarrer—Exécuter—ou touche "Windows+R" et tapes:

%SystemRoot%\System32\restore\rstrui.exe

 

Puis coche " Créer un point de restauration" que tu nommes PC- Clean. Valide.

 

Vous pouvez maintenant fermer toutes les fenêtres.

 

 

Bon dimanche

[Cécillette]

J'ai fait comme tu as dit, voici le rapport :

 

# DelFix v8.7 - Rapport créé le 05/02/2012 à 13:30:04

# Mis à jour le 01/12/11 à 20h par Xplode

# Système d'exploitation : Microsoft Windows XP Service Pack 3 (32 bits)

# Nom d'utilisateur : cecile - CÉCILE (Administrateur)

# Exécuté depuis : C:\Documents and Settings\cecile\Local Settings\Temporary Internet Files\Content.IE5\WUL6EBLJ\delfix[1].exe

# Option [suppression]

 

 

~~~~~~ Dossiers(s) ~~~~~~

 

Supprimé : C:\ZHP

Supprimé : C:\Documents and Settings\All Users\Menu Démarrer\Programmes\ZHP

Supprimé : C:\Documents and Settings\All Users\Menu Démarrer\Programmes\Hijackthis

Supprimé : C:\Program Files\ZHPDiag

Supprimé : C:\Program Files\Hijackthis

 

~~~~~~ Fichier(s) ~~~~~~

 

Supprimé : C:\PhysicalDisk0_MBR.bin

Supprimé : C:\Documents and Settings\All Users\Bureau\ZHPDiag.lnk

Supprimé : C:\Documents and Settings\All Users\Bureau\ZHPFix.lnk

 

~~~~~~ Registre ~~~~~~

 

Clé Supprimée : HKLM\SOFTWARE\TrendMicro\Hijackthis

Clé Supprimée : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Hijackthis

Clé Supprimée : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ZHPDiag_is1

Clé Supprimée : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\HijackThis.exe

 

~~~~~~ Autres ~~~~~~

 

-> Prefetch Vidé

 

*************************

 

DelFix[R1].txt - [1375 octets] - [05/02/2012 13:27:24]

DelFix[s1].txt - [1342 octets] - [05/02/2012 13:30:04]

 

########## EOF - C:\DelFix[s1].txt - [1466 octets] ##########

 

C'est tout bon ?

Bon dimanche à toi aussi.

Modifié le 5 février 2012 par Cécillette

[Cécillette]

Help, ça recommence quand même... Que faire, docteur ? Merci.

[bernard53]

Help, ça recommence quand même... Que faire, docteur ? Merci.

Relance whocrashedSetup et mets moi le rapport s.t.p

[Cécillette]

Ok. Il y a un nouveau crash le 03/02. Merci !

 

 

Crash Dump Analysis

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

 

Crash dump directory: C:\WINDOWS\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Fri 03/02/2012 13:28:18 GMT your computer crashed

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

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

Bugcheck code: 0x19 (0x20, 0xFFFFFFFF82394600, 0xFFFFFFFF82394810, 0x1A42000D)

Error: BAD_POOL_HEADER

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

product: avast! Antivirus System

company: AVAST Software

description: avast! self protection module

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: aswsp.sys (avast! self protection module, AVAST Software).

Google query: aswsp.sys AVAST Software BAD_POOL_HEADER

 

 

 

 

On Tue 08/11/2011 20:51:40 GMT your computer crashed

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

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

Bugcheck code: 0x23 (0xE0100, 0xFFFFFFFFB9AE46C8, 0xFFFFFFFFB9AE43C4, 0xFFFFFFFFF843969A)

Error: FAT_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 that a problem occurred in the FAT 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 FAT_FILE_SYSTEM

 

 

 

 

On Tue 01/04/2008 21:34:02 GMT your computer crashed

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

This was probably caused by the following module: fastfat.sys (Fastfat+0xAA3)

Bugcheck code: 0xC2 (0x7, 0xCD4, 0x0, 0xFFFFFFFF823820A8)

Error: BAD_POOL_CALLER

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Fast FAT File System 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 which cannot be identified at this time.

 

 

On Tue 01/04/2008 10:22:24 GMT your computer crashed

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

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

Bugcheck code: 0x10000050 (0xFFFFFFFFBA32F010, 0x0, 0xFFFFFFFF805AD812, 0x0)

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 31/03/2008 11:06:31 GMT your computer crashed

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

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

Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8050037E)

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 30/03/2008 23:34:46 GMT your computer crashed

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

This was probably caused by the following module: swmidi.sys (Unloaded_swmidi.sys+0x8D00)

Bugcheck code: 0xC2 (0x7, 0xCD4, 0xFFFFFFFF82435B18, 0xFFFFFFFF821AADB0)

Error: BAD_POOL_CALLER

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Microsoft GS Wavetable Synthesizer

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

Google query: swmidi.sys Microsoft Corporation BAD_POOL_CALLER

 

 

 

 

On Sun 30/03/2008 22:18:30 GMT your computer crashed

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

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

Bugcheck code: 0x1000000A (0x0, 0x2, 0x0, 0xFFFFFFFF80500379)

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 Fri 28/03/2008 11:46:37 GMT your computer crashed

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

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

Bugcheck code: 0x1000000A (0x5, 0x2, 0x1, 0xFFFFFFFF80500380)

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 20/03/2008 00:59:11 GMT your computer crashed

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

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

Bugcheck code: 0x1000000A (0xA040005, 0x2, 0x1, 0xFFFFFFFF80500380)

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 17/03/2008 20:40:57 GMT your computer crashed

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

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

Bugcheck code: 0x1000000A (0xFFFFFFFFC3822CE8, 0x2, 0x1, 0xFFFFFFFF8050037E)

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 26/03/2007 21:21:01 GMT your computer crashed

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

This was probably caused by the following module: rtkhdaud.sys (RtkHDAud+0x4F6F)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFF5661F6F, 0xFFFFFFFFF8AC01FC, 0xFFFFFFFFF8ABFEF8)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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

product: Realtek® High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)

company: Realtek Semiconductor Corp.

description: Realtek® High Definition Audio Function Driver

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.

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: rtkhdaud.sys (Realtek® High Definition Audio Function Driver, Realtek Semiconductor Corp.).

Google query: rtkhdaud.sys Realtek Semiconductor Corp. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

 

 

 

 

 

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

Conclusion

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

 

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

 

rtkhdaud.sys (Realtek® High Definition Audio Function Driver, Realtek Semiconductor Corp.)

 

swmidi.sys (Microsoft GS Wavetable Synthesizer, Microsoft Corporation)

 

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

 

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.

 

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.

[bernard53]

encore Avast qui est une cause des soucis.

Le module self protection est en cause donc désactive le.

 

Faites un clic droit avast! icône de la barre - les paramètres du programme> -> «Dépannage» onglet -> check-«Désactiver avast! module self-defense "

 

comme ceci au besoin.

[resolu]aide pour grand nettoyage>rapport hijackthis - Forums Zebulon.fr

Par contre bizarre qu'il soit en cause

 

tu fait ceci en plus.

 

Pour XP:

 

1-Démarrer>exécuter> tapes cmd

 

puis chkdsk X: /f /r

 

 

X étant la lettre de ton DD qui doit être surement C.

 

mets bien un espace entre chkdsk et X: puis entre X: et /f puis entre /f et /r

 

Si ta lettre est le C tu as donc ceci chkdsk C: /f /r

 

- Windows affiche : type fichier NTFS : impossible de verrouiller le lecteur en cours

CHKDSK ne peut s'exécuter parce que le volume est utilisé par un autre processus.

Voulez vous que ce volume soit vérifier au prochain démarrage : Oui ou Non

Valider O et Redémarrer le pc.

 

PS: dis moi tu as AVAST en version payante pour avoir le Pare feu d'intégré. Tu as vérifier que le Pare feu de XP est bien désactivé?

Modifié le 7 février 2012 par bernard53

[Cécillette]

Oui, décidemment, ce Avast ! J'ai désactivé le module d'auto-défense. J'ai la version gratuite du logiciel donc j'utilise le pare-feu de Windows XP(activé donc)... Tu penses que c'est ça qui peut poser problème ?

 

Par contre, quand j'ai tapé "chkdsk C: /f /r ", il m'a parlé de fichiers FAT32 et non pas NTFS. Ca change quelque chose du coup ?