je dispose d'un pc asus et windows 8 ( je sais je sais ...personne n'est parfait ...
) Depuis quelques mois j'ai des crash kernel à répétition ....j'ai tenté avec l'aide d'internet de trouver des solutions mais je n'arrive vraiment pas à trouver le problème.
Je suis actuellement en train de faire via HDTUNE un scan de mon disque, il apparait que certain blocs soient endommagés ;
Pourriez vous m'aider s'il vous plait.
merci
voici le dernier rapport de who crash :
computer name: FRED
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: X401A1, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Celeron(R) CPU B830 @ 1.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4173148160 total
VM: 2147352576, free: 1919602688
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 27/10/2014 18:46:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102714-25453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3C8744)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800A3A54744, 0xFFFFD00041917898, 0xFFFFD000419170A0)
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 Mon 27/10/2014 18:46:43 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800A3A54744, 0xFFFFD00041917898, 0xFFFFD000419170A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 27/10/2014 17:20:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102714-29765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3C8744)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803547E4744, 0xFFFFD0010E68C898, 0xFFFFD0010E68C0A0)
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 Mon 27/10/2014 16:46:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102714-23968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000364B3B50, 0x6B638D0)
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 Mon 27/10/2014 14:29:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102714-27046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00171730AF0, 0x68DBD50)
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 Mon 27/10/2014 13:43:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102714-24265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0008FF4F770, 0xFFFFC0019104F0DA)
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 Mon 27/10/2014 11:50:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102714-24093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000C9B32E80, 0xD985AD0)
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 Sun 26/10/2014 20:34:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102614-25687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00006043A90, 0x7FFEBF6CF098)
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 Fri 24/10/2014 17:13:56 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102414-23265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000494F5E80, 0x64C40F0)
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 Fri 24/10/2014 16:46:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102414-22859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0013C469310, 0xC9BF610)
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
--------------------------------------------------------------------------------
51 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 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 actually 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.
