Ecran bleu "BAD_POOL_HEADER" Windows 8

[Necritia]

Salut tout le monde,
Il y a 4 jours, j'ai reçus mon PC portable acheté sur Amazon (Toshiba Satellite P50-C) mai très rapidement, j'ai commencé a avoir des écrans bleus avec erreur BAD_POOL_HEADER puis le PC redémarre.
Savez vous d'ou cela peut il venir ? ca arrive aléatoirement.
J'ai W8.1 comme OS
Merci

[EinsteinZero]

Bonjour
il s'agit probablement d'un souci de pilote
il serait intéressant que tu lance Whocrashed >>ici sur external mirror 1<< afin d'avoir accès au info sur les crash....
c'est un logiciel sans installation
tu lance le logiciel et tu fais un copié coller du rapport

[Necritia]

Salut, merci pour la reponse rapide.

Voila le rapport:

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 13/09/2015 13:40:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091315-26000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0x19 (0x21, 0xFFFFE0002DC8D000, 0x3200, 0xFFFFFFFFFFFFFFFF)
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.
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 13/09/2015 13:40:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ngvss.sys (ngvss+0x11F6B)
Bugcheck code: 0x19 (0x21, 0xFFFFE0002DC8D000, 0x3200, 0xFFFFFFFFFFFFFFFF)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ngvss.sys
product: Avast NG
company: AVAST Software
description: avast! NG snapshot 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.
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: ngvss.sys (avast! NG snapshot driver, AVAST Software).
Google query: AVAST Software BAD_POOL_HEADER



On Sun 13/09/2015 12:58:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091315-27515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0x19 (0x21, 0xFFFFE0008C0A2000, 0x3200, 0xFFFFFFFFFFFFFFFF)
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.
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 13/09/2015 11:44:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091315-33875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0x21, 0xFFFFE0003B83E000, 0x3200, 0xFFFFFFFFFFFFFFFF)
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.
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 13/09/2015 09:05:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091315-19984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0x21, 0xFFFFE001BA17B000, 0x3200, 0xFFFFFFFFFFFFFFFF)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12/09/2015 10:38:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091215-16875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0x21, 0xFFFFE0011F00E000, 0x3200, 0xFFFFFFFFFFFFFFFF)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12/09/2015 10:19:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091215-19656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0x21, 0xFFFFE001B34F7000, 0x3200, 0xFFFFFFFFFFFFFFFF)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12/09/2015 10:03:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091215-28921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0x21, 0xFFFFE00173355000, 0x3200, 0xFFFFFFFFFFFFFFFF)
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.
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 10/09/2015 13:43:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091015-46828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0x21, 0xFFFFE0005F3EB000, 0x3200, 0xFFFFFFFFFFFFFFFF)
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.
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. 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:

ngvss.sys (avast! NG snapshot driver, 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.

[routman54]

Bonjour ,
Traduction en français :

9 vidages ont été trouvés et analysés. Un pilote tiers a été désignée pour être la cause de pannes du système sur votre ordinateur. Il est fortement recommandé que vous vérifiez les mises à jour pour ces pilotes sur leurs sites Web d'entreprise. Cliquez sur les liens ci-dessous pour rechercher avec Google pour les mises à jour ces pilotes :


ngvss.sys (avast ! Pilote de capture instantanée NG, AVAST Software)


Si aucune mise à jour pour ces pilotes n'est disponibles, essayez de Rechercher avec Google sur les noms de ces pilotes en combinaison avec les erreurs qui ont été signalés pour ces pilotes. Incluez le nom de marque et le modèle de votre ordinateur aussi bien dans la requête. Cela donne souvent des résultats intéressants des discussions sur le web par les utilisateurs qui connaissent des problèmes similaires.



Lisez la rubrique AVERTISSEMENTS GENERAUX pour le dépannage des pannes du système pour plus d'informations.


Notez qu'il n'est pas toujours possible de dire avec certitude si un pilote signalé est responsable de la planter votre système ou que la cause est dans un autre module. Néanmoins, il est suggéré que vous recherchez des mises à jour pour les produits que ces pilotes appartiennent à et visiter régulièrement mise à jour de Windows ou activer les mises à jour automatiques pour Windows. Dans le cas où un morceau de matériel défectueux est à l'origine mal, une recherche avec Google sur les erreurs de contrôle de bogue avec le nom du modèle et la marque de votre ordinateur peut vous aider à approfondir cette examen.

.
Si tu as Avast comme le laisse penser Whocrashed , désinstalles le avec leur utilitaire , tu le remettra plus tard mets l' AV qui est fournit avec le PC , si tu as les deux A.V désinstalles celui du PC au profit d'Avast .
Bonne continuation .

[Necritia]

J'ai effectivement Avast, mais j avais désinstallé celui fournit avec le PC avant.

Je désinstalle quand même Avast ?

[routman54]

Re ,
Si comme c'est marqué c'est lui qui cause problèmes , oui ôtes le des A.V gratuit ce n'est pas ce qui manquent . Personnellement je n'ai jamais eu de problèmes avec mes appareils sont protégés par lui . Peut être un Bug lors de l'installation leur désinstalleur avec les explications et > LA < .
Ou tu le réinstalles après ou tu mets un autre gratuit comme AVG ou Avira .
Bonne continuation .

[EinsteinZero]

Bonsoir
en effet, il semblerait que win 8 n'aime pas trop Avast ces derniers temps, j'ai installé récemment AVG sur le portable d'une amie (sous win 8.1) pas eu de souci de fonctionnement

[Necritia]

J'ai supprimé Avast et installer la version gratuite d'AVG, je vous tiens au courant !
Merci encore

[Necritia]

A propos d'AVG, je vois qu il y a écrit "votre version d'évaluation expire dans 29 jours" après ça passe en version gratuite (donc qui protège un peu moins bien certainement) comme Avast ou c'est vraiment un antivirus payant ?

[EinsteinZero]

tu as par erreur activée la version d'évaluation (y'a un truc à décocher à l'installation) normalement dans 29 jours tu devrais passer à la version gratuite... ou réinstaller le logiciel en faisant attention
tu as bien pris la version gratuite >>ici<< ?

de toutes façons, tu peux rester 30 jours avec la version actuelle histoire de voir si le "BAD POLL HEADER" ne se présente plus

car il est toujours préférable de se "hâter lentement"

[Necritia]

Bon je verrais dans 29 jours :p
En tout cas pour le moment toujours pas de plantage j'ai l impression que c'est réglé !

Merci beaucoup ! Ca me foutait les boules, le portable tout neuf !

[EinsteinZero]

c'est sur... mais toutes ses machines ont leur petits caprices il suffit qu'un pilote n'en tolère pas un autre et "plouf"
reste à espérer que seul avast soit indigeste pour la bête

[routman54]

Re ,
Puisque tu es sous seven , lorsque tu feras la migration vers le W10 , ton Avast passera . Rien ne presse et entre le Sept et le 10 il n'y a pas trop de différence . Mieux vaut attendre qu'il ait muri mais quand même en profiter avant fin Juillet 2016 , car là il ne sera plus gratuit .
Mes trois PC ( même un tout vieux ) sont sous le 10 et je n'ai pas de problèmes pour l'instant . configuration parfois difficile pour un non initié mais ça dépends aussi de l'appareil .
Bonne continuation .