Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD listing netio.sys as reason Help please


  • Please log in to reply
5 replies to this topic

#1 nipstyler

nipstyler

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:43 AM

Posted 18 September 2014 - 02:09 PM

Hi All

 

I have had a new HP probook 640 G1 for about 2 weeks.  After installing Utorrent I have been experiencing BSOD which has been listing Netio.sys as the reason.

 

Following a lot of research I understand that this is triggered by something else.

 

I did not have any issues until the first day I installed the P2P software and have had about 6 BSOD events with two yesterday while downloading torrents.

 

I have included the dumps for the last 3 events and the speccy and minitoolbox output files with the hope that one of you may be able to shed some light on this issue.

 

I have already updated all the drivers I can including the network adaptor and BIOS.

 

One issue I had when I first got the laptop is I noticed that I had a driver error on the MTTA in network devices (stated it was unable to start) which I had to sort out by disabling IPV6 and renewing the driver.

 

Any help you could give me on this issue would be fantastic as I'm at a loss now

 

 

Attached Files



BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,442 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:43 AM

Posted 18 September 2014 - 02:31 PM

Please look through each of the following:

 

http://www.bleepingcomputer.com/forums/t/512348/bsod-while-torrenting-due-to-netiosys/?p=3195205

 

Worth A Read, IMO

 

Worth A Read, #2

 

http://www.computerhope.com/forum/index.php?topic=145907.0

 

Louis



#3 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:11:43 AM

Posted 18 September 2014 - 04:11 PM

This bugcheck is consistent in that all three crashes are the result of the same invalid memory address being referenced from the same address so to me this is a network driver using a bad instruction pointer.

fffff880`03f07648 fffff800`030c8169 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03f07650 fffff800`030c6de0 : fffffa80`06ed9010 00000000`00000006 fffffa80`06ed9010 00000000`00000044 : nt!KiBugCheckDispatch+0x69
fffff880`03f07790 fffff880`023486fd : fffffa80`15ebc280 fffff880`07c93630 fffffa80`0730f350 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03f07920 fffff880`024a751b : fffffa80`15ebc280 fffff880`02475822 00000000`00000000 fffff880`02449845 : NETIO!RtlCopyBufferToMdl+0x1d
fffff880`03f07980 fffff880`02473116 : fffffa80`125c7620 00000000`00000000 fffffa80`075efcf0 00000000`ff8fd36d : tcpip! ?? ::FNODOBFM::`string'+0x1bb3f
fffff880`03f079f0 fffff880`02463f38 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0230417b : tcpip!TcpTcbCarefulDatagram+0x1a46
fffff880`03f07ba0 fffff880`0246199a : fffffa80`075efcf0 fffff880`0245a800 fffffa80`07a2d400 fffff880`02470692 : tcpip!TcpTcbReceive+0x37c
fffff880`03f07cb0 fffff880`024626cb : fffff880`05c1e0fa fffffa80`07ba9000 00000000`00000000 fffff880`03f08000 : tcpip!TcpMatchReceive+0x1fa
fffff880`03f07e00 fffff880`0245af37 : fffffa80`07a69a80 fffffa80`07a633d5 fffffa80`00005060 00000000`00005060 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`03f07ed0 fffff880`0245aaaa : 00000000`00000000 fffff880`02568800 fffff880`03f08090 fffffa80`0752cc00 : tcpip!IppDeliverListToProtocol+0x97
fffff880`03f07f90 fffff880`0245a0a9 : fffff880`03f08158 00000000`00000000 00000000`000001b2 fffff880`03f08080 : tcpip!IppProcessDeliverList+0x5a
fffff880`03f08030 fffff880`02457d4f : 00000000`00000000 00000000`125b9000 fffff880`02568800 fffff880`02568800 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`03f08110 fffff880`02457322 : fffffa80`125b1300 00000000`00000000 fffffa80`125b9000 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`03f08310 fffff880`024c9bfa : fffffa80`00000000 fffffa80`07f46e20 fffffa80`125b9010 fffff880`03f08400 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`03f083f0 fffff800`030d4878 : fffffa80`07f46e20 fffffa80`00000000 fffffa80`06d33040 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x49ca2
fffff880`03f08440 fffff880`02456e42 : fffff880`02456670 00000000`00000014 00000000`00000000 fffffa80`07ecba01 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`03f08520 fffff880`023040eb : fffffa80`125b9780 00000000`00000000 fffffa80`11adc1a0 fffffa80`07a5a858 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`03f08590 fffff880`022cdad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`03f08600 fffff880`02247ac1 : fffffa80`11adc1a0 fffff800`0326e2d8 00000000`00000001 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`03f08a80 fffff880`04d1666c : 00000000`00000001 fffff800`0326e2d8 fffffa80`06d33040 fffffa80`154b0110 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`03f08ad0 fffff880`04d10c17 : fffff880`04d26dd8 fffffa80`06d33040 fffffa80`06d33040 00000000`00000000 : tunnel!TeredoWfpIndicationWorker+0xb4
fffff880`03f08b10 fffff800`033bfc93 : fffffa80`125b87e0 00000000`00000001 fffffa80`154b0110 fffffa80`06d33040 : tunnel!LwWorker+0x1b
fffff880`03f08b40 fffff800`030d2261 : fffff800`0326e200 fffff800`033bfc01 fffffa80`06d33000 fffff800`0326e2d8 : nt!IopProcessWorkItem+0x23
fffff880`03f08b70 fffff800`0336473a : 00000000`00000000 fffffa80`06d33040 00000000`00000080 fffffa80`06ca5b30 : nt!ExpWorkerThread+0x111
fffff880`03f08c00 fffff800`030b98e6 : fffff880`03bd7180 fffffa80`06d33040 fffff880`03be1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03f08c40 00000000`00000000 : fffff880`03f09000 fffff880`03f03000 fffff880`03f088a0 00000000`00000000 : nt!KxStartSystemThread+0x16

Your network drivers are as followed, the top one is your Intel Gigabit driver and the bottom one is the Intel WiFi driver, both are outdated.

You should update them from the Intel download centre here:

 

https://downloadcenter.intel.com/default.aspx

e1d62x64	fffff880`0570e000	fffff880`0578a000	Fri Jul 12 23:22:32 2013 (51e081a8)	0007ad3b		e1d62x64.sys
NETwsw00    fffff880`06258000    fffff880`06daa000    Wed May 29 14:10:47 2013 (51a5fe57)    00b0cc71        NETwsw00.sys


#4 nipstyler

nipstyler
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:43 AM

Posted 19 September 2014 - 01:30 PM

Thank you both for your input 

 

I will update the drivers again this time from the intel site



#5 nipstyler

nipstyler
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:43 AM

Posted 19 September 2014 - 01:33 PM

Sorry for being a bit of a noob on this but could you point me in the direction of the right driver on the intel site

 

I'm not sure how to find out which adaptor driver I need for this laptop

 

Many thanks

 

Matt



#6 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:11:43 AM

Posted 19 September 2014 - 01:35 PM

Go to start

Type 'msinfo32' select Components then Network and then Adapter

Scroll down until you see your Intel network cards and type in their exact model into the website.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users