你好，感谢你对问题的解答。
已用工具分析了dump文件，输出如下：
Debug session time: Tue Aug 19 14:06:23.442 2014 (UTC + 8:00)
System Uptime: 6 days 20:14:12.814
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
..................................................
*** WARNING: Unable to verify timestamp for vdtw30.dll
*** ERROR: Module load completed but symbols could not be loaded for vdtw30.dll
*******************************************************************************
*
*
* Bugcheck Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, bfade366, 91031af8, 910317f4}
Probably caused by : vdtw30.dll ( vdtw30+3c366 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis *
*
*
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bfade366, The address that the exception occurred at
Arg3: 91031af8, Exception Record Address
Arg4: 910317f4, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
vdtw30+3c366
bfade366 ?? ???
EXCEPTION_RECORD: 91031af8 -- (.exr 0xffffffff91031af8)
ExceptionAddress: bfade366 (vdtw30+0x0003c366)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0000002c
Attempt to read from address 0000002c
CONTEXT: 910317f4 -- (.cxr 0xffffffff910317f4)
eax=00000000 ebx=00000301 ecx=00000000 edx=00000000 esi=91031cb8 edi=00000000
eip=bfade366 esp=91031bc0 ebp=91031bc0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
vdtw30+0x3c366:
bfade366 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 0000002c
READ_ADDRESS: 0000002c
FOLLOWUP_IP:
vdtw30+3c366
bfade366 ?? ???
BUGCHECK_STR: 0x7E
EXCEPTION_STR: 0x0
LAST_CONTROL_TRANSFER: from 91031c78 to bfade366
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
91031bbc 91031c78 bfae0057 00000000 91031bec vdtw30+0x3c366
91031bc0 bfae0057 00000000 91031bec 00000556 0x91031c78
91031c78 bfada79c bc051010 00000000 91031cb8 vdtw30+0x3e057
91031cd0 bfad1c17 bc051010 91031d00 00000000 vdtw30+0x3879c
91031d2c bfad3f16 bc072da0 00000000 bfb4a95c vdtw30+0x2fc17
91031d40 bfad70d9 bfb4a95c bc051010 00000000 vdtw30+0x31f16
91031dac 80949c88 00000000 00000000 00000000 vdtw30+0x350d9
91031ddc 8088e0e2 bfad6900 00000000 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: vdtw30+3c366
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vdtw30
IMAGE_NAME: vdtw30.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 46856abf
STACK_COMMAND: .cxr 0xffffffff910317f4 ; kb
FAILURE_BUCKET_ID: 0x7E_vdtw30+3c366
BUCKET_ID: 0x7E_vdtw30+3c366
Followup: MachineOwner
---------
