USB驱动卸载过程中蓝屏，如何根据dump文件定位

小弟的驱动在拔卡的时候中出现蓝屏，dump文件分析结果如下：但不明白问题出在哪里？请大侠帮忙………………

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

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)
A driver unloaded without cancelling timers, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen.
Arguments:
Arg1: a9b92f4e, memory referenced
Arg2: 00000008, value 0 = read operation, 1 = write operation
Arg3: a9b92f4e, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, Mm internal code.

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


WRITE_ADDRESS:  a9b92f4e

FAULTING_IP:
dtm5731_i2+5f4e
a9b92f4e ??              ???

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xCE

PROCESS_NAME:  GSurf.exe

IP_MODULE_UNLOADED:
dtm5731_i2+5f4e
a9b92f4e ??              ???

LAST_CONTROL_TRANSFER:  from 82142a78 to a9b92f4e

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
aa57cafc 82142a78 82026880 00000000 819d2190 <Unloaded_dtm5731_i2.s>+0x5f4e
aa57cbd0 804ef0ef 81860040 81ef2008 81ef2008 0x82142a78
aa57cbf4 f806fac6 821429c0 00ef2008 81ef2008 nt!FsRtlAcquireFileForModWriteEx+0x3df
aa57cc18 f8706435 821429c0 00000000 819ecce0 serenum!Serenum_IncIoCount+0x12
aa57cc34 804ef0ef 821429c0 00000000 806d12d0 bhound5+0x1435
aa57cc58 80575ec1 821429c0 81ef2008 81fe4818 nt!FsRtlAcquireFileForModWriteEx+0x3df
aa57cd00 8056e81e 00000300 00000318 00000000 nt!NtGetWriteWatch+0x1
aa57cd34 8053dbc8 00000300 00000318 00000000 nt!MmDeterminePoolType+0x16e
aa57cd64 7c92eb94 badb0d00 0751ff18 00000000 nt!MiDeleteSystemPagableVm+0xe04
aa57cd68 badb0d00 0751ff18 00000000 00000000 0x7c92eb94
aa57cd6c 0751ff18 00000000 00000000 00000000 0xbadb0d00
aa57cd70 00000000 00000000 00000000 00000000 0x751ff18


STACK_COMMAND:  kb

FOLLOWUP_IP:
dtm5731_i2+5f4e
a9b92f4e ??              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dtm5731_i2+5f4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtm5731_i2

IMAGE_NAME:  dtm5731_i2.s

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0xCE_W_dtm5731_i2+5f4e

BUCKET_ID:  0xCE_W_dtm5731_i2+5f4e

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

顶起来

根据WinBbg的分析，驱动退出时未释放DPC,或者是Timer等。  如果真这样的话，根据pdb文件也不好定位啊， 以为蓝屏的隐患原因在驱动加载的时候已经存在了，只是卸载的时候才蓝屏的。而且这种情况概率很低， 非常疑惑…………

已经照楼上两位说的做过，问题还是不能解决……

直接用windbg 设置symbols FIle path为你的driver 生成目录 source File path目录 Image File
为你的驱动文件 再打开dump 分析 就可以直接定位了

在线等…………

关注中……