This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multiple computers getting netio.sys BSOD after 2022.2.1.9 update

We're having an outbreak of DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD's in driver NETIO.SYS. Netio.sys caused BSOD's are usually tied to network drivers but that doesn't make sense because this started happening all of a sudden on multiple computers. These are fully patched/updated Windows 10 Pro computers. The common thing we're seeing is Sophos was updated to version 2022.2.1.9 around 7/20/22 on all of them. Any insight from Sophos on if the blue screen of death crashes are being caused by the latest version of Sophos?

This thread was automatically locked due to age.

Top Replies

BBallLAL over 2 years ago in reply to Matthew Marsh +5

Yes, it's mindblowing that it would take a multi billion $ company this long to fix it. At least have an option for those affected by bad sofwtare updates to rollback to the previous version instead of…

Parents

0 KevinK over 2 years ago

We are starting to see more user reports about this in our environment. Mostly Lenovo machines, and we're also using Cisco AnyConnect.
Cancel
Vote Up +3 Vote Down

Cancel
0 BBallLAL over 2 years ago in reply to KevinK

Over two weeks since I reported it and still no resolution.
Cancel
Vote Up +3 Vote Down

Cancel
0 Qoosh over 2 years ago in reply to BBallLAL
I apologize for the frustrations. Looking into the development ticket open for this issue, there’s work being done each day. Our team is actively working towards finding a resolution.

If you need an immediate work-around to be implemented, you can use the following steps published in the KBA, though I understand that this is not ideal for all organizations.

Turn off the following within Sophos Central:

Web Control - Disable the policy that applies to the user for that system

Threat Protection - Turn off all settings under "Real-time scanning - Internet"
Kushal Lakhan

Team Lead, Global Community Support
Connect with Sophos Support, get alerted, and be informed.
If a post solves your question, please use the "Verify Answer" button.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up -2 Vote Down

Cancel
0 Matthew Marsh over 2 years ago in reply to BBallLAL

Now at 3 weeks since first reported, still no updates except work arounds. Makes me wonder what their QA process is for new releases...
Cancel
Vote Up +4 Vote Down

Cancel
0 BBallLAL over 2 years ago in reply to Matthew Marsh

Yes, it's mindblowing that it would take a multi billion $ company this long to fix it. At least have an option for those affected by bad sofwtare updates to rollback to the previous version instead of making us disable protection making us more vulnerable.
Cancel
Vote Up +5 Vote Down

Cancel

Reply

0 BBallLAL over 2 years ago in reply to Matthew Marsh

Yes, it's mindblowing that it would take a multi billion $ company this long to fix it. At least have an option for those affected by bad sofwtare updates to rollback to the previous version instead of making us disable protection making us more vulnerable.
Cancel
Vote Up +5 Vote Down

Cancel

Children

0 Matthew Alley1 over 2 years ago in reply to BBallLAL

Yeah we are still having this issue. Just happened to our CEO in the middle of a meeting. My IT manager is suggesting that if they don't get this fixed soon that we will be researching a new AV solution for next year.

It seems like the workaround has helped, but it's hard to verify at this point since it seems like not all of our users are actually reporting their BSODs.
Cancel
Vote Up +3 Vote Down

Cancel