Hi.
I have a fresh install of W8Pro Media Ctr, 32 bit, Avast! 2014.9.0.2013 (NOT Win 8.1)
Can some one please help me resolve this? Right now I have disabled all shields, because the crashes make my computer almost unrecoverable. It is impossible to get into safe mode unless I am in the regular OS first.
Thanks.
computer name: E521W8
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: Dimension E521, Dell Inc, 0UW457
CPU: AuthenticAMD AMD Athlon™ 64 Processor 3500+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 3219640320 total
VM: 2147352576, free: 1938395136
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 3/12/2014 6:17:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031214-77548-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x4EE27)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA7653E27, 0xFFFFFFFFD7C1314C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization 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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Wed 3/12/2014 6:17:13 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x5032E)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFFA7653E27, 0xFFFFFFFFD7C1314C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sun 3/9/2014 9:44:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030914-41605-01.dmp
This was probably caused by the following module: saskutil.sys (SASKUTIL+0x7503)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF9131A503, 0xFFFFFFFF81B9689C, 0xFFFFFFFF81B96460)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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: saskutil.sys (SASKUTIL.SYS, SUPERAdBlocker.com and SUPERAntiSpyware.com).
Google query: SUPERAdBlocker.com and SUPERAntiSpyware.com SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Thu 2/13/2014 11:02:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-112227-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCA5C4)
Bugcheck code: 0x19 (0xE, 0xFFFFFFFFA89B5000, 0x0, 0xFFFFFFFFEA239E37)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.