BAD_POOLCALLER Bsod

System: Custom Build
CPU: AMD FX4100 Quadcore @ 3.6GHZ
Motherboard: Gigabyte 990FXA-UD3 Bios Rev F5 Beta (FX/Steam CEG Crashfix)
Ram:8GB Type(s) DDR3-1333 1x 4GB , DDR3-1333 2x 2GB 1 Slot avilable
HDD's: 1x 500GB WD "BLUE" Drive Sata II 1x Maxtor 200GB SATA 3.0GBps
Videocard: AMD Radeon HD5750 1GB VideoRam Stock Closk 500mhz/1135 , OC'd to 835mhz/1335MHZ (only in effect when in "High Performance mode")
Monitor Count: 2
Monitor types/Resolution: #1 LCD 15' @ 1024x768 75hz , #2 CRT 17' @ 720p Resolution 75hz
Case: XION II
PSU: OCZ700MXSP (700W) "80Plus"
PCI Cards: 1x ATI TV Tuner (TV Wonder Pro PCI via Hacked x64 Driver)
OS: Windows 7 x64 Ultamate
OS State/Boot Params: "Disable Driver Signing Enforcement"
USB Devices: 1x Wifi-N Adapter, 1x Generic USB Mouse, 1x USB generic Logitech Keyboard , 1x Xbox 360 Wireless gaming Reciver , 1x Madcatz Recharge pack Charger Cable 1x USB 24X DVD Burner ,1x UPS System ,1x USB SATA HDD (not attached at that time), 1x "Internal USB PIN" All in one Card reader with 1 USB 2.0 Port (Kindle power/Data Cable attached Kindle not attached)
Soundcard: Onboard Audio (1 cheapie 10$ speaker set connected)

Problem Occured: BSOD Upon "Installing Drivers" after connecting Cellphone to charge (LG "LG235G" Provided by Safe-link phone service thru Tracphone) via Kindle Data/power Cable

Applications running:
Firefox (about 7 to 9 tabs open)
Livestream (was streaming at that time)
Minecraft ("Tekkit 3.0.4")
Teamspeak 3
Skype
MSN Messenger with MSNPlus!
Yahoo Messenger
VLC
Notepad++

Attached required information + Windows Index/System Info + screenshots of CPUID & AMD Vision Center showing GPU Overclock settings

(yes i know i was kinda too anal w/ details)

the biggest fault i can think of. was that i never redid windows when i built the new system,

was a upgrade from am ECS Geforce6100SM-M2 2.0 Mobo /4GB DDR2-667 Ram/AMD Athlon 64 X2 @ 2.6ghz (same videocard/HDD) internal 12X DVD Burner

This may have been a one off, or may be something you have to look forward to every time you USB that phone.

Code:

BugCheck C2, {7, 109b, 5070b00, fffffa800bb3bcb3}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : usbser.sys ( usbser!SelectInterface+397 )
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000005070b00, Memory contents of the pool block
Arg4: fffffa800bb3bcb3, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
LOCK_ADDRESS:  fffff800040cbb80 -- (!locks fffff800040cbb80)
Resource @ nt!PiEngineLock (0xfffff800040cbb80)    Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE: 
    Lock address  : 0xfffff800040cbb80
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0
LAST_CONTROL_TRANSFER:  from fffff80003ffabe9 to fffff80003ed01c0
STACK_TEXT:  
fffff880`033bd3a8 fffff800`03ffabe9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`05070b00 : nt!KeBugCheckEx
fffff880`033bd3b0 fffff880`091df69f : 00000000`00000000 00000000`43425355 00000000`43425355 fffffa80`00000000 : nt!ExDeferredFreePool+0x1201
fffff880`033bd460 fffff880`091e4c5e : ffffffff`ee1e5d01 fffffa80`0bb3bc70 fffffa80`00000002 00000000`00000000 : usbser!SelectInterface+0x397
fffff880`033bd540 fffff880`091e468a : fffffa80`0bbfc1b8 fffffa80`0bbfc010 00000000`00000000 fffffa80`0bcd8a40 : usbser!ConfigureDevice+0xee
fffff880`033bd590 fffff880`091e741a : fffffa80`0bcd88f0 fffffa80`0bc0b280 fffffa80`0bcd8a40 fffffa80`0bbfc010 : usbser!StartDevice+0x162
fffff880`033bd600 fffff800`0428602e : 00000000`00000000 fffffa80`0bbfc010 fffffa80`0bc0b280 fffff880`031d7180 : usbser!UsbSer_PnP+0x25e
fffff880`033bd650 fffff800`03fbdead : fffffa80`0bb24060 fffffa80`0bc0b280 fffff800`03fc75d0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`033bd690 fffff800`04295376 : fffff800`040cb940 fffffa80`0bb15880 fffffa80`0bc0b280 fffffa80`0bb15a28 : nt!PnpStartDevice+0x11d
fffff880`033bd750 fffff800`04295614 : fffffa80`0bb15880 fffffa80`0bb10023 fffffa80`0bb15880 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`033bd7e0 fffff800`042b8d46 : fffffa80`0bb15880 fffffa80`0bb15880 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`033bd810 fffff800`042b9137 : fffffa80`0bb15880 00000000`00000000 00000000`00000001 fffff800`041355d4 : nt!PipProcessDevNodeTree+0x296
fffff880`033bda80 fffff800`03fc9f03 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiRestartDevice+0xc7
fffff880`033bdad0 fffff800`03ed9851 : fffff800`03fc9bf0 fffff800`041c2601 fffffa80`06aa2b00 00000000`00000000 : nt!PnpDeviceActionWorker+0x313
fffff880`033bdb70 fffff800`04166e6a : 00000000`00000000 fffffa80`06aa2b50 00000000`00000080 fffffa80`06a3c9e0 : nt!ExpWorkerThread+0x111
fffff880`033bdc00 fffff800`03ec0f06 : fffff880`031d7180 fffffa80`06aa2b50 fffff880`031e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033bdc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  kb
FOLLOWUP_IP: 
usbser!SelectInterface+397
fffff880`091df69f eb29            jmp     usbser!SelectInterface+0x3c2 (fffff880`091df6ca)
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  usbser!SelectInterface+397
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: usbser
IMAGE_NAME:  usbser.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a66d
FAILURE_BUCKET_ID:  X64_0xc2_7_usbser!SelectInterface+397
BUCKET_ID:  X64_0xc2_7_usbser!SelectInterface+397

Looks like Plug and Play was sailing along and the phone decided that it wanted to be a USB Modem (serial device / com port) and perhaps the driver may have not been up to the task. Maybe if all you are doing is charging the device (phone) perhaps you could do without the third party driver.
usbser.sys is a native Microsoft driver and you seem to have what looks like the latest available

Code:

start             end                 module name
fffff880`091dd000 fffff880`091eb000   usbser     (pdb symbols)          d:\symbols\USBSER.pdb\B8797BFA3015413096F8CBC58689D8971\USBSER.pdb
    Loaded symbol image file: usbser.sys
    Mapped memory image file: d:\symbols\usbser.sys\4CE7A66De000\usbser.sys
    Image path: \SystemRoot\system32\DRIVERS\usbser.sys
    Image name: usbser.sys
    Timestamp:        Sat Nov 20 04:43:57 2010 (4CE7A66D)
    CheckSum:         0001298F
    ImageSize:        0000E000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     usbser.sys
    OriginalFilename: usbser.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  USB Modem Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

And as such is not likely the actual offender.
A single dump file does not a pattern make so if Blue Screens persist then attach new dump files (.dmp) here.
As an aside there is one older driver that you might want to see if you can update;
ManyCam_x64.sys 3/13/2008 Download ManyCam free webcam effects software hopefully there is something a bit more current you can apply.
Good Luck
Randy

well. theres been an annoyance to part of why i feel i needed to reinstall windows 7, everytime about 4HRs aftre a restart, any USB Device disconnect, everything making noise would mute to 1 notch on the mixer. so maybe USB Drivers nee dto be reinstalled