Netio.sys causing BSOD

[Hizawn]

About a week ago I started getting a few BSOD's, which were mainly due to outdated drivers which I promptly updated. 2/3 days passed without any more issues, but then every 6 hours or so I started getting different BSOD's all pointing to Netio.sys. I did some searching and most of peoples issues seem to come from outdated network drivers or Mcafee and I don't have either (Unless Mcafee's got even sneakier).

I included the latest Minidump.

Thank you for any help you can provide.

 

[Hizawn]

Bumping.

Apologies if it's against forum etiquette.

 

[Hizawn]

And again.

Sorry, but I really need help with this.

 

[Hizawn]

Bumping once more, then I'll go try somewhere else.

 

[disceptator]

Deinstall mcaffe and try another solution, maybe a free one.
Check if you still have the problems.

 

[Capt.Jack Sparrow]

Hello,

Please follow this and post us the logs http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

- Captain

 

[Hizawn]

Hello,

Please follow this and post us the logs http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

- Captain

Done.

It's Windows 7 x64;
The original OS was Vista
It's full retail.
The computer is 3 Years old and 7 has been installed for about 6 months.

Thank you.

 

[CarlTR6]

Your dump shows error code D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL. Usual cause is a device driver.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_082910-21403-01.zip\082910-21403-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82838000 PsLoadedModuleList = 0x82980810
Debug session time: Sun Aug 29 11:36:29.040 2010 (GMT-4)
System Uptime: 0 days 5:38:39.616
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {3, 2, 1, 8bf5f553}

Probably caused by : NETIO.SYS ( NETIO!InvalidateFlowContextTable+f )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000003, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8bf5f553, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829a0718
Unable to read MiSystemVaType memory at 82980160
 00000003 

CURRENT_IRQL:  2

FAULTING_IP: 
NETIO!InvalidateFlowContextTable+f
8bf5f553 094804          or      dword ptr [eax+4],ecx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8df9bbac -- (.trap 0xffffffff8df9bbac)
ErrCode = 00000002
eax=ffffffff ebx=8589db08 ecx=00000001 edx=00000200 esi=00000000 edi=8be9026f
eip=8bf5f553 esp=8df9bc20 ebp=8df9bc20 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
NETIO!InvalidateFlowContextTable+0xf:
8bf5f553 094804          or      dword ptr [eax+4],ecx ds:0023:00000003=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8bf5f553 to 8287e82b

STACK_TEXT:  
8df9bbac 8bf5f553 badb0d00 00000200 8df9bbf4 nt!KiTrap0E+0x2cf
8df9bc20 8bf4982b ffffffff 8589db04 8589dae8 NETIO!InvalidateFlowContextTable+0xf
8df9bc50 8bf49872 00007a76 00000000 8589db04 NETIO!WfpProcessFlowDelete+0x38
8df9bc64 8bf49893 00007a76 00000000 8589db04 NETIO!KfdNotifyFlowDeletion+0x19
8df9bc7c 8c099073 8589dae8 828048f0 85e272d8 NETIO!KfdAleNotifyFlowDeletion+0x18
8df9bc94 8c0981a4 8589dac8 828048f0 8c12f720 tcpip!WfpAleEndpointTeardownHandler+0x61
8df9bcc4 8bf49c1e 85e27414 8606bfe0 85fa07f0 tcpip!TcpCleanupTcbWorkQueueRoutine+0x128
8df9bce8 82a5881f 85fa07f0 8c12f720 8606bfe0 NETIO!NetiopIoWorkItemRoutine+0x2f
8df9bd00 828a5f3b 8606bfe0 00000000 85269d48 nt!IopProcessWorkItem+0x2d
8df9bd50 82a466d3 00000001 a41936f2 00000000 nt!ExpWorkerThread+0x10d
8df9bd90 828f80f9 828a5e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!InvalidateFlowContextTable+f
8bf5f553 094804          or      dword ptr [eax+4],ecx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  NETIO!InvalidateFlowContextTable+f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf63

FAILURE_BUCKET_ID:  0xD1_NETIO!InvalidateFlowContextTable+f

BUCKET_ID:  0xD1_NETIO!InvalidateFlowContextTable+f

Followup: MachineOwner
---------

The dump blames netio.sys; but that is likely not the real cause. Netio.sys is Windows system driver.

Begin by uninstalling [FONT=&quot]CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: [/FONT]DuplexSecure - Downloads

You have an obsolete driver on your system. Obsolete drives can and do cause conflicts and crashes. I could not find the program this driver is associated with; but it looks to be a game. Uninstall the software.

awwni5e4.SYS Sat Dec 01 08:07:04 2007

I also find one other out of date driver:

atikmdag.sys Fri Apr 24 06:50:20 2009 - ATI Video driver. See if you can update Catylist Control Center and this driver. If not, remove the Catalyst Control Center and only install the Display Driver Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

After taking care of these three drivers, reboot and see how your system runs. Post back and let us know.

 

[Capt.Jack Sparrow]

Hello,

Seems like the issue is with your Network card i.e. Rt86win7.sys, i would recommend to remove the Drivers completely and Download a fresh copy from website and install it. Don't use Windows Update to Download. Uninstall Everest Home Edition and Download Microsoft Security Essentials and install it. Realtek


Bugcheck

Unable to load image \SystemRoot\system32\DRIVERS\Rt86win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt86win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt86win7.sys
Probably caused by : Rt86win7.sys ( Rt86win7+c209 )

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000009a, 
Arg2: 000502d6
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'dump_dumpfve' and 'crashdmp.sys' overlap

BUGCHECK_STR:  0x4E_9a

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 828f570d to 828e8d10

STACK_TEXT:  
8df524c0 828f570d 0000004e 0000009a 000502d6 nt!KeBugCheckEx+0x1e
8df524d8 8288659a 00000000 c0000000 00000000 nt!MiBadRefCount+0x26
8df52528 8c3497a5 86d97c58 854ae6d8 85470c68 nt!MmUnlockPages+0x497
8df52550 8c31b177 854ae6d8 866ec5c8 00000038 afd!AfdSetupReceiveDatagramIrp+0x274
8df525a8 8c33aab8 85470c68 00000010 86e292e4 afd!AfdReceiveDatagramEventCommonHandler+0x282
8df525f8 8c0825ea 85470c68 00000038 866f0022 afd!AfdTLDgramReceiveEventHandler+0x89
8df52634 8c08cdd2 00000000 86d032f0 00000001 tcpip!UdpDeliverDatagrams+0x3d3
8df52680 8c08f20f 860a4410 000dc000 8df526bc tcpip!UdpReceiveDatagrams+0x142
8df52690 8c08e50e 8df526a4 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
8df526bc 8c08e2d1 8c0ee114 8df52710 c000023e tcpip!IppDeliverListToProtocol+0x49
8df526dc 8c08dfa6 8c0edd98 00000011 8df52710 tcpip!IppProcessDeliverList+0x2a
8df52734 8c08bbe4 8c0edd98 00000011 00000000 tcpip!IppReceiveHeaderBatch+0x1f2
8df527c8 8c08ab75 8642cc10 00000000 855fe201 tcpip!IpFlcReceivePackets+0xbe5
8df52844 8c08ace6 86885448 866ec4c0 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x746
8df52878 8289bfaa 866ec4c0 a40c266e 8608b720 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x11e
8df528e0 8c08ad6e 8c08abc8 8df52908 00000000 nt!KeExpandKernelStackAndCalloutEx+0x132
8df5291c 8bf1a18d 86885402 866ec400 00000000 tcpip!FlReceiveNetBufferListChain+0x7c
8df52954 8bf08670 8687eaa8 866ec4c0 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0x188
8df5297c 8bf085e7 00000000 866ec4c0 863b10e0 ndis!ndisIndicateSortedNetBufferLists+0x4a
8df52af8 8beb3ca5 863b10e0 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
8df52b14 8bf08a2e 863b10e0 866ec4c0 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2d
8df52b3c 8beb3c1e 863b10e0 866ec4c0 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
8df52b64 9195be8a 863b10e0 866ec4c0 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
WARNING: Stack unwind information not available. Following frames may be wrong.
8df52be4 91951cd1 0049e000 8649e000 00000000 Rt86win7+0xce8a
8df52c14 8bf08309 8649e000 00000000 8df52c40 Rt86win7+0x2cd1
8df52c50 8beb39f4 8684544c 00845438 00000000 ndis!ndisMiniportDpc+0xe2
8df52c78 828743b5 8684544c 86845438 00000000 ndis!ndisInterruptDpc+0xaf
8df52cd4 82874218 8df36120 8df3b800 00000000 nt!KiExecuteAllDpcs+0xf9
8df52d20 82874038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
8df52d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
afd!AfdSetupReceiveDatagramIrp+274
8c3497a5 ff7528          push    dword ptr [ebp+28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  afd!AfdSetupReceiveDatagramIrp+274

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf62

FAILURE_BUCKET_ID:  0x4E_9a_afd!AfdSetupReceiveDatagramIrp+274

BUCKET_ID:  0x4E_9a_afd!AfdSetupReceiveDatagramIrp+274

Followup: MachineOwner

Hope this helps,
Captain


Edit: Sorry Carl i didn't know you were looking at the Dump files

 

[CarlTR6]

No problem, Captain Jack. Two sets of eyes are always better than one set. I appreciate the help and backup.

 

[Hizawn]

Your dump shows error code D1, The dump blames netio.sys; but that is likely not the real cause. Netio.sys is Windows system driver.

Begin by uninstalling [FONT=&quot]CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: [/FONT]DuplexSecure - Downloads

You have an obsolete driver on your system. Obsolete drives can and do cause conflicts and crashes. I could not find the program this driver is associated with; but it looks to be a game. Uninstall the software.

awwni5e4.SYS Sat Dec 01 08:07:04 2007

I also find one other out of date driver:

atikmdag.sys Fri Apr 24 06:50:20 2009 - ATI Video driver. See if you can update Catylist Control Center and this driver. If not, remove the Catalyst Control Center and only install the Display Driver Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

After taking care of these three drivers, reboot and see how your system runs. Post back and let us know.

Uninstalled Alcohol 120% and removed a few old games which seemed to get rid of atikmdag. Just read on the ATI website that they don't officially support Windows 7 (At least not with previously released cards). It did say that the Vista drivers do seem to work and the latest release is fairly recent so I'll try that next.

Hello,

Seems like the issue is with your Network card i.e. Rt86win7.sys, i would recommend to remove the Drivers completely and Download a fresh copy from website and install it. Don't use Windows Update to Download. Uninstall Everest Home Edition and Download Microsoft Security Essentials and install it. Realtek


Hope this helps,
Captain


Edit: Sorry Carl i didn't know you were looking at the Dump files

Done, Done, Done, Done and Done.

As soon as the ATI drivers are finished downloading, I'll try pushing the PC a little and report back.

Thank you both.

EDIT: Installed the ATI drivers, rebooted and ran a few fairly intensive programs and so far it's all gone smoothly. Thanks!

 

[CarlTR6]

That is really good news. Thank you for updating us and reporting what you have done. I suspect that Alcohol was a major cause of your crashes. Hmm, that doesn't sound right. I suspect that the program, Alcohol, was a major cause of your crashes. Run your system for two or three days and post back. If you are still BSOD free, we will ask the moderators to mark this thread as solved. Fingers crossed!