Besoin d'aide pour lire rapport HijackThis
Fermé
colossal-dali
Messages postés
16
Date d'inscription
lundi 22 octobre 2012
Statut
Membre
Dernière intervention
20 août 2014
-
15 août 2014 à 02:24
Utilisateur anonyme - 20 août 2014 à 20:06
Utilisateur anonyme - 20 août 2014 à 20:06
A voir également:
- Besoin d'aide pour lire rapport HijackThis
- Lire le coran en français pdf - Télécharger - Histoire & Religion
- Lire epub - Guide
- Lire fichier bin - Guide
- Hijackthis windows 10 - Télécharger - Antivirus & Antimalwares
- Lire iso - Guide
8 réponses
Utilisateur anonyme
15 août 2014 à 03:50
15 août 2014 à 03:50
Bonjour
On va utiliser whocrahsed pour voir l'origine de tes écrans bleu
Tout est bien expliqué ici http://www.bibou0007.com/t3088-whocrashed
merci
@+
On va utiliser whocrahsed pour voir l'origine de tes écrans bleu
Tout est bien expliqué ici http://www.bibou0007.com/t3088-whocrashed
merci
@+
colossal-dali
Messages postés
16
Date d'inscription
lundi 22 octobre 2012
Statut
Membre
Dernière intervention
20 août 2014
15 août 2014 à 19:01
15 août 2014 à 19:01
salut Guillaume et merci pour ta réponse :)
J'ai installé whocrashed et quand je clique sur analyse il me met une fenetre avec ce message : please scroll down the information windows to read the report.
je sais je suis une bille !!!
je dois faire comment pour lancer l'analyse et t'envoyer le rapport.
Merci encor pour ton aide
J'ai installé whocrashed et quand je clique sur analyse il me met une fenetre avec ce message : please scroll down the information windows to read the report.
je sais je suis une bille !!!
je dois faire comment pour lancer l'analyse et t'envoyer le rapport.
Merci encor pour ton aide
colossal-dali
Messages postés
16
Date d'inscription
lundi 22 octobre 2012
Statut
Membre
Dernière intervention
20 août 2014
19 août 2014 à 22:39
19 août 2014 à 22:39
Voila les conclusion de Whocrached
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 19/08/2014 20:35:19 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8806501C)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF8806501C, 0xFFFFFFFFBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: WHEA_UNCORRECTABLE_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
One crash dump has been found and analyzed.
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
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 19/08/2014 20:35:19 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8806501C)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF8806501C, 0xFFFFFFFFBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: WHEA_UNCORRECTABLE_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
One crash dump has been found and analyzed.
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
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
colossal-dali
Messages postés
16
Date d'inscription
lundi 22 octobre 2012
Statut
Membre
Dernière intervention
20 août 2014
20 août 2014 à 14:00
20 août 2014 à 14:00
Ok je vais m'acheter un nouveau ventilo pour le processeur aujourd'hui
speed fan indique en effet une température jusqu a 100° pour temp 0 et 1 ainsi que core 0 et 1; tout le reste a l'air normale.
regarde le nouveau rapport whocrashed que j'ai lancé suite à un écran bleu qui s'enclenche à chaque fois que je lance Evrest pour analyser mon matériel.
Tu verras dans la Conclusion que les deux fichiers responsables du crash sont
kerneld.sys
hal.sys
Il me demande de les mettre à jour ou de les réparer mais j'ai beau chercher sur la toile je n'y arrive pas !!!
Voila le rapport
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 20/08/2014 11:37:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082014-15974-01.dmp
This was probably caused by the following module: kerneld.sys (kerneld+0xAD8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBAEB9AD8, 0xFFFFFFFF8CFE7804, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: kerneld.sys .
Google query: kerneld.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Wed 20/08/2014 11:37:37 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFFBAEB9AD8, 0xFFFFFFFF8CFE7804, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Wed 20/08/2014 10:38:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082014-15459-01.dmp
This was probably caused by the following module: kerneld.sys (kerneld+0xAD8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFAB3DDAD8, 0xFFFFFFFFB9129804, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: kerneld.sys .
Google query: kerneld.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Merci pour tout
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. 2 third party drivers have 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:
kerneld.sys
hal.sys
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 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.
speed fan indique en effet une température jusqu a 100° pour temp 0 et 1 ainsi que core 0 et 1; tout le reste a l'air normale.
regarde le nouveau rapport whocrashed que j'ai lancé suite à un écran bleu qui s'enclenche à chaque fois que je lance Evrest pour analyser mon matériel.
Tu verras dans la Conclusion que les deux fichiers responsables du crash sont
kerneld.sys
hal.sys
Il me demande de les mettre à jour ou de les réparer mais j'ai beau chercher sur la toile je n'y arrive pas !!!
Voila le rapport
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 20/08/2014 11:37:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082014-15974-01.dmp
This was probably caused by the following module: kerneld.sys (kerneld+0xAD8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBAEB9AD8, 0xFFFFFFFF8CFE7804, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: kerneld.sys .
Google query: kerneld.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Wed 20/08/2014 11:37:37 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFFBAEB9AD8, 0xFFFFFFFF8CFE7804, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Wed 20/08/2014 10:38:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082014-15459-01.dmp
This was probably caused by the following module: kerneld.sys (kerneld+0xAD8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFAB3DDAD8, 0xFFFFFFFFB9129804, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: kerneld.sys .
Google query: kerneld.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Merci pour tout
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. 2 third party drivers have 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:
kerneld.sys
hal.sys
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 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.
Utilisateur anonyme
Modifié par Guillaume5188 le 20/08/2014 à 17:19
Modifié par Guillaume5188 le 20/08/2014 à 17:19
Re
Il n'y a pas que le ventilateur a vérifier !!
la pâte thermique sur le processeur
A changer ou en mettre
@+
***-----------------------Contributeur Sécurité-------------------------***
On a tous été un jour débutant dans quelque chose.
Mais le savoir est la récompense de l'assiduité.
Il n'y a pas que le ventilateur a vérifier !!
la pâte thermique sur le processeur
A changer ou en mettre
@+
***-----------------------Contributeur Sécurité-------------------------***
On a tous été un jour débutant dans quelque chose.
Mais le savoir est la récompense de l'assiduité.
colossal-dali
Messages postés
16
Date d'inscription
lundi 22 octobre 2012
Statut
Membre
Dernière intervention
20 août 2014
20 août 2014 à 19:23
20 août 2014 à 19:23
j'ai changé le ventilo en mettant une nouvelle pâte thermique, le résultat est absolument remarquable. toutes les indications sont passées au bleu :)))
Reste à avoir maintenant si le pc devient stable ou si il y a d'autres problèmes en plus mais c'est déjà un soucis en moins.
Les dernier whocrashed me signale une erreur au niveau de ces deux fichier et me demande de les mettre à jours !!! kerneld.sys et hal.sys.
est ce que ça te dit quelques chose ?
Merci
Reste à avoir maintenant si le pc devient stable ou si il y a d'autres problèmes en plus mais c'est déjà un soucis en moins.
Les dernier whocrashed me signale une erreur au niveau de ces deux fichier et me demande de les mettre à jours !!! kerneld.sys et hal.sys.
est ce que ça te dit quelques chose ?
Merci
15 août 2014 à 21:19
J'ai installé whocrashed et quand je clique sur analyse il me met une fenetre avec ce message : please scroll down the information windows to read the report.
je sais je suis une bille !!!
je dois faire comment pour lancer l'analyse et t'envoyer le rapport.
Merci encor pour ton aide