Torrents and IRQ Problems

[DeathscytheHELL]

Old computer: p4 2.0, 640 pc800 Rambus, Netgear Fast Ethernet switched from 3 Com Fast Ethernet, Windows XP Sp2 firewall off, behind NAT

Bit Torrents:
Azureus crashes system on install and run
So I used to use Edonkey BT
Recently using Shareaza

When I used to use edonkey on the old computer it would run fine for months.
Then suddenly crash as soon as it got up to speed on downloads and uploads, I didn't even think of error checking so I would reformat.

I bought a new computer, and Edonkey died so now I use Shareaza.
Three or four weeks and several downloads down, and now I have the same issues on the old computer.

This time I was smart enough to do research
BSOD: IRQ not less than or equal error report
Event Viewer: category 102, event 1003

I learned from searching:
It could be Windows Xp security limited TCPs, which I tried the patch to unlimit, even though I don't have problems for a long time, or on my new computer.
It could be shared IRQs causing the problems, so fixed by making my ethernet card on it's on IRQ, again why after Time?
It could be my router causing the crash because of the same TCP issues... this one confused me... since I had Installed Shareaza on my new computer first and downloaded the same files , no crashes.
It could be my Ethernet card's drivers, so I tried a new one, but it's still an older driver(2003), besides, it worked for a while then crapped out, what's the deal with that?
If this is the problem does anyone know of a "newer" ethernet card?
It could be my memory, so I am testing it now with memtest86....No errors in 2 passes


----Found another solution on a Random Google.
Seems the answer wasn't "Update Network card Driver", I found a site with an OLDER non-certified driver that seems to be the answer, go figure.

 

[mrpsiko]

I get that same BSOD "irql_not_less_than" error on my PixelView 6600GT, but on Windows 64 login, random net surfing, gameplay, sometimes video playback. To be honest, I have no idea, although I've encountered a decent number of 6 series owners reporting the same or similar problems. Are you running WinXP 64, by chance? Support for that seems crappy right now... IDK.

That's about all the help I can give.

 

[dclive]

Originally posted by: DeathscytheHELL
Old computer: p4 2.0, 640 pc800 Rambus, Netgear Fast Ethernet switched from 3 Com Fast Ethernet, Windows XP Sp2 firewall off, behind NAT

Both of you:
A machine will BSOD when it has a hardware problem (overheating, etc.) or a software *driver* problem (which that IRQL would be - it isn't related to hardware IRQs, which are now no longer an issue with a remotely modern OS). To fix this problem, someone just needs to look at the memory dump and see what the issue is.

mrpsiko:Send me e-mails with this thread's URL, the contents of your c:\windows\minidumps directory, and the .cab file output from the MPSReports program. See my .sig for full details.

 

[DeathscytheHELL]

This problem has reated it's ugly head, once again
This time it doesn't show up at all in the event viewer as a warning or error anymore, and hasn't showed it's ugly head in the hour that I have messed around looking things up, downloading and running the debugger, and making this post. over an hour. I am beginning to think it only attacks my computer on nights that I need sleep, and prevents me from going to bed.

Can you check the minidump without the MPSReport cab file?

I ran the latest dump file through the Debugger on my own, and it came up with this error:
Unable to verify timestamp for ntoskrnl.exe
repeatedly.

and at the end:
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : FA312nd5.sys ( FA312nd5+c64 )

unfortunately, I am not sure I ran the program right either, as there was a repetition of
"Your debugger is not using the correct symbols" in boxes.

If this is what I think it is, it's my netgear ethernet card driver, but it's a driver that I am not using. (or not supposed to be using since I downloaded the FA311v2 one and installed that)

One other thing I have been getting as a "warning" in event viewer is that I haven't been able to verify my time with window.time.com.
Could this be a related issue?
Is there a way to use the debugger to check out these errors that don't lead to a minidump?

 

[dclive]

You're correct, it's the netgear driver causing this, per the debugger. Uninstall the card & driver, get the latest one on there, and try again.

Did you follow my guide, and you still got those symbol errors?

You can check a minidump w/o mpsreports; I like to have it for the reasons outlined on the web page.

 

[DeathscytheHELL]

Amazing how clean it is when I read through your WHOLE download instructions!

Is there any information in the dump report about personal info?

 

[dclive]

Not really. One can find the computername and a little bit of machine information, but that's about it.

 

[dclive]

All wrapped up and fixed? Did you upgrade from your older driver?

(Isn't that easy, once you've got the debugger working?)