Avast WEBforum

Avast Products => Archive (Legacy) => Avast Business => Avast Endpoint Protection => Topic started by: diego© on November 05, 2012, 06:17:51 PM

Title: BSOD aswsnx.sys
Post by: diego© on November 05, 2012, 06:17:51 PM
On Mon 11/5/2012 8:28:22 AM computer CB2306-HP crashed
crash dump file: \\CB2306-HP\C$\Windows\minidump\110512-12386-01.dmp
uptime: 00:06:57
How can I stop this from happening. It is only Windows 7 machines.

This was probably caused by the following module: aswsnx.sys (aswSnx+0x18C75)
Bugcheck code: 0x1A (0x31, 0xFFFFFFFF876063C8, 0xFFFFFFFF8059C000, 0xFFFFFFFFAF19F678)
Error: MEMORY_MANAGEMENT
Note: file information has been obtained locally and may not be correct.
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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.
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 MEMORY_MANAGEMENT
Title: Re: BSOD aswsnx.sys
Post by: wpn on November 09, 2012, 12:33:27 PM
did you try to run memtest on the machine already to exclude it is faulty memory?
Title: Re: BSOD aswsnx.sys
Post by: 1tb on November 12, 2012, 06:04:34 AM
I can confirm this happened to us on 2 different servers - first on Nov 1, and again on Nov 12.  On further investigation we found that the avast client (running on the server) has now lost the settings (for example the scan times are set differently to those specified in the SOA). Also on one of the servers we were faced with the SOA wizard (like it thought this was a first time install). Why?
Title: Re: BSOD aswsnx.sys
Post by: ccrane95540 on November 28, 2012, 09:11:27 PM
We get the exact same problem on one of our servers and it reboots it in the middle of the night.  Here is my MiniDump


Code: [Select]
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini112812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Wed Nov 28 06:29:34.443 2012 (GMT-8)
System Uptime: 0 days 2:07:15.094
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b6e02817, b60cb6c8, 0}

Probably caused by : aswSnx.SYS ( aswSnx+3c817 )

Followup: MachineOwner
---------

2: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b6e02817, The address that the exception occurred at
Arg3: b60cb6c8, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
aswSnx+3c817
b6e02817 8904b3          mov     dword ptr [ebx+esi*4],eax

TRAP_FRAME:  b60cb6c8 -- (.trap 0xffffffffb60cb6c8)
ErrCode = 00000002
eax=00000000 ebx=00000000 ecx=b60cb788 edx=8e715e5c esi=00000000 edi=00000000
eip=b6e02817 esp=b60cb73c ebp=b60cb748 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
aswSnx+0x3c817:
b6e02817 8904b3          mov     dword ptr [ebx+esi*4],eax ds:0023:00000000=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0x8E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from b6e03c5c to b6e02817

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
b60cb748 b6e03c5c ffffffff b60cb788 00000000 aswSnx+0x3c817
b60cb770 b6e03de7 b60cb7a4 00000032 8e0c5ab4 aswSnx+0x3dc5c
b60cb7c8 b6e041cf 00000000 00000000 00000000 aswSnx+0x3dde7
b60cb80c b6e045a9 b60cb8f0 8e715e5c b6e12e6e aswSnx+0x3e1cf
b60cb8e4 b6e04716 b60cb920 b6e12dfa 80000514 aswSnx+0x3e5a9
b60cb90c b6de6944 b60cb958 b6e12dfa 80000514 aswSnx+0x3e716
b60cb994 b6ded7c0 000ce904 e7fb63e8 00000001 aswSnx+0x20944
b60cb9bc b6dedf92 000006d0 000ce904 e7fb63e8 aswSnx+0x277c0
b60cbb14 b6deebd5 fbf6cbc8 000ce904 b60cbb38 aswSnx+0x27f92
b60cbb78 8094a1d2 000006d0 000ce904 00000001 aswSnx+0x28bd5
b60cbcc8 8094af23 00b2d90c 001f03ff 00000000 nt!MiCloneProcessAddressSpace+0x4df0
b60cbd3c 8088983c 00b2d90c 001f03ff 00000000 nt!MiDecrementCloneBlockReference+0xd1b
b60cbd64 7c82845c badb0d00 00b2d59c 00000000 nt!MiRemoveUnusedSegments+0xbd4
b60cbd68 badb0d00 00b2d59c 00000000 00000000 0x7c82845c
b60cbd6c 00b2d59c 00000000 00000000 00000000 0xbadb0d00
b60cbd70 00000000 00000000 00000000 00000000 0xb2d59c


STACK_COMMAND:  kb

FOLLOWUP_IP:
aswSnx+3c817
b6e02817 8904b3          mov     dword ptr [ebx+esi*4],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aswSnx+3c817

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSnx

IMAGE_NAME:  aswSnx.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ff44ee3

FAILURE_BUCKET_ID:  0x8E_aswSnx+3c817

BUCKET_ID:  0x8E_aswSnx+3c817

Followup: MachineOwner
---------

2: kd> lmvm aswSnx
start    end        module name
b6dc6000 b6e60000   aswSnx   T (no symbols)           
    Loaded symbol image file: aswSnx.SYS
    Image path: \SystemRoot\System32\Drivers\aswSnx.SYS
    Image name: aswSnx.SYS
    Timestamp:        Wed Jul 04 07:10:43 2012 (4FF44EE3)
    CheckSum:         0009DC0D
    ImageSize:        0009A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Not sure what I need to do to fix this but it is getting annoying to have to come in at 5 am to make sure all of the services are up and running when this server crashes.
Title: Re: BSOD aswsnx.sys
Post by: pk on November 28, 2012, 10:02:32 PM
can you please send me (kurtin@avast.com) your minidumps?
i'll see if this bug is fixed and send you patched version, thanks
Title: Re: BSOD aswsnx.sys
Post by: torvista on February 03, 2013, 10:00:03 AM
I have the same issue:
Quote
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x165C)
Bugcheck code: 0x50 (0xFFFFFFFFA7BD0001, 0x1, 0xFFFFFFFF8054708C, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
I'll send the file,
regards
Steve
Title: Re: BSOD aswsnx.sys
Post by: 1tb on February 04, 2013, 02:04:40 AM
We still see this problem too after months. We fix it sometimes as follows:
1. Disable Sandbox in SOA console
2. Check the settings are not 'magically' lost in SOA (this has happened to us - where sandbox has re-enabled itself) - leading to BSOD in aswsnx.sys and ntoskrnl.exe
3. Uninstall avast and the problem goes away! ???
Title: Re: BSOD aswsnx.sys
Post by: hjason7812 on June 25, 2013, 12:36:14 AM
I just got this bsod on my pc.. it has been doing off and on for awhile now.. if this is due to the program I am going to uninstall this thing and find something else that won't make my computer bsod every 5 minutes...
Title: Re: BSOD aswsnx.sys
Post by: avast@@dvantage77.com on June 25, 2013, 12:57:54 AM
Only version 8 will solve this proble.  In version 7, ASWSNX cannot be removed (believe me, I have tried it!)  In version 8, custom install, uncheck all virtualization components, and it will NOT be installed.  Make sure to ASWclear before ver. 8 custom install.

and Endpoint  ver. 8 RC is AWSOME! and works the same way!


Sincerely,
 
J.R. "AutoSandbox Guy" Guthrie

"At this point in time, the Internet should be regarded as an Enemy Weapons System!"
Title: Re: BSOD aswsnx.sys
Post by: ralbrux on June 27, 2013, 04:28:09 PM
My Nir Soft Blue Screen viewer shows me that I have had 6 BSODs over the last 3 months caused by the address awsSnx.sys +51064.

avast@advantage77.com says the issue can only be solved in v 8 and that one should do a custom install after doing ASWclear (what is that ?).

I am running v 8.0.1489 which is there simply because of automatic updates, so no custom install was ever done and of course no elimination of awsSnx.

Can I disable awsSnx in my currently installed v 8 and if so, how ?

Thanks for any help.

Richard
Title: Re: BSOD aswsnx.sys
Post by: pk on June 27, 2013, 04:29:40 PM
Please send me all your minidumps (\Windows\Minidump folder) to kurtin@avast.com
Thanks.
Title: Re: BSOD aswsnx.sys
Post by: avast@@dvantage77.com on June 27, 2013, 06:13:09 PM
Dear Richard, please send your mini-dumps to P.K. as this process will insure that we know whats going on for the future.  If some chasnges need to be made, P.K. WILL be the guy to do it, as he is the MAN!

What is ASWclear and how do you proceed?

http://advantage77.com/blog/2013/04/11/how-to-do-a-clean-install-of-avast-pro-using-the-avast-removal-tool/

I have only tested this on Endpoint Protection Suite Plus V.8 RC on a File Server (but it should be the same, as both are the version 8 engine.)

This how I did it. After ASWclear, and reboot, then I did a custom install, and under components, I cleared "Sandbox" and "SafeZone" check boxes.   

NOTE:  I really like AutoSandbox, and you WILL lose that feature with this install. AutoSandbox is the only thing standing between us and Polymorphic infection. Symantec has no AutoSandbox, so they just let the infection occur and try to mitigate the damage.

The normal reason I would not install the virtualization drivers are File Servers. We strip those installations to the File System Shield only.

Please let me know your result.  After this install, hopefully you should not be able to find ASWSNX.SYS.


Sincerely,
 
J.R. "AutoSandbox Guy" Guthrie

"At this point in time, the Internet should be regarded as an Enemy Weapons System!"

 
Title: Re: BSOD aswsnx.sys
Post by: ralbrux on June 28, 2013, 03:49:24 PM
Hi pk,

After making my post I had a thought that maybe I was in the wrong forum.  I got to this forum by googling on "bsod aswsnx.sys" and did not pay attention to the forum title when I started reading the thread.   Actually I have a 5-user license for Avast  pro antivirus which is running on boxes on our LAN.  Does this qualify as Business Protection and is it pertinent to this forum?

Please advise me if I'm in the right forum.

Thanks,
Richard
Title: Re: BSOD aswsnx.sys
Post by: dexter@md on December 15, 2013, 10:18:17 AM
Hi,

I just got BSOD with following info:

Quote
121513-16848-01.dmp
15.12.2013 01:22:55   DRIVER_POWER_STATE_FAILURE   0x0000009f   00000000`00000003   fffffa80`07371e30   fffff800`04c5a3d8   fffffa80`0d6d7010   aswSnx.sys   aswSnx.sys+e1400   avast! Virtualization Driver   avast! Antivirus   AVAST Software   9.0.2008.177   x64   ntoskrnl.exe+75bc0               C:\Windows\Minidump\121513-16848-01.dmp   4   15   7601   927,024   15.12.2013 10:54:55   

Looks like issue is still not fixed.
How can I disable the virtualization driver?
Title: Re: BSOD aswsnx.sys
Post by: Inapickle on December 26, 2013, 10:44:01 PM
I also got this BSOD after installing Win 7 SP1 Home Premium 64-bit. This was a clean install. Let windows install all the high priority windows updates and then installed Avast AV (free version). Then got this system crash at windows log-in - first screen froze with scrambled horizontal lines, then BSOD. Nearly freaked when it happened as I feared a hardware problem. Ran MemTest and it passed OK. Did a clean re-install of Win7, updated and installed Avast again. Same problem.

Ran WhoCrashed (WinDbg) on the minidump, which identified aswsnx.sys as the cause.

Report:

Quote
System Information (local)
--------------------------------------------------------------------------------

computer name: XXXXXXXXXXXX
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M5A78L-M LX PLUS
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 4007780352 total
VM: 2147352576, free: 1929555968




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 12/24/2013 7:38:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122413-25334-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800029B0B05, 0xFFFFF8800794EE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 12/24/2013 7:38:30 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x2D53F)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800029B0B05, 0xFFFFF8800794EE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 SYSTEM_SERVICE_EXCEPTION



On Tue 12/24/2013 3:47:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122313-24367-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x18 (0x0, 0xFFFFFA80051EA8E0, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. A third party driver has 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)

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 actually 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.


There I have been no further crashes in the 3 days that have passed since, but obviously I am monitoring things very closely.

I might add that I encountered no such problem with Avast when I was running XP Pro SP3 on the same PC up until a week ago.






Title: Re: BSOD aswsnx.sys
Post by: to246 on December 28, 2013, 10:17:57 PM
Similar problem for me, also on a clean install of Win 7, SP1, running the free version of Avast

The output from WhoCrashed

Quote
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Studio 1558, Dell Inc., 0NJWJR
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4148715520 total
VM: 2147352576, free: 1926381568




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 27/12/2013 17:11:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122713-32011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F5E990, 0xFFFFF88009777130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 27/12/2013 17:11:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x2CB71)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F5E990, 0xFFFFF88009777130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 SYSTEM_SERVICE_EXCEPTION



On Fri 27/12/2013 08:46:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122713-29296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F6F41F, 0xFFFFF88008543140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sun 22/12/2013 09:50:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122213-35927-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F6D41F, 0xFFFFF88008E52140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Mon 16/12/2013 23:14:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121613-34164-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F4C990, 0xFFFFF880074C5130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 07/12/2013 14:02:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120713-44304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D6241F, 0xFFFFF88007587430, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. A third party driver has 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)

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 actually 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.
Title: Re: BSOD aswsnx.sys
Post by: Inapickle on December 29, 2013, 03:23:24 PM
Another BSOD this morning, again identifying aswsnx.sys driver as the cause.

Granted, it is the free version I have been using, and I note that I have posted in the Business Protection section of the forum - but it was actually this thread that WhoCrashed first linked to in the crash report.

But is there really still no solution for this ?? Please don't tell me I'm going to have to ditch Avast to avoid this problem.
Title: Re: BSOD aswsnx.sys
Post by: jason999 on January 12, 2014, 02:24:02 AM
I have the exact same problem, as others have reported.

I'm running Windows 7 / 64-bit and am receiving a BSOD - 'System Service Exception'

-2 reported files: ntoskrnl.exe & aswsnx.sys via 'Who Crashed' program that interprets minidumps.

As far as I'm concerned, based on the prevelance of the reports and how far these reports are dated: this is unacceptable even for the free version.
This has to be the absolute worst offense Avast has ever created.  To the tech's working on this: how many years do you actually need to see this exact problem reported before you actually are capable of solving it? Pathetic.

The BSOD's could be multiple in frequency, or fine for a few hours, yet rest assured, it will happen again.
The AVASTCLEAR program better work
Title: Re: BSOD aswsnx.sys
Post by: Foxfan100 on January 21, 2014, 03:39:11 PM
I'm running paid Avast Internet Security on Win 7 Ultimate 64-bit, and for the first time ever I've had 2 BSODs caused by ASWSNX.SYS in the last 5 days or so.

Nothing has changed system-wise, all the health checks are OK, and I haven't altered anything in Avast. This is  a real nuisance and it would be helpful  to have some answers on the causes of this.
Title: Re: BSOD aswsnx.sys
Post by: Purple Helen on February 06, 2014, 04:13:05 PM
I am yet another victim.  (Windows 7, Home Premium, 64 bit)

15 BSOD crashes since mid December (virtually none before).  I had to teach myself how to use Windows debugger to discover Avast is the culprit.

Frankly I am very close to scrapping Avast and foregoing the rest of my paid subscription - since the new versions it has caused me nothing but pain - the user front end is impenetrable (try to find out how to disable the Firewall!!), it randomly decided my Oxford English Dictionary was a "suspect file" (I've been using it, with Avast running, for years) and deleted it(!) - need I go on?

I have emailed my minidump files to PK and await developments.

Helen.
Title: Re: BSOD aswsnx.sys
Post by: Tricia_TD on March 13, 2014, 10:24:51 PM
My Windows 8.1 64 bit has been crashing with the message SYSTEM_SERVICE_EXCEPTION asw.Snx.sys  This has happened quite a few times now, but I only noted message down today and thought to look on the internet to see what it meant, and came across this thread.

I use Avast Internet Security.  I'm not up on techy things, and don't understand the previous posts.

Can anyone help me please?
Title: Re: BSOD aswsnx.sys
Post by: nobility on March 14, 2014, 04:15:37 PM
I having this problem ever since I went windows 8.1 - random thing but frustrating as hell. A few days ago I uninstalled my Avast free version and downloaded and re-installed the latest version - good for a couple of days and it just got the BSOD a few minutes ago. This has been reported for over a year with AVAST and no solutions - what gives with Avast support - time to get rid of this product and go to something else!
Title: Re: BSOD aswsnx.sys
Post by: camiano on March 20, 2014, 08:30:00 PM
I'm running the Pro version of AVAST on a Lenovo running Win 7 64 bit. About 2 weeks ago I started getting BSOD and, after some blue screen diagnostics, aswSNX.SYS is top of the list! BSOD were twice a day and were getting very annoying.

Uninstalled AVAST and now running Microsoft's MSE - no BSOD for over a week now.

The reason I bought AVAST was it looked good and had good reviews. Sadly I now seem to have wasted my money.

Is there any real solution to this apart from "reinstall and switch off the sandbox"?
Title: Re: BSOD aswsnx.sys
Post by: Purple Helen on March 23, 2014, 04:01:12 PM
Like Caminiano, I've scrapped my subscription to Avast and now rely on MSE - end of BSODs - Eureka!

Avast, don't you care that I will tell everyone I can to AVOID AVAST ????
Title: Re: BSOD aswsnx.sys
Post by: thekochs on March 25, 2014, 07:00:38 PM
OK....I may get blasted for this & I want to go on record I am NOT an expert, nor have any direct knowledge.
However, I'm a very techy person and have been reading this Forum daily since Avast9 came out....waiting/hoping for "me" to update from Avast8 across all PCs....just have one test PC running now.

Anyway, from my readings I understand that aswsnx.sys is the Avast Virtualization driver.
It is linked to Sandbox and one of the options that seems to have helped is to uninstall Sandbox feature.
For my two cents, everyone can determine for their own, I do a CUSTOM install and I've just enabled A/V shields....meaning I uncheck all other options.
I only use Avast as A/V with supplement of active shields from MBAM Pro.......both run nightly scans.
Thus, "for me", all these other features/programs....GrimeFighter, AOS ,etc. are of no use.
I only mention the above because it sounds like Avast is working out some of these items.
In the meantime, one option to see if it has effect/solve.
Go to Control Panel > Programs and Features
Select Avast
In the menu on the left select CHANGE
Remove the tick from Sandbox and then press continue.
On reboot you can decide, or not, to enable Avast hardened mode....if so....set to "aggressive" to replace the sandbox function.
Title: Re: BSOD aswsnx.sys
Post by: Tricia_TD on March 25, 2014, 07:13:02 PM
OK....I may get blasted for this & I want to go on record I am NOT an expert, nor have any direct knowledge.
However, I'm a very techy person and have been reading this Forum daily since Avast9 came out....waiting/hoping for "me" to update from Avast8 across all PCs....just have one test PC running now.

Anyway, from my readings I understand that aswsnx.sys is the Avast Virtualization driver.
It is linked to Sandbox and one of the options that seems to have helped is to uninstall Sandbox feature.
For my two cents, everyone can determine for their own, I do a CUSTOM install and I've just enabled A/V shields....meaning I uncheck all other options.
I only use Avast as A/V with supplement of active shields from MBAM Pro.......both run nightly scans.
Thus, "for me", all these other features/programs....GrimeFighter, AOS ,etc. are of no use.
I only mention the above because it sounds like Avast is working out some of these items.
In the meantime, one option to see if it has effect/solve.
Go to Control Panel > Programs and Features
Select Avast
In the menu on the left select CHANGE
Remove the tick from Sandbox and then press continue.
On reboot you can decide, or not, to enable Avast hardened mode....if so....set to "aggressive" to replace the sandbox function.

So what you're saying is that you think it's the Sandbox causing the problem.
Avast, are you reading this?  Can you not do something to correct the problem?  After all, you are the experts.

Thanks thekochs.  I'll try your suggestion.

Although I have to say that I like the idea of the Sandbox running, but not if it causes my laptop to crash when it feels like it.
Title: Re: BSOD aswsnx.sys
Post by: thekochs on March 26, 2014, 12:40:26 AM
OK....I may get blasted for this & I want to go on record I am NOT an expert, nor have any direct knowledge.
However, I'm a very techy person and have been reading this Forum daily since Avast9 came out....waiting/hoping for "me" to update from Avast8 across all PCs....just have one test PC running now.

Anyway, from my readings I understand that aswsnx.sys is the Avast Virtualization driver.
It is linked to Sandbox and one of the options that seems to have helped is to uninstall Sandbox feature.
For my two cents, everyone can determine for their own, I do a CUSTOM install and I've just enabled A/V shields....meaning I uncheck all other options.
I only use Avast as A/V with supplement of active shields from MBAM Pro.......both run nightly scans.
Thus, "for me", all these other features/programs....GrimeFighter, AOS ,etc. are of no use.
I only mention the above because it sounds like Avast is working out some of these items.
In the meantime, one option to see if it has effect/solve.
Go to Control Panel > Programs and Features
Select Avast
In the menu on the left select CHANGE
Remove the tick from Sandbox and then press continue.
On reboot you can decide, or not, to enable Avast hardened mode....if so....set to "aggressive" to replace the sandbox function.

So what you're saying is that you think it's the Sandbox causing the problem.
Avast, are you reading this?  Can you not do something to correct the problem?  After all, you are the experts.

Thanks thekochs.  I'll try your suggestion.

Although I have to say that I like the idea of the Sandbox running, but not if it causes my laptop to crash when it feels like it.

What I am saying is I am no expert and do not know the inner workings of Avast....only Avast knows that.....so me stating what "is" or "is not" the problem is not only wrong...but also misleading. However, it is well documented in the Forum that aswsnx.sys is the Virtualization driver. I personally have had the experience on other software packages where virtualization caused issues.....good examples is backup imaging software that tries to backup you system while you are still using it. I've seen bad virtualization drivers cause many BSODs in this example. So, my point is that this is something to try and see if it makes an impact for you.

IMHO you still have the Avast "Shields"........Sandbox which I agree is nice feature...but if causes BSODs then not so worth the benefits.
I also have not installed Avast's "Browser Protection".....again this not the Avast internet shields but what is known as AOS....a browser add-on.
This also has caused various issues for people thru their browsers....the suggestion has been is to disable the AOS plugin....I just don't install.
So, for me I am still on Avast8 except one test system....which I've backed down to just "shields" from custom install....which for my one W7 64-bit machine seems solid. The problem with all this is for every one bad post/thread there are so many that do not have issues....so statistically this becomes not relevant......but, it is relevant to the person with the issue........SO, that is why I posted the suggestion.  I hope it helps and will be interested to hear your results.

Lastly, if you are concerned about not having Sandbox then enable Hardened mode and set to aggressive....kind of a similar function/fallback.
However, do some reading on Hardened mode.....some people like it......some do not.

On the positive side I have used AVG, Avira, Windows Defender, Symantec, McAfee.....and Avast is still the best IHMO.
Avast 9 still is in its improvement stages but has come along way since Fall/2013 when first released.
I personally trust the Avast team.....else I would have bailed along time ago.
Title: Re: BSOD aswsnx.sys
Post by: Tricia_TD on March 26, 2014, 01:49:17 PM
OK....I may get blasted for this & I want to go on record I am NOT an expert, nor have any direct knowledge.
However, I'm a very techy person and have been reading this Forum daily since Avast9 came out....waiting/hoping for "me" to update from Avast8 across all PCs....just have one test PC running now.

Anyway, from my readings I understand that aswsnx.sys is the Avast Virtualization driver.
It is linked to Sandbox and one of the options that seems to have helped is to uninstall Sandbox feature.
For my two cents, everyone can determine for their own, I do a CUSTOM install and I've just enabled A/V shields....meaning I uncheck all other options.
I only use Avast as A/V with supplement of active shields from MBAM Pro.......both run nightly scans.
Thus, "for me", all these other features/programs....GrimeFighter, AOS ,etc. are of no use.
I only mention the above because it sounds like Avast is working out some of these items.
In the meantime, one option to see if it has effect/solve.
Go to Control Panel > Programs and Features
Select Avast
In the menu on the left select CHANGE
Remove the tick from Sandbox and then press continue.
On reboot you can decide, or not, to enable Avast hardened mode....if so....set to "aggressive" to replace the sandbox function.

So what you're saying is that you think it's the Sandbox causing the problem.
Avast, are you reading this?  Can you not do something to correct the problem?  After all, you are the experts.

Thanks thekochs.  I'll try your suggestion.

Although I have to say that I like the idea of the Sandbox running, but not if it causes my laptop to crash when it feels like it.

What I am saying is I am no expert and do not know the inner workings of Avast....only Avast knows that.....so me stating what "is" or "is not" the problem is not only wrong...but also misleading. However, it is well documented in the Forum that aswsnx.sys is the Virtualization driver. I personally have had the experience on other software packages where virtualization caused issues.....good examples is backup imaging software that tries to backup you system while you are still using it. I've seen bad virtualization drivers cause many BSODs in this example. So, my point is that this is something to try and see if it makes an impact for you.

IMHO you still have the Avast "Shields"........Sandbox which I agree is nice feature...but if causes BSODs then not so worth the benefits.
I also have not installed Avast's "Browser Protection".....again this not the Avast internet shields but what is known as AOS....a browser add-on.
This also has caused various issues for people thru their browsers....the suggestion has been is to disable the AOS plugin....I just don't install.
So, for me I am still on Avast8 except one test system....which I've backed down to just "shields" from custom install....which for my one W7 64-bit machine seems solid. The problem with all this is for every one bad post/thread there are so many that do not have issues....so statistically this becomes not relevant......but, it is relevant to the person with the issue........SO, that is why I posted the suggestion.  I hope it helps and will be interested to hear your results.

Lastly, if you are concerned about not having Sandbox then enable Hardened mode and set to aggressive....kind of a similar function/fallback.
However, do some reading on Hardened mode.....some people like it......some do not.

On the positive side I have used AVG, Avira, Windows Defender, Symantec, McAfee.....and Avast is still the best IHMO.
Avast 9 still is in its improvement stages but has come along way since Fall/2013 when first released.
I personally trust the Avast team.....else I would have bailed along time ago.

Well I've disabled the Sandbox, so time will tell. . .

Thanks for your help thekochs.  :D
Title: Re: BSOD aswsnx.sys
Post by: thekochs on March 26, 2014, 03:17:38 PM
Well I've disabled the Sandbox, so time will tell. . .
Thanks for your help thekochs.  :D

No problem.....favor to ask......please post back (I assume you will if you have BSOD) but also if you have none.
I think many would like to know the results and if this truly had a positive effect.
Title: Re: BSOD aswsnx.sys
Post by: Tricia_TD on March 26, 2014, 03:54:46 PM
Well I've disabled the Sandbox, so time will tell. . .
Thanks for your help thekochs.  :D

No problem.....favor to ask......please post back (I assume you will if you have BSOD) but also if you have none.
I think many would like to know the results and if this truly had a positive effect.

Yes, will do.  I've marked it in my calendar to remind me, in a month's time.  When/if it doesn't happen, I might forget!  :o
Title: Re: BSOD aswsnx.sys
Post by: thekochs on March 28, 2014, 02:52:02 AM
Well I've disabled the Sandbox, so time will tell. . .
Thanks for your help thekochs.  :D

No problem.....favor to ask......please post back (I assume you will if you have BSOD) but also if you have none.
I think many would like to know the results and if this truly had a positive effect.

Yes, will do.  I've marked it in my calendar to remind me, in a month's time.  When/if it doesn't happen, I might forget!  :o

Good quick summary/post on Hardened Mode: http://forum.avast.com/index.php?topic=142172.msg1032485#msg1032485
Title: Re: BSOD aswsnx.sys
Post by: Tricia_TD on March 28, 2014, 11:21:01 AM
Thanks for that thekochs :D .  I've enabled Hardened Mode now.

No BSOD so far :D .
Title: Re: BSOD aswsnx.sys
Post by: diegs on April 01, 2014, 03:20:49 AM
Hi, I have the similar problem, but my version of avast is free and don´t have the Sandbox option, in this place have "?". My OS is Win8.1 64b.
Title: Re: BSOD aswsnx.sys
Post by: thekochs on April 01, 2014, 03:27:55 AM
Hi, I have the similar problem, but my version of avast is free and don´t have the Sandbox option, in this place have "?". My OS is Win8.1 64b.
As far as the "?" that is a good question..........I thought you could uncheck Sandbox in FREE ?.....perhaps Sandbox is not in FREE ?
You say you have "similar" problem....and using FREE.....you are specifically getting BSODs and you are sure they are aswsnx.sys related ? If so, how do you know ?....e.g. dump file you used util to see, etc.

Perhaps one of the Sr. folks will post.
Title: Re: BSOD aswsnx.sys
Post by: Tricia_TD on May 06, 2014, 10:09:21 PM
So it's a month later, and no more BSOD.  Thank you for your help thekochs.   :D
Title: Re: BSOD aswsnx.sys
Post by: vukwap on September 20, 2014, 05:10:47 PM
I'm using windows 8.1 64bit and haved bsod caused by driver aswSnx.sys , caused by address aswSnx.sys+37ad .
This is my first bsod on this system.
Title: Re: BSOD aswsnx.sys
Post by: Dariusz on July 19, 2015, 10:15:07 AM
I'm getting this BSOD in my latest avast as well !

It actually totally lock down my PC, crashes every program, lag out vred, PS, Vue, 3ds max and other softwares. Makes my life a living hell !

I already was on Hardened mode - Agressive.

Not helping. My PC just lock down and programs crashes. Specially when in the morning I come back to PC and do anyting it goes down badly. Is there another way I can fix the issue?

This problem started to happen ONLY when I installed new GPU, Titan X EVGA SC. Before I was on GTX 680 everything was fine. Also I did reinstall windows etc etc. Any one any help please?!

BSOD :
http://postimg.org/image/esqa8pjkv/
Title: Re: BSOD aswsnx.sys
Post by: LesF on August 01, 2015, 02:50:54 AM
I have had this happen too.  I have freshly re-installed win7-64 after a disk failure.
After all the installs and updates and shuffling about backup files I decided to do a defrag. While this was running there was a BSOD:

The problem seems to be caused by the following file: ngvss.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
etc...


and a few hours later, after restarting, another BSOD:

The problem seems to be caused by the following file: aswSnx.sys
PAGE_FAULT_IN_NONPAGED_AREA


Avast is a fresh re-install with no changes to settings.

Is there a general area to investigate for this?