Ecran bleu répétitif
Fermé
daitenshi
Messages postés
13
Date d'inscription
jeudi 9 décembre 2010
Statut
Membre
Dernière intervention
14 avril 2012
-
Modifié par daitenshi le 9/01/2012 à 17:52
afullana Messages postés 295 Date d'inscription jeudi 11 février 2010 Statut Membre Dernière intervention 8 juin 2012 - 24 janv. 2012 à 10:15
afullana Messages postés 295 Date d'inscription jeudi 11 février 2010 Statut Membre Dernière intervention 8 juin 2012 - 24 janv. 2012 à 10:15
A voir également:
- Ecran bleu répétitif
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran samsung - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Ecran noir pc - Guide
6 réponses
afullana
Messages postés
295
Date d'inscription
jeudi 11 février 2010
Statut
Membre
Dernière intervention
8 juin 2012
19
9 janv. 2012 à 17:53
9 janv. 2012 à 17:53
Ton problème est plus hardware a mon avis.
J'ai vu des virus détruire le secteur de démarrage ou planter complétement des windows/partition, mais pas de bluescreen.
Le code du bluscreen aurait était utile pour savoir l'origine du problème.
Est ce que le pc demarre en mode sans echec avant de faire la réparation (F8 au démarrage pour afficher les options)
J'ai vu des virus détruire le secteur de démarrage ou planter complétement des windows/partition, mais pas de bluescreen.
Le code du bluscreen aurait était utile pour savoir l'origine du problème.
Est ce que le pc demarre en mode sans echec avant de faire la réparation (F8 au démarrage pour afficher les options)
daitenshi
Messages postés
13
Date d'inscription
jeudi 9 décembre 2010
Statut
Membre
Dernière intervention
14 avril 2012
Modifié par daitenshi le 9/01/2012 à 18:24
Modifié par daitenshi le 9/01/2012 à 18:24
J'ai pas pensé à noter ce code :/
Pour la réparation, je n'ai appuyé sur aucune touche le pc m'a proposé deux choix, lancer windows normalement qui redemarrait ma machine en boucle et la réparation qui ne trouve aucun probleme mais qui lance normalement windows quand elle prend fin.
S'il y a eu utilisation du mode sans echec lors de la réparation je ni suis pour rien ^^, mais a vu d'oeil la résolution était normale comparé a celle proposée par le mode sans échec.
J'ai fait pas mal de scan via avast et Malwarebytes notamment, est-ce possible qu'ils aient éliminé juste une partie d'une éventuelle infection ?
Pour la réparation, je n'ai appuyé sur aucune touche le pc m'a proposé deux choix, lancer windows normalement qui redemarrait ma machine en boucle et la réparation qui ne trouve aucun probleme mais qui lance normalement windows quand elle prend fin.
S'il y a eu utilisation du mode sans echec lors de la réparation je ni suis pour rien ^^, mais a vu d'oeil la résolution était normale comparé a celle proposée par le mode sans échec.
J'ai fait pas mal de scan via avast et Malwarebytes notamment, est-ce possible qu'ils aient éliminé juste une partie d'une éventuelle infection ?
afullana
Messages postés
295
Date d'inscription
jeudi 11 février 2010
Statut
Membre
Dernière intervention
8 juin 2012
19
10 janv. 2012 à 20:24
10 janv. 2012 à 20:24
Sa peut etre un pilote ou un logiciel qui pose probleme, essaye de suivre ce tuto pour avoir l'explication du code d'erreur:
http://benquet.com/bsod.aspx
http://benquet.com/bsod.aspx
daitenshi
Messages postés
13
Date d'inscription
jeudi 9 décembre 2010
Statut
Membre
Dernière intervention
14 avril 2012
13 janv. 2012 à 20:47
13 janv. 2012 à 20:47
Désolé pour le retard j'ai repris la fac...j'men serai bien passé ^^"
J'ai essayé d'installer l'outil de windows, sauf que j'ai un echec à la fin de l'installation, je suis allé regarder chez google qui m'a conseillé whocrashed.
Je vous post mon "bilan"
D'apres ce que j'ai compris il y a 2 problemes avec un certain "Kernel" et mon antivirus avast :(
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 09/01/2012 12:16:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010912-18532-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003470250, 0xFFFFF80003470250, 0xFFFFFA8009453198)
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 which cannot be identified at this time.
On Mon 09/01/2012 12:16:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x10F52)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003470250, 0xFFFFF80003470250, 0xFFFFFA8009453198)
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 Mon 09/01/2012 11:42:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010912-24570-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x3, 0xFFFFF8000346A760, 0xFFFFF8000346A760, 0xFFFFFA8009CDB198)
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 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 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.
J'ai essayé d'installer l'outil de windows, sauf que j'ai un echec à la fin de l'installation, je suis allé regarder chez google qui m'a conseillé whocrashed.
Je vous post mon "bilan"
D'apres ce que j'ai compris il y a 2 problemes avec un certain "Kernel" et mon antivirus avast :(
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 09/01/2012 12:16:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010912-18532-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003470250, 0xFFFFF80003470250, 0xFFFFFA8009453198)
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 which cannot be identified at this time.
On Mon 09/01/2012 12:16:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x10F52)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003470250, 0xFFFFF80003470250, 0xFFFFFA8009453198)
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 Mon 09/01/2012 11:42:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010912-24570-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x3, 0xFFFFF8000346A760, 0xFFFFF8000346A760, 0xFFFFFA8009CDB198)
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 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 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.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
daitenshi
Messages postés
13
Date d'inscription
jeudi 9 décembre 2010
Statut
Membre
Dernière intervention
14 avril 2012
17 janv. 2012 à 20:37
17 janv. 2012 à 20:37
quelqu'un a-t-il une solution pour remedier a ce probleme d'ecran bleu ?
(mon pc m'a encore fait le coup aujourd'hui j'ai l'impression que ça arrive de facon plus ou moins aléatoire, plantage ecran bleu, je lance windows normalement et ca remarche...a ne plus rien y comprendre :/ )
(mon pc m'a encore fait le coup aujourd'hui j'ai l'impression que ça arrive de facon plus ou moins aléatoire, plantage ecran bleu, je lance windows normalement et ca remarche...a ne plus rien y comprendre :/ )
afullana
Messages postés
295
Date d'inscription
jeudi 11 février 2010
Statut
Membre
Dernière intervention
8 juin 2012
19
24 janv. 2012 à 10:15
24 janv. 2012 à 10:15
Désinstalle ou met a jour Avast, apparemment c'est un des module du logiciel qui pose problème