Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: s4n17y on February 04, 2022, 08:36:29 AM
-
HI,
Lately I have been getting BSOD and the cause is aswNetHub.sys according to the memory dump:
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000046, The exception code that was not handled
Arg2: fffff8013212824a, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2562
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3395
Key : Analysis.Init.CPU.mSec
Value: 3405
Key : Analysis.Init.Elapsed.mSec
Value: 25959
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 020422-12062-01.dmp
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000046
BUGCHECK_P2: fffff8013212824a
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffc38c`80c2cbc8 fffff801`322f5a9e : 00000000`0000001e ffffffff`c0000046 fffff801`3212824a 00000000`00000000 : nt!KeBugCheckEx
ffffc38c`80c2cbd0 fffff801`3220019f : fffff801`322f5a7c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffffc38c`80c2cc10 fffff801`320e6f17 : ffffc38c`80c2d180 00000000`00000000 ffffc38c`80c2fb60 fffff801`321fae4e : nt!RtlpExecuteHandlerForException+0xf
ffffc38c`80c2cc40 fffff801`320e6986 : ffffc38c`80c2d8a0 ffffc38c`80c2d900 ffffc38c`80c2d3a0 00000000`00000000 : nt!RtlDispatchException+0x297
ffffc38c`80c2d360 fffff801`3212824a : 00000000`00000001 ffffe680`27400180 00000000`00000000 00000000`00000001 : nt!RtlRaiseException+0xf6
ffffc38c`80c2d8e0 fffff801`32085eba : 00000000`00000000 fffff801`4a24cb58 00000000`00000000 ffffc38c`80c2df41 : nt!RtlRaiseStatus+0x4a
ffffc38c`80c2de80 fffff801`32084ea4 : ffffb30d`00000002 00000000`00000001 ffffc38c`80c2e390 fffff801`4a24cb00 : nt!KeReleaseMutant+0x2ca
ffffc38c`80c2df70 fffff801`4a22aab1 : ffffc38c`80c2df20 00000000`00000000 ffffb30d`91408ab1 01d81996`f75a87ae : nt!KeReleaseMutex+0x14
ffffc38c`80c2dfa0 ffffc38c`80c2df20 : 00000000`00000000 ffffb30d`91408ab1 01d81996`f75a87ae 00000000`00000000 : aswNetHub+0x5aab1
ffffc38c`80c2dfa8 00000000`00000000 : ffffb30d`91408ab1 01d81996`f75a87ae 00000000`00000000 fffff801`4a1dd1ff : 0xffffc38c`80c2df20
SYMBOL_NAME: aswNetHub+5aab1
MODULE_NAME: aswNetHub
IMAGE_NAME: aswNetHub.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 5aab1
FAILURE_BUCKET_ID: 0x1E_c0000046_aswNetHub!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d617c233-dc06-b91b-7d1f-2dfc8f5a5a87}
Followup: MachineOwner
---------
1: kd> lmvm aswNetHub
Browse full module list
start end module name
fffff801`4a1d0000 fffff801`4a25b000 aswNetHub T (no symbols)
Loaded symbol image file: aswNetHub.sys
Image path: \SystemRoot\system32\drivers\aswNetHub.sys
Image name: aswNetHub.sys
Browse all global symbols functions data
Timestamp: Mon Nov 29 13:41:41 2021 (61A4BC75)
CheckSum: 000892AE
ImageSize: 0008B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
how do I fix this issue?
Regards
-
- Which Avast..? (Free/Premium/One)
- Which version/build of Avast..?
- OS..? (32/64 Bit..? - which SP/Build..?)
- Other security related software installed..?
- Which AV(s) did you use before Avast..?
-
- Which Avast..? (Free/Premium/One) - Avast Premium Security
- Which version/build of Avast..? - 21.11.2500 (build 21.11.6809.528)
- OS..? (32/64 Bit..? - which SP/Build..?) - Windows 10 19044.1466
- Other security related software installed..? - None
- Which AV(s) did you use before Avast..? - None(clean install of OS happened 1 month ago)
-
You could try the latest beta: https://forum.avast.com/index.php?board=15
-
wow guess this is the extent of Avast's support....guess I'll be moving to a new AV even though I have been an Avast customer for 6 to 7 years
-
Hi, there are some fixes in version 22.1, so I'd suggest to try that first.
If it doesn't help and BSOD continue, report back and we will dig deeper.
-
HI,
Lately I have been getting BSOD and the cause is aswNetHub.sys according to the memory dump:
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000046, The exception code that was not handled
Arg2: fffff8013212824a, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Hi,
Our developers are looking into this issue.
-
Issue still present after updating to the Beta
First BSOD after the beta update
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000046, The exception code that was not handled
Arg2: fffff803329282ba, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for aswNetHub.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2858
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 11208
Key : Analysis.Init.CPU.mSec
Value: 327
Key : Analysis.Init.Elapsed.mSec
Value: 7781
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 021122-14046-01.dmp
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000046
BUGCHECK_P2: fffff803329282ba
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff803`3785cbc8 fffff803`32af5aae : 00000000`0000001e ffffffff`c0000046 fffff803`329282ba 00000000`00000000 : nt!KeBugCheckEx
fffff803`3785cbd0 fffff803`32a0026f : fffff803`32af5a8c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff803`3785cc10 fffff803`328e6f87 : fffff803`3785d180 00000000`00000000 fffff803`3785fb60 fffff803`329faf1e : nt!RtlpExecuteHandlerForException+0xf
fffff803`3785cc40 fffff803`328e69f6 : fffff803`3785d8a0 fffff803`3785d900 fffff803`3785d3a0 00000000`00000000 : nt!RtlDispatchException+0x297
fffff803`3785d360 fffff803`329282ba : 00000000`00000001 fffff803`2e000180 00000000`00000000 00000000`00000001 : nt!RtlRaiseException+0xf6
fffff803`3785d8e0 fffff803`32885eba : 00000000`00000000 fffff803`4947eb58 00000000`00000000 fffff803`3785df41 : nt!RtlRaiseStatus+0x4a
fffff803`3785de80 fffff803`32884ea4 : ffff9104`00000000 00000000`00000001 fffff803`3785e390 fffff803`4947eb00 : nt!KeReleaseMutant+0x2ca
fffff803`3785df70 fffff803`4945bde1 : fffff803`3785df20 00000000`00000000 ffff9104`35a08ab1 01d81f1e`73a0e9a0 : nt!KeReleaseMutex+0x14
fffff803`3785dfa0 fffff803`3785df20 : 00000000`00000000 ffff9104`35a08ab1 01d81f1e`73a0e9a0 00000000`00000000 : aswNetHub+0x5bde1
fffff803`3785dfa8 00000000`00000000 : ffff9104`35a08ab1 01d81f1e`73a0e9a0 00000000`00000000 fffff803`4940d7ff : 0xfffff803`3785df20
SYMBOL_NAME: aswNetHub+5bde1
MODULE_NAME: aswNetHub
IMAGE_NAME: aswNetHub.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 5bde1
FAILURE_BUCKET_ID: 0x1E_C0000046_aswNetHub!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d617c233-dc06-b91b-7d1f-2dfc8f5a5a87}
Followup: MachineOwner
---------
This was the 2nd BSOD after updating
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021122-14046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021322-14296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`04800000 PsLoadedModuleList = 0xfffff800`0542a2d0
Debug session time: Sun Feb 13 18:17:17.083 2022 (UTC + 2:00)
System Uptime: 2 days 8:08:52.066
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`04bf73b0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff868d`616b8670=00000000000000b8
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: ffff88827b206080, Original thread which is the cause of the failure
Arg2: ffff888273c3d080, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2515
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 18306
Key : Analysis.Init.CPU.mSec
Value: 514
Key : Analysis.Init.Elapsed.mSec
Value: 36287
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 021322-14296-01.dmp
BUGCHECK_CODE: b8
BUGCHECK_P1: ffff88827b206080
BUGCHECK_P2: ffff888273c3d080
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffff88827b206080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Discord.exe
DPC_STACK_BASE: FFFFF8000C867FB0
STACK_TEXT:
fffff800`0c865f80 fffff800`04a0c800 : ffff8882`786d9390 00000000`00000000 ffff8882`7960da50 fffff800`20876a85 : nt!KiSwapContext+0x76
fffff800`0c8660c0 fffff800`04a0bd2f : 00000000`00000001 ffff8882`00043b00 fffff800`0c866280 00000000`00000000 : nt!KiSwapThread+0x500
fffff800`0c866170 fffff800`04a0b5d3 : fffff800`00000000 ffff8882`00000000 ffff8882`80a7fc00 ffff8882`7b2061c0 : nt!KiCommitThreadWait+0x14f
fffff800`0c866210 fffff800`1e9ebc43 : fffff800`1ea0eb58 ffff8882`00000000 ffff8882`57c02100 fffff800`04a89300 : nt!KeWaitForSingleObject+0x233
fffff800`0c866300 fffff800`1ea0eb58 : ffff8882`00000000 ffff8882`57c02100 fffff800`04a89300 00000000`00000000 : aswNetHub+0x5bc43
fffff800`0c866308 ffff8882`00000000 : ffff8882`57c02100 fffff800`04a89300 00000000`00000000 fffff800`1e99d7ff : aswNetHub+0x7eb58
fffff800`0c866310 ffff8882`57c02100 : fffff800`04a89300 00000000`00000000 fffff800`1e99d7ff ffff8882`752b6f00 : 0xffff8882`00000000
fffff800`0c866318 fffff800`04a89300 : 00000000`00000000 fffff800`1e99d7ff ffff8882`752b6f00 fffff800`00000000 : 0xffff8882`57c02100
fffff800`0c866320 fffff800`1e99d767 : fffff800`0c866458 fffff800`0c866520 00000000`00000001 fffff800`0c866470 : nt!ExFreeHeapPool+0x280
fffff800`0c866400 fffff800`0c866458 : fffff800`0c866520 00000000`00000001 fffff800`0c866470 ffff8882`00000000 : aswNetHub+0xd767
fffff800`0c866408 fffff800`0c866520 : 00000000`00000001 fffff800`0c866470 ffff8882`00000000 00000000`00000000 : 0xfffff800`0c866458
fffff800`0c866410 00000000`00000001 : fffff800`0c866470 ffff8882`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`0c866520
fffff800`0c866418 fffff800`0c866470 : ffff8882`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff800`0c866420 ffff8882`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`0c866470
fffff800`0c866428 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff8882`00000000
SYMBOL_NAME: aswNetHub+5bc43
MODULE_NAME: aswNetHub
IMAGE_NAME: aswNetHub.sys
STACK_COMMAND: .process /r /p 0xffff88827898d080; .thread 0xffff88827b206080 ; kb
BUCKET_ID_FUNC_OFFSET: 5bc43
FAILURE_BUCKET_ID: 0xB8_aswNetHub!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9ddec478-1451-b023-7c0c-f2d8300c2426}
Followup: MachineOwner
---------
-
Did you miss the post by Avast? Just before your post.
The developers are looking into the problem
-
No I did not miss it, just thought I would give an update..
-
I got 3 of these in the last 24 hours...
This problem was reported a month ago...
"We're looking into it" is really not good enough...
If this happens one more time, I'll have to uninstall the software despite having a premium sub...
- Which Avast..? (Free/Premium/One) - Avast Premium Security
- Which version/build of Avast..? - 22.2.6003 (build 22.2.7013.711)
- OS..? (32/64 Bit..? - which SP/Build..?) - Windows 11 Pro 10.0.22000 Build 22000
- Other security related software installed..? - None
- Which AV(s) did you use before Avast..? - None
-
Hi,
Our developers are still working on this issue.
The only workaround would be to remove the Firewall component. https://support.avast.com/article/Add-Remove-Antivirus-components/
Please accept our apologies for any inconvenience caused.
-
Thank you for you reply, and the workaround!
-
Still no update.......uninstalled this product and installed another one....so much for being a "premium" sub. Wont be recommending Avast in ANY way.......
-
Hi,
The fix will be released in the next version.
-
same problem here.
Avast Premium Security
Version: 22.7.6025 (Build 22.7.7403.738)
Windows 10 Pro (Version 21H2 Build 19044.1826)
seems that the problem isn't fixed in the actual version.
-
same problem here.
Avast Premium Security
Version: 22.7.6025 (Build 22.7.7403.738)
Windows 10 Pro (Version 21H2 Build 19044.1826)
seems that the problem isn't fixed in the actual version.
Hi,
Does it help if you remove the Firewall component? https://support.avast.com/article/Add-Remove-Antivirus-components/