06-30-2020, 09:25 AM
Join Date: Oct 2011
Location: London - UK
OS: Windows 10 Home Version 1909 - 64 Bit
Over 14 years of using Windows XP I never had a single Netio.sys BSOD error.
Reason ? Windows XP never had a Netio.sys driver.
My AV was Avast and Firewall was ZoneAlarm, exactly as I have now with my
Windows 10 Home system. But Windows 10 does have a Netio.sys driver and so
I now get frequent BSOD's.
OK, they automatically resolve themselves, but the process is an inconvenient interruption and infuriating.
My regular failures are due to -
Using WhoCrashed on the last two occasions revealed that an Avast driver was in conflict on one occasion and a ZoneAlarm driver on the next.
It is no use at all just saying get rid of these programs and use Windows Defender, why should I ? They are superb programs. In any case, AVG, Malwarebytes and certainly McAfee also cause Netio.sys crashes.
It is almost indicative of Netio.sys being included in Windows 10 to block all superb third party programs, so that Windows Defender is the only option left to prevent these BSOD from making our lives a misery.
The myriad of exhaustive fixes given on the web for Netio.sys errors is infinite, complex, risky and simply not an option. So I guess I will have to love and tolerate Windows 10 presenting me with these BSOD's on inconvenient occasions.