BSOD when using utorrent windows 7 64 bit

Whenever seeding or downloading from utorrrent or other programs like it my com crashes
Windows 7 64 bit
FULL RETAIL
Bought in 2009

I couldn't figure out how to save the Resource and performance monitor sry

I note you have a USB wireless device. USB wireless is inherently unreliable because the USB ports do not supply adequate power to the device to support stable functionality. We recommend replacing such devices with a PCI wireless card instead...

I wrote the above about the USB wireless device without looking at your .dmp files first. An analysis of the .dmp files shows that the USB wireless device is indeed the culprit of the crashes.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\nicsvogt\Windows_NT6_BSOD_jcgriff2\021912-27534-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e9e670
Debug session time: Sun Feb 19 20:47:58.403 2012 (GMT-7)
System Uptime: 1 days 23:33:03.823
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88004371231, 0, ffffffffffffffff}

Unable to load image \SystemRoot\system32\DRIVERS\WPN111vx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WPN111vx.sys
*** ERROR: Module load completed but symbols could not be loaded for WPN111vx.sys
Probably caused by : WPN111vx.sys ( WPN111vx+a2231 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004371231, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
WPN111vx+a2231
fffff880`04371231 8b402c          mov     eax,dword ptr [rax+2Ch]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f08100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d21588 to fffff80002cd5c40

STACK_TEXT:  
fffff800`00b9bc18 fffff800`02d21588 : 00000000`0000001e ffffffff`c0000005 fffff880`04371231 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9bc20 fffff800`02cd52c2 : fffff800`00b9c3f8 fffffa80`06dca020 fffff800`00b9c4a0 fffffa80`06deb760 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff800`00b9c2c0 fffff800`02cd3bca : fffffa80`00000000 fffffa80`0400e770 fffffa80`0400e770 fffff880`018ac7b0 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c4a0 fffff880`04371231 : fffff880`01739110 fffffa80`075bec40 00000000`00000286 fffff880`042e06b0 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c630 fffff880`01739110 : fffffa80`075bec40 00000000`00000286 fffff880`042e06b0 00000000`00000000 : WPN111vx+0xa2231
fffff800`00b9c638 fffffa80`075bec40 : 00000000`00000286 fffff880`042e06b0 00000000`00000000 fffffa80`075bec40 : ndis!WPP_GLOBAL_Control
fffff800`00b9c640 00000000`00000286 : fffff880`042e06b0 00000000`00000000 fffffa80`075bec40 00000000`00000000 : 0xfffffa80`075bec40
fffff800`00b9c648 fffff880`042e06b0 : 00000000`00000000 fffffa80`075bec40 00000000`00000000 fffff880`0430bca1 : 0x286
fffff800`00b9c650 00000000`00000000 : fffffa80`075bec40 00000000`00000000 fffff880`0430bca1 00000001`063a7810 : WPN111vx+0x116b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WPN111vx+a2231
fffff880`04371231 8b402c          mov     eax,dword ptr [rax+2Ch]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  WPN111vx+a2231

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WPN111vx

IMAGE_NAME:  WPN111vx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  488f1151

FAILURE_BUCKET_ID:  X64_0x1E_WPN111vx+a2231

BUCKET_ID:  X64_0x1E_WPN111vx+a2231

Followup: MachineOwner
---------

WPN111v.sys caused the above crash. This is your Netgear or Atheros Wireless USB Network Adapter, and the driver for it is pre-Windows 7. Having a USB wireless device that uses Vista based drivers is a frequent cause of blue screen crashes analyzed on these forums.

I recently started monitoring the processes and noticed that the wireless usb was taking up a lot of memory. Thank you for the advice; I'll surely use it.