Here's a who crashed report
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 25/03/2013 18:48:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032513-22105-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11894)
Bugcheck code: 0xD1 (0xFFFFFFFFBBC73010, 0x2, 0x0, 0xFFFFFFFF939EC778)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
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: sptd.sys .
Google query: sptd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 25/03/2013 18:48:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x6778)
Bugcheck code: 0xD1 (0xFFFFFFFFBBC73010, 0x2, 0x0, 0xFFFFFFFF939EC778)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport 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 Mon 25/03/2013 17:58:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032513-30856-01.dmp
This was probably caused by the following module: athur.sys (athur+0x7666)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFFFF8801042F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athur.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 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.
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: athur.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 25/03/2013 16:17:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032513-23836-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11894)
Bugcheck code: 0xD1 (0xFFFFFFFFBC4031C0, 0x2, 0x0, 0xFFFFFFFF93BB282A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
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: sptd.sys .
Google query: sptd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 25/03/2013 16:12:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032513-23134-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45B6B)
Bugcheck code: 0xA (0xFFFFFFFF989EC17B, 0x0, 0x0, 0xFFFFFFFF834909D1)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
On Tue 19/03/2013 21:15:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031913-26145-01.dmp
This was probably caused by the following module: athur.sys (athur+0xC2CCB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8CEDECCB, 0xFFFFFFFF8E02793C, 0xFFFFFFFF8E027520)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\athur.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 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.
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: athur.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 19/03/2013 02:58:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031913-23181-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11894)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFFFF92DBBDF9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
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: sptd.sys .
Google query: sptd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 11/03/2013 20:01:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031113-23306-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11894)
Bugcheck code: 0xD1 (0xFFFFFFFFBC1BAE0E, 0x2, 0x0, 0xFFFFFFFF92DB6380)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
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: sptd.sys .
Google query: sptd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 16/02/2013 03:09:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021613-28516-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x1114A)
Bugcheck code: 0xD1 (0xA807, 0x9, 0x1, 0xFFFFFFFF86B47DE8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
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: sptd.sys .
Google query: sptd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 29/01/2013 16:14:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012913-22776-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDBC)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x29962, 0x29885246)
Error: MEMORY_MANAGEMENT
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 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 Sat 26/01/2013 16:36:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012613-31543-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDBC)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x82B8, 0x8250528)
Error: MEMORY_MANAGEMENT
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 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 Tue 08/01/2013 02:36:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010813-23431-01.dmp
This was probably caused by the following module: athur.sys (athur+0xC2CCB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFAEAE5CCB, 0xFFFFFFFF9A9ED93C, 0xFFFFFFFF9A9ED520)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\athur.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 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.
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: athur.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Sun 06/01/2013 20:53:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-27768-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x7EFC)
Bugcheck code: 0xD1 (0xFFFFFFFFF886F186, 0x2, 0x1, 0xFFFFFFFF8C0F2EFC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Sun 06/01/2013 02:34:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010613-23353-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ACB)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFFFFF8344C389)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
On Fri 04/01/2013 12:00:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010413-25849-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB1951)
Bugcheck code: 0x50 (0xFFFFFFFF82D0DEA8, 0x8, 0xFFFFFFFF82D0DEA8, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 15 are included in this report. 7 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:
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
athur.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)
aswsp.sys (avast! self protection module, AVAST Software)
sptd.sys
unknown_module_54454e5c.sys
unknown_module_692d7369.sys
unknown_module_63654465.sys
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.
Sign In
Create Account
