cjoint

Publicité


Publicité

Format du document : text/plain

Prévisualisation

Rapport WhoCrashed

System Information (local)

computer name: SONIA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Satellite L300, TOSHIBA, Portable PC
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4200 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3082809344 total



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 23/10/2014 18:40:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102314-4291434327-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4BA42)
Bugcheck code: 0x1E (0xFFFFFFFFC0000420, 0xFFFFFFFF807E48E0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntkrnlpa.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 23/10/2014 18:40:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athr.sys (athr+0x125E6)
Bugcheck code: 0x1E (0xFFFFFFFFC0000420, 0xFFFFFFFF807E48E0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\athr.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 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: athr.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED



On Thu 23/10/2014 18:19:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102314-4291429538-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4BA42)
Bugcheck code: 0x1E (0xFFFFFFFFC0000420, 0xFFFFFFFF807E48E0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntkrnlpa.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

3 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:

athr.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 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.

Publicité


Signaler le contenu de ce document

Publicité