Windows 7: BSOD BAD_POOL_CALLER Windows 7 x64 Home Premium!

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


Loading Dump File [C:\Users\Yusra\Downloads\zlor\SF_15-09-2012\091512-26629-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02a56000 PsLoadedModuleList = 0xfffff800`02c9a670
Debug session time: Sat Sep 15 18:21:16.109 2012 (UTC + 6:00)
System Uptime: 0 days 0:00:21.075
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 55a0900, fffffa80056a8508}

Unable to load image \SystemRoot\system32\DRIVERS\ssudbus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ssudbus.sys
*** ERROR: Module load completed but symbols could not be loaded for ssudbus.sys
GetPointerFromAddress: unable to read from fffff80002d04100
Probably caused by : ssudbus.sys ( ssudbus+1eb5 )

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

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

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: 00000000055a0900, Memory contents of the pool block
Arg4: fffffa80056a8508, Address of the block of pool being deallocated

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


POOL_ADDRESS:  fffffa80056a8508 

FREED_POOL_TAG:  USBD

BUGCHECK_STR:  0xc2_7_USBD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002bffbe9 to fffff80002ad51c0

STACK_TEXT:  
fffff880`02ff6398 fffff800`02bffbe9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`055a0900 : nt!KeBugCheckEx
fffff880`02ff63a0 fffff880`05cafeb5 : fffff800`02bcc590 00000000`00000000 c00000bb`00000000 00000002`00000001 : nt!ExDeferredFreePool+0x1201
fffff880`02ff6450 fffff800`02bcc58f : 00000000`00000000 c00000bb`00000000 00000002`00000001 ffff0000`00000000 : ssudbus+0x1eb5
fffff880`02ff6458 fffffa80`04790ce0 : fffff880`05cb1189 fffffa80`089b12c0 fffffa80`055a0901 fffffa80`055b1400 : nt!IopDeviceEjectComplete+0x5f
fffff880`02ff6488 fffff880`05cb1189 : fffffa80`089b12c0 fffffa80`055a0901 fffffa80`055b1400 fffff800`02dc8144 : 0xfffffa80`04790ce0
fffff880`02ff6490 fffffa80`089b12c0 : fffffa80`055a0901 fffffa80`055b1400 fffff800`02dc8144 c0000001`00000000 : ssudbus+0x3189
fffff880`02ff6498 fffffa80`055a0901 : fffffa80`055b1400 fffff800`02dc8144 c0000001`00000000 fffffa80`04790ca8 : 0xfffffa80`089b12c0
fffff880`02ff64a0 fffffa80`055b1400 : fffff800`02dc8144 c0000001`00000000 fffffa80`04790ca8 fffffa80`04790cf0 : 0xfffffa80`055a0901
fffff880`02ff64a8 fffff800`02dc8144 : c0000001`00000000 fffffa80`04790ca8 fffffa80`04790cf0 fffff800`00000000 : 0xfffffa80`055b1400
fffff880`02ff64b0 fffffa80`047909e0 : fffffa80`042f3c80 fffff800`02aba042 fffff8a0`00001780 fffffa80`042fc000 : nt!ObpCloseHandle+0x94
fffff880`02ff6500 fffffa80`042f3c80 : fffff800`02aba042 fffff8a0`00001780 fffffa80`042fc000 00000000`00000001 : 0xfffffa80`047909e0
fffff880`02ff6508 fffff800`02aba042 : fffff8a0`00001780 fffffa80`042fc000 00000000`00000001 fffff800`80000000 : 0xfffffa80`042f3c80
fffff880`02ff6510 fffff800`02ab0a20 : 00000000`00004000 fffffa80`05588060 fffffa80`060d2b90 fffff880`05caf46d : nt!EtwpReserveTraceBuffer+0xe2
fffff880`02ff65b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!EtwpEventWriteFull+0x400


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ssudbus+1eb5
fffff880`05cafeb5 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ssudbus+1eb5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ssudbus

IMAGE_NAME:  ssudbus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5011eba4

FAILURE_BUCKET_ID:  X64_0xc2_7_USBD_ssudbus+1eb5

BUCKET_ID:  X64_0xc2_7_USBD_ssudbus+1eb5

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

0: kd> lmvm ssudbus
start             end                 module name
fffff880`05cae000 fffff880`05cc5400   ssudbus  T (no symbols)           
    Loaded symbol image file: ssudbus.sys
    Image path: \SystemRoot\system32\DRIVERS\ssudbus.sys
    Image name: ssudbus.sys
    Timestamp:        Fri Jul 27 07:15:16 2012 (5011EBA4)
    CheckSum:         0002455B
    ImageSize:        00017400
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4