Bug aprés démarrage systématiquement aprés 3 mn
Fermé
christiancine
Messages postés
6
Date d'inscription
samedi 8 novembre 2008
Statut
Membre
Dernière intervention
4 juillet 2015
-
Modifié par *_Francis_* le 4/07/2015 à 14:34
christiancine Messages postés 6 Date d'inscription samedi 8 novembre 2008 Statut Membre Dernière intervention 4 juillet 2015 - 4 juil. 2015 à 14:32
christiancine Messages postés 6 Date d'inscription samedi 8 novembre 2008 Statut Membre Dernière intervention 4 juillet 2015 - 4 juil. 2015 à 14:32
A voir également:
- Bug aprés démarrage systématiquement aprés 3 mn
- Bug yahoo mail - Accueil - Mail
- Forcer demarrage pc - Guide
- Pc lent au démarrage - Guide
- Reinitialiser pc au demarrage - Guide
- Problème de demarrage windows 10 - Guide
1 réponse
christiancine
Messages postés
6
Date d'inscription
samedi 8 novembre 2008
Statut
Membre
Dernière intervention
4 juillet 2015
4 juil. 2015 à 14:32
4 juil. 2015 à 14:32
System Information (local)
--------------------------------------------------------------------------------
computer name: ELDEATH
windows version: Windows 8.1 , 6.3, build: 9600
windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VI IMPACT
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8524488704 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 29/06/2015 15:10:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062915-9609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD00036575180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 29/06/2015 15:10:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x6F)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD00036575180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
--------------------------------------------------------------------------------
computer name: ELDEATH
windows version: Windows 8.1 , 6.3, build: 9600
windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VI IMPACT
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8524488704 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 29/06/2015 15:10:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062915-9609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD00036575180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 29/06/2015 15:10:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x6F)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD00036575180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
