Votre question
Résolu

Écran bleu bad pool header

Tags :
  • Écran bleu
Dernière réponse : dans Systèmes d'exploitation
13 Juillet 2017 14:21:08

Bonjour,

Mon Pc refuse de s allumer en mode normal depuis hier..j ai a chaque fois un écran bleu avec l indication "bad pool header" et seul le mode sans échec fonctionne.

C est un alienware m17x4 avec win 7 home édition sp1.

Comme c est mon ordi pro j aimerai vraiment éviter de le.formater.

Les outils du site dell sont très bien mais le.site ne reconnaît pas.mon modèle en mode sans échec et je ne peux dl aucun pilote.

Aidez moi svp j ai vraiment besoin de mon ordi....

Merci d avance

Autres pages sur : ecran bleu bad pool header

13 Juillet 2017 18:28:16

salut,
commence par regarder si ce soft te dit quel pilote cause probleme et si tu le trouve, re-installe le:
www.resplendence.com/download/whocrashedSetup.exe

tu peux aussi verifier ton HD :
"sfc /scannow" c'est le Vérificateur de fichiers système
"chkdsk /f" pour la corruption HD
m
0
l
13 Juillet 2017 21:24:49

Merci pour ta réponse je regarde ça et reviens vers toi des que c est fini
m
0
l
Contenus similaires
13 Juillet 2017 21:45:14

Hello,

Voici ce que me donne ton logiciel :

On Thu 13/07/2017 21:38:55 your computer crashed
crash dump file: C:\Windows\Minidump\071317-16536-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA801AE0D9F0, 0xFFFFFA801AE0DA10, 0x4020017)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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 13/07/2017 21:38:55 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xB353)
Bugcheck code: 0x19 (0x20, 0xFFFFFA801AE0D9F0, 0xFFFFFA801AE0DA10, 0x4020017)
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 Thu 13/07/2017 01:36:43 your computer crashed
crash dump file: C:\Windows\Minidump\071317-18564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA801B037110, 0xFFFFFA801B037130, 0x4020011)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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 Wed 12/07/2017 23:09:23 your computer crashed
crash dump file: C:\Windows\Minidump\071217-17721-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA801A315170, 0xFFFFFA801A315190, 0x402000A)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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
--------------------------------------------------------------------------------

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

Je fais quoi ? J'essaie de désinstaller les fichiers "ntoskrnl.exe" etc..???

Merci pour ton aide !!
m
0
l

Meilleure solution

21 Juillet 2017 15:47:07

Bonjour, tu mets à jour tes drivers et tu désinstalles avast.
partage
Tom's guide dans le monde
  • Allemagne
  • Italie
  • Irlande
  • Royaume Uni
  • Etats Unis
Suivre Tom's Guide
Inscrivez-vous à la Newsletter
  • ajouter à twitter
  • ajouter à facebook
  • ajouter un flux RSS