Solved BSOD caused by torrentprogram. driver_irql_not_less_or_equal

[christianj]

Hi

Recently my torrentprograms have been causing BSOD. I suspect it is caused by a driver conflict connect to some other software since I never had trouble with torrentprograms before.

My computer is an HP Pavilion dv7
64bit windows 7 home edition. OEM
The computer is less than 6 months old.

BSOD reads driver_irql_not_less_or_equal and something with netio.sys

I have attached a zip file with the health report and the dump files.
Hope someone can help me.

 

[christianj]

Bsod

How long should I expect for a reply to this sort of thread?

Or is the information in the above post lacking in any way?

Kind regards

Christian

 

[christianj]

OK I have tried bittorrent and utorrent. Both programs cause a conflict that results in the BSOD. I tried a different torrent program called deluge that didn't cause it.
Then I tried an older install of utorrent (version 1.8.5), which didn't cause BSOD for a couple of days, and then the BSOD's started again. Always when the torrent program is turned on.

It is probably a driver issue on the network card, but how do I figure out if and why and how to solve it?

Kind regards

Christian

 

[Corazon]

Limit the global maximum number of connections in whichever torrent client you use - start with a value of 200. If it works for a good while without a BSOD, you can try higher values if you want.

Some network adapter drivers don't handle the large number of TCP connections very well, and a few will crash as a result.

 

[christianj]

Ok

I think this problem has been solved. I will mark this case as solved after I post this.

Turning down the maximum number of connections didn't help. However I tried to uninstall a cisco anyconnect secure mobility client I use at work.

I have been running the torrentprogram for a few hours now and it seems stable. No crashes.

So I'll just uninstall the client whenever I need to use a torrentprogram. Isn't really a big deal.

 

[Corazon]

Not an ideal solution, but glad to hear you tracked down the problem. Maybe you can disable that client without uninstalling it.