Windows a redémarré plusieurs fois après un arrêt non planifié
Fermé
takwasahmim
Messages postés
2
Date d'inscription
lundi 16 mars 2015
Statut
Membre
Dernière intervention
17 mars 2015
-
16 mars 2015 à 23:35
takwasahmim Messages postés 2 Date d'inscription lundi 16 mars 2015 Statut Membre Dernière intervention 17 mars 2015 - 17 mars 2015 à 08:28
takwasahmim Messages postés 2 Date d'inscription lundi 16 mars 2015 Statut Membre Dernière intervention 17 mars 2015 - 17 mars 2015 à 08:28
A voir également:
- Windows a redémarré plusieurs fois après un arrêt non planifié
- Windows 10 gratuit - Guide
- Clé windows 10 gratuit - Guide
- Windows 12 - Guide
- Installer windows 11 sur pc non compatible - Guide
- Installer Windows 11 sur un PC non compatible - Guide
1 réponse
takwasahmim
Messages postés
2
Date d'inscription
lundi 16 mars 2015
Statut
Membre
Dernière intervention
17 mars 2015
17 mars 2015 à 08:28
17 mars 2015 à 08:28
j'ai fait une annalyse des "crached " et j'ai obtenue le rapport suivant:
System Information (local)
--------------------------------------------------------------------------------
computer name: TAHER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: SATELLITE C855-278, TOSHIBA, Type2 - Board Vendor Name1, Type2 - Board Product Name1
CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2927419392 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 16/03/2015 21:43:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031615-19546-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBDD71)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF99EFDD71, 0xFFFFFFFF90FA9B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
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 Mon 16/03/2015 21:43:14 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, 0xFFFFFFFF99EFDD71, 0xFFFFFFFF90FA9B98, 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 Mon 16/03/2015 12:22:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031615-19656-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBDD71)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF822BDD71, 0xFFFFFFFF97F8DB98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
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 Fri 06/03/2015 22:04:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030615-19936-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x941F5)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF91E9A1F5, 0xFFFFFFFF9892C7C8, 0xFFFFFFFF9892C3A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a system thread 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 20/05/2014 12:25:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-17097-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x7AEA6)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFFFF85234020, 0xFFFFFFFF82F77B24)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
5 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
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.
Qu'est ce que je peux faire pour résoudre tout ces problèmes?
System Information (local)
--------------------------------------------------------------------------------
computer name: TAHER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: SATELLITE C855-278, TOSHIBA, Type2 - Board Vendor Name1, Type2 - Board Product Name1
CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2927419392 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 16/03/2015 21:43:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031615-19546-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBDD71)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF99EFDD71, 0xFFFFFFFF90FA9B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
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 Mon 16/03/2015 21:43:14 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, 0xFFFFFFFF99EFDD71, 0xFFFFFFFF90FA9B98, 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 Mon 16/03/2015 12:22:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031615-19656-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBDD71)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF822BDD71, 0xFFFFFFFF97F8DB98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
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 Fri 06/03/2015 22:04:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030615-19936-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x941F5)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF91E9A1F5, 0xFFFFFFFF9892C7C8, 0xFFFFFFFF9892C3A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a system thread 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 20/05/2014 12:25:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-17097-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x7AEA6)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFFFF85234020, 0xFFFFFFFF82F77B24)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
5 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
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.
Qu'est ce que je peux faire pour résoudre tout ces problèmes?