BSOD While using uTorrent, NETIO.sys error

[abernha3]

Hey all,

I've been lurking for a bit, trying to figure this out myself, but I haven't been able to. For a little under a week I have been getting a BSOD if I try to torrent something and do something else. If I leave it running on it's own, it can usually complete, unless I am downloading several torrents, then it will crash no matter what. It seems to point to Netio.sys and there is also a driver_irql_not_less_than_equal error. Please let me know what I should do. I am not currently running any anti-virus, since I removed AVG thinking that was the problem. I'm running Windows 7 Home premium 64 bit, service pack 1, on an HP Folio 13. I did attach my dump files for your pleasure, as well. Thanks all.

Andrew

 

[koolkat77]

Welcome

Most of the times NETIO.sys refers to NIC i.e. Atheros AR8152/8158 PCI-E Fast Ethernet Controller, I would recommend to reinstall the drivers.

 

[abernha3]

Thanks for the info. My computer does not seem to have any Atheros gear installed, so I'm not sure that would help. I am running on a Intel Centrino Wireless-N 1030 network adapter. Does that change anything? Thanks again

 

[koolkat77]

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[abernha3]

That certainly did run buggy. I let it go for a couple hours without incident, despite trying my best to make it crash. I was worried about leaving it running, as I am out of town for the next month with no computer backup. The instructions gave me a bit of fear, but also no luck yet. Anything else I could try?

 

[koolkat77]

We'll try to fix it before that.
It needs to run 36 hours. When you get the dumps, upload them.

Its 1.48 am in my area, so I'll be going to bed in a few and will take a look at your dumps when I'm up if you get any in that between.

 

[abernha3]

Still running verifier. Haven't had a BSOD despite my best efforts. It's annoying not being able to use my computer though. It's so slow with this program.

 

[abernha3]

So, I just stopped the verifier without having a BSOD in about 36 hours. Then within 30 minutes of rebooting without it running, got another one. I attached my new zip of the dump files.

 

[koolkat77]

Checked the dumps, same cause.

Have you tried re installing uTorrent?
Does it crash when you're using uTorrent or at other times too?