Been battling this BSOD for a while and cannot track it down.I used Whocrashed and each error mostly reads the same:
"crash dump file: C:\WINDOWS\Minidump\121315-10796-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8004BE5DC72)
Bugcheck code: 0xD1 (0x50, 0x2, 0x0, 0xFFFFF8004BE5DC72)
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. "
Anyone know how I would track down the problematic driver? I have dealt with this issue before but it seemed to go away on it's own for a few months then started happening again. The only change I can recall is updated Nvidia drivers - anyone have those causing such issues?
"crash dump file: C:\WINDOWS\Minidump\121315-10796-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8004BE5DC72)
Bugcheck code: 0xD1 (0x50, 0x2, 0x0, 0xFFFFF8004BE5DC72)
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. "
Anyone know how I would track down the problematic driver? I have dealt with this issue before but it seemed to go away on it's own for a few months then started happening again. The only change I can recall is updated Nvidia drivers - anyone have those causing such issues?