Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 03.05.2012 13:41:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050312-03.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x8D38)
Bugcheck code: 0xC5 (0x0, 0x2, 0x1, 0xFFFFFFFF8310D82A)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software DRIVER_CORRUPTED_EXPOOL
On Thu 03.05.2012 13:41:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x8D38)
Bugcheck code: 0xC5 (0x0, 0x2, 0x1, 0xFFFFFFFF8310D82A)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software DRIVER_CORRUPTED_EXPOOL
On Thu 03.05.2012 12:41:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050312-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF83109EB9)
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 which cannot be identified at this time.
On Wed 02.05.2012 23:40:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050312-01.dmp
This was probably caused by the following module: lnsfw1.sys (lnsfw1+0x9F91)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8080007, 0xFFFFFFFF87142910)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\lnsfw1.sys
product: LNSFW1 Look 'n' Stop Driver
description: LNSFW1 LnS Driver
Bug check description: This indicates that the current thread is making a bad pool request.
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: lnsfw1.sys (LNSFW1 LnS Driver, ).
Google query: lnsfw1.sys BAD_POOL_CALLER
On Mon 30.04.2012 16:46:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini043012-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x232C1)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF871C98E0, 0xFFFFFFFF871C98E8, 0x8010007)
Error: BAD_POOL_HEADER
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 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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software BAD_POOL_HEADER
On Mon 30.04.2012 08:41:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini043012-01.dmp
This was probably caused by the following module: lnsfw.sys (lnsfw+0x36C3)
Bugcheck code: 0xC5 (0x5, 0x2, 0x1, 0xFFFFFFFF83D37010)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\lnsfw.sys
product: Look 'n' Stop Driver
description: Look 'n' Stop Driver
Bug check description: This indicates that the system attempted to access invalid 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. 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: lnsfw.sys (Look 'n' Stop Driver, ).
Google query: lnsfw.sys DRIVER_CORRUPTED_EXPOOL
On Sat 28.04.2012 14:41:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042812-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA2BEF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF83E14D07, 0xFFFFFFFF80FE3C34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 which cannot be identified at this time.
On Wed 25.04.2012 22:22:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042612-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x712F4)
Bugcheck code: 0xC5 (0x1402FE, 0x2, 0x0, 0xFFFFFFFF83D37770)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that the system attempted to access invalid 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. 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 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 Sat 21.04.2012 20:29:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042112-01.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x1A66)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8C0FD7B2, 0xFFFFFFFFBF79086C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswfsblk.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Access Blocking 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: aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software).
Google query: aswfsblk.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M