Ecran Bleu
SOS.SOS
Messages postés
36
Date d'inscription
Statut
Membre
Dernière intervention
-
SOS.SOS Messages postés 36 Date d'inscription Statut Membre Dernière intervention -
SOS.SOS Messages postés 36 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
Voilà 2 jours, j'ai des redémarrages intempestifs : fameux écran bleu. Cela se produit le plus souvent au démarrage.
Ma configuration : Windows Vista Edition Familiale Premium (X86) Service Pack 2
Intel Core 2 Duo E7400 Cadencé à 2.80 GHz
Température CPU (core 0): 46 °C
NVIDIA GeForce 8400 GS
Version DirectX installée: 11.0
Merci à la personne qui va essayer de m'aider.
Voici le rapport de BlueScreenView :
==================================================
Dump File : Mini051416-07.dmp
Crash Time : 14/05/2016 14:28:00
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 0x00000000
Parameter 2 : 0x85fc43f0
Parameter 3 : 0xb2000040
Parameter 4 : 0x00000800
Caused By Driver : hal.dll
Caused By Address : hal.dll+69dd
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+cd9df
Stack Address 1 : hal.dll+69dd
Stack Address 2 : ntkrnlpa.exe+c141c
Stack Address 3 : hal.dll+68f1
Computer Name :
Full Path : C:\Windows\Minidump\Mini051416-07.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 153 256
==================================================
Voici le rapport de WhoCrashed : (8 crash (hal+0x69DD)
System Information (local)
________________________________________
Computer name: PC-DE-VISTA
Windows version: Windows Vista Service Pack 2, 6.0, build: 6002
Windows dir: C:\Windows
Hardware: INTEL, Intel Corporation, DG31PR
CPU: GenuineIntel Intel(R) Core(TM)2 CPU E7400 @ 2.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3485458432 bytes total
________________________________________
Crash Dump Analysis
________________________________________
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 14/05/2016 12:34:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFFFFF803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe CLOCK_WATCHDOG_TIMEOUT
On Sat 14/05/2016 12:26:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051416-07.dmp
This was probably caused by the following module: hal.dll (hal+0x69DD)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85FC43F0, 0xFFFFFFFFB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 14/05/2016 12:11:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051416-06.dmp
This was probably caused by the following module: unknown_module_00071fe8.sys (Unloaded_Unknown_Module_00071fe8+0x150018)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFFFFF803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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. It is suggested you look for an update for the following driver: unknown_module_00071fe8.sys .
Google query: unknown_module_00071fe8.sys CLOCK_WATCHDOG_TIMEOUT
________________________________________
Conclusion
________________________________________
15 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
unknown_module_00071fe8.sys
ntkrpamp.exe
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.
Voilà 2 jours, j'ai des redémarrages intempestifs : fameux écran bleu. Cela se produit le plus souvent au démarrage.
Ma configuration : Windows Vista Edition Familiale Premium (X86) Service Pack 2
Intel Core 2 Duo E7400 Cadencé à 2.80 GHz
Température CPU (core 0): 46 °C
NVIDIA GeForce 8400 GS
Version DirectX installée: 11.0
Merci à la personne qui va essayer de m'aider.
Voici le rapport de BlueScreenView :
==================================================
Dump File : Mini051416-07.dmp
Crash Time : 14/05/2016 14:28:00
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 0x00000000
Parameter 2 : 0x85fc43f0
Parameter 3 : 0xb2000040
Parameter 4 : 0x00000800
Caused By Driver : hal.dll
Caused By Address : hal.dll+69dd
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+cd9df
Stack Address 1 : hal.dll+69dd
Stack Address 2 : ntkrnlpa.exe+c141c
Stack Address 3 : hal.dll+68f1
Computer Name :
Full Path : C:\Windows\Minidump\Mini051416-07.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 153 256
==================================================
Voici le rapport de WhoCrashed : (8 crash (hal+0x69DD)
System Information (local)
________________________________________
Computer name: PC-DE-VISTA
Windows version: Windows Vista Service Pack 2, 6.0, build: 6002
Windows dir: C:\Windows
Hardware: INTEL, Intel Corporation, DG31PR
CPU: GenuineIntel Intel(R) Core(TM)2 CPU E7400 @ 2.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3485458432 bytes total
________________________________________
Crash Dump Analysis
________________________________________
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 14/05/2016 12:34:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFFFFF803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe CLOCK_WATCHDOG_TIMEOUT
On Sat 14/05/2016 12:26:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051416-07.dmp
This was probably caused by the following module: hal.dll (hal+0x69DD)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85FC43F0, 0xFFFFFFFFB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 14/05/2016 12:11:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051416-06.dmp
This was probably caused by the following module: unknown_module_00071fe8.sys (Unloaded_Unknown_Module_00071fe8+0x150018)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFFFFF803D1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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. It is suggested you look for an update for the following driver: unknown_module_00071fe8.sys .
Google query: unknown_module_00071fe8.sys CLOCK_WATCHDOG_TIMEOUT
________________________________________
Conclusion
________________________________________
15 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
unknown_module_00071fe8.sys
ntkrpamp.exe
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.
A voir également:
- Ecran Bleu
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
2 réponses
Bonjour,
Je complète mon post initial, si cela peut éclaircir le problème.
J'ai démarré en mode sans échec avec prise en charge réseau et je n'ai toujours pas eu de problèmes d'écran bleu en 2 heures de fonctionnement !
J'ai utilisez l'outil Vérificateur des fichiers système en tapant la commande SFC /SCANNOW.
Le résultat d'analyse : La protection des ressources Windows a trouvé des fichiers endommagés et a pu les réparer. Malheureusement, cela n'a pas réglé mon problème de BSOD.
Je ne sais pas si cela à un rapport mais avant ce problème, j'avais fait de la retouche photos qui à demandé de la mémoire.
J'ai aussi fait 15 mises à jour de Windows update avant d'éteindre le PC. C'est au démarrage que le problème est survenu.
Je n'ai pas installé quelque chose qui serait à l'origine du problème.
J'installe toutes les mises à jour que Windows Update détecte.
Je n'ai aucun problème dans le gestionnaire de périphérique.
C'est seulement au début du lancement du PC que j'ai beaucoup de BSOD, après le PC fonctionne normalement et sans redémarrage.
Merci d'avance.
Je complète mon post initial, si cela peut éclaircir le problème.
J'ai démarré en mode sans échec avec prise en charge réseau et je n'ai toujours pas eu de problèmes d'écran bleu en 2 heures de fonctionnement !
J'ai utilisez l'outil Vérificateur des fichiers système en tapant la commande SFC /SCANNOW.
Le résultat d'analyse : La protection des ressources Windows a trouvé des fichiers endommagés et a pu les réparer. Malheureusement, cela n'a pas réglé mon problème de BSOD.
Je ne sais pas si cela à un rapport mais avant ce problème, j'avais fait de la retouche photos qui à demandé de la mémoire.
J'ai aussi fait 15 mises à jour de Windows update avant d'éteindre le PC. C'est au démarrage que le problème est survenu.
Je n'ai pas installé quelque chose qui serait à l'origine du problème.
J'installe toutes les mises à jour que Windows Update détecte.
Je n'ai aucun problème dans le gestionnaire de périphérique.
C'est seulement au début du lancement du PC que j'ai beaucoup de BSOD, après le PC fonctionne normalement et sans redémarrage.
Merci d'avance.