Ecran Bleu cause clé wifi [Résolu/Fermé]

Signaler
Messages postés
9
Date d'inscription
samedi 2 février 2013
Statut
Membre
Dernière intervention
13 février 2013
-
Messages postés
9
Date d'inscription
samedi 2 février 2013
Statut
Membre
Dernière intervention
13 février 2013
-
Bonjour à tous,

Alors voila j'ai souvent des blue screen et selon "Whocrashed" ça serait a cause d'un pilote pour ma carte réseau Athéros Ar5007uG.....

J'ai un pc Acer T660 avec Windows 7 64 bit.

J'ai cherché pendant 3 jours à le mettre a jour le seul pilote qui a fonctionné c'est un datant de 2008...

Voici le rapport Whocrashed :

System Information (local)
--------------------------------------------------------------------------------

computer name: ZELDA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) D CPU 3.00GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 1878384640 total
VM: 2147352576, free: 1950953472




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 03/02/2013 14:47:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-29874-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6465D)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 Sun 03/02/2013 14:47:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athrxusb.sys (athrxusb+0x11202)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\athrxusb.sys
product: Driver for Atheros Wireless USB Network Adapter
company: Atheros Communications, Inc.
description: 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: athrxusb.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED



On Sun 03/02/2013 12:39:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-20997-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sun 03/02/2013 00:01:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-26239-01.dmp
This was probably caused by the following module: srvnet.sys (srvnet+0x1E110)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000289B065, 0xFFFFF880056737D8, 0xFFFFF88005673030)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\srvnet.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Server Network 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.
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 Sat 02/02/2013 21:52:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-19266-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x611BD)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 Sat 02/02/2013 21:49:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-20685-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sat 02/02/2013 21:36:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-29686-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sat 02/02/2013 21:20:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-19905-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sat 02/02/2013 21:17:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-20670-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 31/01/2013 22:31:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013113-20935-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 31/01/2013 22:14:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013113-24336-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 31/01/2013 19:50:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013113-27268-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800028B5CB5, 0x0, 0xFFFFFFFFFFFFFFFF)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. 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:

athrxusb.sys (Atheros Extensible Wireless LAN device driver, 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.


Merci pour votre aide







2 réponses

Messages postés
9
Date d'inscription
samedi 2 février 2013
Statut
Membre
Dernière intervention
13 février 2013

Personne?

Help !
Messages postés
9
Date d'inscription
samedi 2 février 2013
Statut
Membre
Dernière intervention
13 février 2013

J'ai changé de clé mais c'est toujours pareil :

computer name: ZELDA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) D CPU 3.00GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 1878384640 total
VM: 2147352576, free: 1935388672




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 08/02/2013 17:27:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020813-41917-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B7AA71, 0xFFFFF880065A5160, 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 Fri 08/02/2013 17:27:19 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: 0x3B (0xC0000005, 0xFFFFF80002B7AA71, 0xFFFFF880065A5160, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Fri 08/02/2013 15:39:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020813-21262-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Fri 08/02/2013 15:36:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020813-21075-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 07/02/2013 20:26:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-16957-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x81E7A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80015D6B50, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 07/02/2013 20:03:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-19468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 07/02/2013 19:55:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-17690-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8002712060, 0xFFFFF80000B9C518, 0xFFFFFA8001B56110)
Error: DRIVER_POWER_STATE_FAILURE
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 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.



On Tue 05/02/2013 19:34:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020513-18252-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 05/02/2013 19:30:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020513-18033-01.dmp
This was probably caused by the following module: athrxusb.sys (athrxusb+0x12920)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\athrxusb.sys
product: Driver for Atheros Wireless USB Network Adapter
company: Atheros Communications, Inc.
description: 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: athrxusb.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED



On Sun 03/02/2013 14:47:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-29874-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6465D)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 Sun 03/02/2013 12:39:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-20997-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sun 03/02/2013 00:01:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-26239-01.dmp
This was probably caused by the following module: srvnet.sys (srvnet+0x1E110)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000289B065, 0xFFFFF880056737D8, 0xFFFFF88005673030)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\srvnet.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Server Network 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.
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 Sat 02/02/2013 21:52:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-19266-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x611BD)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 Sat 02/02/2013 21:49:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-20685-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sat 02/02/2013 21:36:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-29686-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

20 crash dumps have been found and analyzed. Only 15 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:

athrxusb.sys (Atheros Extensible Wireless LAN device driver, 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.
Messages postés
9
Date d'inscription
samedi 2 février 2013
Statut
Membre
Dernière intervention
13 février 2013

s'il vous plait.... Je vais finir par me pendre