Bad pool header écran bleu

Résolu/Fermé
clemclem337 Messages postés 7 Date d'inscription lundi 7 août 2017 Statut Membre Dernière intervention 16 août 2017 - 7 août 2017 à 13:09
clemclem337 Messages postés 7 Date d'inscription lundi 7 août 2017 Statut Membre Dernière intervention 16 août 2017 - 16 août 2017 à 01:59
Salut ! :)

Après avoir consulté pas mal de forums, je viens vers vous car je ne sais pas quoi faire. A chaque démarrage l'écran bleu bad pool header apparait pendant le chargement du bureau. J'ai fait une restauration, lancé malwarebytes mais rien n'y fait. J'ai cru comprendre en lisant sur les forums qu'il fallait lancer des "rapports" mais je ne sais pas du tout comment les interpréter.

Si quelqu'un peut m'aider ça serait super ! Merci d'avance :)
A voir également:

4 réponses

Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 24 644
7 août 2017 à 13:50
Salut,

Utilise Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

~

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/ et 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.

2
clemclem337 Messages postés 7 Date d'inscription lundi 7 août 2017 Statut Membre Dernière intervention 16 août 2017
8 août 2017 à 13:58
Salut, merci pour ta rapidité !

Voici le premier rapport :


--------------------------------------------------------------------------------
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: PROPRIETAIREPC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: Satellite L655, TOSHIBA, Portable PC
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4151148544 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 07/08/2017 13:55:52 your computer crashed
crash dump file: C:\Windows\Minidump\080717-24804-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007F4CC00, 0xFFFFFA8007F4CC20, 0x402001A)
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 Mon 07/08/2017 13:55:52 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, 0xFFFFFA8007F4CC00, 0xFFFFFA8007F4CC20, 0x402001A)
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 Mon 07/08/2017 11:27:21 your computer crashed
crash dump file: C:\Windows\Minidump\080717-23649-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007EEAC00, 0xFFFFFA8007EEAC20, 0x402000C)
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 Fri 04/08/2017 17:37:25 your computer crashed
crash dump file: C:\Windows\Minidump\080717-26910-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007E02490, 0xFFFFFA8007E024B0, 0x402000C)
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 Thu 03/08/2017 23:19:05 your computer crashed
crash dump file: C:\Windows\Minidump\080417-23774-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008219280, 0xFFFFFA80082192A0, 0x4020008)
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
--------------------------------------------------------------------------------

9 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.
0
clemclem337 Messages postés 7 Date d'inscription lundi 7 août 2017 Statut Membre Dernière intervention 16 août 2017
8 août 2017 à 14:02
0