Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 4/14/2014 11:49:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041414-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1BC00)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8063CAA0, 0xFFFFFFFFA36B4724, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 2/15/2014 6:21:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021514-01.dmp
This was probably caused by the following module: saskutil.sys (SASKUTIL+0xA6E0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89424020, 0xFFFFFFFF89424194, 0xFFFFFFFF805D22DA)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Program Files\SUPERAntiSpyware\SASKUTIL.SYS
product: SUPERAntiSpyware
company: SUPERAdBlocker.com and SUPERAntiSpyware.com
description: SASKUTIL.SYS
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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: saskutil.sys (SASKUTIL.SYS, SUPERAdBlocker.com and SUPERAntiSpyware.com).
Google query: SUPERAdBlocker.com and SUPERAntiSpyware.com CRITICAL_OBJECT_TERMINATION
On Fri 1/24/2014 12:57:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22FA3)
Bugcheck code: 0x77 (0xFFFFFFFFC0000056, 0xFFFFFFFFC0000056, 0x0, 0x9B4E000)
Error: KERNEL_STACK_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 Tue 1/14/2014 5:46:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011414-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
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 Mon 1/13/2014 2:55:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
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 Mon 1/13/2014 2:16:26 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
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 Wed 11/20/2013 1:45:41 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
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 Fri 9/20/2013 1:20:23 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091913-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
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 9/19/2013 8:37:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
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 1/31/2013 2:00:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini013013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60488)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537488)
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.
Conclusion
11 crash dumps have been found and analyzed. Only 10 are included in this report. 2 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:
saskutil.sys (SASKUTIL.SYS, SUPERAdBlocker.com and SUPERAntiSpyware.com)
aswsp.sys (avast! self protection module, AVAST Software)
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.