BSOD at random times with a Netio.sys issue

I have a Dell OptiPlex 7020 running Windows 10. I have tried updating all the drivers and having the registry checked for errors. Nothing seems to stop the daily BSOD with a netio.sys error. This is an office desktop behind a Barracuda firewall that runs mainly one accounting program with some internet use throughout the day. Running Windows scans and memory checks from safe mode has not turned up any issues.

Hi,

All crashdumps show stop code 0x0000001E. Network Adapter driver and AVG shown as cause in the dump analysis. Please update or roll back the network driver and remove AVG for testing purposes:

Code:

0x0000001E:    KMODE_EXCEPTION_NOT_HANDLED (25.07.2017 19:21:26) [Windows 10] 
 
CAUSED BY:     memory_corruption    
               e1d65x64.sys [18.06.2015] * Intel Pro/1000 Network Adapter driver * => https://downloadcenter.intel.com/ 
               avgwfpa.sys [27.07.2016] * AVG Firewall driver * => http://free.avg.com/eu-en/free-antivirus-download 
               avgfwd6a.sys [10.08.2015] * AVG * => Support: http://www.avg.com/us-en/support  
               FLTMGR.SYS ***** Invalid * Microsoft Filesystem Filter Manager (Windows System File) 
 
PROCESS:       System 
 
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

1) Upate or roll back network driver
This should be the right one: Download Intel® Network Adapter Driver for Windows® 10*
U can use the Intel update tool too for this: Download Intel® Driver Update Utility

2) Remove AVG

AVG	AVG | Download tools and utilities

Thank you! I did both of the recommended actions this morning. I will update the thread after a few days to see if this has fixed the issue. Thanks again.

Is there any news or did you fix the problem?

After removing AVG and the network driver, I reinstalled a new driver for the NIC. We have not had a BSOD error since then. I am going to reinstall AVG today and see if we can get it to work without any errors. I am going to mark this thread as Solved, as I believe your advice has correctly identified the issues. Thanks again for your help!

Glad to hear that your problem is now fixed. Let us know if there are any other problems.