Jump to content

My TCPIP.sys BSOD crash related to Malwarebytes "Web Access Control"?

Recommended Posts

First, I must explain that you're running a Windows Insider Preview build.
These builds are not as stable as the versions that are released for everyone.
And, you don't have the latest Fast Ring version - so I'm uncertain if this is a Slow-Ring build or you just haven't updated to the latest Fast Ring build (15025).
Lastly, there have been problems with Insider bulds and MalwareBytes Premium - and while Microsoft has changed teh builds, there has been no official statement if the issue has been fixed (that I have seen).

Your UEFI/BIOS (version 7.16) dates from 2011.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 1 Windows Update hotfix installed.  I'm uncertain how many are usually found in your build.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

You have a Linksys AE2500 USB wifi device.  In the past these devices have had problems running with Windows.  I haven't seen these problems recently (when using W10 compatible drivers) - but would suggest keepin an eye on it for now.  Here's my old canned speech about these devices:

I do not recommend using wireless USB network devices.

These wireless USB devices have many issues with Win7 and later systems - using older drivers with them is almost certain to cause a BSOD.
Should you want to keep using these devices, be sure to have the latest W7/8/8.1/10 drivers - DO NOT use older drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Please note that your AE2500w764.sys driver dates from 2014 - well before W10 was released

C: drive only has about 12% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.  This isn't crucial now, but can become a problem as the free space decreases in the future.

Please note the following error:
This means that the timestamp on the NETIO.SYS drivers is old (in this case, it dates from 1970)
IMO this means that the driver is still experimental - and may have problems.

Also interesting is the vmsproxy.sys driver dating from 1989
It's a Windows driver (VMSWITCH Proxy Driver) - but it doesn't appear in my build 14393 system, nor in my build 15014 system.
I have to wonder if it was used only in the 14986 build that you are running, or if it's for a component that isn't used on my system(s).

Finally, please have a look at the older drivers on the system in the listing below.  Those that are corssed out are Windows drivers - so don't worry about them as long as you have all Windows Updates.  The others should be updated to the latest, W10 compatible versions.

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

**************************Mon Feb  6 12:41:18.155 2017 (UTC - 5:00)**************************

Loading Dump File [C:\Users\john\SysnativeBSODApps\020617-140468-01.dmp]
Windows 10 Kernel Version 14986 MP (4 procs) Free x64
System Uptime:0 days 0:24:00.807
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by :NETIO.SYS ( NETIO!FeCompleteClassify+ad )
BugCheck 3B, {c0000005, fffff80a88e018a3, ffffd38066e189c0, 0}
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80a88e018a3, Address of the instruction which caused the bugcheck
Arg3: ffffd38066e189c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3293
  BIOS Version                  7.16
  BIOS Release Date             10/05/2011
  Manufacturer                  Hewlett-Packard
  Baseboard Manufacturer        PEGATRON CORPORATION
  Product Name                  p6-2026
  Baseboard Product             2AC2

3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Feb  6 12:41:18.155 2017 (UTC - 5:00)**************************
cldflt.sys                  ***** Invalid 1996 Invalid 1996 Invalid
synth3dvsp.sys              ***** Invalid 2016 Invalid 2016 Invalid
hvsocketcontrol.sys         ***** Invalid 2028 Invalid 2028 Invalid
intelppm.sys                Tue Jun 13 03:21:26 1972 (049B0476)
vmsproxy.sys                Mon Jan 16 10:31:39 1989 (23D20ADB)

BthA2DP.sys                 Sun Mar 11 15:54:14 2001 (3AABD7E6) - I am uncertain about this one, it may be from Windows Update
PxHlpa64.sys                Wed Mar 12 21:58:17 2008 (47D88A39)
ElRawDsk.sys                Tue Oct 26 05:34:13 2010 (4CC6A095)
gfibto.sys                  Thu Sep  1 21:31:28 2011 (4E6031F0)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
PDFsFilter.sys              Thu May 10 12:29:02 2012 (4FABECCE)
ccSetx64.sys                Mon Sep 23 23:58:04 2013 (52410DCC)
AE2500w764.sys              Wed Dec 31 02:16:34 2014 (54A3A2D2)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
igdkmd64.sys                Tue May 26 23:53:18 2015 (55653FAE)
cthda.sys                   Thu Jun 18 02:14:05 2015 (558261AD)
cthdb.sys                   Thu Jun 18 02:14:10 2015 (558261B2)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)

**Windows 10 released on 29 July 2015**

AmUStor.SYS                 Fri Sep  4 05:22:51 2015 (55E962EB)
mbae64.sys                  Fri Apr 29 06:10:09 2016 (57233301)
ccSetx64.sys                Thu May  5 18:33:33 2016 (572BCA3D)
Ironx64.SYS                 Fri Sep  2 17:44:25 2016 (57C9F2B9)
SRTSPX64.SYS                Fri Sep  2 21:56:42 2016 (57CA2DDA)
SYMEVENT64x86.SYS           Thu Sep  8 15:47:29 2016 (57D1C051)
SRTSP64.SYS                 Tue Sep 13 21:14:58 2016 (57D8A492)
SYMNETS.SYS                 Wed Sep 14 22:43:10 2016 (57DA0ABE)
mbam.sys                    Wed Sep 28 11:45:44 2016 (57EBE5A8)
rt640x64.sys                Fri Oct  7 05:24:19 2016 (57F769C3)
SYMEFASI64.SYS              Wed Oct 12 14:18:04 2016 (57FE7E5C)
BHDrvx64.sys                Fri Nov  4 05:39:20 2016 (581C5748)
MBAMChameleon.sys           Sat Nov 19 14:13:08 2016 (5830A444)
IDSvia64.sys                Fri Dec  2 12:58:53 2016 (5841B65D)
farflt.sys                  Fri Dec 16 11:38:59 2016 (585418A3)
eeCtrl64.sys                Tue Jan  3 15:08:58 2017 (586C04DA)
EraserUtilRebootDrv.sys     Tue Jan  3 15:08:59 2017 (586C04DB)
mwac.sys                    Tue Jan  3 18:21:14 2017 (586C31EA)
MBAMSwissArmy.sys           Wed Jan  4 03:34:33 2017 (586CB399)
hvsocket.sys                Fri Dec 15 01:09:32 2028 (6EE4921C)

[color=#777777][color=#4b0082]vmsproxy.sys[/color] - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.[/color]
[color=#777777][color=#4b0082]farflt.sys[/color] - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.[/color]
[color=#777777][color=#4b0082]hvsocket.sys[/color] - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.[/color]
[color=#777777][color=#4b0082]cldflt.sys[/color] - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.[/color]
[color=#777777][color=#4b0082]synth3dvsp.sys[/color] - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.[/color]
[color=#777777][color=#4b0082]hvsocketcontrol.sys[/color] - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.[/color]


Link to post
Share on other sites

The only way to update NETIO.sys is through Windows Update.
Quite frankly, I don't expect that that is the problem - but as it has that strange date, I believe it's something that they modified for the build that you have.
As such it may be that your drivers (wired/wireless/bluetooth) may not operate properly with this version.

HP doesn't offer W10 drivers for your system - so you have to wonder if it's compatible w/W10
Also, as you're running Insider builds, I also have to wonder if it's compatible with them also.
Unfortunately, the only sure "test" to determine this is to revert to the version of Windows that came on the system.
If it runs without problems there, then you've verified that the problem is compatibility.



Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.