Yes, use uTorrent, Microsoft Security Essentials and Sphinx Firewall Control if you want to see what programs are making outbound TCP or UDP connections. Third party malware and firewall software is sorely lacking in terms of compatibility testing. They will improve but for now use these programs.
sorry for the delay baarod,really...ive given up off downloading torrents for a while.. to the point: the problem doesnt result from firewall-softwares,ive been using only "microsoft essentials" since upgraded to win7...but i did listen to your advise anyway and install that "win7 f.wall controll", nothing changed though... and its not necessarily utorrent,bcs same thing happens with vuze(azureus?) too.. finally -coming from another suffering soul- i found out this "bluescreen wiever" application, and here is results:
==================================================
Dump File : 052010-16286-01.dmp
Crash Time : 20.05.2010 01:28:38
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x90ca796d
Parameter 3 : 0x8d39bbc4
Parameter 4 : 0x8d39b7a0
Caused By Driver : afd.sys
Caused By Address : afd.sys+2396d
File Description : Ancillary Function Driver for WinSock
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\052010-16286-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 052010-17362-01.dmp
Crash Time : 20.05.2010 00:15:00
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x830808ca
Parameter 3 : 0x8078a0e0
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+23e8ca
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\052010-17362-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
briefly these two windows drivers ("ntkrnlpa.exe" and "afd.sys") r causing the crash... and this is the exact dump text in BSDO:
"A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: afd.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0x90ca796d, 0x8d39bbc4, 0x8d39b7a0)
*** afd.sys - Address 0x90ca796d base at 0x90c84000 DateStamp 0x4a5bbf62"
still needing help and thanx to everybody who's trying to give some...
Last edited by ChaOHa; 19 May 2010 at 18:21. Reason: spell cheking and being polite..
Ack, I was looking in the wrong place. It's not a filter like would be caused by firewall or a/v but the network driver itself. It's responding incorrectly to asynchronous winsock calls -- passing bad status back to the kernel. That's going to give you headaches like I had with my Ralink driver initially under 64-bit.
It only crashed under high connection load and that's what ISPs hate any torrent traffic for. You see, torrents and earlier gnutella nets hold LOTS of connections open and that clogs ISP routers. These wonderful folks who we pay for service set limits on connections per IP address. It's called "acceptable use". Once you've exhausted them they abandon them in violation of RFC rules. Newer cards have connection management offloaded to the card ASIC which it controlled by the network driver/firmware. If it's not written to be fault tolerant and the card ASIC is effectively overloaded it passes a hard kernel mode failure to the OS and you see what you are seeing.
Please post your FCC ID or motherboard make and model. A driver will fix this IMHO especially under 64-bit 7.
hi and sorry again (my delays r bcs of the school-finals)... i dont know my FCC ID (i dont live in USA actually), but my motherboard is: Foxconn G31MX-K (2 PCI, 1 PCI-E x1, 1 PCI-E x16, 2 DDR2 DIMM, Audio, Video, Gigabit LAN). bytheway, lately i updated almost all my drivers including the motherboards' & the network-cards' (using drivermax,drivermagician etc.) im using 32bit for now (thinkin' to upgrade to 64bit doh) but my system supports 64bit. and im wondering if its possible to solve the problm without making a hardware-change, or whole system-reformat or upgrade(to 64bit)?... i think i get your main idea. but i thought u torrent defines/finds out how many ports can be used depend on the connection type/speed, isnt it? anyway, i did try to decrease the port number but it took only a bit more time 4 facing with the same BSDO... thanx 4 your concern baarod.. and appreciating more help please..
Realtek RTL8168B/8111B PCI-E Gigabit Ethernet Adapter... it's a "PCI Express 1.0 x1" type chip-set (and ain't onboard, i think)...
Please upload your dmps for analysis.
https://www.sevenforums.com/tutorials...en-forums.html
yeah! it's just at the right of the usb-ports...
and to the jonathan King: don't the "bluescreen-viewer" results i send b4 contain enough info about the dump files? if so, i'd send more by "hijackthis", "processexplorer", "eventviewer" etc... check my older threads pls,bro... thanx anyway... maybe i dont know the difference...
Nope, BlueScreenView is inaccurate, and we need to actual dmp files to run through our own debuggers (windbg).
Quote