BSOD After Windows 10 Update netio.sys

[Dave1117]

Ever since I got the big windows 10 update 15063 my pc started blue screening at random times. In reliability monitor it's giving me multiple logs about my nvidia gpu "stopped working". The blue screen is an IRQL message and under it says something about netio.sys. In the reliability log I have this:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000088, 0x0000000000000002, 0x0000000000000000, 0xfffff80bb32d0906). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: be01a2eb-b2b0-4a3a-b8a2-d5c4d3919524.

I can't seem to find that memory.dmp to post here. My desktop runs superb aside from this. I also have webroot antivirus. I'm gonna take a wild guess that it's the gpu but I wanna make sure I exhaust all my options before I take this thing in for a repair.

Basic Specs:
amd fx-6300
8gb 1600mhz
120gb ssd
1tb hdd
nividia geforce gtx 950
Gigabyte mb
Custom built.

 

[johnbl]

some driver wrote over another drivers data, then the second driver used the data and caused a bugcheck.

generally, you want to update the BIOS, then all of the motherboard drivers and see if you get the bugcheck again.
if you do, you have to turn on verifier.exe to force the bugcheck to happen when the driver writes outside of its assigned memory area. when it does this it the driver will be named in the memory.dmp file.

to turn on verifier you start cmd.exe or powershell as an admin then run
verifier.exe /all /standard
and reboot and wait for the next bugcheck.
when you get a bugcheck the dump file will be in c:\windows\minidump directory if you are set up for a mini memory dump
or it will be stored in
c:\windows\memory.dmp file if your system is set to make a kernel or full memory dump.

without verifier turned on you get a memory dump that shows the victim driver as the cause of the problem.

make sure you know how to get into safe mode so you can turn off verifier.exe if the system bugchecks during boot up.
turn off verifier.exe via
verifier.exe /reset
or your machine will run slowly until you issue the command.

note: if verifier is turned on when the bugcheck happens, then automated tools are likely to correctly identify which driver caused the problem. otherwise the automated tools will just indicate ntoskrnl.exe (windows kernel) as the problem

automated tools to read crash dumps: whocrashed.exe and bluescreenview.exe

 

[Dave1117]

some driver wrote over another drivers data, then the second driver used the data and caused a bugcheck.

generally, you want to update the BIOS, then all of the motherboard drivers and see if you get the bugcheck again.
if you do, you have to turn on verifier.exe to force the bugcheck to happen when the driver writes outside of its assigned memory area. when it does this it the driver will be named in the memory.dmp file.

to turn on verifier you start cmd.exe or powershell as an admin then run
verifier.exe /all /standard
and reboot and wait for the next bugcheck.
when you get a bugcheck the dump file will be in c:\windows\minidump directory if you are set up for a mini memory dump
or it will be stored in
c:\windows\memory.dmp file if your system is set to make a kernel or full memory dump.

without verifier turned on you get a memory dump that shows the victim driver as the cause of the problem.

make sure you know how to get into safe mode so you can turn off verifier.exe if the system bugchecks during boot up.
turn off verifier.exe via
verifier.exe /reset
or your machine will run slowly until you issue the command.

note: if verifier is turned on when the bugcheck happens, then automated tools are likely to correctly identify which driver caused the problem. otherwise the automated tools will just indicate ntoskrnl.exe (windows kernel) as the problem

automated tools to read crash dumps: whocrashed.exe and bluescreenview.exe

after running whocrashed this is what I got Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 5/6/2017 2:18:47 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\050617-73875-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80BB32D0906)
Bugcheck code: 0xD1 (0x88, 0x2, 0x0, 0xFFFFF80BB32D0906)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[johnbl]

often the driver that overwrote the data will be the driver itself.
in this case since the bughceck was in a network component the suspect driver will be a network driver.
I would go to the motherboard vendors website and update the LAN and wireless driver, (and bluetooth driver if you have it)

if you have a usb wireless thumb drive, you often have to update the BIOS, cpu chipset and USB drivers for your motherboard as well as the USB wireless driver itself.

Old network drivers will cause nvidia GPU to stop responding. you can turn off shadowplay and might prevent the problem but then virus scanners can also get messed up. best to update the network driver.

some driver wrote over another drivers data, then the second driver used the data and caused a bugcheck.

generally, you want to update the BIOS, then all of the motherboard drivers and see if you get the bugcheck again.
if you do, you have to turn on verifier.exe to force the bugcheck to happen when the driver writes outside of its assigned memory area. when it does this it the driver will be named in the memory.dmp file.

to turn on verifier you start cmd.exe or powershell as an admin then run
verifier.exe /all /standard
and reboot and wait for the next bugcheck.
when you get a bugcheck the dump file will be in c:\windows\minidump directory if you are set up for a mini memory dump
or it will be stored in
c:\windows\memory.dmp file if your system is set to make a kernel or full memory dump.

without verifier turned on you get a memory dump that shows the victim driver as the cause of the problem.

make sure you know how to get into safe mode so you can turn off verifier.exe if the system bugchecks during boot up.
turn off verifier.exe via
verifier.exe /reset
or your machine will run slowly until you issue the command.

note: if verifier is turned on when the bugcheck happens, then automated tools are likely to correctly identify which driver caused the problem. otherwise the automated tools will just indicate ntoskrnl.exe (windows kernel) as the problem

automated tools to read crash dumps: whocrashed.exe and bluescreenview.exe

after running whocrashed this is what I got Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 5/6/2017 2:18:47 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\050617-73875-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80BB32D0906)
Bugcheck code: 0xD1 (0x88, 0x2, 0x0, 0xFFFFF80BB32D0906)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Dave1117]

Updating the bios gives me the creeps but i'll consider it. I'll start with updating the network drivers.

often the driver that overwrote the data will be the driver itself.
in this case since the bughceck was in a network component the suspect driver will be a network driver.
I would go to the motherboard vendors website and update the LAN and wireless driver, (and bluetooth driver if you have it)

if you have a usb wireless thumb drive, you often have to update the BIOS, cpu chipset and USB drivers for your motherboard as well as the USB wireless driver itself.

Old network drivers will cause nvidia GPU to stop responding. you can turn off shadowplay and might prevent the problem but then virus scanners can also get messed up. best to update the network driver.

some driver wrote over another drivers data, then the second driver used the data and caused a bugcheck.

generally, you want to update the BIOS, then all of the motherboard drivers and see if you get the bugcheck again.
if you do, you have to turn on verifier.exe to force the bugcheck to happen when the driver writes outside of its assigned memory area. when it does this it the driver will be named in the memory.dmp file.

to turn on verifier you start cmd.exe or powershell as an admin then run
verifier.exe /all /standard
and reboot and wait for the next bugcheck.
when you get a bugcheck the dump file will be in c:\windows\minidump directory if you are set up for a mini memory dump
or it will be stored in
c:\windows\memory.dmp file if your system is set to make a kernel or full memory dump.

without verifier turned on you get a memory dump that shows the victim driver as the cause of the problem.

make sure you know how to get into safe mode so you can turn off verifier.exe if the system bugchecks during boot up.
turn off verifier.exe via
verifier.exe /reset
or your machine will run slowly until you issue the command.

note: if verifier is turned on when the bugcheck happens, then automated tools are likely to correctly identify which driver caused the problem. otherwise the automated tools will just indicate ntoskrnl.exe (windows kernel) as the problem

automated tools to read crash dumps: whocrashed.exe and bluescreenview.exe

after running whocrashed this is what I got Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 5/6/2017 2:18:47 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\050617-73875-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80BB32D0906)
Bugcheck code: 0xD1 (0x88, 0x2, 0x0, 0xFFFFF80BB32D0906)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.