Kaspersky causing netio.sys BSOD

[mlnevese]

I just bought a new laptop last week and now I'm getting a netio.sys BSOD randomly. I used to get this with KIS back in the 2013 or 2014 version but it's the first time I'm getting it with the 2017 version.

I have already updated all my network drivers but this time it has not solved the problem. I believe it may be a conflict with Adguard's WFP network driver... any advice?

 

[Wave]

There's an easy way to find out... Uninstall one of them (recommended to be Adguard over your primary security software) and then see if the BSOD crashes still occur. If they do then you know it isn't a conflict-related issue between both those software's, and if it doesn't then you know it's either due to the product you uninstalled, or it was a conflict.

These things can take a huge investigation process. you need to do testing to identify the real cause of the problem (e.g. one product is causing it or compatibility problem, etc.).

Have you tried contacting Kaspersky/Adguard support yet for any info's from themselves?

 

[Wave]

You can also try checking Event Viewer and see if there's any info there, or use a crash dump from BSOD

 

[mlnevese]

Adguard has known compatibility problems with both Kaspersky and Eset... the latest RC was supposed to have solved them. I'll take a look at event viewer and the dump to see who is causing the crash. If it is actually a conflict it may be as simple as turning off https scanning in Kaspersky.

 

[Wingman]

I just bought a new laptop last week and now I'm getting a netio.sys BSOD randomly.

Have you performed a full memory dump and u know it's netio.sys or do you suspect this may be the issue?

 

[mlnevese]

The BSOD message points netio.sys and that would be consistent with a known conflict in previous versions of Kaspersky and Adguard... I'm taking a look ant my system events and dumps right now... I've seem netio.sys BSODS caused by graphics drivers in the past so... who knows

 

[Wave]

What is the crash error on the BSOD screen and what device driver is it coming from?

edit: sorry only just seen your recent reply

 

[mlnevese]

It's a System Service Exception, but I can't see a clear cause in the dump...

021117-34968-01.dmp 11/02/2017 00:16:43 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff803`6116e01a ffffc380`873230b0 00000000`00000000 NETIO.SYS NETIO.SYS+e01a x64 ntoskrnl.exe+14a6f0 C:\Windows\Minidump\021117-34968-01.dmp 4 15 14393 925.516 11/02/2017 00:25:39

 

[mlnevese]

And it's an Adguard conflict... I just found what that memory pointer was


021117-34968-01.dmp 11/02/2017 00:16:43 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff803`6116e01a ffffc380`873230b0 00000000`00000000 NETIO.SYS NETIO.SYS+e01a x64 ntoskrnl.exe+14a6f0 C:\Windows\Minidump\021117-34968-01.dmp 4 15 14393 925.516 11/02/2017 00:25:39

adgnetworkwfpdrv.sys fffff803`63580000 fffff803`63595000 0x00015000 0x58921407 01/02/2017 14:59:51

 

[SpartacusSystem]

I get netio.sys conflict too with Adguard, I made a thread on the Adguard forums, you should too. I unchecked 'Use WFP network driver' and all seems well.

 

[mlnevese]

@SpartacusSystem Sounds like a good idea... I just did that. I also opened a support ticket.

 

[Kubla]

It is the WFP Network driver in Adguard disable it and the BSOD's will stop.

They have released some fixes for it the latest is RC1:

Releases · AdguardTeam/AdguardForWindows · GitHub

But I still get the BSOD with that driver enabled in Adguard so all the bugs are not ironed out yet.