Bad pool header [Résolu]

HelperWil 5 Messages postés dimanche 3 décembre 2017Date d'inscription 4 décembre 2017 Dernière intervention - 3 déc. 2017 à 20:55 - Dernière réponse :  HelperWil
- 9 déc. 2017 à 00:18
Salut. J'ai une erreur de BAD POOL HEADER et le rapport du minidump est a cet adresse http://www.cjoint.com/c/GLdtzrIhety.

voici un autre rapport du logiciel BlueScreenView

==================================================
Dump File : 120317-40046-01.dmp
Crash Time : 03/12/2017 16:53:48
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000020
Parameter 2 : fffffa80`05abe920
Parameter 3 : fffffa80`05abe940
Parameter 4 : 00000000`0402000a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a140
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a140
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\120317-40046-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 9200
Dump File Size : 284 728
Dump File Time : 03/12/2017 16:55:56
==================================================

Merci pour votre aide...
Afficher la suite 
5Messages postés dimanche 3 décembre 2017Date d'inscription 4 décembre 2017 Dernière intervention

8 réponses

Répondre au sujet
Malekal_morte- 143167 Messages postés mercredi 17 mai 2006Date d'inscriptionModérateurStatut 11 décembre 2017 Dernière intervention - 3 déc. 2017 à 21:08
0
Utile
2
Salut,

Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barettes de mémoire défectueuses ou incompatabilités, etc

Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.

plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-plantage-windows/

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

puis :

Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).

Télécharge et lance le scan FRST,
Attendre la fin du scan, un message indique que l'analyse est terminée.

Trois rapports FRST seront générés :
  • FRST.txt
  • Shortcut.txt
  • Additionnal.txt


Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ afin de les partager.
En retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.


HelperWil 5 Messages postés dimanche 3 décembre 2017Date d'inscription 4 décembre 2017 Dernière intervention - 3 déc. 2017 à 21:23
Voici le rapport de whocrashed


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

Computer name: VEHI
Windows version: Windows 8 , 6.2, build: 9200
Windows dir: C:\WINDOWS
Hardware: Aspire E1-431, Acer, EA40_HC
CPU: GenuineIntel Intel(R) Pentium(R) CPU B950 @ 2.10GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6269808640 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 03/12/2017 16:53:48 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120317-40046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A140)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8005ABE920, 0xFFFFFA8005ABE940, 0x402000A)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.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. This problem might also be caused because of overheating (thermal issue).
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 03/12/2017 16:53:48 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xB92F)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8005ABE920, 0xFFFFFA8005ABE940, 0x402000A)
Error: BAD_POOL_HEADER
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 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. This problem might also be caused because of overheating (thermal issue).
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 BAD_POOL_HEADER



On Sun 03/12/2017 16:51:50 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120317-40484-01.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 03/12/2017 14:07:04 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120317-38921-01.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 03/12/2017 14:01:49 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120317-39046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A140)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8005A96950, 0xFFFFFA8005A96970, 0x4020007)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

51 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has 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)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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 pour ton aide...
HelperWil 5 Messages postés dimanche 3 décembre 2017Date d'inscription 4 décembre 2017 Dernière intervention > HelperWil 5 Messages postés dimanche 3 décembre 2017Date d'inscription 4 décembre 2017 Dernière intervention - 3 déc. 2017 à 21:54
Commenter la réponse de Malekal_morte-
Malekal_morte- 143167 Messages postés mercredi 17 mai 2006Date d'inscriptionModérateurStatut 11 décembre 2017 Dernière intervention - 3 déc. 2017 à 21:31
0
Utile
1
Désinstalle Avast! et ça ira mieux.
Malekal_morte- 143167 Messages postés mercredi 17 mai 2006Date d'inscriptionModérateurStatut 11 décembre 2017 Dernière intervention - 3 déc. 2017 à 22:04
Il y a des programmes malveillants en plus :


Voici la correction à effectuer avec FRST. Tu peux t'aider de cette note explicative avec des captures d'écran.
Relance FRST puis sur ton clavier appuyer sur la touche CTRL + Y.
Le bloc-note va s'ouvrir, copie/colle ceci.

CreateRestorePoint:
CloseProcesses:
Task: C:\WINDOWS\Tasks\3d000a63-57f7-4f74-b509-d9377e9b51bc-10_user.job => C:\Program Files (x86)\Ge-Force\3d000a63-57f7-4f74-b509-d9377e9b51bc-10.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-1-7.job => C:\Program Files (x86)\Cinem Plus 2.4cV04.07\b7a8bc60-d211-4ed8-825e-696bd25346e8-1-7.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-10_user.job => C:\Program Files (x86)\Cinem Plus 2.4cV04.07\b7a8bc60-d211-4ed8-825e-696bd25346e8-10.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-3.job => C:\Program Files (x86)\Cinem Plus 2.4cV04.07\b7a8bc60-d211-4ed8-825e-696bd25346e8-3.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-4.job => C:\Program Files (x86)\Cinem Plus 2.4cV04.07\b7a8bc60-d211-4ed8-825e-696bd25346e8-4.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-5.job => C:\Program Files (x86)\Cinem Plus 2.4cV04.07\b7a8bc60-d211-4ed8-825e-696bd25346e8-5.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-5_user.job => C:\Program Files (x86)\Cinem Plus 2.4cV04.07\b7a8bc60-d211-4ed8-825e-696bd25346e8-5.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-7.job => C:\Program Files (x86)\Cinem Plus 2.4cV04.07\b7a8bc60-d211-4ed8-825e-696bd25346e8-7.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\cAzvdXdIVO.job => C:\Users\tokpa ali\AppData\Roaming\cAzvdXdIVO.exe <==== ATTENTION
Task: C:\WINDOWS\Tasks\Driver Booster SkipUAC (tokpa ali).job => C:\Program Files (x86)\IObit\Driver Booster\4.4.0\DriverBooster.exe
Task: C:\WINDOWS\Tasks\LAEQfBPoJfpL7GTLIqBulTsvm3.job => C:\Users\tokpa ali\AppData\Roaming\LAEQfBPoJfpL7GTLIqBulTsvm3.exe <==== ATTENTION
HKU\S-1-5-21-2591061271-2433318840-1904662066-1001\...\Run: [uTorrent] => C:\Users\tokpa ali\AppData\Roaming\uTorrent\uTorrent.exe [1982144 2017-10-31] (BitTorrent Inc.)
2017-11-12 13:42 - 2017-11-12 13:42 - 000000000 ____D C:\ProgramData\ByteFence
2017-12-03 18:24 - 2016-09-04 09:37 - 000000000 ____D C:\Program Files (x86)\Free Window Registry Repair
2017-12-03 17:31 - 2017-07-23 18:22 - 000000000 ____D C:\ProgramData\ProductData
2017-12-03 17:25 - 2016-09-03 16:20 - 000065536 _____ C:\WINDOWS\system32\Ikeext.etl
2015-07-04 16:35 - 2015-07-04 16:35 - 000176640 _____ () C:\Program Files (x86)\Common Files\343d7462-a4eb-4c66-a5ee-bc1600e178d8.dll
2015-04-14 16:28 - 2015-04-14 16:28 - 000004387 _____ () C:\Users\tokpa ali\AppData\Roaming\cAzvdXdIVO
2015-04-19 12:20 - 2016-04-16 07:19 - 000000626 _____ () C:\Users\tokpa ali\AppData\Roaming\LAEQfBPoJfpL7GTLIqBulTsvm3
2016-07-18 08:34 - 2016-07-18 08:34 - 000000600 _____ () C:\Users\tokpa ali\AppData\Roaming\winscp.rnd
2016-05-11 12:27 - 2016-09-09 21:30 - 000006144 _____ () C:\Users\tokpa ali\AppData\Local\DCBC2A71-70D8-4DAN-EHR8-E0D61DEA3FDF.ini
2016-05-14 08:51 - 2016-05-14 08:51 - 000000337 _____ () C:\Users\tokpa ali\AppData\Local\Perfmon.PerfmonCfg
2016-01-21 11:03 - 2016-02-22 17:33 - 000000600 _____ () C:\Users\tokpa ali\AppData\Local\PUTTY.RND
2016-11-18 01:33 - 2016-11-18 01:33 - 000000218 _____ () C:\Users\tokpa ali\AppData\Local\recently-used.xbel
2017-06-24 23:45 - 2017-06-24 23:45 - 000000000 _____ () C:\Users\tokpa ali\AppData\Local\{D88FBEAD-7D1D-49C9-847A-F6C02D516E25}
2017-12-03 16:55 - 2015-07-04 16:35 - 000002104 _____ C:\WINDOWS\Tasks\3d000a63-57f7-4f74-b509-d9377e9b51bc-10_user.job
2017-12-03 16:55 - 2015-07-04 16:26 - 000004512 _____ C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-4.job
2017-12-03 16:55 - 2015-07-04 16:26 - 000003156 _____ C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-1-7.job
2017-12-03 16:55 - 2015-07-04 16:26 - 000002464 _____ C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-5_user.job
2017-12-03 16:55 - 2015-07-04 16:26 - 000002464 _____ C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-5.job
2017-12-03 16:55 - 2015-07-04 16:25 - 000005536 _____ C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-7.job
2017-12-03 16:55 - 2015-07-04 16:25 - 000004176 _____ C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-3.job
2017-12-03 16:55 - 2015-07-04 16:25 - 000002130 _____ C:\WINDOWS\Tasks\b7a8bc60-d211-4ed8-825e-696bd25346e8-10_user.job
2017-12-03 16:55 - 2012-07-26 07:22 - 000000006 ____H C:\WINDOWS\Tasks\SA.DAT
2017-12-03 16:54 - 2017-03-17 06:51 - 000000000 ____D C:\WINDOWS\Minidump
2017-12-03 16:52 - 2016-09-22 23:07 - 000000745 _____ C:\WINDOWS\system32\Drivers\etc\hosts.ics
2017-12-03 16:52 - 2015-07-04 16:26 - 000001050 _____ C:\WINDOWS\Tasks\LAEQfBPoJfpL7GTLIqBulTsvm3.job
2017-12-03 16:52 - 2015-07-04 16:26 - 000001018 _____ C:\WINDOWS\Tasks\cAzvdXdIVO.job
Hosts:
EmptyTemp:
RemoveProxy:
Reboot:


Enregistre le contenu par le menu fichier puis enregistrer.

Ferme le bloc-note, retourne sur FRST et clique sur le bouton "Corriger / Fix"
Un redémarrage sera peut-être nécessaire et automatique.
Un fichier texte apparaît, copie/colle le contenu ici dans un nouveau message.

Redémarre l'ordinateur.


2°)
Réinitialise/Répare les navigateurs WEB concernés par les problèmes :

3°)
Termine par un nettoyage Malwarebytes - Tutoriel Malwarebytes Anti-Malware version gratuite
Commenter la réponse de Malekal_morte-
HelperWil 5 Messages postés dimanche 3 décembre 2017Date d'inscription 4 décembre 2017 Dernière intervention - 4 déc. 2017 à 16:13
0
Utile
2
Bonjour Malekal_morte. Je tiens a te dire merci pour tout. J'ai desinstaller Avast et je crois du moins aue le probleme est regler,
Encore merci et bonne continuation a toi,
Malekal_morte- 143167 Messages postés mercredi 17 mai 2006Date d'inscriptionModérateurStatut 11 décembre 2017 Dernière intervention - 4 déc. 2017 à 17:35
As-tu bien suivi toutes les étapes du nettoyage ?
Oui je crois et je constate depuis les differentes manip que m'a conseile que l'ordi est devenu un peu plus rapide.
Commenter la réponse de HelperWil