Netio.sys

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

ArmsRace

Thread Starter
Joined
Oct 25, 2004
Messages
17
I've been having this issue as of lately and I've searched these forums for a solution and cannot seem to find one. I know its a networking driver issue. I've updated my adapter to the latest drivers and I still get the BSOD. Any suggestions?
 
Joined
Aug 1, 2003
Messages
51,988
What "issue"? Is there a problem? If so, are there error messages? If so, when do they appear, and exactly what do they say?
 
Joined
Aug 4, 2003
Messages
5,620
Please go to C:\Windows and copy the minidump folder there to the desktop. Compress it and upload it here.

How To: Click Go Advanced and scroll down to Manage Attachments
 

ArmsRace

Thread Starter
Joined
Oct 25, 2004
Messages
17
Thank you for your help. I've attached my minidump folder but it looks like it only shows up to yesterday.
 

Attachments

Joined
Aug 4, 2003
Messages
5,620
The file responsible is NETIO.SYS And it is the Network I/O Subsystem. When you updated the drivers, did you get them from the manufacturers site? Please post the Make and the Model of your system.


PHP:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\LG-PC7\Desktop\Minidump\Minidump\020513-8767-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03252000 PsLoadedModuleList = 0xfffff800`03496670
Debug session time: Tue Feb  5 06:53:29.131 2013 (UTC - 8:00)
System Uptime: 0 days 20:59:46.959
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff88001f496fd}

Probably caused by : NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )

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

6: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001f496fd, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003500100
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
NETIO!RtlCopyBufferToMdl+1d
fffff880`01f496fd 448b5228        mov     r10d,dword ptr [rdx+28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003d706f0 -- (.trap 0xfffff88003d706f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003d70910 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001f496fd rsp=fffff88003d70880 rbp=fffff88003d709b0
 r8=00000000ffffffbc  r9=0000000000000044 r10=0000000000000000
r11=fffffa8017a130f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETIO!RtlCopyBufferToMdl+0x1d:
fffff880`01f496fd 448b5228        mov     r10d,dword ptr [rdx+28h] ds:0860:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d0569 to fffff800032d0fc0

STACK_TEXT:  
fffff880`03d705a8 fffff800`032d0569 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03d705b0 fffff800`032cf1e0 : 00000000`00004045 fffff880`03d70cc7 00000000`00000000 00000000`00000044 : nt!KiBugCheckDispatch+0x69
fffff880`03d706f0 fffff880`01f496fd : 00000000`00000000 00000000`00042f90 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03d70880 fffff880`020c40fc : fffffa80`1206be68 fffff880`020927b6 00000000`00000000 fffffa80`11f6d1a0 : NETIO!RtlCopyBufferToMdl+0x1d
fffff880`03d708e0 fffff880`020902e8 : fffffa80`17a130f0 00000000`00000000 fffffa80`1a40c010 00000000`0b53b1c2 : tcpip! ?? ::FNODOBFM::`string'+0x1d0ff
fffff880`03d70950 fffff880`02081b34 : 00000000`00000006 00000000`00000017 00000000`00004045 00000000`00000cc7 : tcpip!TcpTcbCarefulDatagram+0x1a98
fffff880`03d70b00 fffff880`02080aea : fffffa80`10cc9f00 00000000`6dd956ed fffffa80`076121f0 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff880`03d70cb0 fffff880`0208208b : fffffa80`1265dedc fffffa80`10e06140 00000000`00000000 fffff880`03d71000 : tcpip!TcpMatchReceive+0x1fa
fffff880`03d70e00 fffff880`0207a067 : fffffa80`10cc9f00 fffffa80`10cc0cc7 fffffa80`00004045 00000000`00004045 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`03d70ed0 fffff880`02079bda : 00000000`00000000 fffff880`02188800 fffff880`03d71090 00001f80`008700a4 : tcpip!IppDeliverListToProtocol+0x97
fffff880`03d70f90 fffff880`020791d9 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`03d71080 : tcpip!IppProcessDeliverList+0x5a
fffff880`03d71030 fffff880`02076f3f : 00000000`00000000 00000000`1209c000 fffff880`02188800 fffff880`02188800 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`03d71110 fffff880`02076532 : fffffa80`120a15b0 00000000`00000000 fffffa80`1209c000 00000000`00000002 : tcpip!IpFlcReceivePackets+0x64f
fffff880`03d71310 fffff880`020e9eaa : 00000000`00000000 00000000`00000000 fffffa80`1209c010 fffffa80`1ae73cd0 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`03d713f0 fffff800`032dcc48 : fffffa80`119ec090 fffffa80`1ae73cd0 fffffa80`06789b50 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x4ff22
fffff880`03d71440 fffff880`02076092 : fffff880`020758f0 fffffa80`1220b6e0 fffff880`01895a00 00000000`00000001 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`03d71520 fffff880`01f050eb : fffffa80`120a08d0 00000000`00000000 fffffa80`11bbf1a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`03d71590 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!RtlCopyBufferToMdl+1d
fffff880`01f496fd 448b5228        mov     r10d,dword ptr [rdx+28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETIO!RtlCopyBufferToMdl+1d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  5034f6a0

FAILURE_BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

Followup: MachineOwner
 

ArmsRace

Thread Starter
Joined
Oct 25, 2004
Messages
17
Hey Thanks for your time on this. I don't think I did do the nvm update originally but I've since downloaded it unzipped it and double clicked the executable but only a black dos box pops up for a mil of a second and that's it. I'm not sure if its updating anything or not. Regardless now the Neto.sys problem is worse than ever. I now get the BSOD every 10 or so minutes and have to reboot. I'm thinking last resort to back everything up and do a fresh Win 7 install. What do you think? Are there any other options?
 
Joined
Aug 4, 2003
Messages
5,620
Hey Thanks for your time on this. I don't think I did do the nvm update originally but I've since downloaded it unzipped it and double clicked the executable but only a black dos box pops up for a mil of a second and that's it. I'm not sure if its updating anything or not. Regardless now the Neto.sys problem is worse than ever. I now get the BSOD every 10 or so minutes and have to reboot. I'm thinking last resort to back everything up and do a fresh Win 7 install. What do you think? Are there any other options?
Did you read the read me file?

82579VSKU.exe Version 1.2.2

Tool to update the NVRAM for the Intel® 82579V Gigabit Ethernet PHY
Copyright (C) 2012 Intel Corporation

Three tools are included, to support three different operation systems (Windows 32 bit; Windows 64 bit; DOS).

Steps to run the update tool:

1. Download the utility from the Intel download center
2. Select the correct tool file name based on the operating system installed
3. Open a command prompt window with administrator privileges
4. Run the executable file from the common prompt
5. The NVM image will be updated. Reboot the computer for best results.

Usage: [Tool_file_name] [options]
-log [filename] - generate log info
-report [filename] - generate report file
-nosilent - display the user interface

Example command line using the Windows* 64 bit operating system:
82579VSKUW64e -nosilent

Example command line using the Windows* 32 bit operating system:
82579VSKUW32 -nosilent

Whether you are 32 or 64 bit, run the command according to what you have.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Members online

Top