écrans bleu a répetitions...
Posté : dim. 23 févr. 2014 13:55
bonjour voila depuis un petit bout de temps j'ai écran bleu sur écran bleu. j'ai fait un diag de la mémoire et tout est ok voici le rapport des crash du pc . j'ai besoin de vos lumière pour voir d'ou cela peux venir car je désespère. 
... mon pc bien malade je crois. 
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 22/02/2014 22:57:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8A015D5D070)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A015D5D070, 0xFFFFF8A015D5DF70, 0x5F004C0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER
On Sat 22/02/2014 18:54:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-50637-01.dmp
This was probably caused by the following module: athrx.sys (athrx+0x16CC12)
Bugcheck code: 0xA (0xFFFFFA7FFFD29FD0, 0x2, 0x1, 0xFFFFF8000389B4EC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: athrx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. IRQL_NOT_LESS_OR_EQUAL
On Sat 22/02/2014 18:20:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-49358-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF8800191D69E)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF8800191D69E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 21/02/2014 21:49:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022114-49171-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF88005152A07)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88005152A07)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Thu 20/02/2014 21:12:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022014-46488-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xC0000005, 0x0, 0x1, 0x18)
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 Wed 19/02/2014 17:53:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021914-52509-01.dmp
This was probably caused by the following module: athrx.sys (athrx+0x166A77)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF88005585A77)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\athrx.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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: athrx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. UNEXPECTED_KERNEL_MODE_TRAP
On Wed 19/02/2014 17:29:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021914-52962-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800004C828, 0xC57000003CD7A867, 0xFFFFF6800004C820)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 19/02/2014 17:24:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021914-50138-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0x123E2C, 0x6, 0x9)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 13/02/2014 19:33:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-64724-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x65000)
Bugcheck code: 0xBE (0xFFFFF88001AAA000, 0x8000000004C93121, 0xFFFFF8800448CE40, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
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 is issued if a driver attempts to write to a read-only memory segment.
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 Thu 13/02/2014 18:45:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-50840-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF800038826A2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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
--------------------------------------------------------------------------------
43 crash dumps have been found and analyzed. Only 10 are included in this report. 6 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:
athrx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
iastorf.sys (Intel Rapid Storage Technology Filter driver - x64, Intel Corporation)
unknown_module_00000000`00000000.sys
unknown_module_00000000`00001f90.sys
unknown_module_00000000`00000007.sys
unknown_module_00000000`00000006.sys
merci pour votre aide .
... mon pc bien malade je crois. Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 22/02/2014 22:57:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8A015D5D070)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A015D5D070, 0xFFFFF8A015D5DF70, 0x5F004C0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER
On Sat 22/02/2014 18:54:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-50637-01.dmp
This was probably caused by the following module: athrx.sys (athrx+0x16CC12)
Bugcheck code: 0xA (0xFFFFFA7FFFD29FD0, 0x2, 0x1, 0xFFFFF8000389B4EC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: athrx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. IRQL_NOT_LESS_OR_EQUAL
On Sat 22/02/2014 18:20:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-49358-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF8800191D69E)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF8800191D69E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 21/02/2014 21:49:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022114-49171-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF88005152A07)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88005152A07)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Thu 20/02/2014 21:12:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022014-46488-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xC0000005, 0x0, 0x1, 0x18)
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 Wed 19/02/2014 17:53:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021914-52509-01.dmp
This was probably caused by the following module: athrx.sys (athrx+0x166A77)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF88005585A77)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\athrx.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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: athrx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. UNEXPECTED_KERNEL_MODE_TRAP
On Wed 19/02/2014 17:29:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021914-52962-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800004C828, 0xC57000003CD7A867, 0xFFFFF6800004C820)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 19/02/2014 17:24:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021914-50138-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0x123E2C, 0x6, 0x9)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 13/02/2014 19:33:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-64724-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x65000)
Bugcheck code: 0xBE (0xFFFFF88001AAA000, 0x8000000004C93121, 0xFFFFF8800448CE40, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
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 is issued if a driver attempts to write to a read-only memory segment.
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 Thu 13/02/2014 18:45:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-50840-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF800038826A2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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
--------------------------------------------------------------------------------
43 crash dumps have been found and analyzed. Only 10 are included in this report. 6 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:
athrx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
iastorf.sys (Intel Rapid Storage Technology Filter driver - x64, Intel Corporation)
unknown_module_00000000`00000000.sys
unknown_module_00000000`00001f90.sys
unknown_module_00000000`00000007.sys
unknown_module_00000000`00000006.sys
merci pour votre aide .