AdGuard for Windows v6.1.314

Status
Not open for further replies.
Boo Berry

Boo Berry

Moderator + Beta Tester
Moderator
Damn, I jinxed myself above somehow it seems. I got a real random BSOD while not actively browsing the net (Chrome was started but minimized/idle), With ESET Internet Security 10 set to Pause protection (until restart) while playing a game of Microsoft Solitaire Collection (which is filtered through Adguard) in-between games.

Of course the offenders seem to be NETIO.SYS and ntoskrnl.exe which is consistent. Hopefully a one time thing.
 
P

Paul Thijs

New Member
Well unfortunatly , after quite some time i reinstalled KIS 2017 again and i get randomly BSOD's on both machines ( ASUS > W10 ) NETIO.SYS exception. Trying now with disabled WFP driver in Adguard , and see how it keeps up .....or not

dump : On Wed 8-3-2017 14:44:32 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: klwtp.sys (klwtp+0xA0BE)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80A8EF3E9F3, 0xFFFFD300DA164000, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\klwtp.sys
product: System Interceptors PDK
company: AO Kaspersky Lab
description: WFP Network Connection Filter Driver [fre_win8_x64]
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: klwtp.sys (WFP Network Connection Filter Driver [fre_win8_x64], AO Kaspersky Lab).
Google query: AO Kaspersky Lab SYSTEM_SERVICE_EXCEPTION
 
Last edited:
caleb59

caleb59

Member
New RC is available but is this definitely solved problem with ESET and Kaspersky? What when new versions of ESET and Kaspersky will be released? BSOD's may come back?
 
Boo Berry

Boo Berry

Moderator + Beta Tester
Moderator
It should be solved, yes. The build was tested against a KIS RC build too, and was made compatible.

I'm assuming for every major KIS/ESET update, they'll need to be checked to ensure compatibility.
 
caleb59

caleb59

Member
I'm assuming for every major KIS/ESET update, they'll need to be checked to ensure compatibility.
Click to expand...
If so then it will be a titanic work for AdGuard Team - not mention to keep an eye on it - so I guess our happiness will be still limited - new ESET/Kaspersky version = new BSOD's probability...
God damn...
 
Boo Berry

Boo Berry

Moderator + Beta Tester
Moderator
That depends on ESET/Kaspersky doing something with their WFP drivers causing an incompatibility. Right now there shouldn't be one anymore, but you never know what they'll do.

Since ESET/Kaspersky updates seldomly come, keeping track of them shouldn't be too much of an issue.

Also, I don't believe ESET or Kaspersky pushes out new updates immediately either, so there should be time to ensure compatibility and push new Adguard builds if need be.
 
caleb59

caleb59

Member
New BSOD! Again Netio.sys...
Uploading .dmp's...

http://www39.zippyshare.com/v/AWVlAVtK/file.html

Slowly I'm thinking that you'll never pinpoint this issue for good and AdGuard will be always unstable when using WFP driver...
Do I really have to go back to uBlock Origin like some dirty peasant because AdGuard is still unstable?

God damn... I'm pissed off...
 
Last edited:
P

Paul Thijs

New Member
Well ....again BSOD. This time with Avast Premier installed.

On Fri 24-3-2017 03:34:07 your computer crashed
crash dump file: C:\Windows\Minidump\032417-11781-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0xE9F3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8005C28E9F3, 0xFFFFD2805116A860, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 24-3-2017 03:34:07 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswstm.sys (aswStm+0xBB8C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8005C28E9F3, 0xFFFFD2805116A860, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswstm.sys
product: Avast Antivirus
company: AVAST Software
description: Stream Filter
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: aswstm.sys (Stream Filter, AVAST Software).
Google query: AVAST Software SYSTEM_SERVICE_EXCEPTION

I am wondering if it is an Adguard issue or a Windows 10 issue..........
 
vasily_bagirov

vasily_bagirov

Administrator
Staff member
Administrator
@Paul Thijs we've released quite a few builds in an attempt to fix this issue, and the latest one seems to be stable enough. What is the exact version you are using?

We have a huge thread on GitHub dedicated to this problem: https://github.com/AdguardTeam/AdguardForWindows/issues/1565

You can install the latest build either by switching to the beta update channel or by finding a link to it in the thread mentioned above.
 
P

Paul Thijs

New Member
vasily_bagirov said:
@Paul Thijs we've released quite a few builds in an attempt to fix this issue, and the latest one seems to be stable enough. What is the exact version you are using?

We have a huge thread on GitHub dedicated to this problem: https://github.com/AdguardTeam/AdguardForWindows/issues/1565

You can install the latest build either by switching to the beta update channel or by finding a link to it in the thread mentioned above.
Click to expand...
Did already test the latest RC ( 325 / 326 ) , and still got a BSOD. So...i'll stick to Windows Defender for now ...or forever , sick and tired of BSOD
 
Status
Not open for further replies.
Top