Crash à répétition Windows 8.1
Publié : 26 nov. 2015, 20:15
par Feedbacker
Depuis quelques temps mon PC crashe sporadiquement, sans signe avant-coureurs. Parfois je me tape 3 plantages d'affilée, mais généralement il peut tourner sans problème pendant plusieurs jour, même après de longues sessions d'utilisation.
Ces crash consistent en un freeze de quelques secondes puis l'apparition du magnifique BSOD 2.0 trollesque signé Microsoft, suivi d'un redémarrage automatique du PC. Pour info ça ressemble à ça :
Notez bien que l’erreur indiquée n'est pas toujours la même. En regardant sur le net pour chacune des erreurs que j'ai pu rencontrer on trouve de tout : problème software/hardware, pilotes de périphériques non à jour, disque dur endommagé, barrettes de RAM endommagées, mise à jour Windows foireuse et j'en passe.
J'ai fait hier une réinstallation à blanc des mes drivers de CG (avec Display Driver Uninstaller) suite à un énième crash, mais le problème n'est pas résolu pour autant puisque le PC a encore planter aujourd'hui.
Voici le rapport que sort Whocrashed :
Donc il s'agirait a priori un problème de drivers de carte graphique (problème : le site d'AMD me dit pourtant que tout est à jour) et du périphérique wifi (problème : je suis censé choisir quoi dans tout ce merdier ??).
A noter que j'utilise ce laptop depuis 2 ans et qu'il se portait jusque là comme un charme. Je n'ai jamais eu aucun autre soucis avec (mis à part un bug étrange qui me force quelques fois à le relancer la veille pour avoir du son ???). D'ailleurs entre 2 BSOD il fonctionne toujours aussi bien.
Ces crash consistent en un freeze de quelques secondes puis l'apparition du magnifique BSOD 2.0 trollesque signé Microsoft, suivi d'un redémarrage automatique du PC. Pour info ça ressemble à ça :
Notez bien que l’erreur indiquée n'est pas toujours la même. En regardant sur le net pour chacune des erreurs que j'ai pu rencontrer on trouve de tout : problème software/hardware, pilotes de périphériques non à jour, disque dur endommagé, barrettes de RAM endommagées, mise à jour Windows foireuse et j'en passe.
J'ai fait hier une réinstallation à blanc des mes drivers de CG (avec Display Driver Uninstaller) suite à un énième crash, mais le problème n'est pas résolu pour autant puisque le PC a encore planter aujourd'hui.
Voici le rapport que sort Whocrashed :
Spoiler :
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: VAIO
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: SVE1713H4E, Sony Corporation, VAIO
CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6387167232 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 26/11/2015 17:53:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112615-43953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803CBB69888, 0xFFFFD0014C8DA108, 0xFFFFD0014C8D9910)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 26/11/2015 17:53:47 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: athw8x.sys (athw8x+0x25613A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803CBB69888, 0xFFFFD0014C8DA108, 0xFFFFD0014C8D9910)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\athw8x.sys
product: Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Qualcomm Atheros Communications, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device driver
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: athw8x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED
On Wed 25/11/2015 13:57:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112515-137703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001DDF73470, 0xFFFFC000B03CAC08)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 24/11/2015 18:45:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112415-39437-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x31EEC)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD000E9711248, 0xFFFFD000E9710A50, 0xFFFFF8005651A56D)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Tue 24/11/2015 17:52:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112415-35625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x7A (0x5, 0x0, 0x9000, 0xFFFFE0014EB7D900)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 24/11/2015 13:19:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112415-45781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x466FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800E30D56FD, 0xFFFFD00021800608, 0xFFFFD000217FFE10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 14/11/2015 00:53:56 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111415-31234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0007FD07E80, 0x21B3162F)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 10/11/2015 19:31:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111015-25312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802E13DF529, 0xFFFFD000C39DB340, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
On Tue 10/11/2015 16:44:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111015-32015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802D74EB041, 0xFFFFD000CF321CB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
On Tue 10/11/2015 16:27:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111015-47937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000AA0C9AB0, 0x7FF5F798D380)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
athw8x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
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.
System Information (local)
--------------------------------------------------------------------------------
Computer name: VAIO
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: SVE1713H4E, Sony Corporation, VAIO
CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6387167232 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 26/11/2015 17:53:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112615-43953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803CBB69888, 0xFFFFD0014C8DA108, 0xFFFFD0014C8D9910)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 26/11/2015 17:53:47 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: athw8x.sys (athw8x+0x25613A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803CBB69888, 0xFFFFD0014C8DA108, 0xFFFFD0014C8D9910)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\athw8x.sys
product: Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Qualcomm Atheros Communications, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device driver
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: athw8x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED
On Wed 25/11/2015 13:57:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112515-137703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001DDF73470, 0xFFFFC000B03CAC08)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 24/11/2015 18:45:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112415-39437-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x31EEC)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD000E9711248, 0xFFFFD000E9710A50, 0xFFFFF8005651A56D)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Tue 24/11/2015 17:52:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112415-35625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x7A (0x5, 0x0, 0x9000, 0xFFFFE0014EB7D900)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 24/11/2015 13:19:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112415-45781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x466FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800E30D56FD, 0xFFFFD00021800608, 0xFFFFD000217FFE10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 14/11/2015 00:53:56 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111415-31234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0007FD07E80, 0x21B3162F)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 10/11/2015 19:31:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111015-25312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802E13DF529, 0xFFFFD000C39DB340, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
On Tue 10/11/2015 16:44:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111015-32015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802D74EB041, 0xFFFFD000CF321CB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
On Tue 10/11/2015 16:27:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111015-47937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000AA0C9AB0, 0x7FF5F798D380)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
athw8x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
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.
A noter que j'utilise ce laptop depuis 2 ans et qu'il se portait jusque là comme un charme. Je n'ai jamais eu aucun autre soucis avec (mis à part un bug étrange qui me force quelques fois à le relancer la veille pour avoir du son ???). D'ailleurs entre 2 BSOD il fonctionne toujours aussi bien.