On Sat 2011-03-05 06:26:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030511-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1C712)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8053BA38, 0xFFFFFFFFB320CC08, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
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).
On Fri 2011-03-04 14:51:28 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030411-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1E109)
Bugcheck code: 0x100000D1 (0xFFFFFFFF997DB8D0, 0x2, 0x1, 0xFFFFFFFFB4464109)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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).
On Mon 2011-02-28 13:01:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2BCD8)
Bugcheck code: 0x1000000A (0xFFFFFFFF99753464, 0x1C, 0x1, 0xFFFFFFFF80502CD8)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NT:s kernel och system
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 2011-02-25 11:33:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022511-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x69BF)
Bugcheck code: 0x100000C5 (0xFFFFFFFFF89889B0, 0x2, 0x1, 0xFFFFFFFF8054B10D)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
On Thu 2011-02-24 07:47:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022411-01.dmp
This was probably caused by the following module: afd.sys (afd+0x10DA9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF805BB496, 0xFFFFFFFFB8503C00, 0xFFFFFFFFB85038FC)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 which cannot be identified at this time.
On Tue 2011-02-22 12:49:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022211-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2BCD8)
Bugcheck code: 0x1000000A (0xFFFFFFFF99A149E4, 0x1C, 0x1, 0xFFFFFFFF80502CD8)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NT:s kernel och system
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 2011-02-22 10:37:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022211-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0xA34)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF887A94C0, 0xFFFFFFFF887A94D8, 0x1A030001)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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. It is suggested you look for an update for the following driver: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
On Mon 2011-02-21 05:56:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022111-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1D399)
Bugcheck code: 0x100000C5 (0x4, 0x2, 0x1, 0xFFFFFFFF8054B10F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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).
As can be seen, there are quite a few instances relating to Avast. And with Avast disabled I no longer seem to get any crashes.